Manager conversations · Guide

How to Address Attendance Problems With an Employee

Why this conversation gets avoided for months, how to open it with dates rather than impressions, and what to do when the answer turns out to be a family or medical situation.

2026-08-19 · 8 min read

Why this one gets avoided longer than it should

Attendance is the conversation managers put off the longest, because raising it feels petty. Someone is ten minutes late a few times a week and it seems too small to formalize. Then it is four months later, the rest of the team has noticed, and the conversation you finally have carries four months of accumulated irritation that the person did not know about.

The reason to raise it early is that attendance is the one performance issue with an audience. Everyone on a small team knows who is consistently late. When nothing is said, the message they take is not that you are being generous. It is that showing up on time is optional, and the people who do it are absorbing a cost for nothing.

There is also a real chance that something is going on. Attendance problems are frequently the visible edge of a caregiving situation, a health issue, a transport problem, or a second job. You will not find that out by making it a discipline conversation on the first pass.

Get the specifics first, and check yourself

Have actual dates. "You've been late a lot" invites an argument about frequency. "You were more than fifteen minutes late on the 4th, 6th, 11th, and 12th" does not. If you cannot produce the dates, spend two weeks writing them down before you have the conversation.

Know what the actual impact is. Sometimes lateness genuinely breaks something: the phones are uncovered, the shift cannot start, a customer waits. Sometimes it breaks nothing operationally and the issue is fairness to colleagues. Both are legitimate reasons to raise it, and they call for different conversations. Be clear with yourself which one you have.

Check whether the rule is actually the rule. If three people arrive at 9:15 and you are only raising it with one, you have a consistency problem that will surface immediately and will cost you the conversation.

Be alert to the legal edges. Absences connected to a medical condition, a disability, pregnancy, or caregiving may carry protections, and requirements vary by state. If any of that is in play, talk to whoever handles HR or employment counsel before the conversation rather than after.

How to open it

Lead with the pattern and the dates, name the impact, then leave real room for an explanation. This is one of the few hard conversations where you genuinely may not know what is going on, and the opening should reflect that.

Language that works:

  • "I want to talk about start times. You were in past 9:15 on the 4th, 6th, 11th, and 12th. The phones aren't covered until you're here, so it lands on Dana. What's going on?"
  • "I've noticed a pattern with arrival times over the last month and I want to understand it before it becomes a bigger thing. Is something going on?"

Then actually wait. The question is not rhetorical. A manager who asks "what's going on" and then talks for the next two minutes has signalled that the question was decorative.

The responses you should expect, and what to say

"It's only a few minutes." Do not argue about the size of the increment. Move to the impact: "On its own it's small. The reason I'm raising it is that the phones go unanswered and Dana picks it up, and that's been happening two or three times a week."

"Other people are late too." If true, concede it and fix it: "You're right, and I'm going to address that separately. It doesn't change what I need from you." If it is not true, say so plainly. Either way, do not let the conversation become about someone else.

A real personal disclosure. Childcare falling through, a family member's health, a car that keeps failing, a medical issue. Shift immediately out of accountability mode. "Thank you for telling me. Let's figure out what actually works." Then look at whether a shifted start time, a temporary adjustment, or a formal accommodation solves it. Do not respond to a genuine disclosure by restating the policy.

"I get my work done." Sometimes accurate, and it still may not be the whole standard. Be honest about which it is. If the role genuinely does not require fixed hours, consider whether the rule you are enforcing is a real requirement or a habit. If coverage is real, say why: "The output isn't the issue. The issue is that the desk has to be covered at nine."

Defensiveness or an accusation of micromanaging. Stay on the specifics. "I'm not tracking your minutes. I'm raising four days over two weeks that affected coverage."

How to close it

Close with a specific expectation and an explicit acknowledgment of anything you agreed to change.

  1. State the standard clearly. "I need you at the desk at nine." Not "try to be more consistent."
  2. State any accommodation you agreed to. A shifted start, a trial period, a temporary arrangement. Put an end date on anything temporary so it does not silently become permanent and then become a second conversation.
  3. Say what happens if it continues, but only proportionally. On a first conversation that is "if it keeps up we'll need to talk about it more formally," not a warning about termination.
  4. Set a check-in date. Two to four weeks.

Write two lines in your notes. If this becomes a pattern that eventually leads to a formal plan, the dated record of early informal conversations is what makes that step defensible rather than sudden.

Practice scenario: the mid-conversation disclosure

Situation. A reliable employee of three years has been fifteen to thirty minutes late roughly twice a week for the past six weeks. The role requires desk coverage at nine and a colleague has been absorbing it. You have not raised it before now.

How the other person plays it. Initially minimizes, says it is only a few minutes and the work still gets done. If the manager stays specific rather than escalating, discloses partway through that a parent has been ill and they have been handling morning care. Becomes uncomfortable and slightly embarrassed at having disclosed it.

What a good run looks like. Opens with the specific dates and the coverage impact. Does not escalate when the pattern is minimized. Recognizes the disclosure as a turning point and stops running the accountability script. Moves to problem-solving, and lands on a concrete arrangement with a review date rather than open-ended sympathy.

What a bad run looks like. Opening with "you've been late a lot" and losing the next four minutes to arguing about how often. Restating the attendance policy after the disclosure. Or overcorrecting into "take whatever time you need" with no arrangement, which leaves coverage unresolved and the conversation to be had again.

How Capstone Workforce fits

The hardest part of this conversation is the turn it takes halfway through.

Capstone Workforce lets managers practice against a persona that discloses a family situation mid-conversation, which is the moment most managers handle badly. Scored on whether they adjusted. See the NPower case study.

Next step

See how manager conversation practice works

For owners, ops leads, and first-time managers

Get the manager conversation guides as we publish them

Practical walkthroughs for the conversations managers dread: denied raises, PIPs, terminations, attendance, conflict between reports. One situation at a time, with the actual language that works.

No spam. Unsubscribe with one reply. We use your email only to send the platform briefing and PDF companions.

Frequently asked questions

How many instances before I say something?

Earlier than most managers do. A pattern across two weeks is enough to ask a question, and asking a question early is a much smaller intervention than a formal conversation after four months. The first version of this should feel almost too minor to have.

What if the reason turns out to be a medical or family situation?

Stop running the accountability conversation and start a problem-solving one. Depending on the situation and your state, formal accommodation obligations may apply, so loop in whoever handles HR or employment counsel. As a practical matter, a shifted schedule usually solves it and costs far less than replacing a good employee.

Does remote work change this?

It changes what the standard actually is, which is worth being honest about. If the real requirement is availability during core hours rather than a login time, enforce that instead. Managers who track remote start times without a coverage reason tend to lose credibility fast.

What if it is a top performer?

The same conversation, with the impact framed around the team rather than the output. Top performers usually respond well to a fairness argument and badly to a rules argument. "Your work is not the issue. The issue is that Dana covers for you and that is not sustainable" is the version that lands.

Should this be documented from the first conversation?

In your own notes, yes, with the date and what was agreed. Not as a formal written warning to the employee. The private record is what lets you act proportionally later, and it is the thing most managers wish they had when a pattern reaches month five.

See it on your cohort

Rehearse this conversation before you have it for real

30 minutes. Bring the situation you are actually facing. We will show you how the practice scenario runs, what the scoring picks up, and what it costs for a team your size.

CapstoneWorkforce
Case StudyPricingSign In

Last updated: 2026-08-19