Rostering, time and attendance · working file 2 of 2
Proposals: the scored top ten
The criteria were agreed in the scoring workshop before any score was written, so the order could be argued with rather than appealed. Compliance ranks first by standing rule.
The scoring criteria
| Criterion | What it protects | Standing |
|---|---|---|
| Compliance impact | Reduces the risk of non-compliant pay or hours | Ranks first, always |
| Labour-cost accuracy | Hours and cost figures are right | Weighted |
| Team member experience | Team members get visibility and agency | Weighted |
| Manager time | A workaround is removed | Weighted |
| Feasibility | Vendor release, configuration or business change | Weighted |
| Cost and effort | Same order of magnitude, indicative | Weighted |
The scored top ten
| Rank | Item | Principle | Release |
|---|---|---|---|
| 1 | Soft warning on shifts of five to five and a half hours | Few hard stops, visible warnings | Released 1.63, November 2024 |
| 2 | Hard stop on shift supervisor breaks | The one place a hard stop was right | Released 1.63, November 2024 |
| 3 | Manager break auto-wizard, rerun when a shift changes | Remove a workaround | Released 1.64, 2025 |
| 4 | Reporting at multiple levels | One view per person | Released 1.64, 2025 |
| 5 | Shared employee punches and leave in one view | One view per person | Scheduled |
| 6 | Auto-populated leave on the schedule | Remove a workaround | Released 1.64, 2025 |
| 7 | Change a shift to a leave shift | Remove a workaround | Released 1.64, 2025 |
| 8 | Consent workflow for leave | Consent is not an admin step | Released 1.64, 2025 |
| 9 | Time off shift history | Team members can see their own record | Released 1.63, November 2024 |
| 10 | Leave shifts on the mobile shift list | Team members can see their own record | Scheduled |
Every item cites its insight and its evidence count in the source register; no item enters the list without one. Eight of the ten carried a named release across November 2024 and 2025, and ten further releases followed in early 2026.
Reconciliation with the vendor calendar
| Vendor release item | Status after reconciliation | Business position |
|---|---|---|
| Cross-schedule compliance | On the release calendar | Joint item, aligned with the shared-employee view |
| Labour dashboard | On the release calendar | Keep; replace the paid per-restaurant add-on with an in-house report |
| Pay-period reopening review | On the release calendar | Fast-track; the phantom-shift workaround depends on it |
| Hard stop on supervisor breaks | Negotiated | Guided enforcement with visible warnings instead, except where a hard stop was right |
| Five-hour shift warning | On the release calendar | Adopted as item one; the risk sits across 100,000+ rostered shifts at the boundary |
| Time-off shift history | On the release calendar | Adopted as item nine |
| Single sign-on | Shipped | The largest live fix; the registration cluster collapsed |
| Platform standardisation | Ongoing | A standard feature list per restaurant, with the variant tail by design |
| Reporting at multiple levels | 2025 draft | Adopted as item four |
| Leave management tickets | 2025 draft | Split into items six to ten |
Rollout
Pilots were live by close: single sign-on, open-shift hours and manager clock-in. Release communication was templated and routed through the platform user group and the franchise channels, so the rationale for the top ten travelled with the roadmap rather than behind it. The blueprint lives on as a living document with a half-yearly review, which is the cadence that keeps the model out of the bin.
Working file from employment at KFC South Pacific, anonymised: no restaurant, colleague or vendor is named, and the figures are the ones the case study states. Back to the case.