Time Tracking

How to Track Employee Overtime Accurately

Most overtime errors are not maths errors. They start earlier, when a missed clock-out, an unrecorded lunch break or a verbal “can you stay late?” turns into a number nobody can check. This guide shows how to track employee overtime from the attendance record itself, so the hours you pay are the hours that were worked and agreed.

  • 13 min read
  • 2,568 words
ShareTelegramXLinkedIn
A warehouse worker in an orange hi-vis vest taping a parcel in the evening, seen through an office window, with a colour-coded weekly roster on the desk in frontTime Tracking

What is employee overtime tracking?

Employee overtime tracking is the process of recording the hours an employee works beyond their scheduled or legally defined working time, getting those hours approved, and passing them to payroll with enough evidence to explain every number.

It rests on three different quantities that are easy to mix up. Scheduled time is what the roster planned. Worked time is what the attendance record shows, after unpaid breaks are removed. Approved overtime is the part of the difference that a manager has agreed to pay as overtime. Accurate overtime tracking keeps all three visible instead of collapsing them into one figure on a timesheet.

A note on the law: overtime rules are set by each country, and sometimes by state, sector or collective agreement. The daily or weekly threshold, the pay rate, who is exempt, whether overtime can be refused and whether time off can replace payment all vary. This guide covers how to keep accurate overtime records. It is not legal advice, and every employer should follow the labour law that applies where their people work.

Extra time is not automatically overtime

The single most useful rule for overtime tracking is to separate extra time from overtime. Extra time is a measurement: the attendance record shows someone was on the clock longer than their shift. Overtime is a decision: someone with authority agreed that the work was needed and should be paid at the overtime rate.

Why the distinction matters: an employee who Slides Out twelve minutes late because the car park was full has extra time but did no extra work. An employee asked to stay ninety minutes to receive a delivery did. If payroll pays every extra minute automatically, rounding noise and forgotten clock-outs become wages. If payroll ignores extra minutes entirely, real unpaid work goes unnoticed, which in many countries is a legal risk rather than a saving.

Here is how the three numbers look for one realistic day.

Worked example. Maya is scheduled 09:00–17:00 with a 60-minute unpaid lunch. Her manager asks her to stay for a late delivery. Figures are illustrative.
MeasureHow it is foundResult
Scheduled time8 hours on the roster minus the 60-minute unpaid lunch7h 00m
Recorded spanSlide In 08:52, Slide Out 18:409h 48m
Worked timeRecorded span minus the unpaid lunch8h 48m
Extra timeWorked time minus scheduled time1h 48m
Overtime requestedMaya asks for the delivery time, 17:00–18:30, with a reason1h 30m
Overtime approvedManager confirms the delivery work and approves the request1h 30m

Why attendance and overtime records must be connected

When overtime lives in a different place from attendance, payroll becomes a reconciliation job. The clock-in times are in one system, the “please stay late” message is in a chat, and the employee’s own note is on paper. On pay day someone has to decide which of the three is true.

Connecting them means an overtime request always points at a real working day with real attendance behind it. A reviewer can see the scheduled shift, the actual Slide In and Slide Out times, the breaks deducted and the extra time before deciding. If a request asks for two hours but the record shows forty minutes of extra time, the mismatch is visible before anyone is paid, not after.

It also protects employees. When worked time is recorded independently of the approval, a manager cannot quietly make extra work disappear by never approving it; the extra time is still on the record for the business to review and, where the law requires, to pay.

Common ways businesses track overtime, compared

Most businesses move through the same methods as they grow. Each one fails in a predictable place, and knowing where helps you decide when it is time to change. If your team still runs attendance in a spreadsheet, our guide to tracking attendance without spreadsheets covers the migration itself.

How common overtime tracking methods compare on the questions payroll actually asks.
MethodWhere the hours come fromWhere approval livesWhere it breaks
Paper timesheetsEmployee writes times from memorySignature at the end of the weekTimes are rounded or reconstructed; no link to the schedule
Shared spreadsheetTyped in by a manager or employeeA column or a commentFormulas get overwritten; no record of who changed a cell
Chat messagesWhatever was said in the threadA “yes, stay” messageApprovals are hard to find and never match the hours
Wall time clockPunch or fingerprint at the doorSeparate paper formHours are captured, but approval and reasons are not
Attendance app with approvalsTimestamped Slide In and Slide OutA request on the same working dayOnly as good as the schedule and the review habit behind it

