ACGME Duty Hour Rules for Scheduling: The Complete Compliance Guide (2026)

Key Takeaways

• Accreditation Council for Graduate Medical Education (ACGME) duty hour violations are frequently underreported, with insufficient rest between shifts being the most common infraction.

• Common compliance mistakes include miscalculating the 80-hour weekly average, extending the 24-hour duty limit during handoffs, and creating conflicts between call and mandatory conference schedules.

• Proactive compliance requires building call and educational schedules together, tracking hours in real time, and shifting from violation detection to prevention.

• Thrawn prevents violations by design, delivering mathematically optimized schedules that treat all ACGME rules as non-negotiable constraints from the start.

Your site visit is three months out. The ACGME documentation is scattered across PDFs. Your schedules live in a spreadsheet that's been passed down for three chief classes, and you're not entirely sure it's compliant.

This is the guide that clears that up. Every major duty hour rule, how it hits your schedule, the specific scenarios that trip programs up, and how to prevent violations before they happen — all in one place.

Why ACGME Duty Hour Compliance Is More Than a Box to Check

Resident work hour restrictions didn't appear out of nowhere. The ACGME introduced them in 2003 in response to growing evidence linking sleep deprivation in residents to medical errors and patient harm. The rules have evolved since, but the underlying logic hasn't: exhausted physicians make mistakes, and the training environment shouldn't systematically exhaust the people learning in it.

The stakes for non-compliance go well beyond paperwork. A citation during an accreditation review can trigger increased oversight, a focused site visit, or probationary status. Beyond accreditation risk, violations erode resident trust in program leadership — and as one residency thread on r/emergencymedicine captured it, "we've lately had problems with schedules containing duty hour violations and inequality between individual residents."

There's also a reporting gap worth understanding. A UVA study on duty hour compliance found that when researchers introduced a non-punitive reporting system, recorded violations jumped from 10 to 179. Residents often stay late for valuable educational experiences or seamless handoffs — and many fear punitive consequences for reporting. That gap between what's logged and what's happening is a silent compliance risk for your program.

The Core ACGME Duty Hour Rules: A Field Guide for Schedulers

These are the rules that govern ACGME duty hour compliance scheduling. Each one carries specific implications for how you structure rotations, call shifts, and rest periods.

The 80-Hour Weekly Limit

The rule: Residents cannot work more than 80 hours per week, averaged over a four-week period. This includes:

• All clinical and educational activities

• At-home call with patient care duties

• Patient-related administrative work

Scheduling impact: This is the foundational constraint your entire schedule is built around. The four-week averaging window gives you some flexibility — a resident can run high one week if another week is lighter. But that averaging can also mask a pattern of consistently high-hour weeks if you're not monitoring across the full period.

Common violation scenario: A resident rotates through the ICU for three consecutive high-acuity weeks, logging 85+ hours each week. The scheduler plans a light elective in week four to bring the average down. Then the elective service picks up unexpectedly. The four-week average ends up over 80 — and no one catches it until the monthly report.

The 24-Hour Continuous Duty Limit

The rule: Residents cannot be assigned more than 24 consecutive hours of clinical and educational work. Programs may allow up to four additional hours for the following patient safety activities, but no new clinical responsibilities can be assigned after the 24-hour mark:

• Care transitions

• Handoffs

• Brief educational activities

Scheduling impact: This shapes the structure of every call shift. Traditional 24-hour call is permissible, but the handoff window is not a free pass for additional work. The moment a new patient is assigned to a post-24-hour resident, you have a violation.

Common violation scenario: A PGY-2 finishes a 24-hour call at 7 AM. During sign-out, a complex new admission arrives. The resident stays until noon to manage the workup and complete documentation, taking on new clinical responsibilities well past the 24-hour limit.

Required Days Off: One in Seven

The rule: Residents must have at least one day — defined as one continuous 24-hour period — free from all clinical and educational duties every week, averaged over four weeks.

Scheduling impact: This rule is more nuanced than it looks. "Post-call Sunday" does not automatically count as a free day if the resident is expected back Monday morning. The 24-hour window has to be genuinely free — no mandatory conferences, no beeper coverage, no clinical duties.

Common violation scenario: A resident works Monday through Friday, takes a 24-hour Saturday call (7 AM to 7 AM Sunday), and returns to their rotation Monday at 7 AM. On paper it looks fine. In practice, they have not had a continuous 24-hour free period — Sunday was post-call recovery, not a guaranteed duty-free day.

