# The timesheet exception register for a weekly payroll run

Most timesheets are routine. A few need someone to decide. This register counts those few and sorts them by reason, so you know what is left after automation.

Updated 7 November 2026 . 7 min read . Alexey Shurov

## The short answer

Before anyone automates timesheets into payroll, count the ones that need a person to decide. Log each one in a register, give it a category from a fixed list, and name who settles it. After a few weeks you can see how many timesheets are routine, and which reasons keep coming back.

A routine timesheet can be checked by rules. An exception cannot. A missing day, an overlap or an unapproved overtime claim needs someone who knows the facts. This register makes that work visible, so it is planned and not a surprise on payroll day.

## Which timesheets need a person, in two minutes

In under three minutes you will know how to count the timesheets that need a person, what to log for each one, and what to fix first.

Every example in the video is made up to show the method.The words of the video

Do some timesheets hold up your weekly payroll run? Before you automate anything, give me three minutes. I'll show you a simple register that counts the ones needing a person, and why.

First, what is it? A timesheet looks wrong, so you log it in one row. You give it a reason from a fixed list. Then you name who decides, and note when it clears.

Here's what I've learned. Most timesheets are routine, and a rule can check them. But a missing day or an overlap needs someone who knows the facts. So count those few, and payroll day stops being a surprise.

Here's a made up example. Worker A's sheet is missing, and the line manager clears it in under two hours. Worker C's overtime has no sign off, so it waits until Tuesday.

Here's a made up month for one team. Out of fifty two timesheets, forty six were routine. Six needed a person, and most cleared within a morning. Automation would remove the routine checking and leave that short list.

So here's the register. Each odd timesheet gets one row. Give it a category from a fixed list, and name who decides. Then note the outcome, and when it was logged and cleared.

If one category dominates, look at its cause. In my experience, many missing sheets point at how sheets are collected. A rule cannot cope with bad input, so fix that first.

One more thing I always check. If rows wait a long time, the decider is usually unavailable. I'd ask who covers each decider when they're away.

So that's the register. A few weeks show how many sheets are routine, and which reasons keep coming back. Then you know what to fix first, and what a person keeps.

The register, the category list and made up sample rows are free on shurco.ai. Keep it for four weekly runs.

### 1. Log every exception once, when you find it

Use one row for each timesheet that cannot go through as submitted. Write who it belongs to, when you found it and what looked wrong. Do this during the check, not on Friday from memory.

### 2. Give each row one category

Pick from the category sheet below. One row gets one main category. If two things are wrong, log the one that stops payment first. A fixed list can be counted. Free text cannot.

### 3. Name who decides

For each category, write down who has the answer. A line manager knows if overtime was agreed. The payroll lead knows the pay code rules. A row with no named decider is a gap in your process, and the register shows it.

### 4. Record the outcome and when it cleared

Write what was decided, such as corrected, approved as submitted, held or sent back. Add the day and time it cleared. The gap between logged and cleared shows which categories hold up the run.

### 5. Count at the end of each run

Count the timesheets received and the rows in the register. Then count rows by category. Do this for four weeks. The top two categories show where the manual work really sits.

## The blank register

One row per exception, filled in during the weekly check. Keep it with the timesheets.

| Entry ref | Worker | Logged (day, time) | Category | What looks wrong | Who decides | Outcome | Cleared (day, time) |
|---|---|---|---|---|---|---|---|
|  |  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |  |

[Download this sheet as a file for Excel](data:text/csv;charset=utf-8,%EF%BB%BFEntry%20ref%2CWorker%2C%22Logged%20%28day%2C%20time%29%22%2CCategory%2CWhat%20looks%20wrong%2CWho%20decides%2COutcome%2C%22Cleared%20%28day%2C%20time%29%22%0D%0A%2C%2C%2C%2C%2C%2C%2C%0D%0A%2C%2C%2C%2C%2C%2C%2C%0D%0A%2C%2C%2C%2C%2C%2C%2C%0D%0A%2C%2C%2C%2C%2C%2C%2C%0D%0A)

## The categories

A starting list. Change the names to suit your firm, then keep them fixed for the whole trial.

| Category | What it looks like | Who usually decides | Can a rule settle it |
|---|---|---|---|
| Missing timesheet | No sheet by the cut off | Line manager | Only to flag it |
| Impossible times | Overlapping shifts or a day over 24 hours | Worker and line manager | Only to flag it |
| Unapproved overtime | Hours above contract with no sign off | Line manager | Partly |
| Missing break | Long shift with no break recorded | Payroll lead | Partly |
| Wrong job code | Code not on the current job list | Line manager | Partly |
| Leave clash | Hours worked on a day of booked leave | Line manager | Only to flag it |
| Pay rate query | Shift type does not match the rate | Payroll lead | No |
| Late submission | Arrives after the cut off | Payroll lead | No |
| Other | Anything not listed above | Payroll lead | No |

