Protect Five Minutes: Clock In Grace Period Rules for US Employers

A clock-in grace period is an attendance tolerance your company sets internally, not a payroll exception written into federal law. If an employee performs any work during that window, the Fair Labor Standards Act requires you to pay for every minute of it. Employees should insist on pay for time worked; managers should treat unpaid grace minutes as a compliance risk, not a scheduling convenience.

TL;DR:

Employers must pay employees for any work performed during a clock-in grace period, regardless of whether it is officially outside scheduled hours.

Work done before clocking in or during a grace window that benefits the employer is legally compensable once employer control or task performance begins.

Rounding practices that are not perfectly neutral over time can mask actual worked minutes, especially if paired with untracked early or late punches.

If timekeeping software logs exact clock-in times, employers should avoid using rounding, especially in states with strict enforcement, to prevent underpayment risks.

A clear policy separates attendance discipline from wage calculations, enforcing strict controls on early tasks and documenting all exceptions to ensure compliance.

Heyhive

useheyhive.com

Make Every Punch Count

Heyhive records GPS-verified clock-ins for field employees, helping managers keep accurate time records while reducing scheduling and payroll administration.

Explore Heyhive

What Does a Clock-In Grace Period Actually Mean?
When Does Time During a Grace Period Have to Be Paid?
Rounding vs. Grace Periods: Why Combining Them Gets Risky
Where Rounding and Grace Periods Create the Most Legal Risk
Building a Grace Period Policy That Actually Holds Up
Configuring Your Timekeeping System to Eliminate Unpaid Minutes
Why Accurate Pay on Every Punch Protects More Than Payroll
Let Heyhive Handle the Punch-to-Paycheck Details
Sources

What Does a Clock-In Grace Period Actually Mean?

Most employers set grace periods lasting a few minutes, letting staff clock in shortly before or after their scheduled start without triggering an attendance flag. It exists to smooth out the friction of hourly work: nobody wants to discipline someone for clocking in at 9:03 because the parking lot was full. But a grace period is a tolerance for lateness, not a waiver of wages.

Employee handbooks usually frame it as a courtesy tied to punctuality tracking, sometimes bundled with rounding language that confuses the two concepts entirely. That confusion is where most wage problems start.

The core distinction to hold onto:

Policy tolerance governs discipline. It decides whether an employee gets a warning for clocking in seven minutes late.
Wage rule governs pay. It decides whether that employee gets paid for the minutes they actually worked, regardless of what the attendance policy says.

A written attendance policy can excuse a late punch from a disciplinary standpoint while still legally requiring full pay for time worked. Employers who conflate the two, treating the grace window as a place where hours simply disappear, are the ones who end up explaining themselves to the Department of Labor.

When Does Time During a Grace Period Have to Be Paid?

The DOL's Fact Sheet 22 on hours worked under the FLSA draws a clear line: time is compensable when an employee is under employer control or is actually performing work. Sitting in your car in the parking lot before your shift is not compensable. Powering on a register, prepping a workstation, or helping a customer who walked in ten minutes early absolutely is, even if it happens inside an "unpaid" grace window.

The DOL's Hours Worked Advisor reinforces this: voluntary early arrival where no work happens doesn't need to be paid. The moment work starts, the clock legally starts too.

Run any disputed punch through this sequence:

Was the employee required to be present at that time, or did they arrive voluntarily?
Did they perform any task that benefits the employer, however small?
Did a manager know about it, direct it, or fail to stop it?
Would a reasonable person call this "working," regardless of what the time clock label says?

If the answer to two or three is yes, you owe pay for that time.

Pro Tip: Train shift leads to physically stop early arrivals from touching a register, a headset, or a task list until the clock officially starts. If they can't touch it, they can't be "working" it, and the compensable-time question disappears before it starts.

Rounding vs. Grace Periods: Why Combining Them Gets Risky

Rounding and grace periods solve different problems, and stacking them is how minutes quietly vanish from paychecks. 29 CFR 785.48 permits rounding punches to the nearest 5, 6, or 15 minutes, but only if the rounding is neutral over time, meaning it doesn't systematically favor the employer.

The 15-minute version of this is often called the 7-minute rule: a punch at 8:07 rounds down to 8:00, while a punch at 8:08 rounds up to 8:15. That's fine on its own. The trouble starts when a grace period sits on top of it.

Picture this: an employee clocks in at 8:04, inside a five-minute grace window, but also starts stocking shelves at 8:02 because a delivery truck showed up early. The grace policy says no penalty for lateness. The rounding rule says round to 8:00. But the DOL's compensable-time standard says pay starts at 8:02, the moment work began, and rounding can't be used to erase it.

