Scheduled vs. Actual Hours: How to Track and Close the Gap

By Nicole Hullihen, former SaaS Chief Operating Officer and Microsoft MVP · Updated October 13, 2026

The schedule says 40 hours. The time clock says 44. Payroll says overtime. Somewhere between the plan and the punch, four hours appeared, and nobody quite knows where they came from.

Comparing scheduled hours to actual hours is one of the simplest ways to find hidden labor costs, spot overtime before it happens and build schedules that match how work really gets done. This guide shows how to calculate the gap, what causes it, what the law requires and how to close it.

Note: This is general information, not legal advice. Wage and hour rules vary by state and city, so check the rules where your team works.

Scheduled Hours vs. Actual Hours

The schedule is a plan. Time records are the facts. When the two disagree, the time records win for pay purposes, which is why the gap matters.

How to Calculate the Gap

A positive number means people worked more than planned. A negative number means less. Look at it three ways: by shift, by employee and by week.

Example: One Week for One Employee

No single day looks alarming, but together they add four hours of overtime. For a non-exempt employee earning $20 an hour, that's four hours at $30, or $120 more than planned for one person in one week, before employer payroll taxes.

Example: A Team View

The team view shows where to look. Alex's gap is a pattern worth asking about. Taylor's was a one-time coverage need.

What Is a Normal Gap?

There's no official standard. A few minutes per shift is normal and expected, since people don't clock in and out to the exact second. What matters is the pattern:

• Small and random: normal. Some days run a little over, some a little under.
• Consistently positive: shifts are scheduled too short for the work, or something keeps causing overruns.
• Consistently negative: people leave early, start late, or the schedule includes more hours than you need.
• Concentrated in one person, shift or day: a specific cause worth investigating.

Track your own variance for a few months to learn what's typical for your business, then watch for changes.

Common Causes of Hours Running Over

Common Causes of Hours Running Under

• Late arrivals and early departures. See how to handle an employee who is always late.
• Overstaffed slow periods, where managers send people home early.
• Unrecorded breaks that are longer than scheduled.
• Missed punches that make worked time look shorter than it was.

Be careful with that last one. A missed punch doesn't mean the time wasn't worked. Correct it with an approved edit before paying. See the timesheet edit form.

What the Law Requires

Pay for Actual Hours Worked

Under the Fair Labor Standards Act, non-exempt employees must be paid for all hours actually worked. The Department of Labor explains that work not requested but "suffered or permitted" is work time that must be paid. So if an employee stays 30 minutes past their scheduled shift to finish a task, that time must be paid, even if it wasn't approved. You can address unapproved overtime through your policies, but you can't refuse to pay for it.

Overtime Is Based on Actual Hours

Federal overtime of at least time and a half applies to hours actually worked over 40 in a workweek for non-exempt employees, not scheduled hours. Some states also have daily overtime rules. See overtime laws by state.

Early and Late Punches and Rounding

Federal regulations allow employers to disregard early or late punches when employees clock in early or stay late without doing any work, and allow rounding to the nearest 5 minutes, tenth or quarter of an hour, as long as rounding doesn't, over time, result in employees being underpaid for time they actually worked. If someone clocks in early and starts working, that time counts. See the time clock rounding guide.

State and Local Scheduling Laws

Some states and cities add rules about the schedule itself. For example:

• Oregon requires certain large retail, hospitality and food service employers (500 or more employees worldwide) to give written schedules at least 14 calendar days in advance and to pay extra in many cases when they change the schedule after it's posted.
• California requires reporting time pay in many cases when an employee reports to work as scheduled but is sent home or given less than half their scheduled day: half the scheduled day's hours, at least two and no more than four hours, at the regular rate.
• Several cities have their own "fair workweek" or predictive scheduling laws for certain industries.

If you operate in one of these places, your scheduled-vs-actual comparison isn't just a cost tool. It also helps you document schedule changes and any extra pay owed.

How to Track Scheduled vs. Actual Hours

