Stop rebuilding the schedule process every year

Every June, a new chief steps into block scheduling and often finds the same blank slate the last chief faced. The hospital did not forget how to run a residency. The program did not lose its rotations overnight. What disappeared is the working memory of how last year’s schedule was actually built—the exceptions, the soft deals, the “we always do it this way” rules that never made it into a durable process.

That annual rebuild is expensive. It burns chief time, stretches coordinators, and forces leadership to rediscover constraints that the program already paid to learn. The educational goal is not a prettier spreadsheet. It is institutional continuity: a scheduling process that survives turnover because the knowledge lives in the system, not only in someone’s head.

Where the process actually lives today

In many GME programs, scheduling knowledge is scattered. Some of it sits with the outgoing chief. Some of it lives in last year’s workbook, with tabs nobody wants to open. The rest is buried in Slack threads, email chains, and hallway agreements about which services cannot run thin, which pairings never work, and which vacation windows are sacred.

When that knowledge is informal, turnover resets the clock. The new chief inherits a blank grid and a set of stories rather than a defined process. They rebuild coverage logic from scratch, re-learn hospital quirks the hard way, and recreate fairness norms that were already negotiated once. The schedule eventually works—but the program pays a full restart cost every academic year.

Aim for a repeatable process, not a one-off calendar

A finished block schedule is an output. The durable asset is the process that produced it: the requirements that make this residency unique, written clearly enough that next year’s chief can apply them without archaeology. Coverage floors, rotation capacities, night and weekend norms, clinic continuity expectations, and request priorities should be documented as rules—not remembered as folklore.

Encoding those requirements does not remove judgment. Leadership still decides what is hard, what is soft, and what can flex when the hospital changes. It does change the handoff. Instead of “here is last year’s grid; good luck,” the next chief inherits a system: a known set of constraints, a known sequence of steps, and a clear place to record exceptions. Continuity becomes the default rather than a heroic knowledge transfer.

Iterate on rules instead of reinventing the year

Hospitals evolve. A service adds capacity. A site changes night coverage. ACGME expectations or local wellness policies shift. Those changes should update the process—not force a full reinvention of how scheduling works. When requirements are explicit, the year’s work becomes revision: adjust the rule that changed, regenerate or rebuild from that baseline, and review the result. The rest of the institutional knowledge stays intact.

That iteration loop is how programs stop treating each June as year zero. The first year of encoding takes effort. The payoff shows up when chiefs turn over and the schedule does not have to be rediscovered from Slack history and half-remembered spreadsheets. Platforms built for residency block scheduling, including OSO Schedule, are useful in that framing because they keep program rules in one place and make next year’s starting point the process—not an empty grid.

What continuity protects

Process continuity protects more than chief weekends. It protects fairness norms that residents already understand, coverage standards the hospital relies on, and the scarce administrative attention that should go to curriculum and coaching rather than reconstructing the same constraint map every summer. New chiefs still own the schedule. They should not have to rebuild the method for making one.

If your program starts from scratch each year, treat that as a knowledge problem, not a personnel problem. Capture the requirements that make the residency unique, hand the next chief a living process, and update rules when the hospital changes— so the schedule can improve year over year instead of being reinvented every June.