Writing Down Where the Day Starts
One page per site, listing what happens at the edge and whether it is inside the paid day. Producing it is where the decisions actually get made.
The page, for one site
| What happens | Required by | Paid? |
|---|---|---|
| Walk from the gate to the terminal | Site layout | Not paid |
| Collecting a radio and keys | Operations procedure | Paid |
| Changing into branded uniform | Written dress rule | Paid |
| Security search on entry | Site security policy | Paid |
| Personal preparation and coffee | Nobody | Not paid |
Five lines, one afternoon, and the site has a position it can defend. Three of the five changed from what the handbook said.
Most organisations have a policy about clocking and no document at all about the boundary. The policy says when to clock and what happens if you are late. It does not say which activities are inside the paid day, which is the question everything turns on.
The practical lesson in “Writing Down Where the Day Starts” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring download time tracking software, Monitask resources for download time tracking software can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
The missing document is one page per site. It takes an afternoon, it settles a class of disputes permanently, and the act of producing it is where the organisation finds out what it has been doing.
For a separate benchmark relevant to “Writing Down Where the Day Starts”, consult the UKRI award-management guidance. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.
What goes on the page
Each activity that happens between arriving and starting work, and between finishing and leaving. Observed rather than imagined — somebody stands at the gate for a morning and writes down what people do.
How long each takes, timed rather than estimated. The estimates are always shorter than the measurements, in both directions and for both parties.
Who requires it, and where that requirement is written. A procedure, a dress code, a security policy, an instruction from a supervisor, or nothing.
Whether it is inside the paid day, and what makes that so: the clock's position, the shift pattern, an allowance, or a decision recorded on this page.
Producing it
Walk the site first. The office version of this exercise produces a list of four things and the gate version produces eleven, and the seven that only appear at the gate are the interesting ones.
Time them on an ordinary morning rather than a quiet one. Shift change is the condition that matters and it is the condition under which nothing gets measured, because everybody is busy.
Ask the people doing it. They will tell you about the step nobody in management knows exists — the second door that is locked until seven, the kit store with one person serving twenty, the machine that has to be started before anything else can happen.
Deciding the contested lines
The list will have two or three items that nobody can classify, and they will be the longest ones. That is normal and it is the output of the exercise rather than a failure of it.
Resolve them by decision rather than by omission. Each contested item has exactly three honest outcomes: it is required and therefore paid, it is genuinely optional and the organisation will behave accordingly, or it is required and the shift pattern changes so that it falls inside the paid day.
What is not available is leaving it undecided, because an undecided item is being decided every day by default in the employer's favour, and that default is what accumulates into a liability.
Who signs it
Somebody with authority over both the site and the pay arrangements, which is usually not the same person as the one who runs the clock.
The signature matters because the page is an employment document in substance. It describes what is paid for, and in a dispute it will be read as the organisation's position. A page produced by a facilities manager with no authority to commit to pay is a useful inventory and not a position.
Keeping it alive
It changes whenever the site changes: a new entrance, a relocated changing room, a different uniform rule, a terminal moved during a refurbishment, a new security procedure.
Attach it to the change process for those things rather than reviewing it on a calendar. The failure case is a site that moved the terminal during a refit in March and is still operating on a boundary document written for the old layout.
An annual confirmation that nothing has changed takes five minutes and gives the page a date, which is what makes it useful three years later.
What having it changes
Disputes shorten from months to an afternoon, because there is a document that predates the dispute and says what was agreed.
Inspections become routine rather than exploratory, because the first thing an inspector asks is what counts as working time here, and the page is the answer.
And the organisation stops carrying an unquantified liability, which is worth more than either.
The shortest useful version
If an afternoon is not available, there is a version that takes twenty minutes and is worth most of it: list the activities, mark each required or not, and write the date.
No timings, no signatures, no basis column. It will not settle a dispute on its own and it does establish that somebody thought about the question on a particular date, which is more than most sites have. The fuller version can follow; the twenty-minute one stops the position being purely retrospective, and that is the main thing it is for.