June 7, 2026 · Tickin

Do Breaks Count as Hours Worked? How Break Tracking Should Work

"Does my lunch break count as paid time?" is one of the most common — and most fumbled — questions in any small team. Get it wrong and you either overpay, underpay, or quietly erode trust. The fix isn't a policy document nobody reads; it's break tracking that's accurate, automatic, and visible to everyone.

Gross hours vs. net worked time

Start with the only distinction that matters:

Gross hours = clock-out minus clock-in. The raw span of the day.
Break time = every break taken during that span.
Net worked time = gross hours minus break time.

Net is what you should pay on and measure overtime against. A nine-hour day with a 48-minute break is 8h 12m of net work, not nine hours — and your records should say so without anyone doing mental math.

Do breaks count as hours worked?

It depends on the break, and your policy should be explicit:

Short breaks (a quick coffee, a five-minute stretch) are usually paid and often left inside worked time.
Meal breaks (a real lunch where someone is off the clock) are typically unpaid and should be subtracted from worked hours.

The principle: if someone is genuinely off-task and free to leave, that time generally shouldn't count toward paid worked hours. Whatever you decide, the system has to apply it the same way every single day — consistency is what makes it fair.

Why manual break tracking always drifts

Asking people to remember their breaks and report them honestly at the end of the week is a losing game. Nobody recalls whether lunch was 35 or 50 minutes. So the numbers get rounded, guessed, or ignored — and your payroll inputs quietly become fiction. The only break data you can trust is data captured the moment a break starts and ends.

What good break tracking looks like

A break system worth using should:

Start and stop in one tap or command — low enough friction that people actually use it (/break in Slack, a button on the web).
Subtract automatically from worked hours — no manual deduction at month-end.
Handle the forgotten break — if someone clocks out without ending a break, close it cleanly using the elapsed time so the timesheet stays honest.
Show the breakdown — gross, break, and net hours side by side, so employees and admins see exactly how a number was reached.

Breaks and overtime: the connection people miss

Here's where gross-vs-net really bites. If overtime is measured on gross hours, a long lunch can push someone "over" the daily threshold on paper even though they didn't actually work extra. Measure overtime on net worked time and that never happens — a break never accidentally triggers overtime, and real overtime is real.

How Tickin handles it

In Tickin, breaks pause the work timer. An employee types /break when they step away and again when they're back; net worked time is always clock-out minus clock-in minus the sum of every break. Forgot to end one before clocking out? Tickin closes it automatically and uses the elapsed time. Daily and weekly summaries show gross, break, and net side by side, and overtime detection runs on net hours — so a long lunch never trips the threshold by accident. Break tracking is included on every plan.

Get accurate hours without the spreadsheet

Tickin tracks breaks automatically and deducts them from worked time, so your attendance and payroll numbers are right the first time. Start a 14-day free trial, no credit card required — or book a demo to see it in your own workspace.