Chasing the Hours
Collecting hours is the largest single piece of work in a small payroll and the one most easily reduced. Most of the fix is in the format.
Nobody elseif the person who does this is away
Collecting hours is the largest single piece of work in a small payroll — commonly half the total time — and the one most easily reduced. Most of the reduction comes from fixing the format rather than from chasing harder.
The input problem described in “Chasing the Hours” is easier to manage when hours and changes have a visible owner. A team evaluating inspect the linked workflow resource for employee screen monitoring software can connect employee-controlled time records with projects and approvals, while the payroll system remains the source of truth for pay calculations.
The target is not punctuality. It is that nothing has to be interpreted.
Additional context for “Chasing the Hours” is available from Fair Work pay guidance. A sound review distinguishes general practice from the rules and records that apply to one employer.
Why it takes so long
Not because people are late, though some are. Because what arrives needs work: a photograph of a handwritten sheet, a message saying "same as last week except Tuesday", a spreadsheet with its own column order, a verbal total.
| What arrives | What it costs to use |
|---|---|
| A shared sheet, totalled and checked | Nothing; it is read |
| A spreadsheet in its own column order | Reading and reordering |
| A photograph of a handwritten sheet | Transcription and a guess |
| "Same as last week except Tuesday" | A reconstruction |
Each needs reading, interpreting and transcribing, and each carries a chance of error.
The cost of four formats
A business taking hours four ways is doing four different jobs and reconciling the results. Standardising on one is worth more than any amount of reminding.
What a usable format has
The person, the dates, the hours per day, anything unusual flagged, and a total the sender has checked.
That is a small ask and it moves the checking back to the person who knows what actually happened.
Who should total it
Whoever worked the hours or supervised them. A total arriving unchecked means the payroll person is reconstructing somebody else's week from a grid.
The approval step
Somebody other than the person who worked the hours confirming they are right, before they reach payroll.
In a very small business this is the owner glancing at them, which takes a minute and catches most of what goes wrong.
Exceptions are the whole job
Ordinary weeks need no attention. What needs attention is the unusual: a half day, an absence, extra hours, a shift covered for somebody else.
Asking people to flag exceptions explicitly, rather than leaving them to be inferred from a grid of numbers, removes most of the interpretation.
"Same as last month"
Workable for salaried staff and dangerous for hourly ones. It is a statement about intention rather than about what happened, and it is how a week of absence reaches a payslip as a full week of pay.
Nil returns
Worth asking for. A manager who sends nothing is indistinguishable from a manager with nothing to send, and the difference is a day of chasing.
"Nothing to report" as an explicit reply removes an entire category of uncertainty.
Chasing well
One message, two days before the cut-off, to the specific people, naming what is outstanding. Not a general reminder to everybody, which the people who have already sent theirs will read and the people who have not will not.
When the hours never come
Run what you have and correct afterwards, having told the person affected. Holding the whole run for one missing timesheet puts everybody's payment at risk for one person's paperwork.
The record of what you used
Keep what arrived, as it arrived, against the period. When somebody queries a payslip four months later, the question is almost always about hours, and the answer is almost always in what was sent.
The improvement worth making first
One format, one place it is sent, one deadline, and exceptions flagged explicitly.
That combination typically halves the time spent on this, and it costs one conversation rather than any money.
The sheet that does most of the work
One shared sheet, one row per person, one column per day, a column for exceptions and a total that calculates itself.
Filled in by whoever supervises, checked by them, and available to you on the cut-off without anybody sending anything.
It removes the transmission step entirely, which is where a surprising amount of the delay lives: the hours existed on the 14th and reached you on the 17th because somebody had to remember to send them.
What to do about photographs of paper
Common, and worse than it looks: unreadable totals, missing days, ambiguous handwriting, and no way to query anything without going back to the person.
Where paper is genuinely necessary, the useful compromise is paper that is totalled and signed by a supervisor, then transcribed once by them rather than by you.
Transcription by the person who was there is a different activity from transcription by the person who was not.
Keeping the exceptions visible
A month of ordinary hours needs no attention at all. Building the format so that exceptions stand out — a separate column, a flag, a note — means the person entering can skim the ordinary and read the unusual.
That is the difference between twenty minutes of entry and an hour of reading.
The system you do not need
Build a system. A business of fourteen people does not need a time and attendance deployment to fix this; it needs a shared sheet with the right columns and an agreement about when it is filled in.