Free template · Four weeks · Escalation columns
An on-call template built around the question people actually ask at 2am
An on-call schedule names who is reachable outside rostered hours, and in what order. A usable one is not a list of names against dates: it needs a primary, a secondary and a backup as separate columns, a phone number beside each, and an explicit time at which call passes from one person to the next.
Free · No email address · No account
Where can I download a free on-call schedule template?
Here: the two buttons below. No email address, no account, and no thank-you page with a sales sequence behind it.
Opens in Excel, Google Sheets, LibreOffice or Numbers. The printable version is laid out landscape for a wall.
What is in it
- Twenty-eight days, one row per day, with a worked example on the first row.
- Primary, secondary and backup columns, each with a phone number column beside it.
- A service column, so a group running more than one rota keeps them in one file.
- An explicit handover time column, and weekends flagged in the notes.
At a glance
- An on-call schedule says who is covering outside normal hours, and, the part most templates miss, who is tried next when the first person does not answer.
- Primary, secondary and backup belong in three separate columns. One column of names is a rota with a single point of failure, and everybody discovers that on the night it matters.
- Every name needs a number beside it. A rota that sends someone hunting for a directory at two in the morning has failed at the only moment it was for.
- Handover time must be explicit. 'Monday' is not a time, and the argument about whether Monday call began at 00:00 or 08:00 always happens after the incident.
- This template is four weeks, one row per day per service, with weekends flagged so the fair-share conversation has something to count.
What is an on-call schedule template?
An on-call schedule template is a reusable grid of dates against the people covering them, structured so that it answers not only who is on call but who is tried next.
The distinction is the whole point. A calendar with one name per day is an on-call schedule in the same way that a list of ingredients is a meal: it contains the right nouns and it will not survive contact with the evening. What the person holding the phone at two in the morning needs is an ordered list (this person, then this person, then this person, and here are the numbers), because the single most likely thing to happen on a call rota is that the first person does not pick up. That is not a failure of character. It is a person asleep, in a shower, or in a tunnel.
So the columns here are primary, secondary and backup, each with a number beside it, plus the service the rota belongs to and the time call changes hands. Five of those eleven columns are the escalation. That ratio is deliberate.
What should an on-call schedule include?
The date, the service, three named people in order, a phone number for each, the handover time, and a note column that marks the weekends.
Each of those earns its place by being the thing whose absence causes a specific, recognisable failure, which is a better test for a column than whether it seems useful.
Three names, in order
Primary, secondary, backup. One name is a single point of failure; two is better; three is where most rotas stop being interesting. The order is the information: 'these three are around' is not an escalation chain, it is a group chat.
A number beside every name
The rota is read by people who do not know your team: a switchboard, a locum, a nurse on a different floor at 02:00. A name without a number sends them to find a directory, and the directory is out of date, and now there are two problems.
An explicit handover time
Write 08:00, not 'Monday'. Every rota that says 'Monday' has had the conversation about whether Monday call started at midnight or at eight, and it has had it retrospectively, in a meeting, about an incident.
A service column
Most groups run more than one rota, and keeping them in separate files is how a person ends up primary on two of them on the same night without anyone noticing until the pager goes twice.
Weekends marked
Not for the rota, for the argument afterwards. 'I always get the bad weekends' is answerable with a number or it is answerable with a conversation, and the number is quicker and ends better.
How do I build an on-call rota?
Count what everyone carried last time before you place anyone this time, then place the unpopular dates first and let the ordinary weeknights fall out at the end.
The order is the same as any rota, with one addition that is specific to call: it is the only rota where the perceived fairness matters as much as the coverage, because the people on it are giving up their evenings rather than working a shift they turned up for. So start from the count. Who carried the last three weekends, who had Christmas, who has done four nights in a row of second call because they are reliable and it was easy to ask them. If you cannot answer that from a file, the rota you are about to build will be fair only by accident, and nobody will believe it either way.
Then place the hard dates: public holidays, the weekend of the conference everyone is at, the night your only paediatric cover is at a wedding. Then fill the weeknights, which are the easy ones and are therefore the ones to leave until you have no options left to spend.
Publish it where it can be read without an account, and make sure the version on the wall and the version in the inbox are the same version. A call rota that exists at two revisions will send two people to bed believing different things, and one of them is going to be right in a way that does not help.
What a call rota in a spreadsheet cannot do
It cannot ring the second person. It is a document, and documents do not escalate.
Everything up to the moment of the call, this sheet does perfectly well. The moment of the call is where it stops: nothing here notices that the primary did not acknowledge inside ten minutes, nothing moves to the secondary, and nothing writes down what time any of it happened, which is the record you will want afterwards, and the one nobody ever has. It also cannot answer the question at all unless the asker has the file, which at 02:00 they very often do not.
That gap is what on-call software is for, and it is a small enough gap that plenty of groups reasonably decide the spreadsheet is fine. MedAligna publishes the current on-call on a link that needs no login, walks the escalation chain when nobody acknowledges, and timestamps every step. It also counts the weekends and holidays per person, so the fairness conversation has a number in it rather than everybody's memory of last November.
Questions people actually ask
- Do I need to give an email address?
- No. Both links download directly, with no form and no follow-up.
- Why are primary, secondary and backup separate columns?
- Because the order is the information. The most likely event on any call rota is that the first person does not answer: asleep, in a shower, in a tunnel. A rota that has not written down who is tried next has left that decision to whoever is panicking at the time.
- How long should an on-call shift be?
- That is a decision about your team, not one we can make for you, and it depends on the volume of calls as much as the length of the block. What matters for the template is that whatever you choose, the handover moment is written down as a time rather than a day.
- Can I use it for more than one service?
- Yes. The service column is there for exactly that. Copy the block of dates and change the service name. Keeping them in one file is what lets you see that the same person is primary on two rotas on the same night.
- Does it track who has done the most weekends?
- It marks the weekends so you can count them, which is a real improvement on not marking them, and it is still counting by hand. A file cannot tell you who worked the last occurrence of each holiday.
Related
The board that answers the pager question
Who is on call right now, who is second, who is backup, all on a link that needs no login, with an escalation chain that actually escalates. Fourteen days free.