1. Publish a clear schedule with exact start and end times for every shift.
2. Use a reliable time clock so actual hours come from punches, not memory. See how to track employee hours.
3. Compare daily for problem shifts and weekly for overtime risk.
4. Flag variances over a set threshold, such as 15 minutes per shift or two hours per week.
5. Ask about patterns, not single days.
6. Adjust the schedule based on what you learn.
7. Review monthly to see whether the gap is shrinking.

A Simple Weekly Tracking Template

Add a notes column and fill it in. "Covered call-out," "truck arrived late" or "inventory night" turns numbers into decisions. You can build this in a spreadsheet using our timesheet template.

How to Close the Gap

Fix the Schedule

• Schedule the real length of shifts, including opening and closing tasks.
• Staff busy days and times based on sales or job data.
• Add short overlaps where shifts hand off work.

Fix the Process

• Look for tasks that always run long and find out why.
• Cross-train so one absence doesn't create a chain of overtime.
• Set a clear policy for when employees may clock in and when overtime needs approval.

Fix the Conversation

When one person's hours run over or under regularly, ask before assuming:

That last line matters. It makes clear that the goal is an accurate schedule, not unpaid work.

Common Mistakes

• Paying from the schedule instead of time records.
• Ignoring small daily gaps that add up to weekly overtime.
• Editing time to match the schedule. Changing records to remove time actually worked can create wage claims.
• Telling employees to work "off the clock" to stay within budget. This is not allowed for non-exempt employees.
• Only reviewing at payroll time, when it's too late to adjust the week.

Why This Matters for Labor Costs

The gap between scheduled and actual hours is often the biggest reason labor costs come in over budget. Closing even part of it can make a real difference. See labor cost percentage: how to calculate and control it for the bigger picture.

Setting a Clock-In and Overtime Policy

A short written policy reduces surprises on both sides. It should cover:

• Clock-in window: how early employees may clock in before a scheduled shift, for example no more than 5 minutes.
• Start of work: that employees shouldn't begin working until they've clocked in.
• Overtime approval: who must approve extra hours in advance.
• Leaving late: what to do when a task will run past the end of the shift.
• Missed punches: how to report and correct them.
• Pay: that all hours worked will be paid, even when a policy wasn't followed.

That last point protects you as much as your employees. A policy can require approval for overtime and set consequences for not following the rules, but it can't make worked time unpaid. See how to create an HR policy for a format.

Worked Example: Fixing a Closing Shift

A small cafe schedules its two closers from 3:00 PM to 9:00 PM. Every week, both employees clock out around 9:45 PM. That's 45 minutes over per person per shift, or about 7.5 extra hours a week across both closers on five closing shifts.

Instead of telling the closers to hurry, the manager asks what's happening. The answer: the cafe closes at 9:00, but cleaning, counting the drawer and taking out trash can't start until the last customers leave. The fix isn't speed; it's an honest schedule. The manager changes the closing shift to 3:30 PM to 9:45 PM, cutting a slow half hour at the start of the shift and scheduling the real closing time at the end. Scheduled and actual hours now match, labor stays about the same and nobody feels pressured to rush or stay unpaid.

Metrics to Watch

Pick two or three to watch each week. Hours variance and unplanned overtime are the best place to start.

Talking to Your Team About the Gap

Employees are often the best source of information about why hours don't match the schedule. They know which tasks take longer than planned, which days are always busier and where time gets lost. Share the numbers with your team, without singling anyone out, and ask for ideas:

When people see that the goal is an accurate schedule and fair pay, not cutting their hours, they're much more likely to share what's really happening. Over time, that conversation leads to schedules that fit the work and fewer surprises at the end of every pay period.

Track Actual Hours Accurately With Updoot

Updoot's employee time clock records every punch to the minute, from a phone, browser or kiosk, with GPS punch locations so you can see where people clocked in. The payroll report shows regular hours, overtime and PTO for every employee each pay period, and the KPI dashboard puts hours worked next to budget vs. actual, so gaps show up while you can still fix them.

Sources

• U.S. DOL: Fact Sheet #22, Hours Worked Under the FLSA
• U.S. DOL: Overtime Pay
• eCFR: 29 CFR 785.48, Use of Time Clocks
• Oregon BOLI: Predictive Scheduling
• California DIR: Reporting Time Pay FAQ

Frequently Asked Questions