Attendance regularization is a request to correct a day's attendance record, for example when someone forgot to clock in or out. The person gives the correct time and a reason, and a manager approves or rejects it. A short policy keeps corrections fair and easy to check.
When regularization is needed
- A forgotten clock-in or clock-out.
- A phone that died before clocking in.
- A visit to a client or another site that day.
- A system error on the day.
How the request works
- The person opens the day in the app and taps request correction.
- They enter the correct time and a short reason.
- The request goes to the manager's inbox.
- The manager approves, rejects or asks for more detail.
- An approved request replaces the record for that day, and the old record stays in the history.
A short policy
Ask for a correction within three days of the date.
Give the correct time and a reason.
Your manager decides. Nobody approves their own request.
Watch for patterns
A few corrections are normal. The same person asking every week, or a manager approving everything, is worth a look. Reports should show how many corrections each person and each approver makes.
Keep the record honest
| Good practice | Weak practice |
|---|---|
| A reason on every request | No reason needed |
| Time limit on requests | Anything can be changed months later |
| History of the change is kept | The old time is overwritten |
| A second person decides | People approve their own |
Questions people ask
What is attendance regularization?
A request to correct a day's attendance record, approved by a manager.
How long should staff have to ask?
Three days is common. Set what suits your team.
Who approves it?
The manager, with a back-up. Nobody approves their own request.
Does the old record disappear?
It should not. A good system keeps the history of each change.
Where Zentaro Pulse fits
In Zentaro Pulse the employee asks, the manager decides in one inbox and the change is kept in the history. Launching 2027.
Get early access