Chief resident handover: passing on the call schedule without losing everything.

What gets lost when the chief resident changes

The outgoing chief resident leaves an Excel file, or a link to a Google Sheet. The file arrives intact. What's missing is everything the outgoing chief knew without writing it down: why Dr. G is never on call on Wednesdays, whether Friday counts as a weekend, who already had their Christmas weekend, which column she fixed by hand because the formula miscounted the off-service residents.

The incoming chief discovers these rules one at a time, usually when a colleague writes that "that's not how we usually do it". Each discovery costs a conversation, and sometimes a call given to the wrong person. On a schedule built among peers, it's the team's trust that takes the hit.

The example in this article picks up the fictional service from our article on the resident call schedule: eight program residents, Dr. A to Dr. H, and off-service residents who change every block. Dr. C is finishing her year as chief resident and Dr. D is taking over.

The five things to hand over

1. The service's rules and the exceptions granted

Start with the rules that apply to everyone. These are the ones the team follows without thinking and that an incoming chief can't guess: Friday counts as a weekend worked, an unavailability request sent after the deadline is handled with a swap, a swap is reported to the chief resident before the call. The service also applies the residents' collective agreement, but that is written down elsewhere. Here, you record what your service added on top.

Exceptions come next, one line each. Each one needs five pieces of information, and the end date is the one people forget. An exception without an end date becomes a permanent rule that nobody can explain anymore.

Who	Constraint	Until	Approved by	Note
Dr. G	No Wednesday night calls	2027-08-31	Program director, 2026-09-10	Class on Thursday mornings
Dr. E	No Friday calls	2027-06-30	Program	Accommodation, details in the program's file
Dr. A	Avoid the weekend of 2027-07-02	2027-07-04	Chief resident, 2027-02-15	Swap promised in return for a weekend taken in February

The second line shows how to write an exception that touches on health or private life. You record what has to be respected and until when, not why. The handover document will circulate, and the incoming chief doesn't need the reason to apply the constraint. The third line is the kind of promise that most often disappears: a call given back in return for a favour, settled in conversation, that nobody else knows about.

2. The running count for the year, up to the last block

If the service keeps a running count for the year, hand it over up to date as of the last completed block, swaps included. For each program resident, you need the calls worked and the shares owed, in total and for weekends. The gap between the two shows who is ahead and who is behind. A count that stops two blocks before the handover forces the incoming chief to recount schedules she didn't build.

One decision remains to write down: what happens to that count on July 1? The team changes on that date. Some residents finish, new R1s arrive. Resetting everything to zero is simple. Carrying over the gap of residents who stay means a resident who took two extra calls in June doesn't lose them when the year turns. Both choices hold up, as long as the choice is written down and the team knows it. In the example, Dr. C and Dr. D choose to carry over the gaps of residents who stay and start the R1s at zero.

3. The calendar of what is already known

A good part of next year is already known at handover time. Write it in a single calendar, so the incoming chief doesn't rediscover it block by block.

• The start dates of the blocks, and for each one the unavailability deadline and the publication date. The schedule has to be given out at least five working days before the block starts, so count backwards from there.
• Exam dates already announced, since a resident is released from call for the seven days before.
• Academic half-days and mandatory activities that come back every week or every month.
• Statutory holidays in the summer and fall. July 1, the first day of the residency year, is also a holiday.
• Vacation already granted for the summer.

Add a line for the new R1s. During their first six months, from July to December, an R1 on in-house call must be able to rely on a physician or a resident other than an R1 on site. The first schedule of the year has to account for that from July 1.

4. The file, explained tab by tab

If the schedule lives in an Excel file, add a first tab called "Read me". One line per tab: what it contains, what gets filled in by hand and what calculates on its own. Formulas that point at residents' names typed into cells are the ones that break at the first change of team. Replace them, or at least flag them.

