How to track employee lateness automatically
06.09.2026
Tracking employee lateness is usually treated as a disciplinary subject. In practice the real value of the lateness indicator is different: it is an early signal showing where the schedule, the commute or the organisation of work does not fit. This guide looks at how lateness is measured correctly, which rules must be written in advance, and what automatic tracking actually changes.
What lateness is and when it starts
Defining lateness is harder than it looks. A company has to answer three questions first:
- From which moment does lateness count - the scheduled time, or after a grace period?
- How long is the grace period, and is it the same for every department?
- Is the lateness deducted from working hours, or only recorded?
When these questions have no written answers, each department applies its own version and the indicator becomes useless for comparison.
The problem with manual tracking
In a paper log lateness is practically not measured at all. When the record is written afterwards the time is "approximate" and the lateness disappears entirely. In a spreadsheet the situation is slightly better, but three problems remain:
- The figure is entered by a person, so subjectivity stays.
- The reason is not recorded anywhere.
- The trend is invisible: is this month better or worse than the last?
What automatic tracking gives
With automatic tracking the arrival is recorded and compared with the schedule. The result is information on three levels:
| Level | Question | Use |
|---|---|---|
| Individual | How often was this person late this month? | Conversation and support |
| Department | Which team has the highest lateness? | Reviewing the schedule |
| Time | On which days does lateness rise? | Finding the cause |
The third level is the one most often overlooked, although it is the most useful for making decisions.
A practical example
At a call centre the morning shift started at 9:00 and the lateness figure was high. Management first treated it as a discipline issue: warnings were given, the figure improved for a while, then returned.
The automatic report showed something different: lateness was concentrated on the first two days of the week and in one team only. That team travelled from the same side of the city and hit the morning traffic.
The solution was not a disciplinary measure - the team's shift was moved to 9:30 and the end of the day shifted accordingly. The following month the lateness figure dropped sharply. A penalty could not have achieved that, because the cause was not with the employees.
How the rule should be written
A good rule is short and unambiguous. An example:
- The working day starts at the time shown in the schedule.
- Arrival within ten minutes is not counted as lateness.
- Up to three occurrences a month are handled through a conversation with the manager.
- Transport, health and business-trip cases are recorded separately.
- A record is corrected only with the direct manager's approval.
Once these five points are announced to the team, the indicator stops being a subject of argument.
What should not be measured
Using lateness as a standalone indicator is a mistake. If someone arrives five minutes late every day but stays forty minutes longer in the evening, looking only at lateness gives the wrong conclusion. That is why the report should show actual working time and overtime alongside it.
Communicating with the team
When automatic tracking is introduced, three things must be explained clearly: what is measured, why it is measured, and what the result affects. If the purpose is correcting the schedule rather than punishing people, that should be said directly - and then demonstrated in practice.
Letting employees see their own records matters too. It creates transparency and reduces the number of correction requests.
The causes of lateness
Behind a lateness figure there are usually several different causes, and taking action without separating them leads nowhere. Four groups appear in practice.
Structural causes: the shift time collides with traffic, the handover hour is inconvenient, or the time genuinely needed to reach the site is unrealistic. This is the most common group and the easiest to fix - changing the schedule is enough.
Process causes: extra time is needed to reach the recording point, changing and preparation are outside working time, or a queue forms at the terminal. In these cases the employee did arrive on time and only the record is late.
Individual causes: personal circumstances, health, family obligations. This group calls for conversation and flexibility, not penalties.
Cultural causes: an environment where lateness is treated as normal. This is the hardest group and changes only through consistent management.
The order of measures
The practical sequence for working with lateness is: measure first, then separate the causes, then remove the structural ones, and only after that address individual cases.
Most companies apply this order in reverse - they start immediately with warnings and penalties. The result is short-lived: the figure improves for a few weeks and then returns to its previous level, because the cause was never removed.
Fixing structural causes, by contrast, produces a lasting result and costs nothing - often it is enough to move the schedule by half an hour.
Early leaving and the other side
The second indicator to track alongside lateness is early leaving. Read together, the two complete the picture: systematic early departure usually points to poorly planned workload.
The third indicator runs in the opposite direction - unpaid overtime. In many companies lateness is monitored carefully while the hours worked in the evening are recorded nowhere. That asymmetry creates a sense of unfairness and damages attitudes towards the whole system.
For that reason all three should appear side by side in the report: lateness, early leaving and overtime.
Choosing the grace threshold
How long the grace period should be looks like a technical parameter but is in fact a management decision with a real effect on the outcome.
A very narrow threshold of zero to three minutes marks every small delay as lateness. The figure is then permanently high and the team stops taking it seriously - because almost everyone counts as late.
A very wide threshold of twenty to thirty minutes creates the opposite problem: the figure always looks good and genuine lateness stays hidden.
In practice five to ten minutes is the most commonly used range. Two factors guide the choice: the nature of the work - a job requiring shift handover needs a narrower threshold - and the real time it takes to reach the recording point.
The threshold should be chosen once, announced in writing and not changed frequently; a moving rule makes indicators impossible to compare.
The next step
The simplest way to start tracking lateness is a one-month observation period: measure only, take no action. After a month the numbers point at the cause themselves, and the decision has a basis.
QRGate collects records at the moment of arrival and calculates lateness automatically against the schedule. See what QRGate can do or learn more.