[Download this sheet as a file for Excel](data:text/csv;charset=utf-8,%EF%BB%BFCategory%2CWhat%20it%20looks%20like%2CWho%20usually%20decides%2CCan%20a%20rule%20settle%20it%0D%0AMissing%20timesheet%2CNo%20sheet%20by%20the%20cut%20off%2CLine%20manager%2COnly%20to%20flag%20it%0D%0AImpossible%20times%2COverlapping%20shifts%20or%20a%20day%20over%2024%20hours%2CWorker%20and%20line%20manager%2COnly%20to%20flag%20it%0D%0AUnapproved%20overtime%2CHours%20above%20contract%20with%20no%20sign%20off%2CLine%20manager%2CPartly%0D%0AMissing%20break%2CLong%20shift%20with%20no%20break%20recorded%2CPayroll%20lead%2CPartly%0D%0AWrong%20job%20code%2CCode%20not%20on%20the%20current%20job%20list%2CLine%20manager%2CPartly%0D%0ALeave%20clash%2CHours%20worked%20on%20a%20day%20of%20booked%20leave%2CLine%20manager%2COnly%20to%20flag%20it%0D%0APay%20rate%20query%2CShift%20type%20does%20not%20match%20the%20rate%2CPayroll%20lead%2CNo%0D%0ALate%20submission%2CArrives%20after%20the%20cut%20off%2CPayroll%20lead%2CNo%0D%0AOther%2CAnything%20not%20listed%20above%2CPayroll%20lead%2CNo%0D%0A)

## Labelled sample rows

**Made up example.** Every row here is made up to show the method. Worker A and the others are not real people.

| Entry ref | Worker | Logged (day, time) | Category | What looks wrong | Who decides | Outcome | Cleared (day, time) |
|---|---|---|---|---|---|---|---|
| TX-01 | Worker A | Mon 09.30 | Missing timesheet | Nothing received for the week | Line manager | Sheet supplied and corrected | Mon 11.15 |
| TX-02 | Worker B | Mon 09.42 | Impossible times | Two shifts overlap on Wednesday | Line manager | Second shift removed | Mon 10.20 |
| TX-03 | Worker C | Mon 10.05 | Unapproved overtime | 6 hours above contract, no sign off | Line manager | Approved as submitted | Tue 08.50 |
| TX-04 | Worker D | Mon 10.30 | Wrong job code | Code J-77 is not on the job list | Line manager | Changed to J-71 | Mon 13.00 |
| TX-05 | Worker E | Mon 11.10 | Leave clash | Hours on a booked leave day | Line manager | Held | Tue 09.30 |
| TX-06 | Worker F | Mon 14.25 | Pay rate query | Night shift paid at day rate | Payroll lead | Rate corrected | Mon 15.40 |

[Download this sheet as a file for Excel](data:text/csv;charset=utf-8,%EF%BB%BFEntry%20ref%2CWorker%2C%22Logged%20%28day%2C%20time%29%22%2CCategory%2CWhat%20looks%20wrong%2CWho%20decides%2COutcome%2C%22Cleared%20%28day%2C%20time%29%22%0D%0ATX-01%2CWorker%20A%2CMon%2009.30%2CMissing%20timesheet%2CNothing%20received%20for%20the%20week%2CLine%20manager%2CSheet%20supplied%20and%20corrected%2CMon%2011.15%0D%0ATX-02%2CWorker%20B%2CMon%2009.42%2CImpossible%20times%2CTwo%20shifts%20overlap%20on%20Wednesday%2CLine%20manager%2CSecond%20shift%20removed%2CMon%2010.20%0D%0ATX-03%2CWorker%20C%2CMon%2010.05%2CUnapproved%20overtime%2C%226%20hours%20above%20contract%2C%20no%20sign%20off%22%2CLine%20manager%2CApproved%20as%20submitted%2CTue%2008.50%0D%0ATX-04%2CWorker%20D%2CMon%2010.30%2CWrong%20job%20code%2CCode%20J-77%20is%20not%20on%20the%20job%20list%2CLine%20manager%2CChanged%20to%20J-71%2CMon%2013.00%0D%0ATX-05%2CWorker%20E%2CMon%2011.10%2CLeave%20clash%2CHours%20on%20a%20booked%20leave%20day%2CLine%20manager%2CHeld%2CTue%2009.30%0D%0ATX-06%2CWorker%20F%2CMon%2014.25%2CPay%20rate%20query%2CNight%20shift%20paid%20at%20day%20rate%2CPayroll%20lead%2CRate%20corrected%2CMon%2015.40%0D%0A)

## How to read the register

If exceptions are a small share of timesheets and most clear within an hour, the manual part is light. Automation would remove the routine checking and leave a short list for a person.

If one category dominates, look at its cause. Many missing sheets point at how sheets are collected. Many wrong job codes point at an out of date job list. Fix those first, because a rule cannot cope with bad input.