Required Rest Between Shifts

The rule: Residents must have a minimum of 8 hours off between scheduled clinical and educational periods, with a 10-hour minimum strongly recommended.

Scheduling impact: This is where "shift swings" create the most violations. An evening shift ending at 11 PM cannot be followed by a 7 AM start. Even mandatory morning conferences count — a required grand rounds at 7 AM is a duty period.

Common violation scenario: The UVA study found that short break violations were by far the most frequent type, accounting for 134 of 179 recorded violations. A resident leaves the hospital at 8 PM after a long clinical day and is scheduled for a mandatory educational conference at 6:45 AM. Less than 11 hours of rest — a violation that's easy to generate accidentally when call and conference schedules aren't built together.

Beyond the Core Four: Other Rules That Catch Programs Off Guard

The 80-hour limit and 24-hour shift cap get the most attention, but these rules trip up programs just as often:

• In-house call frequency. Residents cannot be scheduled for in-house call more often than every third night, averaged over four weeks. A stretch of busy service coverage can push past this without careful tracking.

• PGY-1 specific limits. First-year residents operate under stricter rules — their shifts cannot exceed 16 consecutive hours. This is a critical distinction that generic spreadsheet formulas frequently miss when applying blanket duty hour logic across all PGY levels.

• At-home call counting. Pager call time counts. If a resident is called back to the hospital from home call, those hours — and the associated rest requirements — apply to the 80-hour weekly total.

Why Good Schedules Go Bad

Understanding the rules is one thing. Understanding why compliant schedules fail in practice is what separates programs that sail through site visits from programs that don't.

• Unplanned absences. One sick call forces an emergency patch job. The chief scrambles to find coverage — often by extending a resident who's already near their hour limit, or by collapsing someone's rest period. As one chief described the experience, building a schedule in spreadsheets means that a single change means "rebuilding a house of cards."

• The educational value trap. Residents stay late for a rare surgery or follow a complex patient case through the night. The motivation is the right one, but the program is still accountable. As the UVA research demonstrates, these voluntary violations are the hardest to track and the most underreported.

• Manual tracking breaks down. Spreadsheets require error-free formulas and consistent data entry. As one chief resident noted, "I ended up manually writing schedules because it was less tedious than back checking an auto generated schedule" — a telling sign that even automated generators can introduce errors requiring full manual review.

• Conference schedules aren't built with call schedules. Mandatory educational events that cross rest period boundaries are a leading source of violations — and they happen precisely because call schedules and educational calendars are built in separate documents with no coordination.

How to Build a Compliant Schedule: A Proactive Framework

Research on resident duty hour reform consistently identifies the same structural approach for programs that get it right. The pattern looks something like this:

1. Involve your residents early. Ask them where the current schedule breaks down. They know where the real violations happen, even if they're not reporting them. This also builds buy-in before the schedule goes live.

2. Define what counts as duty time. Mandatory conferences, at-home call with patient contact, and administrative work tied to patient care all count. Make sure your chiefs and coordinators are using the same definitions.

3. Build call and educational schedules simultaneously. Separate documents guarantee cross-schedule conflicts. If your conference calendar and call schedule aren't coordinated, short-break violations are inevitable.

4. Track in real time, not monthly. A 2025 study published in ScienceDirect found that an automated text-message-based duty hour reporting system dramatically improved both reporting accuracy and resident confidence in the compliance data. Waiting until month-end to audit hours means violations are already locked in.

5. Build in a review step before publishing. As one experienced scheduler recommended, "make sure you have a staff member who is experienced at scheduling review it before it is published to make sure there are no rule violations or inequitable schedules."

6. Audit frequently and adjust. Schedules are living documents. Rotation demand shifts, service volumes fluctuate, and residents' situations change. A quarterly check-in isn't enough for programs with high call volume.

From Violation Detection to Violation Prevention

Most programs operate in violation-detection mode. The schedule is built, published, and then audited — and violations are found after the fact. At that point, the options are limited: document the violation, investigate the cause, and hope it doesn't come up in the site visit.

The more defensible model is violation prevention — building schedules where compliance is a constraint at generation, not a check at the end.

