The strongest unpaid-time analysis identifies the task, frequency, duration, and how the employer knew.
‘I worked off the clock’ is a conclusion. The useful facts are more concrete: which task, on which days, for how long, under whose instruction, and what system record shows it happened. Good wage cases are built from repeatable work patterns, not inflated estimates.
What The Repeating Task Can Look Like
Opening software before the first punch, closing a location after clocking out, answering required messages at home, completing security checks, or working through an automatically deducted meal period. Each task leaves a different evidence trail.
Find The Recurring Task
A strong analysis identifies a repeatable task rather than a vague statement that employees worked hard. Examples include booting systems, logging into multiple applications, opening or closing a location, security checks, required communications, handoffs, equipment checks, remote follow-up, or work during an automatically deducted meal period. Measure frequency and duration honestly. Small amounts can matter when repeated, but credibility declines when estimates ignore variation, days off, interruptions, or contrary records.
Show How The Employer Knew
Knowledge may be direct—supervisors saw or instructed the work—or constructive because production records, staffing levels, deadlines, system timestamps, or operational design made the work apparent. An employer may rely on a reporting policy, while the worker may show that reporting was discouraged, edits were rejected, or the workload could not be completed within recorded time. The analysis should examine both the written correction process and what happened when people tried to use it.
Audit The Deduction And Edit Trail
Automatic meal deductions, rounding, manager edits, default schedules, and exception codes should be tested against actual operations. The important record is often not only the final timecard but the audit trail showing original punches, edit reason, editor, timestamp, and approval. A lawful-looking policy can fail if the system consistently removes time without a realistic method for correction.
Records That Can Reconstruct Missing Time
- Timekeeping audit trails and edit histories.
- Computer and application login records.
- Alarm, badge, security, point-of-sale, phone, or vehicle data.
- Meal interruption messages and workload records.
- Staffing schedules and expected opening/closing duties.
- Complaints about time, rejected corrections, or instructions not to record overtime.
Where The Analysis Can Break Down
- Compensability and de minimis arguments can be legally and factually complex.
- A system timestamp may show access but not continuous work.
- A worker who knowingly reports inaccurate time may face credibility attacks even when the employer also had knowledge.
- Privacy and policy rules constrain how system data may be obtained.
What To Do Next
- 1. Identify three representative weeks and reconstruct them from multiple sources.
- 2. Request or preserve the original timecard and edit history where lawfully available.
- 3. Record the task, frequency, approximate duration, supervisor knowledge, and reporting barrier.
- 4. Do not exaggerate precision; separate measured time from estimated time.