KarmaSchedule Sign in

ACGME duty hours and the schedule

Published by KarmaSchedule · Last reviewed

Duty-hour requirements are the clearest example of a constraint that is cheap to satisfy when a schedule is built and expensive to discover afterwards.

The requirement areas that shape a schedule

Total hours, averaged. A cap on duty hours per week, averaged over a defined number of weeks, counting all in-house clinical and educational activity. The averaging is what makes this a scheduling constraint rather than a daily one — a heavy week is permissible if the window balances.

Maximum continuous duty. A cap on how long a single duty period may run, with separate provision for the time allowed afterwards for transitions of care. This is what makes a 24-hour call period a different object from a run of day shifts.

Minimum time free between duty periods. The turnaround. In practice this is the limit most often threatened by a swap, because the swap looks at the shift being moved and not at the gap on either side of it.

Required time free from duty. A minimum number of days free, averaged over four weeks, and provision for time free after night duty.

In-house call frequency. A limit on how often in-house call may occur.

Supervision. Requirements about who must be present or available for a trainee at a given level — not a duty-hour rule, but a scheduling constraint that interacts with all of them.

Why hard rules beat reports

A duty-hour report is a list of things that already happened. By the time it shows a violation, a trainee has worked the hours, the programme has the exposure, and the only available action is explanation.

A hard rule is a constraint on what can be created. A generated schedule satisfies it by construction. A proposed swap that would break it is refused at the moment it is proposed, with the rule named, to the person proposing it.

The practical difference is where the effort goes. With reports, the effort is continuous vigilance by a programme coordinator. With rules, the effort is a one-time configuration that is then enforced on every change by everyone.

Limits that differ by training year

A PGY-1 and a senior resident are not under identical constraints and are regularly on the same rota. Configure training year as a staff category and set rules per category, so one schedule carries both sets of limits.

Maintaining two schedules to handle this is the common workaround and it is how a trainee ends up double-booked.

What remains the programme's job

Three things, and they are not small:

Keeping the configuration current. When requirements are revised, the rules have to be revised. Nothing automates that.

The gap between scheduled and worked. A schedule is a plan. Hours actually worked can exceed it, and duty-hour compliance is about what was worked. Scheduling software constrains the plan; attestation and whatever your programme uses for actual hours cover the rest.

Activity outside the schedule. Educational activity, moonlighting where permitted, and clinical work not represented as an assignment all count towards limits and are not visible to a scheduling tool unless they are entered.

A tool that claimed to deliver compliance would be claiming to do all three. It cannot.

Common questions

Can software guarantee duty-hour compliance?

No, and any claim otherwise should be treated with suspicion. Software can build a schedule that satisfies the limits you configure and can report the resulting counts. Whether your configuration matches your accrediting body's current requirements, and whether what was scheduled is what was worked, remain the programme's responsibility.

Why build against the limits rather than audit the schedule afterwards?

An audit finds violations that have already happened — a trainee has already worked the hours. A schedule generated against hard limits cannot contain a violation of them, and a swap that would create one is refused at the point it is proposed.