Coverage gaps are named, not hidden
Open shifts, over-hours, and conflicts appear before publish with the rule that flagged them. A person stays in control of the final call.
For teams accountable for coverage
Coverage you can see.
Decisions you can defend.
Shiftd surfaces open seats, conflicting assignments, and over-hours before you publish. Staff get the schedule on their phone the moment it goes out. Every change leaves a record.
Built for hospital units and every team where a gap in coverage is a real problem, not a spreadsheet footnote.
For schedulers
One workspace runs the schedule. From first draft to operational record.
Every schedule lives in a single workspace: lifecycle, assignments, coverage, compliance, approvals, and history. This is what a scheduling week looks like inside it.
-
Overview
Know where the schedule stands, always.
The lifecycle panel states the current phase, what staff can see, and the next action. Publishing runs through a wizard that shows coverage gaps, conflicts, and unfilled seats before a single person is notified.
LifecyclePhase 03/08 · Admin adjustment- Staff visibility
- Hidden until publish
- Open seats
- 2 of 279
- Conflicts
- 0
- Signup window
- Closed Apr 2
Publish & notify The wizard reviews gaps, conflicts, and unfilled seats first -
Assignments · Conflicts
Conflicts point at their own fix.
Double-bookings and rule violations are named with the assignment that caused them. Resolve jumps straight to the highlighted cell in the grid, so the fix is one click from the finding.
Mon Tue Wed Thu Fri J. Alvarez D D · N · M. Cruz · N N · D K. Osei D · D D · R. Patel N N · · N -
Compliance
Tier obligations, scored while you build.
Each clinical staff member's shift obligations are checked against the schedule: under, over, or in range. When someone is short, assign them a shift straight from the row.
StaffRuleActualStatusK. Osei Nights · min 4 2 of 4 Under Assign shift →R. Patel Weekends · min 2 2 of 2 In rangeS. Boone All shifts · max 16 17 of 16 OverM. Cruz Nights · min 4 5 of 4 In range -
Approvals
Every request, one inbox.
Trades, giveaways, and time off arrive in a department-wide inbox. Decide with the schedule open next to you; the decision is pushed to the staff member's phone.
Department-wide · 2 awaiting decisionTrade R. Kim ↔ M. Cruz · Apr 22 · Night Approve DenyTime off D. Okafor · May 2–4 Approve DenyGiveaway T. Reyes → open seat · Apr 30 Approved · staff notified -
History
Every change has a before and after.
A schedule-scoped audit trail records phase moves, assignment changes, and publish events, each attributed to the person who made the call. Defensible by design.
Apr 16 19:42 S. Park approved trade · R. Kim ↔ M. Cruz requestApr 15 18:05 A. Whitfield moved phase · Self-signup → Admin adjustment lifecycleApr 14 09:12 A. Whitfield reassigned Thu 4/16 night · open seat → J. Alvarez assignmentApr 12 07:58 System closed signup window · 214 bids received windowMar 30 14:31 A. Whitfield released schedule for self-signup · 42 staff notified notify
The eight-phase lifecycle
Build, review, adjust, publish. Every handoff leaves a record.
Draft. Admins lay out the bones: dates, shift types, and how many of each role every day needs. Staff see nothing yet.
Self-signup. A signup window opens and staff bid for the shifts they want from their phones. Caps and role rules screen every bid.
Admin adjust. Schedulers fill what signup left open, resolve conflicts, and rebalance hours with the coverage grid in view.
Supplemental. Still short? An extra-shift signup opens for the unfilled seats, with a hole report tracking what closes.
On-call. Call coverage layers on as its own child schedule, so escalation never muddies the base assignments.
Locked. Edits stop. The schedule holds still for a final read before the rules run.
Balanced. Every rule runs once more: hour caps, role match, tier obligations. Anything that fails is named.
Published. Staff are notified and the schedule becomes the operational record. From here, changes flow through requests.
Publish makes the schedule visible to staff. After that, changes flow through requests and custom shifts, so the operational trail stays intact.
For staff
Staff get answers, not screenshots.
The moment a schedule publishes, it is in every pocket. The iPhone app is built for the 11pm check: next shift, requests, done.
-
Next shift first
The dashboard leads with the next assignment: date, time, shift. One glance answers it.
-
Signup windows
When self-signup opens, staff get a push and bid for the shifts they want. Caps and role rules apply to everyone the same way.
-
Requests by phone
Trades, giveaways, and time off are submitted in seconds. The decision comes back as a push notification, with a record behind it.
-
Calendar, synced
Every assignment flows into a personal calendar feed for Apple or Google Calendar. The schedule lives where their life already does.
Trade approved
Apr 22 is covered by M. Cruz
Good evening, Dana
Next shift
Thu, Apr 16
19:00–07:30
Extra shift signup open · closes in 2d 4h
→
Why teams trust it
No automation magic. The schedule shows its work.
Rules apply the same way every time
Every assignment runs through the same backend engine: caps, role match, lifecycle phase, permissions. The UI cannot bypass a constraint, even by mistake.
Every change has a before and after
Drafts, signups, admin adjustments, call coverage, and publish decisions stay traceable. Nothing important changes without a record.
Run the next schedule in Shiftd.
Workspaces are invite-only. Ask us for a pilot, or sign in to the workspace your department already runs.