The List You Actually Work From
Every run is built from six inputs. In most small businesses four of them live in conversations, which is why the run is rebuilt from memory each month.
Nobody elseif the person who does this is away
What has to be in one place before a run can start
Whoever supervises
Two peopleIf they are away: Reconstructed from messages, badly
Whoever agreed them
Nobody elseIf they are away: They reach the run if one person remembers
Whoever hired
Nobody elseIf they are away: Somebody works a month unpaid
Whoever was told
Nobody elseIf they are away: A person is paid after leaving, and it is recovered awkwardly
Whoever approved it
Nobody elseIf they are away: Full pay for a week that was unpaid leave
The employee
Two peopleIf they are away: A payment to a closed account
4 of 6 tasks have nobody else who can do it.
Six inputs, and four of them exist only in somebody's recollection. One small employer's own arrangement, not a model for anybody.
A payroll run is built from six inputs: hours, changes, starters, leavers, absence and bank details. In most small businesses four of those live in conversations rather than anywhere findable.
The practical lesson in “The List You Actually Work From” is that payroll depends on a sequence somebody can explain. When a small team reviews open the product information here for how Monitask works, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.
The run is therefore reconstructed each month from recollection, which works until the month it does not.
For an outside reference relevant to “The List You Actually Work From”, consult Citizens Information pay resources. Compare general guidance with the employer’s jurisdiction, contracts and current payroll process.
Why one list and not six systems
Because a business of this size will maintain one dull shared document and will not maintain six processes. Anything requiring more effort than typing a line will be skipped in the week it matters.
What it looks like
A sheet with a tab or a block per period. Date, person, what, from when, who said so.
No approvals, no workflow, no owner other than whoever is writing. The moment it acquires structure it stops being filled in.
Who writes on it
Anybody who can cause a payroll event: whoever hires, whoever agrees a rate, whoever approves a day off, whoever is told about a resignation.
If only the payroll person can write on it, it only records what the payroll person already knows, which defeats it.
When it gets written
In the conversation. The entire mechanism rests on the line being added while the thing is being agreed, rather than afterwards when intentions compete with the rest of the day.
Read against what you are keying
Start to finish, against what you are about to key. Three minutes, and it is the only step that catches something agreed three weeks ago by somebody now on holiday.
The forward section
Changes effective later: a rise from next quarter, a drop in hours from the new term. These are lost most reliably of all, because they are agreed now and are not due yet.
A dated line, read each month, handles them.
What the list replaces
Four conversations at the cut-off asking whether anything has changed. Those conversations produce the answer "I don't think so" from people who are busy, which is not the same as nothing having changed.
What it is evidence of
What was agreed and when. A dated line written by the person who agreed it is a considerably better record than two people's memory of a conversation, and it is occasionally the only record there is.
The weekly version
For a weekly payroll the same list, read weekly. The volume is lower per period and the forgetting is just as common.
Keeping it after the run
Do not clear it. The period's lines stay, closed, as the record of what that run was built from.
When somebody queries a payslip in four months, this is where the answer is.
Where it should live
Wherever the business already keeps shared documents, reachable by more than one person, and not inside the payroll software.
Reachable by more than one person is the part that matters for everything in the last section of this collection.
The failure mode
It stops being written on, quietly, over about two months, and nobody notices until a run is wrong.
The signal is the payroll person asking people what changed, which is the thing the list was supposed to replace.
How to restart it
Not with a reminder about process. With one month of adding every change yourself, at the moment, visibly, so the habit has an example.
Ten seconds and three minutes
Ten seconds per line and three minutes a month to read. Against which it addresses the single largest category of small-business payroll error.
What it is not allowed to become
A form with required fields. A workflow with approvals. A system with a login. A thing somebody owns.
Every one of those has been tried in small businesses and every one of them kills it, because the entire mechanism depends on a line taking ten seconds to add in the middle of a conversation about something else.
The version for a business that already has tools
If the business runs on a messaging platform, a single channel works as well as a sheet, provided somebody transfers the lines into the period record before the run.
The requirement is not the medium. It is that there is exactly one place, that everybody knows which it is, and that it is read before each run.
Who reads it besides you
A deputy running a payroll in your absence has no other way of knowing what happened that month. The list is the single document that makes cover possible at all, because the sequence tells them how and the list tells them what.
That is a second reason to keep it somewhere more than one person can reach, and it is the reason that matters most in the week it is needed.
The one sentence
Payroll accuracy is a recording problem that happens outside payroll, and the recording has to be done by the people the events happen to.