Everybody Wants the Same Fortnight
Planned leave is the one absence you know about in advance, and it is routinely approved into a shape that guarantees the summer will be covered by agency.
Second week of August
Needed on shift
6
Rostered
4
Actually present
4
Two of the six were on approved leave and the rota was built around it. Nothing went wrong on the morning. The shortfall was approved in March by three people who each saw one request.
Annual leave is absence with months of notice. It is the easy case and it is handled worse than the hard one, because the approval decisions are made individually and the consequence is collective.
The practical issue in “Everybody Wants the Same Fortnight” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring interview reimbursement policy, Monitask can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.
Three managers each approve a reasonable request. Nobody looks at the total. In August the unit runs with four of six for a fortnight, and the mornings during that fortnight have no absorption left in them at all.
For an independent benchmark relevant to “Everybody Wants the Same Fortnight”, consult the Xero accounting resources. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.
The quota, and why percentages fail
Most operations have some rule — one person off at a time, or a percentage of the team. Percentages fail because they ignore capability: two people off out of eight is fine unless both hold the thing only they hold.
The quota has to be expressed against the requirement rather than against headcount. What must remain is enough people and enough of each capability to run every shift in that period, with some margin for the absence nobody planned for, which will also occur.
Booking windows
A deadline for the popular periods, with requests considered together rather than first-come. First-come rewards whoever reads email at the right moment and produces the clustering described above.
Publishing the outcome together also makes the allocation visible, which is what makes a refusal acceptable. A person told no in isolation experiences a decision about them; a person who can see that four others asked for the same fortnight understands an allocation.
For the rest of the year, first-come is fine and much cheaper to administer.
The thing to check at approval
Not just how many are off, but what remains. Before approving, the check is the same one-absence test applied to the resulting rota: with this person away, does every shift that fortnight still meet requirement and still hold two of each capability.
If it does not, the choice is to refuse, to approve conditionally on cover being arranged, or to approve and plan cover now — in March, when bank and agency availability is good and cheap, rather than in August when it is not.
The third option is the one most often missed. Known leave is the best possible time to book cover, and operations routinely wait until the week before.
Carry-over, and the December problem
Leave that must be taken before a year end produces a December or March cluster that nobody planned for. It is entirely predictable from the leave balances, which the organisation holds.
Run the balances in September. Anybody with a large untaken balance is going to take it in the last quarter, and knowing who and roughly when lets it be spread. Leaving it produces a scramble in which the operation both runs short and has to refuse requests, which is the worst combination.
Shutdowns
Where the operation can close or reduce, a planned shutdown converts a scattered problem into a known one. It is not available everywhere and where it is, it is cheaper than any other approach to the summer.
Where it is not available — care, transport, security, anything continuous — the opposite applies: the peak period needs more cover planned, not less, and the planning has to happen when the leave is approved rather than when it begins.
Measuring it afterwards
Shifts below requirement during approved-leave periods, compared with the rest of the year. If the peak weeks are substantially worse, the approval process is producing them.
That is a finding about a decision made in spring, by people with time to think, which is a much easier thing to fix than a morning.
Protecting the quiet refusal
Leave allocation decisions are disproportionately contested when the reasons are invisible, and disproportionately accepted when the constraint is stated in advance.
Publish the rule before the window opens: how many can be off, what capabilities must remain, and how ties are settled. A person refused under a published rule has been treated consistently. A person refused with no stated basis has been treated by somebody's judgement, and will reasonably ask why the refusal landed on them.
The leave that was never requested
The opposite problem, and a quieter one: people who do not take their entitlement. It looks like a benefit to the operation and it is not.
Untaken leave accrues as a liability, lands in a cluster at the year end, and in the meantime the person is working a full year without a break, which produces exactly the absence the operation is trying to avoid. Run the balances twice a year and prompt the people with large ones. It is a cheap intervention that improves both the December problem and the absence rate, and it is usually nobody's job.