Timesheet approval

Timesheet approval is the check a manager makes on the hours employees recorded, against the schedule, before those hours go to payroll.

Written by: Rinaily BonifacioUpdated on:

In a normal week most timesheets are right and a few are not: a missed clock-out, a shift that ran late, a break nobody recorded. Approval is where those few get caught, before they become a wrong payment and a correction in the next pay run.

What is timesheet approval?

Timesheet approval is the process of reviewing and validating the work hours employees record on their timesheets, so they are accurate before payroll processing begins. The approver, usually the line manager or the shift lead, compares the recorded hours with the schedule and approves them, declines them or sends them back for a correction.

An approved timesheet is the version payroll works from. Until then the hours are pending: recorded, but not yet confirmed by anyone. In the US the same step is often called time card or timecard approval, and it works the same way.

The timesheet approval process, step by step

  1. Employees record their hours, by clocking in and out or by entering start, end and break times.

  2. Timesheets are submitted, or simply closed off, by an agreed deadline, such as Monday 10:00 for the previous week.

  3. The approver compares each day with the schedule and looks at the differences: late finishes, missing clock-outs, unrecorded breaks, hours on a day off.

  4. Each entry is approved, declined, or returned to the employee with a note on what needs fixing.

  5. The period is locked, so approved hours can no longer change unless someone with the right to do so reopens it.

  6. Approved hours go to payroll as an export or through a payroll integration.

Step 3 is where the time goes. A day that matches the schedule needs no thought, so the real work is in the exceptions. That is why many teams approve matching hours automatically and spend their attention on the rest.

Types of approval workflow

Workflow

How it works

Suits

Manager approval

The line manager or shift lead approves the hours of their own team

Most single-site teams

Two-step approval

The manager approves the shifts, then HR or payroll checks totals and pay codes before the export

Several sites or departments, or a separate payroll team

Automatic approval on a schedule match

Hours that match the scheduled start and end are approved without a click; anything else waits for a manager

Large teams with stable schedules

Employee confirmation first

The employee confirms their week, then the manager approves

Teams where staff enter hours by hand, for instance on a ready-made timesheet

Teams that still work on paper or in a spreadsheet can use the same steps with a timesheet template: one column for the scheduled hours, one for the recorded hours, and a sign-off per week.

What to check before you approve a timesheet

A normal day should take seconds to approve and an odd one about a minute. These are the differences worth stopping for:

  • Hours past the scheduled end. Was the late finish agreed? Extra time nobody asked for is unauthorised overtime, and approving it without a word makes it the norm.

  • A missing clock-out. The shift has a start and no end, so the total is either zero or whatever the system filled in.

  • Breaks. A break that was taken but not recorded inflates paid hours. One that was recorded but not taken can point to a shift that was short of staff.

  • Clock-ins well before the shift. Ten minutes early every day adds up across a team, and your rounding rule decides whether those minutes are paid.

  • Leave or sickness on a day with worked hours. One of the two entries is wrong.

  • Start or end times changed after the shift without a note. Most of these edits are innocent, and the same pattern is how time theft goes unnoticed.

A worked example: one week in a café

Sam works four day shifts in a café, each scheduled 09:00-17:00 with a 30-minute unpaid break. That is 7:30 hours a day and 30:00 hours for the week. At the end of the week the timesheet shows this:

Day

Recorded

Hours as recorded

What the manager does

Monday

09:00-17:00, 30-minute break

7:30

Matches the schedule, approved

Tuesday

09:00-18:10, 30-minute break

8:40

Sam stayed to cover a colleague who came in late. The shift lead confirms it, so 1:10 is approved as overtime

Wednesday

Clocked in at 09:00, no clock-out

open

Sam confirms leaving at 17:00. End time added, 7:30 approved

Thursday

09:00-17:00, no break recorded

8:00

The break was taken, so 30 minutes come off. 7:30 approved

Approved: 31:10 hours against 30:00 scheduled. Without the review, payroll would have paid Thursday's break, missed Wednesday or paid whatever the system filled in, and treated Tuesday's extra time as if nobody had decided on it. Three of the four days needed a decision. Each took under a minute because it was made in the same week, while everyone still remembered the shift.