What is the best way to track overtime? A seven-step method

The best way to track overtime is to capture worked time automatically from attendance, compare it with a schedule that includes unpaid breaks, and require an approved request before any extra time is paid as overtime. The steps below work with any tool, although software removes most of the manual effort.

  • Step 1: Write down your overtime rules. Record the daily or weekly threshold, the rates and any approval requirement that applies to your location, and who counts as eligible. Put them in your attendance policy so employees know them too.
  • Step 2: Give every employee a schedule. Overtime is measured against something. Set start and end times per weekday, rest days and unpaid break windows, so “extra” has a clear baseline.
  • Step 3: Record start and finish times with a trusted timestamp. Times taken from a server, not typed by hand or read from a phone clock that can be changed, remove the most common source of disputes.
  • Step 4: Calculate extra time per working day. Worked time minus unpaid breaks minus scheduled time. Keep late starts and early departures as their own figures rather than silently netting them off.
  • Step 5: Require a request with a reason. The employee, or the manager on their behalf, names the date, the hours and why. A reason turns a number into something a reviewer can check.
  • Step 6: Approve against the record. The reviewer compares the request with the attendance for that day and may approve fewer hours than were asked for. Nobody approves their own overtime.
  • Step 7: Close the period before payroll. Resolve missing clock-outs and pending requests first, then hand payroll the approved hours and rates, with the attendance behind them.

Schedule vs actual worked hours: early starts, late starts and grace periods

Comparing the schedule with actual hours surfaces four situations: arriving early, arriving late, leaving early and leaving late. Only one of them, staying late for work, is the classic overtime case, but all four affect the total.

Grace periods decide how much of this counts. A grace period of five or ten minutes around the start and end of a shift stops normal variation, such as a queue at the entrance, from being recorded as lateness or extra time. Choose grace periods deliberately and apply them to everyone; an unwritten grace period that one supervisor honours and another does not is how disputes begin.

Early arrivals deserve a clear rule. Many employees arrive fifteen minutes early to change or take a handover. Decide whether that time is work. If they are expected to be working, it is worked time, and in many jurisdictions it must be paid whether or not anyone approved it. If they are simply early, the schedule, not the arrival time, should set the start of paid time, and your policy should say so.

Late starts should not be quietly offset against overtime later in the week unless your local rules and your written policy allow it. Record both: 12 minutes late on Tuesday and 90 minutes of approved overtime on Thursday are two facts a manager may need to discuss separately.

Missed clock-outs, forgotten breaks and overnight shifts

Three exceptions cause most overtime errors. Handle each with a rule rather than a guess.

  • Missed clock-out: if an employee forgets to Slide Out, the day has a start but no finish. A careless system either shows a 20-hour shift or drops the day. The right behaviour is to flag the day as missing a clock-out, count no extra time from it, and fix it through a correction that keeps the original record next to the change.
  • Unrecorded breaks: if a 60-minute unpaid lunch is not deducted, every full day shows an hour of false extra time. Scheduled break windows, including more than one break per shift, keep this consistent without asking employees to clock out for lunch.
  • Overnight shifts: a shift from 22:00 to 06:00 belongs to one working day, the day it started. If a system splits it at midnight, each half can look short on one date and long on the next, creating phantom lateness and phantom overtime. Our guide to attendance management for shift workers explains this in detail.
  • Reminders help prevent all three. A reminder before a shift ends, planned from the roster rather than the phone clock, catches many missed clock-outs before they happen.

Building an overtime approval workflow that holds up

An approval workflow answers three questions: who can approve, when approval happens, and what the approver can change.

Who: the employee’s manager or supervisor, never the employee themselves. This includes branch managers, who manage a team that includes themselves. When a manager needs overtime, someone else decides it.

When: pre-approval is cleaner for planned overtime, such as an inventory count on Saturday. Post-approval is unavoidable for the unplanned kind, such as a late delivery. A good workflow allows both but always ties the request to a specific working day.

What: the approver decides the outcome, the approved hours and, where your payroll uses it, the rate. The approver should be able to approve fewer hours than were requested, but not rewrite what the employee originally asked for. The request, the decision, who made it and when should stay on record.

Which overtime records should you keep?

