Staff Shift Schedule

Show who is working when for the week, with coverage gaps visible at a glance.

involved Admin & Operations

What it adds

A weekly grid of staff shifts with draft and published states and coverage warnings.

What your agent is told to do

1
Build the minimum coherent version first: a week grid, shifts you can create and move, a draft state, and a publish action. Leave shift swapping, time-off requests, and labour-cost forecasting out until the grid is in daily use.
2
Keep an editable draft separate from what staff currently see, and change nothing for them until the week is published. A schedule that shifts under people as the manager thinks aloud is worse than a printed sheet.
3
Show coverage as a strip along the grid, comparing the people scheduled in each hour against a required level, so a gap is visible without reading every row.
4
Reuse the app's Recurring Schedule Builder for repeating shift patterns rather than adding a second recurrence engine, and reuse the existing notification channels for change notices instead of introducing a new one.
5
Do not store a shift as a day plus two clock times. Store real start and end instants with a zone, or overnight shifts and clock-change weeks will be wrong in ways nobody notices until someone is not there.

Edge cases it handles

Two shifts overlapping for the same person must be flagged at the moment of the edit, with both shifts named. Discovering the clash on the day means one of them goes uncovered.
Hours below the required coverage level must be marked clearly on the grid, and the required level should be settable per day part rather than as a single number for the whole week.
An overnight shift belongs to the day it started on and must be drawn as one continuous block spanning midnight, not as two fragments on separate days.
Published shifts stay exactly as staff last saw them while a draft of the same week is edited, including through a partial or abandoned editing session.
On publish, notify only the people whose own shifts actually changed, and tell them what changed. A broadcast to the whole team on every publish gets muted, including the week it mattered.
A week that crosses a daylight-saving change contains a day of twenty-three or twenty-five hours. The grid must render it and shift durations must be computed from instants.
Deleting or deactivating a staff member must not silently erase their published shifts; surface the resulting coverage gap instead.
The grid must remain usable on a phone for someone checking their own shifts, even if editing stays a desktop task.

Definition of done

A weekly grid shows every staff member's shifts with draft and published states kept separate.
Overlapping shifts for one person are flagged during editing.
Coverage below the required level is visible on the grid without opening each shift.
Overnight shifts render as one continuous block on their starting day.
Publishing notifies only the staff whose own shifts changed, and says what changed.
Shift times are stored as instants with a zone and survive daylight-saving weeks.
Repeating shift patterns use the app's existing recurrence builder.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Content Reporting

Maintenance Mode

Audit Log

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.