This is conceptually straightforward but operationally difficult to pull off manually. ACGME duty hour compliance scheduling requires tracking at least five interlocking rules simultaneously, across every resident, across every rotation, with real-time visibility into how a single change affects the whole picture. Spreadsheets weren't designed for this.

Commercial scheduling tools help in some cases, but as the user research above shows, many programs find that the tools require hours of manual setup, generate errors that still need human review, and come with interfaces that are "atrocious" to work with. The setup is tedious. The output isn't trusted. And the program ends up manually verifying anyway.

This is the problem that Thrawn was built to solve differently.

Stop Building Schedules. Start Reviewing Them.

Thrawn is a done-for-you managed scheduling service for residency and fellowship programs — not scheduling software you operate yourself. Programs send their constraints: rotation requirements, vacation requests, call coverage needs, and ACGME duty hour rules. Thrawn's proprietary Scheduling Programming Language (SPL) — a mathematical optimization engine built by a team of MIT mathematicians and computer scientists — generates a finished, compliant schedule for review.

ACGME compliance isn't audited after the fact. It's built in as a non-negotiable constraint at generation time. The schedule you receive is mathematically structured to satisfy every duty hour rule — the 80-hour weekly limit, the 24-hour continuous duty cap, PGY-1 specific limits, rest period requirements, and call frequency rules — before it ever reaches your inbox.

Two capabilities are worth highlighting for compliance specifically:

• Automated ACGME duty hour compliance. Violations are prevented at the generation stage. The chief's job shifts from manually checking hours in a separate spreadsheet to reviewing a finished schedule that's already compliant.

• Cross-schedule simultaneous optimization. Block, call, clinic, and attending schedules are treated as one interconnected system. The short-break violations that emerge when conference and call schedules are built in separate documents don't exist when they're optimized together.

There's also a fairness dimension worth mentioning here. The perceived fairness and actual data disconnect — where residents "felt like it was unfair but the reports said otherwise" — doesn't disappear with better spreadsheets. Thrawn's Fairness & Equity Engine mathematically balances nights, weekends, and holidays across residents, providing objective, provable equity rather than a chief's best-effort manual distribution.

According to Thrawn, the service currently operates across 19 departments at 14 hospitals spanning multiple top-20 academic health systems. As Dr. R. Kapoor, a Clinical Fellow in a Neurocritical Care Fellowship, described the experience: "We provided the team with the vacation requests of our clinical fellows and scheduling requirements for various rotations, and Thrawn quickly followed up with a couple of clarifying questions. Within such a short time, our yearly block fellowship schedule was complete!"

If your program is heading into a site visit and ACGME duty hour compliance scheduling is still being tracked manually, a consultation with Thrawn is worth the conversation. Programs send their constraints and receive finished schedules — a personalized consultation can show whether the model fits your program's specific setup.

Frequently Asked Questions

What is the most common ACGME duty hour violation?

Insufficient rest between shifts is the most frequent violation. This often happens when mandatory morning conferences are scheduled too close to the end of an evening shift. Building call and educational schedules together is critical to prevent this common error.

How should we count hours for at-home call?

Time spent at home on call only counts toward the 80-hour limit when a resident is called back to the hospital. All time spent in the hospital after being called in, plus any associated travel time, must be logged as duty hours and is subject to rest requirements.

Do mandatory educational conferences count as duty hours?

Yes, all mandatory educational activities count as duty hours. This includes grand rounds, didactics, and simulation sessions. Scheduling these events without coordinating with the clinical call schedule is a primary cause of insufficient rest period violations.

Are the duty hour rules different for interns (PGY-1s)?

Yes, PGY-1 residents have stricter limits. Their shifts cannot exceed 16 consecutive hours, unlike the 24-hour cap for upper-level residents. Using a single set of rules for all residents is a common scheduling mistake that leads to PGY-1 violations.

How does the "one day off in seven" rule work with post-call days?

A day off must be one continuous 24-hour period free from all clinical and educational duties. A post-call day only counts if the resident is not required to return for any duties before that 24-hour window is complete. Averaging is permitted over four weeks.

How can we handle sick calls without causing a domino effect of violations?

Rapid re-optimization is key. Manually patching schedules under pressure often leads to errors. Thrawn's service uses mathematical optimization to quickly find a new, fully compliant schedule, preventing the cascading violations that often result from last-minute changes.