Somebody left on Friday without clocking out. Their shift is still running on Monday morning, the timecard says nineteen hours, and payroll is Tuesday.
You are allowed to fix this. Editing time records is normal and lawful. What is not lawful is editing them in a way you cannot later explain — and the difference is entirely in what you write down at the time.
The rule almost nobody gets wrong on purpose
An employer may correct a time record. An employer may not reduce recorded time to a number that suits the roster. The test an auditor applies is simple: does the record show what actually happened, and can you show why it was changed?
Rounding a forgotten clock-out down to the scheduled end time, every time, across a whole team, is where a correction stops being a correction. It is also very visible in the data, because it produces suspiciously tidy timecards.
What a defensible correction contains
- The original value. Never overwrite it. The first record is evidence.
- The corrected value, and the actual finish time it reflects.
- A reason in plain words — “forgot to clock out, confirmed with Ava she left at 17:10”.
- Who made the change, and when they made it.
- The employee’s acknowledgement, wherever you can get it.
That last one is the one most systems skip and the one that ends arguments. A correction the employee saw and did not dispute is a very different document from one they learned about on their payslip.
Better still: let them ask
The strongest version of this is not a manager editing a timecard at all. It is the employee requesting the fix, with the times they say they worked, and a manager approving it. Now the record shows the person whose wages they are asked first — which is exactly the order a dispute will ask about.
How ClockAll does it
- An employee can request a correction from their own timecard, naming the times they say they worked and why.
- A manager approves or denies it, and a denial carries the reason back to them.
- Every edit keeps the original punch, the new one, the reason, who changed it and when — the record grows, it never gets overwritten.
- The employee is notified whenever their timecard is changed, including when a manager edits it directly. An audit trail satisfies an auditor; it does not reach the person whose pay moved.
- A shift left running is flagged as an unusually long shift the same day, so it surfaces before payroll rather than during it.
- If a period is approved while somebody’s shift is still open, the approval says so by name — those hours are not in the pay run, and silence there is how a missing Friday becomes an unpaid one.
Records are kept six years, which is longer than any US state requires — the point of a time clock is being able to answer a question about a Tuesday three years ago.
Common questions
Can I just not pay them for the shift they forgot to clock out of?
No. Hours worked must be paid whether or not they were recorded correctly. The missing punch is a record-keeping problem, not a pay question.
Can I dock time as a penalty for forgetting?
No. Deducting worked time as a disciplinary measure is a wage violation in most jurisdictions. Discipline is a separate conversation from the timecard.
Should the employee sign off on the change?
Where you can, yes. An acknowledged correction is far stronger evidence than a unilateral edit, and it costs nothing to ask.
How long should we keep the old value?
Keep the whole history. Federal rules want payroll records for three years; New York and New Jersey want six. Six is the safe floor, and it costs nothing to hold.
ClockAll is a software company, not a law firm, and nothing here is legal advice. Wage-and-hour rules change and vary by city and state — check your own before you rely on any of it.