Missed punch correction request
Missed punches happen for dull reasons. A finger does not read, the terminal is busy at shift change, somebody is sent straight to a client site. The correction form exists so the fix leaves a trail instead of an edited cell.
Raised by the person whose punch is missing, usually the same day. Not for disputing a punch that did register — that is a different conversation with a different form.
Manual punch correction request Employee name and code: As it appears on the device mapping Date of the missed punch: DD / MM / YYYY Which punch is missing: Check in / check out / both Actual time: HH:MM, twenty-four hour clock Assigned shift that day: Shift name and its time window Reason the scan did not register: Terminal fault, reader did not read, off site, other Witness or corroborating record: Who saw it, or the door log, visit note or meeting that confirms it Requested by: Signature and date Approver decision: approved / approved with a different time / declined Time recorded: __:__ Approver name: ____________ Date: ______ Reason, if declined or altered: ______________________________________
How to fill it in
- Raise it the same day. Memory of a Tuesday morning is worth little by Friday. Same-day requests are the ones that get approved.
- Give a corroborating record. A calendar entry, a visitor log, a first message sent. A bare assertion puts the approver in an awkward spot.
- Write the shift as well as the time. The approver needs to know what the time is being judged against before they can judge it.
- Record the decision on the same sheet. An approval kept in an inbox disappears at the next audit. Keep the decision attached to the request.
- Watch for repeats on one terminal. Several requests naming the same device in a week is a hardware problem, not a people problem.
Manual punch requests are a built-in tab in PeopleMuster, beside the attendance record itself. Each one carries an approval decision rather than silently rewriting the punch. Manual punch requests in the product.
Questions people ask about this letter
How many corrections in a month is too many?
Set a number in your policy and hold to it. Any threshold beats an unwritten instinct that lands differently on two people doing the same thing.
Can a manager raise the correction on someone's behalf?
Yes, and often that is faster. Record who raised it, because a correction approved by the same person who requested it is not a control.
What if the device was offline for the whole shift?
Handle it as one batch, not thirty forms. Write a single note naming the outage window and the people affected, and have it signed once.