Schedules, backup, and leave:
the program machinery to ask about

Why this session — and why it specifies nothing

Schedules, coverage, and leave are where residency’s administrative machinery touches residents’ actual lives — and they are among the most program-specific systems in medicine: block structures, request windows, swap permissions, backup mechanics, and leave policies differ legitimately from program to program. So this page follows the same rule as the state-law worksheet: the questions are the curriculum; the answers come from your chiefs, your coordinator, and your program’s written policies, delivered live, with the actual documents on the screen. Run it in orientation week, and hand every intern the answered version.

The schedule — how it is built, and how it changes

• How is the annual schedule actually constructed? Who builds it, on what block structure, balancing which constraints — coverage, education requirements, continuity-clinic cycles, fairness across classes? Understanding the constraints is what makes the schedule feel like engineering instead of arbitrariness — and makes requests realistic.
• When and how do preferences get in? The request window for vacations and special dates — when it opens, when it closes, and what happens to requests that miss it.
• How do changes and swaps work after publication? Who must approve, how far in advance, what counts as an even trade — and which permissions are the resident’s to arrange versus the chiefs’ to grant. The unauthorized hallway swap that leaves a service uncovered is a professionalism event, not a favor.
• When is the change window? Many programs rebuild or adjust schedules at a set point in the year — know when yours is, because that is when requests actually move.

The backup system — the lottery you hope never wins

• What is our backup system called, and how does it work? Jeopardy, backup call, the lottery — every program maintains a mechanism for covering sudden absence. Know the mechanics: who is on the list, how assignments are drawn, how you are notified, and how fast you must be available when activated.
• What are my obligations while on backup? Availability windows, distance limits, the sobriety expectation — backup is a duty status, not a theoretical one.
• What is the etiquette? Two norms travel everywhere: the resident whose absence activated backup thanks their backup — visibly — and nobody games the system, because the lottery’s fairness is the only thing that makes it tolerable. The backup system is the structural version of this bootcamp’s oldest lesson: the program plans for humans being human, and using the system honestly is professionalism, not weakness.

Calling out sick — the exact protocol, rehearsed

• What is the exact call-out procedure? Who must you contact — chief, program office, service attending — by when, through which channels? Most programs require more than a text to a friend, and the 5 a.m. version of you should not be improvising the answer. Write the actual steps on a card in this session.
• What documentation follows, and when? Notification rules, return-to-work expectations, and when a clinician’s note is required.
• And the norm, stated by the chiefs out loud: working while genuinely ill is not heroism — it endangers patients and teammates, and it is exactly what the backup system exists for. The intern who calls out correctly and early is doing it right; the night-float session’s fatigue rule and the sustainable-intern session’s help-seeking rule are the same rule wearing different symptoms.

Medical leave and parental leave — three documents govern

Real leave — illness, surgery, a new child, a family crisis — sits at the intersection of three separate rule sets, and residents need all three:

• Your program’s policy — how leave is requested, how coverage is arranged, how the schedule absorbs it.
• Your institution’s employment machinery — HR policies, accrued time, short-term disability where it exists, and federal family-leave protections where they apply. This is also where the money session’s disability-insurance teaching stops being theoretical.
• The board’s training requirements — because time away can interact with board eligibility, and certifying boards now publish deliberate allowances for leave during training. Ask the specific question: how much leave can I take before my training time extends, and how does our program handle it? The answer has gotten meaningfully more humane in recent years — and it is a number your program director can give you precisely, for your situation, which is why the question belongs in this room and the answer does not belong on this page.

Two norms close the section. First: ask early. A leave the program can plan for is a scheduling exercise; a leave discovered late is a crisis — and program directors would rather help you plan a parental leave months out than untangle one mid-block. Second: taking the leave you are entitled to is not a career confession. The machinery exists because residents are people; the bootcamp has made this point eleven different ways by now, and it is still true here.

Pocket card

Notes

This page is a facilitation framework and deliberately specifies no policy: scheduling, coverage, sick-call, and leave rules are your program’s and institution’s, and board-eligibility interactions are governed by the certifying board’s current published policies — verify all of it locally, in writing, before relying on any of it. Last reviewed July 2026.