
Key Takeaways
You just inherited "the file."
It's a sprawling Excel spreadsheet — color-coded cells, frozen rows, cryptic formulas, and a tab structure that only made sense to the chief who built it. Your job now is to take this and somehow produce a complete, fair, ACGME-compliant schedule for every resident in your program for the next twelve months.
Welcome to chief year.
This guide walks through the entire block scheduling process from scratch: the Accreditation Council for Graduate Medical Education (ACGME) constraints you can't ignore, the rotation types and complement rules you need to understand, how X+Y residency scheduling works and when to use it, and how to build a working master template. Then, after all of that, we'll show you why this entire process is increasingly unnecessary.
A block schedule assigns residents to specific clinical rotations — inpatient medicine, the ICU, emergency, elective weeks — in defined multi-week blocks across an academic year. Instead of a resident floating between clinic and inpatient duties unpredictably, they're assigned to one rotation for a set period, then move to the next.
The goal is to satisfy two things simultaneously: the educational requirements defined by the ACGME, and the operational need to keep services adequately staffed. Balancing those two goals is where the complexity begins.
Before you touch a spreadsheet, you need to document every constraint that will govern the schedule. These fall into four categories.
ACGME Requirements
The ACGME sets the non-negotiables: duty hour limits, mandatory rotation minimums by specialty, PGY-level requirements, and supervision standards. These aren't guidelines — they're accreditation requirements. Violations during a site visit can put the program on probation. For Internal Medicine, the ACGME program requirements specify the minimum time residents must spend in each clinical domain. Know these cold before you build anything.
Duty hours, specifically, are the constraint that generates the most anxiety in Graduate Medical Education (GME). Tracking them manually throughout the year is risky and tedious — but more on that shortly.
Rotation Requirements by PGY Level
Not all rotations are open to all residents. PGY-1 residents have specific required experiences. PGY-2 and above have different requirements as they advance. Some rotations have prerequisites. Build a rotation inventory that lists:
That last point matters more than most chiefs realize. As research on Family Medicine residency scheduling highlights, maintaining a uniform number of residents in clinic each day is essential for standardizing patient load and supervisory coverage — some rotations simply can't coexist with clinic duties.
Complement Constraints
Complement refers to the required number of residents assigned to a given service at any point in time. Every rotation has a minimum (to maintain safe coverage) and often a maximum (to avoid over-staffing). Document these for every service. They become the hard walls your schedule cannot violate.
Resident Requests
Vacation requests, elective preferences, and personal scheduling constraints. Collect these early and treat approved requests as hard constraints — not wishful thinking to revisit later.
Once constraints are documented, you need to decide on the structural model for the year.
Traditional Block Scheduling
The standard approach: residents rotate through required services in defined blocks. The challenge is that clinic duties are often scattered across the inpatient year — what one resident described as "random clinic appointments scheduled at the end of the day during ICU or inpatient weeks." This creates continuity problems for patients and cognitive whiplash for residents.
The other risk is clustering: without deliberate sequencing, a resident can end up with 2–3 demanding inpatient blocks in a row, with no structured recovery. As discussed on r/Residency, "you can really get screwed over by having 2-3 difficult blocks in a row."
X+Y Residency Scheduling
X+Y scheduling — also called alternating block scheduling — was developed specifically to address these pain points. It alternates between inpatient blocks (X weeks) and ambulatory or clinic blocks (Y weeks) in a predictable, repeating pattern.
Common configurations include 4+1, 3+1, and 6+2. In a 4+1 model, a resident spends 4 weeks on an inpatient rotation, then 1 week in continuity clinic, then cycles back. In a 6+2 model, 6 weeks inpatient followed by 2 weeks ambulatory.
The JGME research on X+Y models in internal medicine demonstrates that this structure enhances ambulatory education without creating the conflicts that plague traditional models. Residents who've experienced it tend to be direct about the benefit: as noted on r/Residency, "this ensures that no matter how hard your four week inpatient block is, you will always have a break after that."
The predictability matters too. With X+Y, residents can plan their year far in advance — knowing exactly when guaranteed weekends off will fall, when they'll be in clinic, and when they'll be on service.
With your model selected and constraints documented, you're ready to build.
The master template is a grid: residents on the Y-axis, block periods across the X-axis. If you're on a 4+1 system with 13 four-week blocks per year, you'll have 13 columns and one row per resident.
The JGME implementation guide recommends the following construction sequence:
Download a starter block schedule template: A basic Google Sheets template with cohort tracking, block grid layout, and complement counting formulas is available to help you get started. Adapt it to your program's specific rotation inventory and PGY requirements.
This process sounds orderly on paper. In practice, it rarely is.
You've followed every step. You've documented constraints, chosen a model, built the template, and triple-checked the complements. Then a resident contacts you with a schedule conflict. Or vacation requests come in late. Or a rotation gets added mid-year.
One change, and the house of cards starts to wobble.
This is the reality that every chief resident eventually hits, regardless of how carefully they built the initial schedule:
The time cost of all this is significant. Building and maintaining a manual annual schedule — across block, call, clinic, and attending schedules — can consume weeks of work across an academic year. That's time chief residents spend on logistics instead of clinical education, leadership, or anything the chief year was supposed to be about.
The core problem isn't that chiefs aren't capable of building schedules. It's that the tool and the process are fundamentally mismatched to the complexity of the problem.
Residency block scheduling is, at its heart, a constraint satisfaction and optimization problem. The number of possible valid schedules is enormous. The number of truly optimal schedules — ones that satisfy all hard constraints while fairly distributing assignments and respecting preferences — is far smaller. Finding them manually, in a spreadsheet, is like solving a thousand-variable equation by trial and error.
This is the problem that mathematical optimization engines are designed for.
Thrawn is a done-for-you managed scheduling service that uses a proprietary Scheduling Programming Language (SPL) — built by a team of mathematicians, computer scientists, and logistics experts from MIT — to generate complete, optimized schedules from program constraints. Programs don't operate the system themselves. They describe their requirements, and Thrawn delivers finished schedules for review.
The experience in practice is straightforward. As Dr. R. Kapoor, a Clinical Fellow in Neurocritical Care, described it: "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!"
The technical capabilities address every failure mode of the manual process directly:
Block scheduling is genuinely complex. The rules are real, the stakes are real, and the time required to do it manually is real. This guide exists to help any chief who needs to understand the process — and most will.
But understanding the process doesn't mean you have to own it forever. The complexity that makes automated residency block scheduling valuable is the same complexity that makes manual scheduling so costly: dozens of constraints, hundreds of assignment decisions, and thousands of possible configurations that need to resolve into one coherent, fair, compliant schedule.
Programs at multiple top-20 academic health systems have already shifted to optimization-based scheduling. If your program is still building in spreadsheets, a consultation with Thrawn is worth exploring — the onboarding process starts with a conversation about your program's specific constraints, not a software demo.
Block scheduling assigns residents to specific rotations for set periods. X+Y scheduling is a model that alternates inpatient blocks (X weeks) with ambulatory/clinic blocks (Y weeks). This creates a predictable pattern that can improve work-life balance and continuity of care in clinic.
Manual scheduling is a complex constraint problem. A single change creates a "domino effect," requiring multiple other changes to maintain ACGME compliance, fairness, and staffing levels. Spreadsheets cannot easily manage this complexity, leading to errors and burnout for the chief resident scheduler.
True fairness requires mathematically balancing assignments like night float, weekends, and difficult rotations. Automated optimization tools can distribute these duties equitably across all residents, removing the subjectivity and potential for unconscious bias inherent in manual scheduling methods.
The biggest risk is an ACGME compliance violation. Manually tracking complex duty hours and rotation requirements in spreadsheets is error-prone. A single data entry mistake or oversight during a schedule change can put a program's accreditation at risk during a site visit.
Thrawn is a managed service, not just software. Instead of learning a new tool, programs provide their rules and requests to a dedicated specialist. Thrawn's optimization engine then delivers complete, compliant, and fair schedules for your team to review, saving programs from the hundreds of hours typically spent on manual scheduling.
The best way to retain knowledge is to move it out of a single person's head and into a system. Documenting all constraints and using a managed service like Thrawn ensures that institutional rules are preserved year after year, preventing knowledge loss when a new chief resident takes over.