Start with the current ACGME requirements
Resident scheduling is not just a fairness problem. It is also a duty-hour and program policy problem. A scheduling tool can help structure the work, but the program remains responsible for validating schedules against current ACGME requirements and local policies.
The ACGME sources checked on June 10, 2026 describe core rules including the 80-hour weekly limit averaged over four weeks, one day in seven free of clinical work and required education averaged over four weeks, and in-house call no more frequently than every third night averaged over four weeks.
What the schedule maker should track
Chief residents and program coordinators need a schedule that makes constraints visible before publication.
- Clinical and educational work hours
- In-house call and night float
- Time free after extended call
- One day in seven free, averaged over four weeks
- Vacation, preferences and rotation requirements
How SaniShift fits the workflow
SaniShift is not a legal or accreditation compliance engine. It is a scheduling workflow for organizing residents, shifts, availability, constraints, swaps and fairness review.
Use it to model the schedule clearly, then validate the result through the program's official review process. This is especially useful before publication, when changes are easier to make.
Separate schedule design from compliance sign-off
A safer residency scheduling process separates the draft-building step from the compliance sign-off step. The schedule maker can use software to organize rules, availability and swaps, but the program still needs a defined review path before publication.
That review should include the chief resident or scheduler, the program coordinator when applicable, and whoever owns institutional duty-hour policy. The goal is to prevent a generated calendar from being mistaken for an approved compliance decision.
This separation also makes revisions easier. The scheduler can find coverage gaps, rest concerns and fairness issues while the draft is still flexible, then bring a clearer version to the people responsible for program rules. It reduces the chance that compliance review becomes a last-minute rewrite.
Swaps can create duty-hour problems
Resident swaps should not be invisible. A private trade can solve one conflict while creating a duty-hour, rest or fairness issue elsewhere.
SaniShift supports swap requests with schedule maker approval. That gives the chief resident or program lead a chance to review the impact before the schedule changes.
What to review before publishing
Before a resident schedule goes live, review both coverage and burden. Coverage asks whether the right people are assigned to the right services. Burden asks whether nights, weekends, holidays, heavy sequences and post-call patterns are defensible.
A visible review process also helps after publication. When a resident asks why a difficult assignment landed on them, the program can point to the rule set, the constraints considered and the approved swap history instead of reconstructing the decision from messages.
Keep patient data out of the schedule
Resident schedules should not contain patient details. SaniShift stores no patient data (PHI), so it operates outside HIPAA's scope. Use it only for staff scheduling information such as residents, shifts, availability, constraints, open shifts, swaps and exports.
What to document for each schedule cycle
For each cycle, keep a clear record of the rules used to build the draft: rotation requirements, clinic coverage, in-house call, night float, days free, unavailable dates, approved vacations and any local policy constraints. The record does not need patient information, but it should explain the scheduling logic.
That documentation helps when a resident asks why a change was denied or why a sequence was unavoidable. The answer can refer to coverage, education, duty-hour review and fairness instead of a private spreadsheet history that only one person understands.
Use software as a workflow, not as legal advice
No scheduling product should be treated as the final authority on accreditation, wage-hour or institutional policy. Requirements change, specialties differ and local rules matter. SaniShift is useful because it organizes the scheduling workflow before review, not because it replaces the review.
The safest pattern is simple: build the draft in a structured tool, inspect coverage and fairness, review current ACGME and local requirements, then publish only after the program's normal sign-off. That gives residents a clearer schedule and gives program leaders a cleaner audit trail.