Then run the test that counts. Before the handover meeting, ask the incoming chief to recount the last block alone, from the file and the document. Whatever she can't do without calling you is what's missing. If the file doesn't survive the test, that's the moment to decide whether it's worth fixing or whether to move to something else. Our article on the limits of Excel helps make that call.

5. The people to contact

The call schedule goes through several people the incoming chief doesn't know yet. Write down their name, their role and the best way to reach them: the program coordinator, the office of the director of professional services that signs the schedule, the programs that send residents to the service and the person who confirms their names before each block, and the attending responsible for settling a conflict the team can't resolve.

The handover meeting, in 30 minutes

The document does most of the work, but a short meeting keeps it from sitting in an inbox. Hold it after the recount test, so the incoming chief's questions are already prepared. Half an hour is enough if the document exists.

Minutes	Topic	By the end, you know
0 to 5	Where the schedule lives	Where the published schedule, the count and the swaps are, and who has access
5 to 15	The exceptions, one by one	Which ones stay and which ones end on June 30
15 to 20	The running count for the year	Whether it resets or carries over on July 1
20 to 25	The calendar and the July block	Who builds the July block, and for which publication date
25 to 30	Contacts and next steps	The date of a follow-up call after the first block

The July block deserves a closer look. It has to be published before July 1, during the outgoing chief's year, but the incoming chief is the one who will manage it. Decide who builds it. If it's the outgoing chief, the incoming one follows closely and handles swaps from day one.

The incoming chief's first two weeks

Introduce yourself to the team and to the programs that send residents, along with the unavailability deadline for the next block. Announcing that date early avoids the wave of requests the night before publication.

Reread the list of exceptions and remove the ones that have ended. Check supervision for the new R1s on every in-house call in July. And at the end of the first block, update the count yourself, swaps included, even if the outgoing chief built the schedule. It's the first time the count passes through your hands, and it's when you find out whether it holds. Our article on on-call replacement shows how to handle the first weeks' dropouts without ten phone calls.

The handover checklist, to copy

For the outgoing chief resident, before the meeting:

1. Write down the service rules the team follows without thinking.
2. List each exception with the person, the constraint, the end date and who approved it, with no medical or personal reason.
3. Record the swap promises still to be honoured.
4. Bring the running count for the year up to the last completed block, swaps included.
5. Propose a rule for the count on July 1: reset or carry over the gaps.
6. Fill in the known calendar: blocks, deadlines, publication dates, exams, academic half-days, holidays, vacation granted.
7. Add a "Read me" tab to the file and flag the fragile formulas.
8. Write the list of people to contact, with their role.
9. Ask your successor to recount the last block on her own.

For the incoming chief resident, in the first two weeks:

1. Know who builds the July block and when it's published.
2. Announce the next block's unavailability deadline to the team and to the programs that send residents.
3. Remove the exceptions that have ended.
4. Check supervision for the new R1s on every in-house call.
5. Update the count yourself at the end of the first block.
6. Make the follow-up call with the outgoing chief.

Where Synchro fits

With Synchro, half of this checklist already lives in the tool at handover time. The count carries over from one period to the next and everyone sees the counters, criterion by criterion. Each resident writes their unavailability in plain language, and it stays in their profile from one schedule to the next. When a call changes hands, the swap goes through the tool and the counters follow for both residents. The incoming chief therefore inherits a count she doesn't have to redo, and swaps that didn't stay in a group chat.

Synchro doesn't replace the handover document. The service's own rules, the story behind an exception, the July 1 decision and the contacts still have to be written by hand, and the outgoing chief is the one who knows them. Synchro touches no patient data. Our GMF-U page also says what is still missing for the teaching side of family medicine residency.

Further reading

• How to build the on-call schedule for a resident team
• How to distribute on-call shifts fairly in a medical team
• How to build a hospital department's on-call schedule: a step-by-step method
• Hospital department on-call schedule: what differs from an FMG's
• GMF-U scheduling software
• On-call scheduling software