Drafting fair schedules and the admin work around them
Charge nurses and managers lose hours to schedule-building, swap requests, and the follow-up messages nobody enjoys writing. In focus groups, nurses said an AI scheduler could act as "a neutral entity" that reduces the emotional burden on whoever builds the schedule and distributes weekends more fairly — but every group insisted a human keeps final authority, because "a computer can't feel how someone's really doing."
You are a scheduling assistant for a charge nurse. Draft a schedule proposal for {{schedule_period}} and flag fairness problems. The final call is always mine. Staffing rules: {{staffing_rules}} Requests and constraints — staff are listed by code only, never by name: {{shift_requests}} Output: 1. A schedule table: staff code by day, shift type in each cell (D/N/O) 2. "Rule violations I could not avoid" — every cell that breaks a rule, and which rule it breaks 3. "Fairness check" — weekend, night, and holiday counts per person compared to the unit average 4. "Requests I could not honor," each with the specific reason 5. A short, neutral message template I can adapt for staff whose requests were not honored Rules: - Never invent availability, requests, or qualifications that are not in my list. If information is missing for someone, leave their row blank and flag it. - Apply my rules exactly as written. Where two rules conflict, show me the conflict — do not silently pick a winner. - No judgments or speculation about why anyone requested time off.
Fill in your details and the prompt updates live — then copy.
Schedule proposal, Feb 2-15 (D = day, N = night, O = off): RN-A: D D O O N N O | O D D O O N N RN-B: O N N O N N O | N N O O N O N Rule violations I could not avoid: none. Fairness check: RN-C carries 3 of 4 weekend shifts this period against a unit average of 2 — consider swapping Feb 8 with RN-A. Requests I could not honor: RN-D's Feb 6 — granting it drops day shift below the 4-RN minimum with RN-A already on approved PTO. Message template: "I wasn't able to grant Feb 6 this cycle because of minimum staffing. You're first in line for the next open request."
The full workflow
- Replace every staff name with a code before pasting anything
- List your hard rules (ratios, qualifications, contract terms) explicitly — the AI only knows what you type
- Review every flagged conflict and fairness note yourself before publishing
- Make the final schedule decision personally and communicate it through normal channels
Watch out for
Staff privacy is regulated too: approved accommodations, FMLA, and medical restrictions are confidential employment information. Use codes, never names, and never state the reason behind an accommodation in the prompt.
Union contracts and state staffing laws are hard constraints the AI does not know — verify the draft against your CBA and required ratios before publishing.
Keep the human decision visible: nurses in studies accepted AI-drafted schedules only when a person they could appeal to retained final authority.
Where this comes from
Every use case on this site is grounded in real reports from working nurses — not invented by us.