Treat the missing punch as an unresolved fact
A missing checkout does not establish when work ended. It can result from a forgotten action, a device problem, a pending offline event or a rejected capture. Ask the worker and supervisor for the relevant work date and available evidence before entering a time.
Attendify leaves an open segment and a blocking exception rather than inventing an end time. The employer still needs to account for actual work; exclusion from a software export is not a decision about pay entitlement.
Record a specific correction
Illustrative case: the original check-in is 08:00 and checkout is missing. The supervisor investigates and has a basis for a 17:10 finish. A useful reason records the relevant context and source of that decision, without adding unnecessary sensitive personal information.
Scroll the table sideways to read all columns.
| Record | Value in this example |
|---|---|
| Original attendance | 08:00 check-in; no captured checkout |
| Proposed correction | Close shift at 17:10 on the correct work date |
| Reason | Supported explanation of the missed capture and investigated finish |
| Decision | Applied directly, or approved/rejected through the enabled queue |
| Effective calculation | Original check-in plus applied correction and configured rules |
The example is fictional. It does not prescribe a default finish time or prove which evidence is sufficient in every workplace.
Understand the two product modes
An administrator with the correction capability submits the change. If the company does not require approval, it applies directly. If approval is required, a request stays pending until a permitted reviewer approves or rejects it. A pending proposal is not yet an applied correction.
The workflow does not enforce a separate second person or multiple levels. Current correction RPCs check tenant/capability but are not universally restricted by site scope. The mobile worker has no self-service request screen; agree how workers contact the responsible reviewer.
Recheck the result and the export
After application, inspect the time, local work date, configured break and remaining exceptions. The original capture remains separate from the correction. If a previous payroll export already exists, reconcile the new result and follow the receiver’s correction policy rather than silently sending a second file.
A short operational checklist is: investigate → record reason → decide → inspect calculation → reconcile handoff. Use correction controls, audit records and payroll reconciliation together.