In most small businesses, leave management is an improvisation: whoever asks first wins, the same reliable two people cover every gap, and the school holidays — dates published years in advance — somehow ambush the roster four times annually. The result is a quarterly cycle of friction that everyone accepts as natural. It isn't. Leave runs drama-free on three lightweight mechanisms and a clear understanding of where the legal lines sit. Here's the system.
Mechanism one: make leave visible a year out
Most leave conflict is a visibility failure. The fix is a single shared leave calendar — in your roster system, your HR app, or a shared calendar; the tool barely matters — showing approved leave for the whole team, twelve months forward, with the known crunch points pre-marked: school holiday blocks, your industry's peak periods, the Christmas shutdown, the EOFY fortnight if you're in finance-adjacent work. When everyone can see that two of five are already away in the second week of January, the third request arrives as a conversation, not a collision. Pair it with an expectation that's pure kindness in disguise: big blocks of leave get requested early. "First half of next year's plans by October" isn't bureaucracy; it's what lets you say yes more often.
Mechanism two: decide the fairness rules before you need them
The trouble spots are predictable, so legislate them in advance, in writing, while nobody's upset: How many people from one team can be away at once? When demand for a period exceeds that cap, what breaks the tie — first-asked, rotation of priority years for school-holiday slots, seniority? (Rotation is usually the durable answer for the perennial conflicts; first-asked rewards calendar speed and breeds resentment among parents who all need the same weeks.) How much notice for a week-plus block? What's the rule during your declared peak periods? Five questions, one page, applied consistently — including to the owner's family holidays, which is where these policies traditionally die.
Worth knowing where the law sits: annual leave is taken by agreement, and an employer can refuse a request only on reasonable business grounds — but a policy with transparent caps and notice expectations is precisely what makes a refusal reasonable, and what makes most refusals unnecessary.
Mechanism three: cross-cover as infrastructure, not heroics
If leave hurts, the wound is single-person dependency, not the holiday. For every role, the question is "who is the designated second?" — not a master of the job, but competent in its weekly essentials, supported by the documented processes we're forever recommending. Build the pairs deliberately, let the second actually drive a few times a year while the first is present (the cheapest training there is), and require a one-page handover note for any absence beyond a couple of days: live jobs, looming deadlines, who's been promised what. The handover habit alone removes half the re-entry chaos that makes people dread their own holidays.
Sick leave: support genuinely, manage patterns properly
Personal leave is an entitlement, not a favour — the baseline response to illness is coverage and zero guilt, and a culture where people work sick costs more than the leave ever would. That said, patterns are manageable: evidence requirements (a certificate after a defined threshold) applied consistently are lawful and reasonable; an attendance conversation — private, factual, framed as "is everything okay, and is there something we should adjust?" — is appropriate when a genuine pattern emerges (the every-second-Monday shape everyone notices and nobody names). What's not appropriate: disciplining the entitlement itself, surveillance theatrics, or treating one person's pattern with policy applied to no one else. Document the conversations, support what's real, and address what isn't — in that order.
And school holidays specifically: for parents, these aren't preferences, they're constraints. The businesses that handle them best plan capacity around the blocks (lighter scheduling, casual cover arranged in advance), use the rotation rule for the contested weeks, and — where the work permits — treat flexibility (adjusted hours, remote days) as a coverage tool rather than a concession. Predictable flexibility beats heroic coverage every time.
FAQ
Can I direct someone to take leave if their balance is huge?
In many awards, yes — excessive balances can be addressed by direction, with notice and reasonableness requirements. But the conversation almost always beats the direction: most large balances belong to people who feel they can't leave, which is a coverage problem you own.
What do we do when everyone wants Christmas week?
Declare the shutdown (if you have one) formally and early, cap the adjacent weeks per the policy, and rotate priority year to year. Publish the outcome in October — certainty early beats generosity late.
Casuals and leave — what applies?
Casuals don't accrue paid leave (the loading compensates), but the planning mechanisms apply identically: visibility, notice expectations for unavailability, and cross-cover. A casual workforce makes the calendar more important, not less.
Single-person dependencies are what turn holidays into crises — and they're exactly what our free Business Health Check surfaces. Five minutes, clearer picture.
About the author
Nick Lucock
Chief Executive Officer, Valont
Nick leads Valont's day-to-day operations across Finance, People, Operations and Growth. He writes about how the work actually gets done — the processes, systems, and tools that keep Australian SMEs compliant and growing.
LinkedIn →