Most physician groups still build call by hand, in a spreadsheet, a month at a time. The work is the same in every specialty: list what has to be covered, collect what people need, decide what fair means, fill the hardest slots first, and check the result before anyone sees it.
This guide walks through those steps in the order experienced schedulers use them. It applies whether you keep a spreadsheet or use software, and the examples come from emergency medicine, hospitalist, anesthesia, OB/GYN and radiology groups.
Start with everything that has to be covered, not with the people. A line is anything that needs a name on it: home or in-house call, a 7p to 7a night, a day shift, a clinic session, an OR room, a rounding or ICU week, a swing shift. For each one, write down when it runs, how many people it needs, and who can work it.
When it runs matters more than it looks. A 24-hour call that runs 7a to 7a ends when the next day's OR starts. A Monday to Sunday week of nights ends on Monday morning. Writing the real hours down is what lets you see, later, which combinations leave someone working 30 hours straight.
Who can work it matters just as much. Some lines are physician-only, some take APPs, some need a subspecialty pool such as IR, cardiac anesthesia or stroke. Note also which lines one person may hold on the same day, such as a clinic session inside a service week, and which they may not.
A hard rule is one the schedule must never break: every line covered, approved vacation honored, the day after 24-hour call kept free, work-hour limits for anyone in training, credentialing for who can take which line. A preference is something you want most of the time: spacing between calls, no back-to-back weekends, someone's standing wish to be off on Tuesdays.
Be strict about which list each rule goes on. A rule you can't keep every month belongs with the preferences, or the first tight month forces you to break it quietly. Write both lists down where the whole group can see them. Most arguments about the schedule are really arguments about rules nobody wrote down.
Open requests for the month well before it starts, with a due date, and collect them in one place rather than in texts and hallway conversations. Ask for vacation and conference days, the days people would rather be off, the days they would like to work, and how much work they want, such as no more than four calls or at most two weekends.
Approve time off before you build, so the schedule never has to be rebuilt around a vacation you learned about late. Then remind only the people who haven't entered anything. Everyone who did gets a schedule built around what they asked for, which is most of what people mean when they call a schedule fair.
Counting calls is not enough, because a Saturday is not a Tuesday. Most groups give each kind of day a weight: a weekday call counts 1, a weekend call 1.5 to 2, a holiday 2 to 3, and a night more than a day. Each person's fair share is then the total, divided by the group and scaled by FTE, so a half-time partner carries about half the load.
Keep the tally across the whole year, not month by month. Any single month is lumpy; someone has to take the extra weekend. What matters is that it evens out by the end of the year. Track holidays by name, so whoever worked Thanksgiving last year is not first in line for it this year.
Keep separate tallies for separate lines. Backup call is not first call, and APPs should be compared with APPs. Mixing them makes someone carrying heavy backup look like someone carrying heavy call.
By hand, the order matters. Lock anything already promised, such as a holiday trade or someone's fixed 7 on, 7 off pattern. Then fill holidays, then weekends, then nights and 24-hour call, then weekday call, and last the day shifts and clinic sessions that have the most people to choose from.
As you place each call, cross off the day after it for that person if your rule keeps post-call days free, and check the spacing rules before moving on. Most mistakes in a hand-built schedule are made at this step, late in the evening, around the twentieth day of the month.
Before anyone sees the draft, check that every line is covered on every day, that nobody is booked twice on one date, that nobody works the morning after a 24-hour call or a week of nights, and that the spacing rules held. Then check the requests: which were met, and which could not be, so you can tell those people before they find out.
Last, compare each person's weighted total with their fair share for the year so far. A second pair of eyes on the draft catches what the builder no longer sees.
Publish one version that everyone works from, ideally on their phones and in their own calendars, so nobody is reading an old printout. Handle trades the same way every time: the two people agree, the scheduler approves, and the trade is checked against the same rules as the schedule. Keep the history, because next month's fairness depends on it.
A spreadsheet works for a small group with one or two lines. The signs it has stopped working are familiar: more than eight or ten people, three or more lines that interact, requests arriving by text, arguments about who works more, and someone spending several evenings a month on it.
Scheduling software builds the month from the same rules this guide describes. VitalScheduler is one option: everyone enters requests in the app, the generator fills every line around them with your hard rules kept and your preferences weighed, the Report shows each person's load against a fair share across the year, and trades happen in the app with the rules checked. Each specialty has a preset to start from, and it is free for 60 days with no card.