Employee Tardiness: How to Address Chronic Lateness Without Losing Good People
Tardiness is the attendance problem managers most often mishandle, in both directions. Some ignore it until it has spread across the team and the punctual majority is resentful. Others treat a single late Tuesday as a disciplinary matter and lose a good employee over a school run. The fair approach sits between: a clear threshold everyone knows, a distinction between patterns and incidents, a documented conversation before any formal step, and an honest account of what lateness means when the team is remote.
Why Tardiness Is Worth Addressing at All
A few late minutes seem trivial, and for a single person on a single day they are. The problem is what chronic lateness does to everyone else. Shift handovers slip. Meetings start late or start without the person and repeat themselves. Colleagues cover the first fifteen minutes and notice that nobody covers theirs. And once one person’s lateness is visibly tolerated, the team’s norm moves, because the punctual are not rewarded for it and the late are not corrected.
That last effect is the real cost. Tardiness is contagious in a way most attendance problems are not, and the manager who addresses the first case early rarely has to address a fifth.
The counterweight is that lateness is often a symptom. Childcare, transport, a health issue, a shift pattern that does not fit the person’s life, or disengagement from a job that has gone stale all show up first as a late start. Addressing the symptom without asking about the cause fixes nothing and sometimes loses the employee. Our guide to absenteeism covers the same distinction for absence.
Set a Threshold Before There Is a Problem
Fairness starts with a rule that existed before the case. The attendance policy should state what counts as late (a grace period of five to ten minutes after the scheduled start is common), how lateness is recorded, what number of instances in what period triggers a conversation, and what the escalation path is after that. Our attendance policy template includes the standard clauses.
A workable threshold is something like three late starts in a rolling 30 days triggers an informal conversation; a repeat in the following 60 days triggers a documented one. The numbers matter less than their existence. A manager applying a rule the team already knows is being fair; a manager inventing one for a particular person is being arbitrary, and everyone can tell.
The rule should be the same for everyone at the same level, and applied the same way. Selective enforcement, where the high performer’s lateness is overlooked and the struggling employee’s is not, is the fastest route to a grievance and, in many jurisdictions, a discrimination claim.
Pattern or Incident?
Before any conversation, look at the record. One late start is an incident and needs nothing more than a “everything okay?”. A late start every Monday is a pattern with a probable cause. Late starts that began three weeks ago after eighteen months of punctuality are a change, and changes have reasons.
Reliable attendance records make this distinction possible. Managers working from memory tend to remember the most recent lateness and the most annoying one, which produces conversations about the wrong thing. Attendance tracking that records actual start times, rather than a manual sign-in sheet that everyone fills in at ten, shows the pattern as it is. It also protects the employee, because “you are always late” is refuted by a record showing three lates in ninety days.
Look also at what the lateness coincides with. Late starts that pair with late finishes are a shifted day, not a shortened one, and for many roles that is a scheduling conversation rather than a conduct one. Late starts that pair with long hours and weekend activity may be the first visible sign of burnout, and the wrong response to those is a warning.
The Conversation
Private, prompt and specific. Within a day or two of the threshold being crossed, not at the next quarterly review. Open with the record, not the interpretation: “You have started after 9:15 on four days in the last month” rather than “you have been unreliable”. Then ask, and listen. Most tardiness has a reason the manager did not know about, and a surprising share of it is fixable with a schedule change.
Agree what happens next: an adjusted start time if the role allows, a fix for the underlying cause if there is one, or simply a clear expectation restated. Write it down, in a note both people see. The note is not a warning; it is the record that a fair conversation happened, and it is what protects both sides if the pattern continues.
If the cause is a protected one, such as a disability, a medical condition or caring responsibilities, the conversation shifts to accommodation, and the attendance policy has to yield to employment law. Managers who are unsure should involve HR before, not after, the documented conversation.
Punctuality Overview, Last 30 Days
On-time start rate by week
Late starts by weekday
▲ Monday accounted for most late starts; two employees moved to a 9:30 start on Mondays and the repeat count fell.
Illustrative eMonitor dashboard.
Tardiness When the Team Is Remote or Hybrid
Remote work does not abolish lateness; it changes what it means. For a role with fixed hours, customer support or a shift-based operation, a late login is a late start and the same rules apply. For a role with flexible hours, “late” only makes sense against an agreed overlap window or a meeting time, and the policy should say which.
The workable remote equivalent is a start window rather than a start time: available by 9:30 on at least four days, for instance, with the fifth flexible. Lateness is then measured against the window, and the record comes from the first activity of the day rather than a badge swipe. Our guide to tracking time for remote employees covers how to do that without minute-level surveillance.
Two remote-specific patterns are worth knowing. The employee who logs in on time and does nothing for forty minutes is not late, but the behaviour is the same, and it is better handled as a focus or engagement question than a punctuality one. And the employee whose “late” starts pair with late finishes in another timezone is not late at all; they are working their own day, and the dashboard needs to know their timezone.
When It Becomes a Formal Matter
Escalation is warranted when the pattern continues after a documented conversation with no underlying cause that the employer can address, or when the lateness is causing measurable harm to colleagues or customers. At that point the attendance policy’s formal steps apply: typically a written warning, a review period, a final warning and, rarely, dismissal.
Every step should rest on the same record and the same threshold that applied from the start. Managers who skip the informal stage, or who escalate on a different standard than the one the team knows, lose the case if it is ever tested. Our guide on writing up an employee covers the documentation, and the compliance guides cover jurisdiction-specific requirements around warnings and dismissal.
The Record That Makes the Conversation Fair
eMonitor records actual start times per employee and per timezone, so tardiness conversations start from a pattern both people can see.
Preventing It
Most chronic lateness is preventable with three things the policy conversation tends to reach last. Schedules that fit the people on them: a parent asked to start at 8:30 will be late until the schedule changes. Start windows rather than start times wherever the role allows. And a team culture where punctuality is noticed, because a team that starts on time makes lateness visible without anyone having to enforce it.
The manager’s own punctuality is the loudest signal in the room. A leader who is habitually five minutes late to every meeting has already set the standard, and no policy will override it. Our guide on improving employee attendance covers the broader programme.