Attendance corrections
How to Handle Missed Clock Punches in an Auto Repair Shop
When an employee misses a punch, first identify the incomplete event and the actual time involved. Record the employee’s explanation, route a correction to an authorized reviewer, and check the resulting timesheet. A planned shift is context for the review, not proof of when the employee worked.
Updated · Strut product team
01 / Attendance corrections
Identify what is missing before correcting the total
A forgotten clock-in, a forgotten clock-out, and an incomplete break need different facts. Ask for the affected date, shop, approximate event time, and what happened. If the employee is still shown as working, inspect that active state before deciding how to resolve it. Avoid submitting repeated actions when a screen is slow: first refresh the confirmed record so a correction does not duplicate a punch that was already saved. Strut’s clock actions require a connection and do not silently save offline punches.
- Name the missing event, not just a target total
- Check the recorded state before retrying
- Distinguish an offline attempt from a saved punch
02 / Attendance corrections
Write a request that can be reviewed
A useful correction request gives the reviewer enough context to assess it without guessing. An illustrative explanation is: ‘I forgot to clock out on Monday at the main shop. I finished at 4:15 PM after the closing handoff. Please review the missing end time.’ Keep the explanation about attendance. Avoid placing customer details or private reasons for absence in a note that other reviewers do not need. If the time is uncertain, state that and ask for a review rather than presenting an estimate as established fact.
- Include the date and relevant shop
- Describe the event and proposed time clearly
- Explain uncertainty instead of disguising it
Information to gather
Affected record
1Employee, date, shop, and the missing clock or break event.
Employee explanation
2What happened and the proposed time, with any uncertainty made clear.
Review decision
3An authorized reviewer’s decision and the resulting timesheet check.
03 / Attendance corrections
Review the correction through the authorized workflow
Separate an employee’s request from a manager’s decision. In Strut, personal time tools provide correction requests; authorized team reviewers handle decisions in the Requests workflow. A published shift can help the reviewer understand the context, but changing that shift does not repair an attendance event. Follow the correction path that applies to the record, and verify the resulting hours rather than assuming that a submitted request has already changed the timesheet.
- Use the employee request and authorized review paths
- Check the decision rather than assuming approval
- Verify the affected day after the correction
04 / Attendance corrections
Recheck the period before the payroll handoff
An open session or unresolved correction can make an apparently complete period unfinished. Before exporting hours, check that active work has ended, corrections have been reviewed, and the timesheets are approved and locked as required. Strut’s payroll CSV is a handoff of recorded hours, not a payroll calculation or native integration. If a correction arrives after a handoff, document how the source record and the subsequent payroll adjustment are reconciled rather than quietly maintaining two conflicting versions.
- Resolve active sessions and outstanding requests
- Review the corrected hours before locking
- Keep later adjustments traceable to the source
Map this to your shop