All case studies
Case Study · 2025 · Internal R&D · 12 engineering days

Shiftboard

Constraint-driven rota scheduling for distributed hourly workforces.

Reference implementation for our constraint-driven scheduling standard.

shiftboard.app / rosters / week 32ShiftboardRosterCoverageRequestsTimesheetsSitesReportsCoverage — week 324 sites · 68 staff · 3 open requestsFill rate by dayMon92%Tue88%Wed100%Thu74%Fri96%Sat61%Sun80%Shift assignmentsSHIFTSITEASSIGNEDSTATUSThu 06:00–14:00Depot North6 / 8UnderstaffedThu 14:00–22:00Depot North8 / 8ConfirmedFri 06:00–14:00Line B7 / 7ConfirmedSat 08:00–16:00Line B4 / 7Open
The problem

Multi-site operations of five to thirty staff commonly run rotas through group chat and printed sheets. Availability changes are lost, double-bookings surface on the day, and there is no reliable record of hours actually worked — an operational and compliance exposure.

What we built
  • A week-grid scheduler with drag-to-assign shifts, per-person availability, and live conflict detection for overlaps, unavailability, and over-hours.
  • An offline-tolerant mobile view so staff can review and claim open shifts on degraded connectivity, syncing on recovery.
  • A published-versus-draft rota model so managers can restructure a week without notifying staff until it is formally published.
The result

Building a two-week rota for a simulated 22-person operation moved from roughly 40 minutes of manual spreadsheet work to about 6 minutes, with conflicts caught at assignment rather than on shift. Every constraint rule is covered by unit tests.

Want this level of documentation on your project?

Every engagement ships with the same written record: what changed, why, and what it measured.

Start a conversation