Handling Clock Corrections With a Clear Approval History
Missed clock outs and wrong taps happen. What matters is how they are corrected, who approves the change and whether you can see the history later.
Anyone who uses clock in and clock out will eventually need to correct a time. A contractor forgets to clock out at the end of a long day, taps clock in while still on the train, or loses signal halfway through a shift. These are ordinary mistakes. The question is how they get fixed and whether the fix can be trusted later.
This article covers how to handle clock corrections in a way that is fair to contractors, practical for managers and clear for anyone reviewing the records afterwards.
Why corrections need a process
Without a defined process, corrections tend to happen informally. A contractor messages their manager, the manager edits the time, and the original entry disappears. That works until someone asks why the hours on an invoice differ from the clock record, or a contractor disputes a change they did not agree to.
A good correction process protects both sides. Contractors know their request has been seen and decided. Managers know they are not quietly rewriting someone's hours. Clients and auditors can see what happened and why.
Record the original time on the server
Corrections only make sense if the original time is reliable. If contractors can type any clock time they like, there is nothing to correct against. Recording clock in and clock out times on the server, at the moment they happen, gives you a fixed starting point.
Since V2.0.0, JN Tempo records clock in and out times on the server, and breaks are recorded too. That means a correction is always a visible change from a known original, rather than an edit to a number nobody can verify.
Ask for a reason with every request
Every correction request should include a short reason. It does not need to be long. 'Forgot to clock out, finished at 17:30' is enough. The reason helps the manager decide quickly and helps anyone reading the record later understand what happened.
Set expectations about what a good reason looks like and give contractors a few examples during onboarding. Encourage them to request corrections promptly, while the day is still fresh, rather than at the end of the period.
Let the manager decide, not edit
The cleanest model is that the contractor requests a correction and their manager approves or rejects it. The manager does not change the time directly. This keeps responsibility clear. The contractor states what they believe is right, and the manager confirms or declines.
In JN Tempo, the contractor requests a correction with a reason and the manager approves or rejects it. If the manager rejects it, the original time stands and the contractor can follow up with more detail.
Give managers simple guidance on when to approve. Ask them to check that the corrected time is plausible for the placement, consistent with other days, and supported by the reason given. Where something looks wrong, a quick conversation is usually better than a silent rejection.
Keep every change in the history
The history is what makes corrections trustworthy. It should show the original time, the requested time, the reason, who decided and when. Nothing should be overwritten without a trace.
JN Tempo keeps every clock correction in the history, and the wider audit log records submissions, approvals, rejections and changes to contractors and placements, which admins can export. When a question arises months later, you can answer it from the record rather than from memory.
If a corrected time has already been billed, the history also tells you which invoice may need adjusting, so the client's records and yours stay aligned.
Watch for patterns
Occasional corrections are normal. Frequent ones from the same person or placement are worth a closer look, not as a disciplinary matter but because they usually point to a practical problem.
Reviewing corrections once a month by placement is usually enough to spot patterns like the ones below. Fixing the cause reduces the number of requests managers have to handle and makes the clock record more reliable for billing.
- A site with poor signal where clocking out is unreliable.
- A shift pattern that does not fit the way clocking is set up.
- A contractor who has not been shown how clocking works on their phone.
- Unclear rules about breaks or travel time.
Putting it in place
Write a one page note covering how to request a correction, what counts as a good reason, how quickly managers should respond and where the history can be found. Share it with contractors and managers, and point new starters to it during onboarding. The JN Tempo guided tours and the help button beside clock corrections can support this. You can try the process for yourself with a 14 day free trial at jntempo.jnhorizon.com.
See how JN Tempo handles it
Timesheets, approvals, expenses and reporting for teams that work with contractors.