Putting the Year on One Page
An hour once a year putting every payroll date on one visible calendar removes most of what goes wrong in a small payroll.
Written downif the person who does this is away
An hour spent once a year putting every payroll date on a single calendar — visible to more than one person — removes most of what goes wrong in a small payroll. It is the cheapest control available here and the one most small businesses do not have.
The continuity issue in “Putting the Year on One Page” calls for records another authorised person can understand. For teams researching Monitask pricing, a clearer Monitask pricing workflow can add transparent time and project evidence when access is limited, corrections remain visible and payroll credentials stay in the proper system.
The reason to do it is not tidiness. It is that a date held in one head moves whenever that head is busy.
The questions raised in “Putting the Year on One Page” can also be checked against Acas pay and wages guidance. Use that material to identify the evidence and owner needed for the next payroll run.
What goes on it
Pay dates for the year. The cut-off and keying day behind each. The statutory filing dates. Year end. Public holidays. Known absences of whoever runs it. The months with an extra run, if any.
Seven kinds of entry, most knowable a year ahead:
- Pay dates.
- The cut-off and keying day behind each one.
- The statutory filing dates, marked as immovable.
- Year end.
- Public holidays.
- Known absences of whoever runs it.
- The months with an extra run, if any.
Seven kinds of entry, most of them knowable twelve months ahead.
Why one page rather than reminders
Reminders tell one person about one thing at one moment. A calendar shows the collisions: the month where a holiday, a leave week and a pay date land together, which is the month that will go wrong.
Collisions are invisible in a list and obvious on a grid.
Who should be able to see it
At least one person other than whoever runs payroll. The entire point is that the schedule survives the absence of the person who knows it.
A calendar in somebody's personal diary is not this.
Marking what cannot move
The statutory dates, differently from your own. The distinction matters when something has to give, and in the week it has to give nobody has time to work out which is which.
The entry people forget
Funding. The day the money must actually be in the account, which is not the pay date and depends on the payment method.
It is the most commonly missing entry and the one whose absence is most visible to employees.
How far ahead
A full year. Doing six months means doing it twice and forgetting the second time.
When to make it
In a quiet month, not in a run week, and ideally just after year end when the new year's dates are known and nothing else is due.
What to do with the cut-offs
Tell people. A cut-off that only exists on the payroll calendar is a cut-off only one person is keeping, and the changes will keep arriving late from everybody else.
The version that is actually used
Shared, in whatever calendar the business already uses, with real entries rather than an attachment. A document nobody opens is not a control.
The annual review it enables
With a year on one page, the review described earlier in this collection takes ten minutes rather than an hour, because the collisions and the near misses are visible rather than remembered.
What it costs to maintain
Almost nothing once made. Dates change rarely; the maintenance is adding a leave week when somebody books one and moving a pay date when a holiday requires it.
Not a process document
A process document, a policy, or a substitute for the written sequence described later here. It is a calendar, and its whole value is that it is looked at rather than read.
The test of whether it works
Ask somebody other than the person who runs payroll when this month's cut-off is. If they can answer, the calendar is doing its job.
Why collisions are the whole point
A list of dates tells you each date exists. A grid tells you that the holiday, the leave week and the cut-off are in the same seven days.
The second is actionable and the first is not, and it is the only reason this is worth doing as a calendar rather than as a note.
Most businesses have all the information already, distributed across three places, and have never seen it on one page.
Marking the person as well as the date
Leave is usually recorded for everybody and read by nobody in the context of payroll. Putting the payroll person's leave on the same view as the pay dates takes seconds and is what surfaces the two months a year that need cover.
What it replaces
The monthly question of whether anything unusual is coming up, asked and answered from memory by somebody who has four other things in mind.
A calendar answers it by being looked at, which is a lower bar than being remembered.
The entry that gets added during the year
Known absences, as they are booked. It is the only part that needs maintaining, it takes ten seconds, and it is the part that makes the calendar useful rather than merely accurate.
The one line to take
Most payroll failures in small businesses are not errors of calculation. They are collisions nobody saw, in a month nobody looked at, on a schedule nobody else could see.