Can an employer refuse to pay an employee who forgot to clock in?

No. The FLSA requires payment for all hours worked regardless of whether the employee clocked in. The employer bears the burden of maintaining accurate records. Withholding pay as punishment for a missed punch is a wage violation. Your system should have a mechanism for capturing or reconstructing those hours consistently and documenting the correction.

Do employees get paid for being on standby or on call?

It depends on whether the employee's freedom is substantially restricted during the standby period. If the employee must remain on premises or cannot use the time for personal purposes, the time is generally compensable. The determination is fact-specific. The safest practice is to capture standby hours and apply the engaged-to-wait test rather than assuming non-compensability.

Can an employer require non-exempt employees to arrive 15 minutes early without pay?

No, if the early arrival involves any work activity, including briefings, system logins, or equipment checks. That time is compensable from the moment the employee is required to be present and engaged. A rounding rule that systematically erases those minutes adds a second layer of exposure.

Do non-exempt employees have to clock in and out?

The FLSA requires employers to keep accurate records of hours worked for non-exempt employees but does not mandate a specific method. Clocking in and out is the most defensible method because it creates a contemporaneous, attributable record. The employer bears the burden of accurate recordkeeping, not the employee.

What are the most common FLSA overtime mistakes employers make?

Three stand out: calculating overtime on scheduled hours rather than hours actually worked, failing to include non-discretionary bonuses in the regular rate for overtime calculation, and applying comp-time arrangements that are not permitted for private-sector non-exempt employees. All three are upstream capture failures as much as they are policy failures.

Why FLSA Timekeeping Systems Fail Before Payroll Runs

Why is FLSA compliance an infrastructure problem, not an education problem?

The answer is straightforward: employers who know every FLSA rule still accumulate back-pay exposure because their timekeeping systems cannot record hours that fall outside a clean clock-in and clock-out. The DOL's definition of "hours worked" under the FLSA is broad. It covers all time during which an employee is required to be on the employer's premises, on duty, or at a prescribed workplace. Yet most time capture systems are built around a single event pair: punch in, punch out.

In the experience of EasyClocking by WorkEasy Software working with HR and payroll teams across hourly workforces, the compliance gap is consistently not in the policy binder. It is in the timekeeping system's inability to handle anything that is not a scheduled shift. Consider what falls through:

An employee who forgets to clock in but works a full shift
A maintenance technician on standby at home waiting for a dispatch call
A warehouse worker required to attend a pre-shift safety briefing before the scheduled start time
A rounding rule that systematically favors the employer by a few minutes per shift

Each of these is a well-documented FLSA obligation. Each is also a scenario that manual timesheets and basic punch clocks handle poorly or not at all. The rest of this post maps four specific gap categories where real-world timekeeping systems break down, and what defensible automation looks like for each. If you want to understand the foundational terms, the FLSA hours worked definition in the glossary is a good starting point. For a broader evaluation framework, see the compliance timekeeping framework.

Why are missed punches the highest-frequency FLSA liability vector?

Missed punches, not overtime miscalculation, are the most frequent source of FLSA underpayment claims. The reason is simple: a missed punch is invisible until someone disputes it. When an employee forgets to clock in, the system shows no record of work performed. If a manager fills in the gap from memory, the correction is inconsistent and undocumented. If no one fills in the gap, the employee is underpaid.

The FLSA is clear on this point: an employer cannot legally withhold pay because an employee forgot to clock in. The employer bears the burden of maintaining accurate records of hours worked. When your correction process relies on a supervisor remembering what happened three days ago, you have a compliance problem that compounds with every pay period.

Manual missed-punch correction workflows introduce a second layer of risk. Inconsistent application of corrections across employees, shifts, or supervisors can become evidence of discrimination or retaliation in a wage dispute. If one employee's missed punch is corrected and another's is not, the question shifts from recordkeeping to intent.

EasyClocking by WorkEasy Software addresses this with missed-punch automation that applies a configurable policy rule at the moment of gap detection, not at payroll close. The correction is documented, consistent, and defensible before the pay period ends. You can review missed punch pay questions for more detail on how the FLSA treats these scenarios, or read about payroll errors upstream data to understand how missed punches cascade into payroll mistakes.

Why are standby and on-call hours the most legally contested gap?

Standby and on-call time is compensable under the FLSA when the employee's freedom is substantially restricted during the waiting period. The legal distinction, rooted in the "engaged to wait vs. waiting to be engaged" framework, is well established. But it is almost never operationalized in timekeeping systems.

