Every absence is different. A 6am sick call needs a different response to a teacher’s planned leave, and both are different again from someone going on extended leave for a term. Treat them all the same way, working down a phone list until someone picks up, and you’ll spend your morning on the phone regardless of which one you’re dealing with.
The schools that handle absences well aren’t the ones with the biggest casual list. They’re the ones matching the right booking method to the right kind of gap. Here are three scenarios that play out in schools every week, and how each one looks different on ClassCover compared to the old way of doing it.
1. The 6am Sick Call
The scenario: A Year 5 teacher texts the principal at 6:05am. They’re unwell and won’t be in. Class starts at 8:45am, and there’s no lesson plan sitting ready.
The old way: Whoever’s on relief duty starts working through a contact list, calling names one at a time. The first two don’t answer. The third picks up but can’t do it. By the time someone says yes, it’s 7:40am, and the plan for the day, briefing the casual, printing anything they need, is now rushed into twenty minutes instead of the hour it should have had.
On ClassCover: The coordinator opens the app and sends an All At Once booking to every available casual on the school’s preferred list at once. Instead of one call at a time, the request reaches everyone simultaneously via push notification, backed up by SMS and email for anyone who might miss the app alert. Whoever accepts first gets the booking, and everyone else is notified that the booking has been filled, so there’s no confusion or double booking. A confirmed casual is usually locked in well before 7am.
Why All At Once bookings work here: Speed matters more than choice. You’re not trying to get your favourite casual specifically, you’re trying to get any qualified, available casual into that classroom before the bell. Sending an All At Once booking request to everyone on your list who’s free removes the sequential guesswork of calling down a list.
2. The Planned Leave Request
The scenario: A teacher puts in for a personal day three weeks out, for a specific date they already know. There’s no urgency, but there is a strong preference: the school wants a casual who already knows the class, ideally the same one who covered last time.
The old way: The coordinator makes a mental note (or a note on a sticky pad) to call the preferred casual “closer to the date.” Sometimes that follow-up happens on schedule. Sometimes it slips, three weeks becomes three days, and now a planned absence has turned into a semi-urgent scramble because nobody locked in the booking early.
On ClassCover: The coordinator sends an individual request to the specific casual they want, as soon as the leave is approved, three weeks out rather than three days. The casual gets the request immediately and can accept at their convenience, well ahead of the date. Because it’s booked early, there’s time to brief the casual properly, share any specific class notes, and confirm details, rather than everything happening in a rush the day before.
Why individual requests work here: There’s no urgency to trade away control for speed. You know exactly who you want, they’re free, and locking it in early means one less thing to track as the date approaches.
3. The Extended Absence
The scenario: A teacher goes on longer leave, parental leave, medical leave, long service leave, for a full term or more. The school needs consistent coverage for the whole period, not a new casual improvising from scratch every day.
The old way: The school either finds one casual willing to commit to the whole block informally (and hopes they don’t get a better offer elsewhere partway through) or ends up with a rotating cast of different casuals each week, each one starting from zero on classroom routines, student needs, and where things are kept.
On ClassCover: The coordinator sets up a recurring booking with a preferred casual, covering the relevant days each week for the length of the leave. The casual has certainty about the commitment upfront and can plan around it, rather than wondering week to week whether the booking continues. The school gets consistency for the class: one person learning the students, the routines, and the term’s work, instead of a different casual walking in cold every few days.
Why a recurring booking works here: Extended absences are exactly the case where continuity matters more than speed or flexibility. A single, committed casual booked for the whole period is a materially better outcome for the students than the best individual sub arriving fresh each week.
Comparing the Three Approaches
| Scenario | Booking method | What matters most | Old-way pain point |
|---|---|---|---|
| 6am sick call | All At Once | Speed | Sequential phone calls, wasted minutes |
| Planned leave | Individual request | Choice and lead time | Follow-up slips through the cracks |
| Extended absence | Recurring booking | Continuity | Rotating casuals, no consistency |
The Common Thread
None of these three scenarios are solved by a bigger casual list on their own. They’re solved by matching the booking method to what the absence actually needs: broadcast when speed is everything, an individual request when you already know who you want and have time to ask them properly, and a recurring booking when what the class needs is one familiar face for weeks at a time.
The old way treats every absence the same, work the phone list until someone says yes. Once a school starts treating a sick day, a planned day, and a term-long leave as three different problems, filling them stops being the stressful part of the morning.
Try ClassCover Free in your school
Get started with a 30-day free trial and see how ClassCover can work for you.
Start free trial