Rounding without neutrality checks tends to drift toward underpayment, especially in fast-paced shifts where early work is common.
Grace periods paired with rounding can mask real worked minutes inside a window nobody is tracking closely.
Practitioner guidance from QuickBooks increasingly recommends exact-minute pay over rounding, since modern systems already capture the true punch time and exact pay removes the neutrality burden entirely.

A useful benchmark: surveys of employer practice show most companies allow up to five minutes of early clock-in, some let staff clock in whenever work actually starts, and a smaller group forbids early punches outright. There's no single "correct" number, but every version of the policy has to defer to actual minutes worked when a dispute arises. Understanding your own time rounding configuration matters more than picking a popular increment.

Where Rounding and Grace Periods Create the Most Legal Risk

Rounding rules that pass federal muster don't automatically pass state muster, and that gap is where the real exposure lives. California courts have moved aggressively against neutral rounding, with recent decisions treating it as presumptively risky once an employer's system can already record punches to the exact minute. The reasoning is straightforward from the bench's perspective: if your software knows the true time, rounding stops looking like an administrative convenience and starts looking like an unnecessary source of underpayment.

That logic is spreading beyond California, and it changes how you should think about your own systems.

If your timekeeping software already logs exact minutes, ask why you're rounding at all instead of just paying what it recorded.
If you operate in a state with active wage-and-hour enforcement, treat rounding as a liability until proven otherwise, not a neutral default.
If your workforce is hourly, high-turnover, or spread across multiple sites, the odds of a rounding-related complaint rise with headcount and complexity.
If you're unsure whether your current setup meets the neutrality standard, that uncertainty itself is a reason to talk to labor counsel before a claim forces the conversation.

None of this means rounding is illegal everywhere. It means the margin for error keeps shrinking, and exact-minute pay is the safer default for any employer running modern time-tracking software.

Building a Grace Period Policy That Actually Holds Up

A defensible policy separates discipline from pay in writing, then backs it with system settings that make the separation real. Here's language and a process you can adapt today.

Sample policy wording: "Employees may clock in up to [X] minutes before or after their scheduled shift without an attendance mark. This grace period applies to punctuality tracking only. Any time worked, including tasks performed before an official shift start, will be paid in full at the employee's regular or overtime rate."

Operational steps to put behind that wording:

Prohibit any task activity during unpaid grace minutes, and communicate that rule explicitly to shift supervisors.
Require a clock-in the instant any task begins, even if the employee is technically still inside the grace window.
Document every manager-approved exception in writing, including who approved it and why.
Maintain a running audit log of early punches, exceptions, and approvals so you can reconstruct any disputed shift months later.

Pro Tip: Handle lateness through a points system, verbal coaching, or written warnings, never through a pay deduction. Docking pay for a late clock-in converts a discipline issue into a wage violation, and it's one of the easiest mistakes for a claimant's attorney to prove.

This structure lets you enforce punctuality without ever touching a paycheck, which is the entire point of separating the two systems in the first place. For a deeper look at discipline that doesn't cross into wage territory, see this guide to building a late policy that holds up under scrutiny.

Configuring Your Timekeeping System to Eliminate Unpaid Minutes

Most unpaid-minute disputes trace back to software settings, not bad intentions. A short checklist closes the gap:

Turn off any automatic trimming feature that silently deletes punches inside the grace window.
Set the system to record and store exact clock-in and clock-out times, not just rounded totals.
Require a manager note attached to any exception or early-start approval.
Use GPS-verified timestamps for field or multi-site teams so location and time are logged together, not just the punch itself.
Run a weekly early-punch report comparing approvals against actual task logs to catch patterns before they become claims.

Good attendance tracking practices and detailed attendance reporting turn this from a manual chore into a routine payroll reconciliation step.

Why Accurate Pay on Every Punch Protects More Than Payroll

Paying exact minutes worked isn't just the safer legal position, it's the one that costs you the least in the long run. Litigation over a few unpaid minutes per shift rarely stays small once a class of employees realizes it happened to all of them. GPS-verified punches and a real audit trail don't just win disputes, they usually prevent them from being filed at all. Fair pay practices also tend to show up in retention data, since employees notice when their hours are tracked honestly, a key aspect highlighted in Office recruitment and keeping your high performers. Review your grace period wording and your system settings together, not separately, because a good policy paired with a leaky configuration still creates unpaid time.

— Heyhive

Let Heyhive Handle the Punch-to-Paycheck Details

Every risk covered above, unpaid grace minutes, rounding drift, missing audit trails, comes down to one thing: your system needs to capture exact time and prove it later. Heyhive records clock-ins to the exact minute, so you're never relying on rounding to decide what an employee earned. Field and multi-site teams get GPS-verified clock-ins that log location alongside time, which turns a disputed punch into a two-minute lookup instead of a weeks-long investigation.