Most employers have a standby policy in writing. Few have an automated mechanism for capturing when standby begins and ends. The determination of whether standby time was compensable is left to manager memory, employee self-report, or retroactive reconstruction during a dispute. Industries with high standby frequency, such as field services, healthcare, and transportation, show the widest gap between policy intent and captured hours.

The compounding risk is significant. Standby hours that are compensable but uncaptured can push an employee over the 40-hour overtime threshold without anyone noticing until a DOL audit or an employee complaint surfaces the discrepancy. At that point, the employer must reconstruct records that were never created.

What the platform at EasyClocking by WorkEasy Software has shown in field-service and similar implementations is that standby disputes almost always surface at the worst possible moment, during an audit or complaint, because the hours were never systematically recorded in the first place. The fact-specific nature of the "engaged to wait" test makes consistent, contemporaneous capture even more important. A policy that says "standby is not compensable" is not a defense if the actual conditions of standby restricted the employee's freedom and no one recorded the hours. If you are evaluating your current approach, consider the standby pay compliance benchmarks as a reference point.

Where do training time and pre-shift requirements create the sharpest FLSA exposure?

Training time is compensable under the FLSA unless all four conditions of the non-compensability test are met: the training must be voluntary, held outside regular hours, not directly related to the employee's job, and the employee performs no productive work during it. All four conditions must be satisfied. Mandatory onboarding, required certifications, and job-related safety training almost always fail at least one condition, making them compensable.

The pre-shift pattern is where employer intent and FLSA obligation diverge most sharply. Requiring employees to arrive early for briefings, equipment checks, or system logins without recording that time as hours worked is a compensable-time violation. Many employers treat these minutes as administrative overhead rather than work, but the FLSA disagrees.

Rounding rules interact with this gap in a damaging way. Even when pre-shift time is captured, an employer-favorable rounding policy can erase the compensable minutes. A rounding rule that is neutral over time is permissible under the FLSA, but one that systematically shaves minutes from the start of shifts is not.

EasyClocking by WorkEasy Software's schedule-anchored time capture flags pre-shift activity automatically. If an employee badges in before their scheduled start and the shift includes a required briefing, the system records compensable time from badge-in, not from the scheduled start. This eliminates the gap between what your policy says and what your timekeeping system actually captures. For related guidance, see training time capture procedures and off-the-clock work compliance.

How do overtime edge cases compound every upstream gap?

Overtime errors are almost always downstream symptoms of upstream capture failures. A missed punch that adds unrecorded minutes to a workday, combined with standby time that was captured but not flagged as compensable, combined with a pre-shift briefing that was rounded away, can push a non-exempt employee over 40 hours in a workweek without any single system triggering an alert. No manual review process catches this interaction reliably.

Three common overtime mistakes illustrate the pattern:

Calculating overtime on scheduled hours rather than hours-worked hours. The FLSA's 40-hour threshold applies to hours actually worked, not hours scheduled. If your system calculates overtime from the schedule, every upstream capture gap is invisible to the overtime calculation.
Failing to include non-discretionary bonuses in the regular rate. The FLSA requires that non-discretionary bonuses be factored into the regular rate before calculating overtime premiums. Many payroll systems do not automate this.
Applying comp-time arrangements to private-sector non-exempt employees. Comp time in lieu of overtime pay is generally not permitted for private-sector non-exempt employees under the FLSA. Employers who offer "time off instead of overtime pay" are creating liability.

In the experience of EasyClocking by WorkEasy Software, the employers with the cleanest overtime records are not the ones with the most sophisticated overtime policies. They are the ones whose time capture systems have no gaps upstream of the overtime calculation. When missed punches, standby, and training time are captured accurately and consistently, the overtime math takes care of itself. For more on how overtime rules interact with state-level requirements, see multi-state overtime compliance.

How EasyClocking by WorkEasy Software Addresses This

EasyClocking by WorkEasy Software is built around the gap chain described in this post. The platform automates missed-punch resolution with configurable policy rules applied at detection, not at payroll close. Schedule-anchored time capture records pre-shift activity from the moment an employee badges in, not from the scheduled start, so compensable training and briefing time is never rounded away. Overtime calculations run on hours-worked hours with automated rule application for overtime thresholds, rounding, and shift differentials. The result is a defensible record that flows into payroll through 20+ direct integrations, so your payroll team runs on captured data, not reconstructed estimates.

Why FLSA Timekeeping Systems Fail Before Payroll Runs

What You Need to Know

Sources

Related on EasyClocking

Is your time tracking system fair to your team?

Frequently Asked Questions

Clocked

Not Ready for a Quote? Start Here.