Scheduling across branches without double-booking your consultants

A single-site fertility clinic can run its calendar on convention and conversation. A four-branch chain cannot — and the failure mode is not dramatic. It is a consultant who is booked at two sites on a Tuesday afternoon, discovered at 2:40pm by a front desk that has already checked both patients in.

Three layers, in strict order

Multi-branch scheduling breaks when the layers are collapsed. Keep them separate and in this order:

Layer 1 — Branch hours and slot templates

Each location has working hours and a slot structure. This is the outermost constraint: nothing can be booked outside it, regardless of who is available. Branches differ — a satellite site open three mornings a week has a genuinely different shape from the flagship — and pretending otherwise is where over-booking begins.

Layer 2 — Doctor availability and leave

Against those hours sits each doctor’s weekly availability, their bookable slots and their leave dates. A consultant who works Monday and Wednesday at one branch and Tuesday at another has one availability record, not three, or the conflict is unrepresentable.

Layer 3 — The daily roster

The roster is where availability becomes commitment: assigning doctors to specific time blocks for a specific day, within branch hours, with double-booking prevented at the point of assignment rather than detected afterwards.

Only then does an appointment become bookable. If your system lets front desk book a slot that no roster entry supports, the roster is decorative.

The rules that prevent most incidents

• No slot without a roster entry. Availability is a claim; a roster entry is a commitment. Book only against commitments.
• Leave beats everything. Approved leave removes slots from the bookable pool immediately, everywhere, without a human remembering to cancel them.
• Reschedules require a reason. Mandatory remarks on cancel, reschedule and add-time turn an unexplained calendar into a readable one.
• One doctor, one place, one time. Enforce this at assignment, across branches, not within a single branch view.
• Visit type drives duration. An assessment consultation and a treatment review are not the same length. Slot templates that pretend they are will run late by mid-morning.

Where forecasting helps

Once rosters are structurally sound, the remaining problem is shape rather than conflict: are you rostering the right capacity, at the right branch, on the right day? Historical demand by branch, visit type and season answers that far better than intuition, and it is the sort of question a model answers well because the data is already structured.

The same applies to no-shows. Every clinic knows some appointments will be missed; few know which ones in time to do anything. Scoring upcoming appointments for no-show risk turns a confirmation-call list from a hopeful ritual into a targeted one, and lets you open same-day slots where they will actually be used.

A quick diagnostic

Ask your front desk lead one question: can you book an appointment that the roster does not support? If the answer involves the phrase “but we would never do that”, you have a structural problem waiting for a busy Tuesday.