Correcting attendance: amendment requests
Attendance records go wrong — a device misses a tap, someone forgets to check out, a day is scheduled against the wrong activity. Amendments are how they get put right: on the record, with a reason and an approver, rather than by quiet edit.
Where: your own schedule area to raise one; Calendar › Approvals to decide You need: nothing to raise one for yourself; amending someone else's needs the team attendance rights
Which correction, when
Choosing correctly matters more than it looks, because two of these fix the evidence and one overrides the conclusion:
| Request | Use it when | What it does |
|---|---|---|
| Timelog amendment | The check-in or check-out time is wrong | Fixes the tap, and lets KAMI recalculate the day |
| Event amendment | The event exists but is wrong — wrong activity, hours or status | Overrides the record |
| Event request | The event does not exist — unscheduled work | Creates the day |
Prefer the timelog amendment wherever the tap is what went wrong. It fixes the cause and lets the rules do their work; an event amendment states a conclusion and hides why the day was wrong in the first place.
How to raise one
From your own schedule area, open the day and raise the correction with a reason. It appears under my requests while it waits, and lands in your approver's Approvals queue.
Whether you can type a free-text reason or must choose from a list is a company setting — some companies allow free entry reason, others require structured ones so corrections can be analysed rather than merely read.
The deadline nobody mentions until it bites
Corrections are not open indefinitely. Your company sets:
- an attendance lock — a period before which no new events or amendments may be made at all
- correction days — how long a given day stays fixable
Once those close, the record stands. That is deliberate: payroll cannot run on a period that keeps moving. The practical consequence is worth telling every new joiner — raise corrections in the week they happen, not when you notice on a payslip.
Companies can also disable amendment requests entirely, or use a custom amendment request flow. If you cannot find the option to correct a day, that is configuration rather than a fault.
What Happens Next
- The request waits with your approver. The original record stands until it is approved — so the calendar and timesheet keep showing the old version in the meantime.
- Once approved, the day is recalculated and flows into the timesheet.
- Once declined, nothing changes and the day remains as it was — which usually means it is still wrong, and needs a different correction.
- If the lock closes while a request is pending, it can no longer be actioned.
When a correction is not the answer
- The day is marked absent but you worked. Check the hours first. KAMI marks a day absent when hours fall below the shift's threshold even with both taps present — the record may be accurate and the threshold wrong. That is a conversation with whoever owns Shifts, not an amendment.
- Everyone's day is wrong the same way. One correction each is thirty wasted approvals. A rule, holiday class or shift is misconfigured; fix that and refresh the events.
- The setting changed but old days did not. That is staleness, not error. Refresh the events — see Events.
Tips
- Raise it the same week. The most common attendance complaint is a correction raised after the lock closed, which nobody can help with.
- Write a reason someone can act on. "Wrong" tells the approver nothing; "device offline, arrived 08:05" tells them everything.
- Attach the evidence where your process expects it. A correction supported by a rota or an email is approved in seconds.
- For approvers: check the time logs before approving. A missing tap with a plausible explanation is routine; a rewritten day with no supporting record deserves a question.
Troubleshooting / FAQ
Q: My correction was approved but the day still looks wrong. The event may need refreshing, or the correction fixed a different thing from the one that is wrong. Check the time logs against the event.
Q: I cannot raise a correction at all. Either the period is locked, or amendment requests are disabled for your company.
Q: My request has been pending for a week. Chase it from the approvals queue. If the attendance lock closes first, it cannot be actioned at all.