Skip to content

Built by the Lab for Rigular

Roster

Workforce scheduling, without the spreadsheet.

Roster schedules the teams of an operation that runs on shifts: who, where, when, under which rule. And when the day doesn't go to plan, the schedule follows. It is one of Rigular's four products, whose software the Lab builds.

Roster

Screens

Roster, as it runs.

  1. Roster · planning
    A depot's roster: three teams, three shifts (morning, afternoon, night), leave and sick days on the same grid.
  2. Roster · statistiques
    Hours per person over the period: worked, absences, training, overtime.

What the Lab did

Rigular goes after what slows an operation down, in energy, real estate, finance and field teams. The Lab is its engineering partner; we built Roster alongside its other tools.

The full story of the Rigular work, the financial flows and the scale, has a case study of its own. Roster is here because it is a product in its own right, one that people open every morning.

What it does

  1. 01

    Rules, not guesses

    Constraints (skills, rest, contracts) are data; the plan respects them or says why it can't.

  2. 02

    Changes on the day

    An absence, a peak, a swap: the schedule updates and everyone concerned knows.

  3. 03

    A record that holds

    Hours worked and planned, exportable for payroll and for the audit.

And yours?

A trade,
a product waiting to exist?

Tell us the trade and what's stuck. You'll get a candid yes or no within a week, and a first idea of how we'd go about it.