If rows wait a long time to clear, the delay is usually the decider being unavailable. Name cover for each decider.

## What can change the answer

A bank holiday week, a new starter group or a change of pay rules will give a different mix. Note these weeks and look at them apart from the rest.

A very large site or team can hide small problems in the totals. Add a column for site or team if your firm has more than one.

## When this is the wrong tool

If timesheets are already entered once in a system that checks them as they go, there is little to log. Look at the rows that still reach payroll by hand.

The register counts the exceptions. It does not settle disputes about pay, and it does not replace a judgement about a person's circumstances. Those stay with a manager and the payroll lead.

## What the counts tell you

| Count | How to work it out | What it tells you |
|---|---|---|
| Exception rate | Rows in the register divided by timesheets received | How much of the run needs a person |
| Top two categories | Count rows by category and rank them | Where the manual work sits |
| Time to clear | Cleared time minus logged time, by category | Which reasons hold up the run |
| Rows with no decider | Rows where the Who decides box stayed empty | Gaps in who owns the answer |

## What to do with the result

Take the exception rate, the top two categories and the clearing times to whoever would build or buy the automation. Ask how they would handle each top category, and what they would send to a person.

For a view of which task to automate first, the tool on this site takes the same facts and gives a plain answer.[

Client result . Staffing

10 → 2

About 80 percent less manual work on the weekly run

People needed on the weekly payroll run, client-confirmed.

Read how the system works](https://shurco.ai/solutions/timesheet-to-payroll-automation/)

## Common questions

### How many weeks should I keep the register?

Four weekly runs is a sensible start. It shows the usual mix and one or two odd weeks. Keep going if the categories keep changing.

### What counts as a timesheet exception?

Any timesheet that cannot go to payroll as submitted without someone checking or deciding something. Routine sheets that pass every check are not logged.

### Does the register need any software?

No. A shared spreadsheet or a printed sheet is enough. The value is in logging each case when you find it.

### What if the register shows few exceptions?

Then the manual work is small. Automation may still remove the routine checking, but the gain will be modest, so weigh it against the effort.

## Useful next[Free toolWhat to automate first, a scoring toolPick a task your team repeats every week and answer five quick questions. You get a plain answer on whether it is worth automating, what helps and what to watch. Score up to four tasks and it tells you where to start, and you can keep the result as a private plan page.](https://shurco.ai/tools/what-to-automate-first/)[PlaybookHow to build a business case for AI automationA finance director does not approve AI. They approve a measured task, an honest cost and a way to tell whether it worked. Here is the one page that gets a yes, and the numbers to put on it.](https://shurco.ai/guides/business-case-for-ai-automation/)[Free toolAI automation ROI calculatorPut in the hours a task takes, what an hour costs and what the system would cost to build and run. It shows the hours returned to the team and how long the automation takes to pay for itself.](https://shurco.ai/tools/ai-automation-roi-calculator/)

## More guides[WorksheetThe incident worksheet for an agent that keeps repeating an actionWhen an agent repeats the same action instead of stopping, you need three things before you fix anything. A trace of what it did, a clear statement of when it should have stopped, and a test case you can run again after the fix.](https://shurco.ai/guides/agent-loop-incident-worksheet/)[GuideAI agent pricing in 2026, what vendors actually chargeVendors now charge for agents by the conversation, the outcome, the action or the credit. Here are the published prices, what each unit really means, and how to compare them on your own workload.](https://shurco.ai/guides/ai-agent-pricing/)[ServiceA monthly test for your customer facing AI assistantOnce a month, I ask your website or phone assistant ordinary customer questions. You get what it got wrong, its exact words and what to change. The first test is free.](https://shurco.ai/guides/ai-assistant-monthly-test/)[PlaybookHow to automate daily site reports across many sitesThe report takes days because the data lives in many places and someone has to chase it. Here is how to gather it in parallel, catch the numbers that disagree and produce a report a manager can check.](https://shurco.ai/guides/automate-daily-site-reports/)[PlaybookHow to automate quoting for a manufacturer or distributorSlow quotes lose work. There are three quite different kinds of quoting automation, and most buying mistakes come from picking the wrong kind. Here is how to tell which one your quotes need.](https://shurco.ai/guides/automate-quoting-for-manufacturers/)[PlaybookHow to automate sales order entry in Business CentralCustomers email orders as PDFs, spreadsheets and free text, and someone keys each line into Business Central. Here are the three ways to take that work away, with what Microsoft's own agent does and where it stops.](https://shurco.ai/guides/automate-sales-order-entry-business-central/)

## Check your own timesheets in two minutes

Five questions about how the work reaches you and how it is checked. You get a plain answer on whether it is worth automating, with no sign up. [Start with question one.](https://shurco.ai/tools/what-to-automate-first/?k=timesheets) Or [tell me about the work](https://shurco.ai/#contact) and I will reply myself.

Web version https://shurco.ai/guides/timesheet-exception-register/