The Staff Member Who Always Has an Excuse: How to Stop Accepting Them Without Starting a War

You know this person. They have an answer for everything. A reason for every missed deadline. A context for every performance concern. A circumstance that explains away every expectation that was not met.

And here is the complicated part: sometimes the reasons are real. Life happens. Teaching is hard. Classrooms are complex. Not every missed expectation is a character flaw.

But the pattern — the consistent pattern of explanation rather than accountability, of reasons rather than results — that is the issue. And addressing the pattern is different from addressing any single incident. It requires a different kind of conversation and a different kind of follow-through.

One excuse is a reason. Two excuses is a pattern. Three excuses is a choice. The principal who does not name the difference has made a choice too — to accept the performance level the staff member has decided is enough.

Why Principals Keep Accepting the Excuses

Because the excuse is usually plausible. Because the conversation to reject it feels like calling the person a liar. Because the principal has other things they would rather spend their limited political capital on. Because this staff member, whatever their performance issues, has seniority or community relationships or union knowledge that makes conflict with them feel costly.

All of those are real factors. None of them are reasons to let the pattern continue.

The cost of continuing to accept the excuse is paid by the students in that classroom, the colleagues who are working harder than they should because this person is not, and by the staff culture — which watches what you allow and calibrates its own effort to the floor you set.

The Conversation That Changes the Pattern

Stop addressing the individual excuse. Start naming the pattern. The conversation is not: ‘You were late on this assignment.’ The conversation is: ‘I want to talk about a pattern I have been observing. Over the past [time period], [name the specific instances]. In each case, there was a reason. I want to acknowledge that the reasons have been different each time. What I also need to say is that the pattern itself — regardless of the individual reason — is the concern I am addressing today.’

This reframe is important. You are not calling any single reason false. You are naming that the accumulation of reasons has become a performance issue — and that you are addressing the pattern, not any one instance.

What Comes After the Conversation

The expectation going forward is stated clearly and specifically — not ‘I need you to be more reliable’ but ‘I need [specific deliverable] by [specific date] without exception.’

The follow-up date is named in the conversation and honored. If the pattern continues, the documentation sequence begins. If it improves, that improvement is acknowledged — specifically, not generally.

The excuse may still come. Your response changes: ‘I hear that. Here is the expectation regardless of that circumstance.’ Say it calmly. Say it consistently. Eventually the staff member learns that the excuses will be heard and then set aside — and adjusts their behavior to match the actual standard rather than the negotiated one.