What to Say to an Employee Who Is Chronically Late

The meeting was supposed to start at 9:00 am. It’s 9:07. You’re watching the small digital clock on your monitor tick over as you make small talk with the three other people in the room. Then the door opens and in he comes, laptop under one arm, with a perfectly reasonable explanation already forming on his lips. “So sorry, the traffic on the bridge was a total standstill.” You nod, say “No problem, grab a seat,” and try to ignore the tight feeling in your chest. You know it’s not the traffic. Or rather, you know that tomorrow it will be something else just as plausible. You find yourself searching for things like, “my employee is always late with a good excuse,” because the real problem isn’t the excuse; it’s that you’re trapped in a conversation that’s not about the actual problem.

The reason this conversation feels impossible is because it operates on two different tracks at the same time. The employee is talking about the instance, the specific, legitimate-sounding reason for today’s lateness. You, however, are concerned with the pattern, the recurring disruption and its effect on the team. By offering a valid-sounding reason, the employee forces you into a dilemma: either you challenge the reason and look like an unreasonable micromanager (“Are you saying I’m lying about the traffic?”), or you accept it and feel powerless as the pattern continues. This is a classic communication trap. It’s not a test of your empathy; it’s a structural problem in the conversation itself.

What’s Actually Going On Here

When an employee presents a reason for being late, they are framing the problem as an external, uncontrollable event. A traffic jam, a sick kid, a freak transit delay. Each reason, viewed in isolation, is understandable. We’ve all been there. The trap is that by engaging with the reason, you implicitly agree to judge it. Is it a good enough reason? And that’s a losing game. You don’t have the information to be a fair judge, and it’s not your job to audit your employees’ lives.

This pattern gets locked in by the team around the employee. When someone is consistently late, other people adjust. A reliable team member starts prepping the morning report “just in case.” The daily stand-up informally shifts to 9:10 am. Someone else learns to handle the first client call of the day. The system becomes resilient to the disruption. This is meant to be helpful, but it has the unintended consequence of absorbing the impact. It cushions the late employee from the natural consequences of their behaviour, hides the true cost from the organisation, and allows the pattern to become a stable, unchanging feature of your team. The problem is no longer just one person’s lateness; it’s a team-wide workaround that breeds resentment.

What People Usually Try (and Why It Backfires)

Faced with this loop, most managers reach for a few standard moves. They seem logical at the time, but they almost always reinforce the problem.

• The Vague Warning. It sounds like: “We really need everyone here on time for the morning huddle.” This fails because it’s a general appeal to professionalism, not a direct engagement with a specific person’s behaviour. It’s abstract and easy to ignore because the employee can tell themselves, “She’s not talking about me; my reasons are valid.”

• Playing Problem-Solver. It sounds like: “Have you tried using a different traffic app? Maybe if you left 15 minutes earlier?” This backfires by shifting the responsibility from the employee to you. You are now co-signing a solution. When it fails, and it will, the employee can implicitly blame the solution, not their own planning: “I tried leaving earlier like you said, but then there was a fender-bender.”

• The Escalating Threat. It sounds like: “This is an official warning. If you are late again, it will go on your record.” While sometimes necessary, this move often comes too early. It jumps straight to a formal process without ever having a real conversation about impact. It turns an operational problem into a legalistic one, and it focuses all the attention on the next incident instead of the cumulative damage of the past ones.

• Accepting the Excuse. It sounds like: “Okay, I understand. Just try your best tomorrow.” This is the most common move because it’s the path of least resistance. It feels empathetic, but it actively teaches the employee that a good excuse successfully closes the conversation. You’ve just trained them to keep doing exactly what they’re doing.

A Better Way to Think About It

The goal is not to prove that their excuse is invalid. The goal is to make it irrelevant. You need to shift the conversation from the reason for the lateness to the impact of the lateness. The reason is their business. The impact is your business, and the team’s.

This means you must deliberately refuse to get pulled into a debate about traffic, childcare, or the city’s bus schedule. You are not there to judge the validity of their life’s logistics. You are there to ensure your team can function predictably. Your job is to hold the frame of the conversation on the professional consequences, not the personal circumstances.

This isn’t about being unkind. It’s about being clear. You can accept that their reason is 100% true and still hold them accountable for the outcome. The move is to acknowledge their reality without argument and then re-anchor the conversation in your own: the reality of the work. You are shifting the focus from their intention (“I didn’t mean to be late”) to the team’s requirement (“We need you here at 9 am for this to work”).

A Few Lines That Fit This Move

These are not scripts to be memorized. They are examples of language that performs the specific move of acknowledging the reason while reframing the problem in terms of its impact.

• “I hear you on the traffic. Let’s set the specific reason for today aside, because the real issue is the pattern. When you’re not here at 9 am, the rest of the team can’t start the daily planning session, and that’s a problem we need to solve.”

  • What this does: It explicitly separates the instance from the pattern, validating their experience while holding the line on the business problem.

• “I’m not going to question your reasons for being late. I trust you. What I need to talk about is the predictable result, which is that your colleagues have to cover for you in the first 30 minutes of every day. That’s not a sustainable system for them.”

  • What this does: It builds trust by refusing to play detective, which gives you more standing to talk about the non-negotiable impact on the team.

• “It sounds like the mornings are really tough. That’s separate from the problem we need to solve here, which is the unreliability of your arrival time. What can you put in place to ensure you are consistently here by your 9 am start time?”

  • What this does: It shows empathy for their situation but creates a firm boundary between their personal logistics and their professional commitment. It places responsibility for solving the problem squarely back on them.

• “I understand today’s delay was unavoidable. The problem is that a series of unavoidable things has led to a predictable pattern of late arrivals. The reasons may change, but the outcome is the same. We need the outcome to change.”

  • What this does: It names the dynamic out loud. It neutralizes the power of any single excuse by focusing on the cumulative effect.