The Week Off
A week of annual leave in the wrong week stops five of the seven things a payroll run needs. The date does not care, and the problem is entirely foreseeable.
Nobody elseif the person who does this is away
What one week of annual leave actually stops
The owner
Nobody elseIf they are away: Nobody asks, and the inputs do not arrive
The owner
Nobody elseIf they are away: Whatever was agreed that month does not reach the run
The owner
Nobody elseIf they are away: It waits, and the slack is gone when she returns
The owner
Nobody elseIf they are away: Nobody else has a login that can
The owner
Two peopleIf they are away: A co-director can move the money, given the figure
The accountant
A bureauIf they are away: Submitted, if the figures reached them
The owner
Nobody elseIf they are away: It waits a week
5 of 7 tasks have nobody else who can do it.
Five of seven stop, and the date does not. One small employer's own arrangement; not a model for anybody.
A week of annual leave taken by the person who runs payroll, falling in the wrong week of the month, stops most of what a run needs. The pay date does not move for it.
The deadline in “The Week Off” becomes more workable when collection and approval happen before the final payroll cut-off. Organisations considering see the full software outline for employee monitoring with screenshots can make that timing visible without assuming that activity data alone explains whether a payroll step is complete.
The problem is entirely foreseeable and is nonetheless met as a surprise in most small businesses.
For an outside reference relevant to “The Week Off”, consult Google Workspace resources. Compare general guidance with the employer’s jurisdiction, contracts and current payroll process.
Which week is the wrong one
The one containing the cut-off, the keying or the approval — usually a stretch of about ten days before the pay date.
For a monthly payroll that is a third of the month, which means a randomly chosen week collides about a third of the time.
What stops
Chasing. Entering changes. Keying. Approving. Answering questions. Everything that needs either the knowledge or the login.
What does not stop
Funding, if somebody else has bank access and a figure. The filing, if it is outsourced. The pay date itself, which arrives regardless.
The three available responses
Do it early, before going. Do it late, after returning. Have somebody else do it.
Most small businesses use the first, which works and quietly makes the leave worse.
Doing it early
Running the payroll before departure, with estimated or incomplete inputs, and correcting afterwards.
Workable for a stable salaried payroll. Poor for an hourly one, where the hours for the period have not happened yet.
Doing it late
Only possible if the leave ends before the pay date with enough days left. Frequently it does not, and the result is a late payment caused by somebody's holiday.
Having somebody else do it
The only answer that actually resolves it, and the one that requires preparation in a quiet month: a written sequence, a login, and somebody who has watched a run.
Those three things are the subject of the rest of this section.
The leave that is not planned
Illness. Everything above assumes notice, and the hardest version of this problem is the one with none.
A business prepared for planned absence is automatically prepared for unplanned absence, which is the strongest argument for preparing at all.
Looking at the calendar together
Leave dates and pay dates on one view, a year ahead. The collisions are visible in a minute and there are usually two or three.
Knowing which months they are converts the problem into a plan.
What to do about the collisions
Either move the leave, which is often unreasonable, or arrange cover for those specific months, which is tractable.
Arranging cover for two months a year is a much smaller task than building a general capability, and it covers most of the risk.
The quiet cost of always working around it
The person who runs payroll never takes leave in the week they want to, or works during it. Over years this is a real cost borne by one person, invisible to everybody else, and nobody has ever counted it.
The question worth asking out loud
Whether the person who runs payroll has ever taken leave without either working during it or moving the dates.
In most small businesses the honest answer is no, and that answer is the finding.
What a prepared business looks like
The sequence written, a second login, the calendar shared, and the filing outsourced. Four things, an afternoon, and none of them expensive.
Looking at it as a probability
A monthly payroll has roughly ten days in which absence stops the run. Somebody taking four weeks of leave a year, placed at random, collides with that window more often than not.
Put that way it stops being bad luck and becomes an expected event that the business has simply never planned for.
What "arranging cover" actually means
Not training anybody in payroll. A written sequence, a login, bank access, a reachable credential, and somebody to telephone.
Four of those five are administrative arrangements made in an afternoon, and the fifth is a phone number. The reason this gets postponed is that people imagine it requires teaching somebody the job, which it does not.
The cost that falls on one person
Years of taking leave around a payroll calendar, or working during it, is borne entirely by whoever runs it and is visible to nobody else.
It does not appear in any cost comparison, it is never raised, and in a small business it is frequently the owner, who treats it as part of owning the business rather than as a thing that could be arranged differently.
The question that settles it
Has the person who runs payroll ever taken a week off, in a run week, without working?
In most small businesses the honest answer is no. That answer is the finding, and everything else in this section is what to do about it.
The reframing that helps
This is not about payroll. It is about whether one person can be unavailable for a week without a fixed obligation being missed, and payroll is simply where that shows first.