Blog

8 Nov 2026

On-Call Rotation Scheduling: A Fair, Practical Guide

An on-call rotation is a roster that shares out-of-hours availability across a team, so one named person (plus a backup) is always reachable and nobody carries the duty all the time. A good one has a fixed pattern, a clear handover, a backup, an escalation path and a record of who did what. This guide shows you how to build one, what to put in a template, what Australian employers should check about pay and rest, and what to look for in scheduling tools.

WattleKeep Routine Calls Off the RotaWattle’s AI front desk answers customer calls, handles enquiries, books appointments, and hands complex conversations to staff.Explore Wattle

TL;DR

Pick the pattern from team size and how often you get paged: daily, weekly or fortnightly blocks, with shorter shifts when pages are frequent.
Fair does not mean identical. Weight shifts by how disruptive they are, and let people share their availability.
Every slot needs a primary, a secondary and a manager escalation, plus a handover with a stated time zone.
In Australia, check your award or agreement for on-call allowances and rest breaks before you publish the roster.
Cut the number of calls that reach the rota at all by filtering routine enquiries first.

What an on-call rotation actually is
Choosing a rotation pattern
How to make the rotation fair
What to put in an on-call schedule template
Handovers, swaps and time zones
Escalation: who steps in when the first person doesn’t
Pay, allowances and rest for Australian employers
Features to look for in on-call scheduling tools
Fewer call-outs, fewer burnt-out people
Where Wattle fits
A simple starting rota you can copy
FAQ
Sources

What an on-call rotation actually is

Someone who is on call holds the phone or pager for a set window. When an alert or call comes in, they are expected to respond promptly and set aside what they were doing. GitLab’s handbook describes it in just those terms, and it also describes a looser “best effort” model where no single person has responsibility for responding at any given moment.

The idea applies well beyond software. Plumbers, electricians, property managers, IT support teams, care providers and security firms all run some form of it. The rotation part simply means the duty moves around: each period, one person or a small group carries it, then hands over to the next.

Three decisions define any rotation:

Coverage: when does someone need to be reachable (24x7, weeknights only, weekends only)?
Pattern: how long is each block, and in what order do people take it?
Response rules: how fast must the person respond, and what happens if they don’t?

GitLab splits coverage into levels: 24x7, 24x5 full, 24x5 partial and best effort. It also separates tiers: Tier 1 is paged by automated alerting, Tier 2 is paged by a person asking for more help, and a third layer handles escalations when leadership is needed or a page is missed. You don’t need that exact structure, but naming your own levels stops arguments later.

Choosing a rotation pattern

The right pattern depends on two numbers: how many people share the rota and how often something actually wakes them up.

Grafana’s documentation lays out three common choices in its best practices, and the logic is easy to adopt:

Pattern Best for Trade-off Daily (24 hours) High alert volume, distributed teams Frequent handovers, more admin Weekly (7 days) Most teams, a good balance A bad week can be exhausting Fortnightly (14 days) Small teams with few alerts Long stretches of limited freedom

Weekly is the most common starting point. If you have only three or four people, a fortnight can work when pages are rare, but it falls apart if each night brings a call.

Shift length and rest

Google’s SRE Workbook recommends capping shifts at 12 hours for rotations that handle one or more pages per day. It also says shorter shifts are better for mental health, and that 12 hours overnight is preferable to 24 hours or more. It adds that many countries have laws on maximum working hours, breaks and conditions, so your roster has to respect them.

A practical split for a busy team is a day shift and a night shift handed over at fixed times. For a quiet team, a weekly block with a named backup is usually enough.

Weekday and weekend blocks

Many small teams split the week: one person covers Monday to Thursday nights, another takes Friday to Sunday. It spreads the heavier weekend load and gives people a predictable shape to their month. Whichever split you use, rotate the weekends so the same person doesn’t always lose them.

How to make the rotation fair

Equal shift counts are a starting point, not the finish. Google’s SRE guidance notes that fairness doesn’t mean a uniform spread of each shift type: people have different needs and preferences, so the team should share them and meet them sensibly.

ONES suggests judging a roster on five criteria: coverage, distribution, availability, predictability and sustainability. Coverage comes first, then safety and sustainability. A few habits make that concrete:

Weight shifts by disruption. A Saturday night with three call-outs is not the same as a quiet Tuesday. Track how often each slot actually gets interrupted and count heavy slots more.
Collect availability privately. Ask people for hard limits (a second job, caring duties, travel) separately from preferences (would rather avoid school holidays).
Give recovery time. Someone who was up half the night shouldn’t open the next day as if nothing happened.
Publish early. A roster released weeks ahead lets people plan their lives and swap shifts without a scramble.

Review the load every quarter. If one person has absorbed most of the busy slots, adjust the order, not just the next week.

What to put in an on-call schedule template

You can run a perfectly good rotation in a spreadsheet. Excel or Google Sheets works until the team grows, swaps become frequent or you need automatic alerts. A useful template has these columns:

Column Why it matters Date and start/end time Exact handover moments, not just “Week 12” Time zone Time assumptions are a common cause of handoff failures Primary First person to respond Secondary Steps in if the primary doesn’t answer in time Escalation contact Manager or owner for prolonged or serious issues Phone and backup contact method One number that actually gets answered Shift type Weeknight, weekend, public holiday Swap/notes Who agreed to cover whom, and when Hours worked Feeds pay, allowances and rest checks

Building it in Excel step by step

List your people in one tab, with phone numbers and any hard availability limits.
In a second tab, create one row per shift for the next three months, with start and end date-times.
Fill the Primary column by cycling through your list in order. A simple formula using INDEX and MOD on the week number repeats the cycle automatically.
Fill the Secondary column by offsetting one place in the list, so yesterday’s primary doesn’t back themselves up.
Add conditional formatting to highlight blank cells, double-booked people and public holidays.
Add a “Hours worked” column and sum it per person each month to spot imbalance.
Lock the Primary and Secondary columns, and record swaps in the Notes column rather than overtyping.

The weak point of a spreadsheet is communication. Nobody is notified when it changes, so agree one place where the current version lives and tell the team whenever a swap is made.

Handovers, swaps and time zones

Most rota failures happen at the seams. A short handover routine fixes most of them:

Hand over at a fixed time stated with its time zone, especially if staff are spread across Perth, Sydney and elsewhere. Daylight saving differs between states, so write the zone, not just the clock time.
Pass on open issues, anything customers were promised and any known risks for the coming shift.
Confirm the incoming person has acknowledged the handover, not merely seen it.
Make swaps a two-step process: the two people agree, then one person updates the roster and tells the manager.

Keep a standing rule for sick leave: the secondary steps up, and the manager finds a new secondary the same day.

Escalation: who steps in when the first person doesn’t

A rota without an escalation path is a hope. Redstone HR describes a three-layer escalation path: a primary who owns the first acknowledgement, a secondary who steps in if the primary doesn’t respond in the required window or the issue exceeds their scope, and a manager level for prolonged incidents, staffing failures or decisions needing authority. Their emphasis is on certainty rather than complexity: everyone should know when the issue leaves their hands and when they are expected to step in.

Primary, secondary, and manager escalation roles

Write down three things for each layer: how long you wait before moving up (for example, 10 minutes without acknowledgement), which channel you use (call first, then SMS), and who owns communication with the customer. Physical-site operations face the same questions on a bigger scale, and this walkthrough of responding within minutes at Australian facilities shows how to define who responds when an alert is missed, prolonged or outside the first responder’s scope.

If your escalation involves customer calls, our guide to call escalation rules covers how to write and test them.

Pay, allowances and rest for Australian employers

On-call is a work arrangement, so awards and agreements apply. The rules differ by industry, which means the first step is to find your award, not to copy a figure from elsewhere. Two examples show how different they are.

Social, Community, Home Care and Disability Services Award (SCHADS): the Fair Work Ombudsman says an employee gets an on-call allowance if they are required to be available to be recalled to work, including returning to the workplace or a client’s premises or performing remote work. The amount depends on whether the on-call period is Monday to Friday or a weekend or public holiday.
Plumbing and Fire Sprinklers Award 2020 (MA000036): the award text says a fire sprinkler fitter on call outside ordinary hours must be readily contactable by phone. Listed entitlements include an additional $76.10 per week for permanent stand-by on a roster, or for other on-call, $7.83 per night Monday to Friday and $55.96 per day on Saturdays, Sundays and public holidays, plus payment for telephone rental. The same award says someone who has worked continuously for 20 hours, including holiday work, can’t be required to resume for at least 12 hours. Allowance amounts are updated over time, so confirm current figures on the award page.

Before you publish a roster, check:

Which award, enterprise agreement or contract covers each person on it.
Whether it sets an on-call allowance and how it is calculated.
What happens when someone is recalled: minimum engagement, overtime rates and travel time.
Minimum rest periods between a late recall and the next shift.

If you are unsure how an award applies, the Fair Work Ombudsman’s helpline or your HR adviser can confirm it for your situation.

Features to look for in on-call scheduling tools

When a spreadsheet stops coping, look for tools that do these things:

Recurring rotations with overrides, so a swap or leave doesn’t break the cycle.
Escalation policies that move automatically from primary to secondary to manager.
Reliable notifications over more than one channel, with acknowledgement tracking.
Calendar integration, so shifts appear where people already look.
Gap detection, flagging empty shifts and double bookings. Grafana’s docs recommend schedule quality reports for this.
Time zone handling that shows each person their own local time.
Reporting on hours worked and number of call-outs per person, to feed fairness reviews and allowance calculations.

The best fit is the one your team will actually open. A simpler tool that plugs into your calendar and phone beats a feature-heavy one nobody maintains.

Fewer call-outs, fewer burnt-out people

The fairest rotation is the one that rarely wakes anyone. Many after-hours calls aren’t emergencies: they’re quote requests, opening-hours questions, bookings and reschedules. If each of those pages a person, the rota carries work it never needed to.

Our guides on after-hours answering in Australia and overflow call management look at how to filter calls before they reach a person. For trades the principle is to separate urgent calls from quotes, so only genuine emergencies reach the person on call. To size the problem, try the after-hours revenue calculator.

Our view: protect the rota by protecting the phone

We build Wattle for service businesses, and the pattern we see is simple: an on-call roster gets resented when it is asked to do the front desk’s job. A technician on call at 9pm shouldn’t be fielding a question about Saturday opening hours.

That is why we design Wattle as an always-available front desk. It answers calls and chats, qualifies the enquiry, books appointments and collects the details a human would otherwise ask for. You decide the rules: which situations count as urgent, and when a conversation is handed to staff. Handoff is a policy you write, not an afterthought, and we think it should be written before the first call arrives.

Used this way, the on-call person is reserved for the calls that truly need a person. The rotation gets lighter, response to real emergencies gets faster, and customers still get an answer at 2am.

Christopher

Where Wattle fits

Wattle is an AI customer communications platform that answers calls across phone, web chat, WhatsApp and SMS, books appointments into your connected calendar, and hands sensitive or complex conversations to staff. You configure the agents, the workflows and the handoff rules, and every conversation lands in one inbox with recordings and transcripts.

Plans are published at A$99 per month (Starter), A$499 per month (Pro) and A$999 per month (Max), and you can compare them on the pricing page. If you want to see how the handoff side works first, read our piece on AI agent handoff policy, or browse the feature list.

A simple starting rota you can copy

For a team of five that gets a few after-hours calls a week:

Weekly blocks, handover at 8:00am Monday, with the time zone written in the roster.
Primary rotates in a fixed order; secondary is the person next in line.
Manager is the third layer for every week.
Routine calls are answered and booked by your front desk or an automated agent, and only urgent matters page the primary.
Primary has 10 minutes to acknowledge; then the secondary is called.
Review call-outs per person every quarter and adjust the order if load is uneven.
Check allowances and rest rules against the relevant award before each new roster is released.

Adjust the block length to fit your volume. If pages arrive daily, move towards shorter shifts. If they arrive monthly, longer blocks reduce the number of handovers.

FAQ

How long should an on-call shift be?

It depends on how often people are paged. Google’s SRE guidance suggests a 12-hour cap for rotations handling one or more pages a day. Quieter teams commonly use weekly blocks, and very small teams with rare alerts can stretch to a fortnight.

What should an on-call schedule template include?

At minimum: shift start and end with the time zone, primary, secondary, escalation contact, phone number, shift type and a notes column for swaps. Add hours worked if you need to calculate allowances or check rest.

How do I create an on-call schedule in Excel?

List your people, create a row for each shift, then cycle names through the Primary column using a formula based on the week number. Offset the Secondary column by one person and add conditional formatting to catch gaps and clashes. Agree one place where the current version is stored.

Do Australian employees get paid for being on call?

Often they do, but it depends on the award, agreement or contract. Some awards set a daily or weekly on-call allowance, and others have rules on recall and rest. Check your applicable award on the Fair Work Ombudsman website before you publish a roster.

Sources

Give every caller a good first answer.

Request access