What this prompt does
This prompt has Claude or ChatGPT design a healthcare staff scheduling system. You define the [facility_type] and [staff_count], then describe the [staff_roles], the [shift_patterns], the [scheduling_rules], and the [framework]. From that, the model designs a schedule calendar, a staff roster and availability view, shift management, swap and coverage requests, analytics and compliance, a staff-facing mobile experience, and the framework implementation.
It works because healthcare scheduling is a constraint-solving problem, not a simple calendar. By forcing the model to reason about [scheduling_rules] — minimum rest between shifts, maximum weekly hours, nurse-to-patient ratios — it designs conflict detection, coverage indicators, and an auto-schedule generator that respects those constraints. The [staff_roles] and [shift_patterns] variables drive the color-coding and shift templates, so a 12-hour nursing rotation and an 8-hour support shift are handled distinctly.
When to use it
- You're building a workforce scheduling tool for a hospital, clinic, or care facility.
- You need coverage gaps and understaffing surfaced visibly before any shift is generated.
- You want conflict detection for double-booking, rest-period violations, and credential gaps designed in.
- You're modeling shift swaps, call-outs, and overtime broadcasts with approval flows.
- You need compliance tracking for ratios, max hours, and credential expirations.
- You want a staff-facing mobile view with check-in, swap requests, and PTO submission.
Example output
The model returns a module-by-module design document. The calendar view is specified with day, week, and month modes, role color-coding, and coverage indicators (green, yellow, red). Shift management covers reusable templates, an auto-schedule generator, and conflict detection. The analytics module details overtime reports, fairness metrics, and burnout-risk indicators. The closing [framework] section adds drag-and-drop assignment, real-time WebSocket updates, and role-based views. It's a detailed operational spec, not finished scheduling logic.
Pro tips
- Make
[scheduling_rules]concrete and quantified (for example "minimum 11h between shifts, 1:4 ratio on med-surg") so conflict detection has real thresholds. - List
[staff_roles]fully; the color-coding and credential tracking depend on knowing every role. - Match
[shift_patterns]to your facility so the shift templates (7-on/7-off, rotating, fixed) reflect reality. - Use
[facility_type]to set scope — an ER plus ICU plus med-surg hospital needs different coverage rules than a single clinic. - The auto-schedule generator is described as UI and logic intent; the actual solver is yours to build behind it.
- Ask for the mobile staff view separately if you want geofenced check-in and push-notification flows detailed.
