A text on Sunday night
The rota is in a spreadsheet, or on the wall. Holiday requests come in by message. A regular pharmacist calls in sick. You message three locums you know, one replies yes, another replies yes later, and now you have two people coming or nobody sure who confirmed.
With a couple of branches it gets harder. A gap at one branch is spotted on Thursday for Saturday. Agencies are called. Rates go up the closer you get to the day. A pharmacy cannot open for its core services without a responsible pharmacist, so the owner ends up covering it themselves.
Why gaps are found late
Gaps are not hard to predict. Holidays, training days and regular locum days are known weeks in advance. But the rota does not show them clearly as gaps. It shows names in boxes, and an empty box on a busy spreadsheet is easy to overlook.
Bookings then happen in text threads and phone calls, so the rota is updated only when someone remembers. The confirmed state of a shift is in someone's messages, not on the rota.
Locums themselves are juggling several pharmacies. A message asking "are you free on the 14th?" gets a quick yes, but whether that yes is a firm booking or a maybe depends on how both sides read it. Without a clear confirmation that both sides can see, a locum can end up double-booked, and the branch finds out at nine in the morning.
What the scramble costs
| Issue | Effect |
|---|---|
| Gaps spotted late | Short notice bookings at higher rates, or none at all |
| Unclear confirmations | Two locums turn up, or none does |
| Owner covering | The owner's own time goes on shifts instead of the business |
| No locum history | You cannot see which locums you use most or what you spend |
| Branch staff unsure | Teams do not know who is coming tomorrow |
A rota and booking tool that shows gaps early
- A pharmacist rota per branch showing every session, who is covering and whether it is confirmed, with empty and unconfirmed sessions in a colour that is impossible to miss.
- Leave requests entered into the same tool, so approving leave creates the gap on the rota immediately.
- A locum list of pharmacists you are happy to use, with their availability preferences, contact details and notes such as which branches they know.
- Shift offers sent by text or email to chosen locums with a link to accept. First to accept is booked, the others are told it is filled, and the rota updates.
- Confirmations recorded with a reminder to the locum a day or two before, and a heads-up to the branch team.
- A monthly summary of locum days and cost by branch, for planning and for your accountant.
If you already use a staff rota product that covers most of this, we will say so. Many are designed for large chains and fit small groups poorly, which is where a lighter tool helps.
A rota you can trust four weeks ahead
Gaps show up when leave is approved, not the week before. Offers go to the right locums in one step, and the booking is on the rota the moment it is accepted. Branch teams can see who is coming. You stop keeping the real rota in your text messages.
Over time, the summary shows how much you rely on locums and where, which feeds into decisions about hiring or changing opening hours.
Locums notice the difference as well. They get clear offers, a confirmation they can refer back to, and a reminder of the branch address and parking before the day. The good ones are more likely to come back, and building a small pool of reliable locums is the best protection against the Sunday night scramble.
Is locum cover a weekly scramble?
- The rota lives in a spreadsheet or on paper
- Locums are booked by text and confirmations get lost
- Gaps are noticed only a few days before the shift
- You cover shifts yourself more often than you would like
- You do not know what you spent on locums last quarter