If an employee, an accountant or a labour inspector asks how an overtime payment was calculated, you should be able to answer from records rather than recollection. Retention periods are set by local law, so check how long yours must be kept. At minimum, keep for each overtime day:

  • The schedule that applied that day, including break windows
  • The original start and finish times, with how they were recorded
  • Any correction, with its reason and approver, stored alongside the original rather than replacing it
  • The overtime request: date, hours requested and reason
  • The decision: approved or declined, hours approved, rate applied, reviewer and time of decision
  • The pay period in which the overtime was paid

Preparing payroll: an overtime checklist for the end of each period

Run this checklist before hours leave your attendance system. It takes minutes when records are clean and saves hours of rework when they are not.

  • No working day in the period is still missing a clock-out
  • No overtime request is still pending
  • Every approved request matches extra time on the attendance record for that day
  • Days on approved leave or public holidays are not counted as absences
  • Overnight shifts are counted once, on the day they started
  • The rates and thresholds match your written policy and local law
  • Employees can see their own recorded hours before the period closes, so disagreements surface early

Eight common overtime calculation mistakes

These mistakes appear in businesses of every size. Most of them come from the record, not the formula.

  • Paying raw extra time as overtime, so a forgotten clock-out becomes a wage.
  • Ignoring extra time that was genuinely worked because nobody approved it in advance.
  • Forgetting to deduct unpaid breaks, which adds false extra time to every full day.
  • Splitting overnight shifts at midnight, which distorts both days.
  • Using a phone’s own clock, which the user can change, as the source of the time.
  • Applying a weekly threshold where the law uses a daily one, or the reverse.
  • Rounding in one direction only, for example always rounding start times up and finish times down.
  • Overwriting the original record when correcting it, which leaves no way to show what changed and why.

How SlidesClock handles overtime

SlidesClock is built around the rule this guide started with: extra minutes on an attendance record are not payable overtime until someone approves them.

Employees Slide In and Slide Out on their own phone. The time comes from the server, and the day is compared with the employee’s work schedule, including grace periods, rest days, unpaid break windows and overnight shifts. The daily record shows late minutes, early-leave minutes, worked time and extra time, and flags any day missing a clock-out.

Overtime itself is a request. An employee files the date, hours and reason in the app; their manager is notified, reviews it against the day’s attendance and approves or declines it, and may approve fewer hours than were asked for. A manager cannot approve their own overtime, and the original request cannot be edited after it is filed. Leave and overtime requests are available on every plan, including the free plan for up to 5 employees.

For the rest of the pay cycle, attendance reports and CSV or PDF exports start on the Standard plan, and attendance corrections and the optional payroll tools, which use approved overtime hours and rates, are on Premium. SlidesClock does not decide your overtime thresholds or guarantee payroll compliance; you configure the rules that apply to you. See pricing for what each plan includes, or try SlidesClock free.

Frequently Asked Questions

What is the best way to track employee overtime?

Record start and finish times automatically with a trusted timestamp, compare worked time minus unpaid breaks with each employee’s schedule, and require an approved request before extra time is paid as overtime. Keep the original records and the approval together.

Is every minute over a shift counted as overtime?

No. Minutes beyond a shift are extra time. They become overtime when an authorised manager approves them, although in many countries work the employer allowed or knew about must be paid even without prior approval. Check the rules that apply to you.

How do you calculate overtime hours for a day?

Take the time between the start and finish of work, subtract unpaid breaks to get worked time, then subtract the scheduled time for that day. The result is extra time; the approved part of it is overtime. Local law may also require weekly totals.

What should happen when an employee forgets to clock out?

The day should be flagged as missing a clock-out and produce no extra time until it is fixed. The employee requests a correction with a reason, a manager reviews it, and the original record is kept alongside the correction.

Can a manager approve their own overtime?

They should not. A sound approval workflow sends a manager’s own overtime to someone else. In SlidesClock a reviewer cannot decide their own overtime request.

Does SlidesClock calculate overtime pay?

SlidesClock records extra time and handles overtime requests and approvals on every plan. On Premium, optional payroll tools use approved overtime hours and the approved rate. You remain responsible for applying the overtime law of your country.

Keep going on slidesclock.com

Related reading

More practical guides on attendance & verification

Start Work. Just Slide.

Start free for up to 5 employees at 1 branch. Upgrade when your team grows.