Who approves timesheets?

The person who saw the shift approves it, which is usually the line manager or the shift lead on duty. They know whether the late finish was agreed and whether the break happened; payroll can only see the numbers. Where there is a second step, HR or payroll checks totals and pay codes across the team.

Two rules keep the process honest. Nobody approves their own hours, managers included: theirs go to their own manager or to HR. And every approver has a named deputy, so a holiday or a sick day doesn't leave a whole team's hours pending on payday.

What happens if a timesheet is not approved?

Unapproved hours stay pending. If payroll pays only approved hours, the pay for those shifts slips to the next run as a correction. If payroll pays from the schedule instead, the employee gets the planned hours and the difference is topped up or recovered later. Neither is what anyone expects on payday, and both take more admin than the approval would have. A fixed weekly deadline and a deputy prevent most of it, a point our guide to employee time tracking makes about approvals that land after the payroll cut-off.

Correcting a timesheet after approval

Mistakes still get through. While the period is open, reopen the entry, correct it with a note saying why, and approve it again. Once payroll has run, leave the approved period as it is and put the difference into the next pay period as a correction, so the record shows what was paid and when. Locking a period after approval is what makes that record reliable: hours that have already been paid can't be changed quietly afterwards.

Timesheet records and UK law

The Working Time Regulations 1998 require employers to keep records adequate to show they comply with the working time limits, and to keep them for two years from the date they were made (regulation 9). Since 1 January 2024 you don't have to record each worker's daily hours, as long as you can show compliance another way. National Minimum Wage records have a longer life: six years, counted from the end of the pay reference period they cover (National Minimum Wage Regulations 2015, regulation 59).

For most shift teams the simplest way to show compliance with the Working Time Regulations is the approved timesheet itself: the hours actually worked, confirmed by a manager while the week was still fresh, and kept long enough to cover the six-year minimum wage period as well.

Approving timesheets in Shiftbase

Time tracking in Shiftbase puts clocked hours next to the shifts in the schedule. You choose whether clocked time is approved always, only when the start and end match the schedule, or never without a manager. Anything that doesn't match stays pending for review. Hours are approved, declined or set back to pending one at a time or for the whole view, and closing a day stops anyone changing hours after that date.

Approved hours feed Reports, where you export the totals or the detail per employee for payroll. Scheduling, time tracking and absence management run in the same Shiftbase account, so the hours you approve and the leave you record come from one place. Try Shiftbase free for 14 days with your own team's timesheets.

Frequently asked questions

An approved timesheet is a timesheet whose hours a manager has checked and confirmed, which makes it the version payroll pays from. Until a timesheet is approved, its hours are pending and can still change.

Managers should approve timesheets at least once per pay period, before the payroll cut-off, and a weekly review works better even on monthly payroll. A shift from last week is still easy to check with the people who worked it; a shift from four weeks ago is a guess.

Employees should not approve their own timesheets. They can confirm their hours before submitting them, but the approval comes from someone else. That applies to managers too: a manager's own hours go to their manager or to HR.

Timesheets as such are not a legal requirement in the UK, but working time records are. Employers must keep records that show they comply with the Working Time Regulations for two years, and National Minimum Wage records for six years. An approved timesheet is the most common way to keep both.

Overtime hours are best approved as a separate decision from the regular hours on a timesheet, because overtime often has its own rate and its own budget. Agreeing extra hours before the shift and approving the recorded hours afterwards keeps the two apart, and makes overtime nobody asked for visible instead of quietly paid.

Timesheets can be approved automatically when the recorded hours match the schedule, which is a common setting in employee time tracking software. Hours that don't match still wait for a manager, so automatic approval saves the clicks on normal days without skipping the review of the odd ones.

Rinaily Bonifacio
Rinaily BonifacioSenior Content Marketer

Rinaily writes for Shiftbase about HR, scheduling and building teams people actually want to work in. She turns the messy reality of workforce planning into practical advice you can put to work today.

See all terms