Make the explanation part of the record
Attendance disputes are difficult to resolve when the only surviving artifact is a changed spreadsheet cell. Attendify keeps corrections separate from captured attendance and records supported administrative activity in a server-stamped audit log.
Correction reasons explain why a time or status was adjusted. Approval activity connects a request to a decision. Other supported activity includes workforce administration, imports, configuration and export actions. The audit capability controls access to the activity view.
Follow an exception through the workflow
A useful review begins with the original attendance, identifies the missing or disputed element, then follows the correction and its outcome. The calculated timesheet should be explainable from captured events and applied corrections, rather than a number with no history.
Scroll the table sideways to read all columns.
| Reviewer question | Evidence to inspect |
|---|---|
| What was originally captured? | Attendance event and available capture evidence |
| What change was requested? | Correction type, work date, proposed time and reason |
| Who decided it? | Recorded decision actor and outcome when approval is used |
| What was sent onward? | Export run and the file/reconciliation retained by payroll |
This table describes a review process. It does not mean every external action or every database operation appears in one universal log.
Know what append-only means here
Normal application correction records are not updated in place through the correction flow. Supported audit records are append-only through application access controls. This is not a claim of cryptographically sealed evidence, WORM storage or protection against every privileged infrastructure action.
Likewise, a record of approval is not proof that the approver was independent of the requester. Review actual role grants and organizational responsibilities where separation matters.
Retention needs an owner
Attendance hours, accepted selfies, biometric templates and operational logs can have different purposes and retention requirements. Do not assume all of them should be kept forever or deleted together. Confirm the applicable retention and access arrangements before deployment.
The security overview explains the data boundary. The record preparation guide separates practical review evidence from jurisdiction-specific recordkeeping requirements.