A team member asks for a week off in December. It is a reasonable request. They have leave owing, the family has plans, and they asked early. The manager says, "Let me check and come back to you."
Then the checking begins. Who else is already off that week? The wall planner shows two names, but someone mentioned on WhatsApp that they might also take a few days. Who can cover the deliveries if this person is away? Only one other person knows the route and the customers, and she has also asked for leave around Christmas. Is the week before the public holiday busy? Last year it was. The manager spends twenty minutes on the puzzle, and still is not sure.
Multiply that by every leave request in the year, add the December rush and school holidays, and a quiet administrative task becomes a recurring source of time lost and uncertainty for everyone involved.
A right that has to be fitted around the work
South Africa's Basic Conditions of Employment Act gives employees at least 21 consecutive days of annual leave on full pay in each annual leave cycle, or by agreement one day of leave for every 17 days worked. The Department of Employment and Labour's guide explains that leave must be granted no later than six months after the end of the leave cycle, that employer and employee should agree on when it is taken, and that if they cannot agree, the employer decides. Employers may not pay employees instead of granting leave, except when employment ends.
The law, in other words, guarantees the leave but leaves the timing to be worked out. That working-out is where the puzzle lives. South Africa also has twelve public holidays, several of them clustered in March and April and three in December. When a public holiday falls on a Sunday, the following Monday becomes a holiday. Those dates shape when people want leave and when the business is busiest.
Why leave becomes a puzzle
Consider an illustrative case: a Pietermaritzburg business supplying and servicing commercial kitchen equipment, with fourteen staff, including four technicians, two delivery drivers and three people in the office. Leave is requested by WhatsApp or in passing, approved by the owner, and recorded on a wall planner in the office and in the payroll system for pay purposes.
Several things turn each request into a puzzle:
- The record is scattered. Approved leave sits on the wall planner, pending leave sits in messages, and informal "I might take a few days" sits in memory. No single place shows the whole picture.
- Skills are invisible. The planner shows who is away, not what they can do. Whether the business can cope depends on which skills are absent, and that knowledge is in the owner's head.
- Cover rules are unwritten. Nobody has said "we need at least two technicians and one driver every working day". So each decision is made from scratch.
- Requests arrive one at a time. First come, first served sounds fair but means the December puzzle is solved piecemeal, often leaving later requesters disappointed without understanding why.
Mellorca has written about a related situation, where a planned absence exposes knowledge nobody wrote down, in when parental leave means handing over an undocumented job. The leave puzzle is the everyday version: the same underlying issue showing up as a scheduling headache several times a year.
The human tax: time and predictability
The time cost falls first on the person approving. Each request means checking several sources and sometimes several conversations. In a small business that person is often the owner, who has little time to spare.
The predictability cost falls on everyone. The person asking for leave waits for an answer, sometimes for days, and cannot book travel or confirm plans with family in the meantime. Colleagues wonder whether they will be left short. The approver worries about having made a mistake. None of this is dramatic, and some workplaces handle it with goodwill and flexibility. But for the person who has asked for leave, the wait can turn something that should feel like an entitlement into something that feels like a favour. That is offered as a reasonable interpretation, not a measured finding.
There is also a fairness question. When the puzzle is solved informally, people may not understand why one request was approved and another refused. Clear rules tend to feel fairer, even when the answer is no.
What could change
- Put all leave in one place. A shared calendar, the leave module of a payroll or HR system, or a scheduling app. Microsoft's Shifts app, for example, lets employees submit time-off requests that managers approve or deny, and approved requests update the schedule automatically. A simple shared spreadsheet also works for a small team, if everyone uses it.
- Write down minimum cover. For each role or skill, how many people must be present on a working day? With that rule written down, many requests can be answered at a glance.
- Record skills, not just names. A short skills list shows who can cover what. It also shows where only one person can do something, which is the real risk. Mellorca's guide on how to know whether your business depends too much on one person covers this in more depth.
- Plan the peaks early. Invite December and school-holiday requests by a set date, then decide them together using agreed criteria, such as rotation from year to year.
- Cross-train deliberately. If only one person knows the delivery route, a second person learning it is the most effective fix for the leave puzzle, and for the business's resilience generally.
- Answer within a set time. A promise to respond to leave requests within, say, three working days removes much of the waiting.
Approval rules matter too. If only the owner can approve leave, every request queues behind their other work; when staff need to ask who approves what looks at how unclear approval paths slow businesses down.
Trade-offs
- Rules reduce discretion. Written cover rules can make it harder to accommodate a genuine family need that does not fit. Leaving room for exceptions matters.
- Cross-training costs time. Teaching a second person a role takes hours from both people, and some staff value being the one who knows.
- Visibility cuts both ways. A shared leave calendar shows everyone's absences, which some people may consider private. Showing only "away" rather than the reason helps.
- Peak planning creates disappointment. Deciding December leave in one round makes the trade-offs visible, and some people will not get what they asked for.
- A tool does not fix understaffing. If the business cannot cover leave at all, the issue is capacity, and no calendar will solve it.
Why it matters
For the business, simpler leave decisions mean fewer surprises, better cover and less time spent by the owner on administrative puzzles. For the people, the change is in how leave feels. A request that is answered quickly, against rules everyone understands, lets someone book the trip, tell the family and look forward to the time off rather than wondering whether it will happen.
That is the dividend: time returned to the approver, and predictability for the person asking, so that leave can be planned as the right it is.
Sources and further reading
- Basic Guide to Annual Leave (last verified 10 October 2026)
- https://www.labour.gov.za/DocumentCenter/Acts/Basic%20Conditions%20of%20Employment/Act%20-%20Basic%20Conditions%20of%20Employment.pdf (last verified 10 October 2026)
- Public holidays in South Africa - South African Government (last verified 10 October 2026)
- Manage shift requests and time off in Shifts - Microsoft Support (last verified 10 October 2026)
Related Mellorca reading
- The Saturday Morning Spent on Invoices
- Why Holidays Still Need a Laptop in the Suitcase
- What Changes When Status Updates Stop Being a Chore