Correct the working record without rewriting the capture
A missed checkout should lead to an investigation and a recorded decision. Attendify stores a correction separately from the original attendance event. The timesheet calculation layers that correction over the capture history, so the adjusted result has an explanation.
Authorized administrators can supply a missing check-in, close a shift, excuse an absence or lateness, or discard a punch from the effective calculation. A reason is required. The worker mobile app does not currently provide a self-service correction-request screen.
Choose direct application or an approval queue
The company setting determines the correction workflow. When approval is off, a permitted correction is applied directly. When approval is required, the request stays pending until an administrator with the approval capability approves or rejects it. Approval creates the applied correction; rejection leaves the proposed change unapplied.
Scroll the table sideways to read all columns.
| Stage | Evidence to review |
|---|---|
| Request | Worker, work date, correction type, proposed time and reason |
| Decision | Approve/reject outcome, decision actor and recorded context |
| Calculation | Original punches plus applied correction, with remaining exceptions |
| Payroll handoff | Reviewed hours and export exceptions |
Example: a phone fails before checkout
A supervisor checks the worker’s account of the shift and the available site evidence, then requests a checkout at the supported time with a reason. If approval is enabled, the request goes to the queue. A permitted reviewer considers the request and either applies it through approval or rejects it for further investigation.
Do not replace missing evidence with a default full shift. Equally, an incomplete record should not be treated as proof that no work happened. The employer’s review process must address the actual working time.
Understand the approval boundary
This is correction approval, not multi-level payroll authorization. A user may hold both correction and approval permissions; the current workflow does not enforce an independent second person. These RPCs check company membership and capability, but do not provide a universal site-scoped write restriction. Configure responsibilities carefully and discuss requirements that need stronger separation before rollout.
The audit trail explains supported activity records. A company should also define response times, evidence expectations and how a worker can raise a concern.