How to Calculate Work Hours Accurately (Without Getting It Wrong)
From overnight shifts to unpaid breaks and decimal conversions, this guide walks through every real-world scenario so your timesheet always adds up correctly.
Ever checked your payslip and felt like the numbers just didn't add up? You're not alone. Calculating work hours seems simple until the real-world complications kick in — overnight shifts, two separate break periods, or a payroll system that expects 8.5 instead of 8:30. One small mistake, multiplied across dozens of employees and fifty-two weeks, can mean significant overpayments or underpayments.
Below, we run through the same cases payroll teams see every week: plain daytime shifts, stacked breaks, midnight crossings, and the decimal quirks that make 8.30 not mean 8.5. Use it to sanity-check a payslip, train a new hire, or settle a "that can't be right" moment before it turns into a formal query.
Start With the Basic Formula
For a standard daytime shift, everything begins here:
Hours worked = End time − Start time − Unpaid break time
That's it. If someone clocks in at 09:00 and leaves at 17:30 with a 30-minute unpaid lunch, here's the working:
- 17:30 − 09:00 = 8 hours 30 minutes
- 8 h 30 min − 30 min = 8 hours exactly
Simple enough when the shift is clean. The complications start when you have multiple breaks, shifts that cross midnight, or a finance system that won't accept time in HH:MM format.
The Decimal Conversion Most People Skip
Payroll software almost universally wants hours in decimal form — 8.5, not 8:30. The conversion is straightforward: divide the minutes by 60, then add to the whole hours.
Quick conversion examples
- 7 hours 15 min → 7 + (15 ÷ 60) = 7.25 h
- 9 hours 45 min → 9 + (45 ÷ 60) = 9.75 h
- 6 hours 20 min → 6 + (20 ÷ 60) = 6.33 h (rounded to 2 decimal places)
Here's why this matters: if you multiply a rate of $18/h by what you think is 8 hours 30 minutes but enter it as 8.30, you'll pay for 8 hours and 18 minutes instead of 8 hours and 30 minutes. That's 12 minutes short, every single day. For a team of 20 people working 250 days a year, that adds up to a meaningful underpayment — and a potential wage dispute.
Handling Multiple Breaks in a Single Shift
Many shift workers take two or three breaks during a long day. Every unpaid break needs to come off the total. Here's a worked example:
A warehouse worker clocks in at 08:00 and out at 17:30, taking a 30-minute unpaid lunch and two 15-minute rest breaks that are also unpaid.
- Raw time span: 17:30 − 08:00 = 9 h 30 min
- Total unpaid break: 30 + 15 + 15 = 60 min (1.0 h)
- Net paid time: 9.5 − 1.0 = 8.5 h
One important detail: many employment contracts and local labour laws treat short rest breaks (10–15 minutes) as paid time, meaning you should only subtract the unpaid lunch. Always check your workplace policy before subtracting any break — the rule must be consistent for every employee in the same role.
Overnight and Cross-Midnight Shifts
This one trips people up more than any other scenario. If the end time is numerically smaller than the start time, you have a midnight-crossing shift.
The fix is simple: add 24 hours to the end time before subtracting.
Example: night shift from 22:00 to 06:30
- Adjusted end time: 06:30 + 24:00 = 30:30
- Hours worked: 30:30 − 22:00 = 8 h 30 min (8.5 h)
Good time-clock software handles this automatically because it stores entries as full timestamps rather than clock-face times. If you're working in a spreadsheet or on paper, apply this 24-hour correction any time the end time reads earlier than the start time — it's a reliable trick that never fails.
Clock Rounding: What Employers Can (and Can't) Do
Some businesses use a 15-minute rounding rule to simplify timesheet entries. Under the most common version, clock-in and clock-out times within 7 minutes of a quarter hour round toward it; 8 minutes or more rounds away from it.
So 8:07 rounds to 8:00, but 8:08 rounds to 8:15. Applied the same way to both entry and exit, the rounding theoretically averages out over time.
The legal requirement in most jurisdictions is that rounding must not consistently shortchange employees. If a quarterly review of time records shows that rounding systematically reduces pay, the practice doesn't survive an audit. Track and review rounding patterns every three months to stay compliant.
Daylight Saving Time: Two Days a Year Worth Noting
Most of the year, DST is invisible to payroll. But twice a year — when clocks spring forward and fall back — overnight workers have a shift that's either 7 hours or 9 hours long instead of the usual 8.
Labour law in most regions is clear: workers get paid for the actual time they worked, not a standard 8-hour assumption. A nurse on a 22:00–06:00 shift during spring-forward night worked 7 hours; on fall-back night she worked 9 hours. Both must be paid accurately.
Systems that store timestamps in UTC handle DST automatically. Systems that store local clock times need a manual one-hour correction on those two nights each year — mark them in your payroll calendar so they're never missed.
Building Your Weekly Total and Spotting Overtime
Once you have daily decimal hours, a weekly total is just addition. Convert each day, then sum:
| Day | Hours worked |
|---|---|
| Monday | 8.50 |
| Tuesday | 9.00 |
| Wednesday | 8.00 |
| Thursday | 9.50 |
| Friday | 7.75 |
| Weekly total | 42.75 h |
This employee worked 42.75 hours against a 40-hour threshold — generating 2.75 overtime hours. If overtime is paid at 1.5× the base rate of, say, $20/h:
- Regular pay: 40 × $20 = $800
- Overtime pay: 2.75 × ($20 × 1.5) = $82.50
- Gross pay: $882.50
Six Mistakes That Cause Payroll Headaches
- Not converting to decimal before multiplying by the hourly rate.
- Subtracting breaks twice — once manually and once because the system already excluded them.
- Using the wrong time zone for remote employees across regions.
- Ignoring DST on those two overnight crossover dates.
- Rounding at each daily stage instead of rounding only the final weekly total — small errors compound fast across a large workforce.
- Applying different break rules to different employees in the same role, which creates inconsistency and potential discrimination claims.
Record-Keeping: What You Need to Retain
Most countries require payroll records to be kept for three to five years. Store both the raw clock-in/out timestamps and the calculated totals. If a dispute surfaces 18 months later, being able to trace every step from raw timestamp to final gross pay demonstrates good-faith compliance and makes resolution far faster.
When to Use a Calculator Instead of a Spreadsheet
Manual timesheets and spreadsheets work fine for a single employee or a small team with predictable schedules. Once shift patterns vary — or you're managing a rotating team with overnight workers and variable break structures — errors creep in quickly.
CalcTap's Work Hours Calculator lets you enter start time, end time, and break duration for each day of the week. It returns totals in both HH:MM and decimal format, flags overtime automatically, and handles midnight crossings without any extra steps. Use it to double-check manual timesheets or as the primary tool for anyone who doesn't yet have dedicated payroll software.
Accuracy in timekeeping isn't just about compliance — it's about trust. Employees who see their hours correctly reflected every week are measurably more engaged. Employees who notice discrepancies, even small ones, quietly start looking elsewhere.