Explanation vs excuse: what to say after you drop the ball

An explanation gives the reason, owns your part and says what changes, with a date. An excuse gives the same reason and stops there. The facts can be identical. What you do with them isn't.

Take a missed callback. "Sorry, it's been a crazy week" is an excuse. It names no event, owns nothing and leaves the client guessing whether it'll happen again. "I didn't put your callback in my calendar. That's on me. I'll call you tomorrow at 10" is an explanation. Same week, same miss, and now the client knows where they stand.

The dictionary won't settle it for you. Even there the two blur: one of the meanings Merriam-Webster gives for excuse is simply "reason". An explanation is just something that explains. So you can't sort the two by their words. You sort them by what comes after the words.

"My laptop died on Tuesday" explains why the quote didn't go out on Tuesday. Say it on Friday, with the quote still unsent, and it's an excuse. Nothing about the sentence changed. The calendar and the follow-through did.

That's the test people run without noticing. The listener isn't grading your reason. They're asking one question: will this happen again? An explanation answers it. An excuse leaves it open, and an open question about you gets filled with the worst guess.

It's also why a reason works once and then stops working. In the first pipeline review of the quarter, "their legal team was slow" is fair. By the third stalled deal it's an excuse, and your manager is right to hear it that way, because you knew about the legal step and didn't plan for it. Say this instead: "Two deals have stalled at the buyer's legal review. From now on I ask about their legal step on the first call and build it into the close date."

Mostly to protect how you see yourself. Psychologists have a name for it. The APA Dictionary of Psychology calls it the self-serving bias. You take the credit when things go well, and when they don't, you blame outside factors. A sales week hands you plenty of those. The market was flat. The buyer went quiet. Some of them are even true, and that's exactly why they come so easily.

Three more pushes show up when you sell:

• The number is public. Your calls and your target sit on a board or come up in a review, so a miss feels like a verdict on you.
• Honest answers have cost you before, and if the last one got you a lecture, you'll dress up the next.
• It's a habit. "It's been busy" got you through once, and now it comes out before you've thought.

If you run a team, the second push comes from you. The first and third come from the rep, and trying harder won't shift them. What does shift them is an honest answer that's quicker to write than the excuse, and four short lines are quicker than a paragraph of reasons.

Owning a skill or organisation miss works better than denying it, and better than saying nothing. Three papers point the same way.

Peter Kim, Donald Ferrin, Cynthia Cooper and Kurt Dirks ran two studies on repairing trust after an alleged violation, published in the Journal of Applied Psychology in 2004. Trust was repaired more successfully when people apologised for a miss about competence and denied a miss about integrity. It also went better when people had apologised and later evidence showed they were at fault, or had denied it and later evidence showed they weren't. A forgotten follow-up or a late quote is a competence miss. If it was yours, own it. If it truly wasn't, say so plainly and keep the record that shows it.

Ferrin led the same team in 2007 to test what happens when you say nothing at all. In their two lab studies, held in two countries, saying nothing won back less trust than the best answer for each kind of miss, and for a skill miss the best answer was an apology. Their reading: after a skill miss, silence tells the other person nothing about whether you'll do better. Going quiet on a client after a missed deadline is that response.

At Ohio State, Roy Lewicki, Beth Polin and Robert Lount tested how 755 people reacted to apologies built from up to six parts, published in 2016. Of the six, acknowledging responsibility mattered most, and an offer to repair the damage came second. The explanation of what went wrong tied for third with regret and a promise to do better, while asking for forgiveness counted least. People were also less willing to accept an apology for a lack of integrity than for a lack of competence.

So your reason sits in the middle of the list, below your part and your fix. And a made-up reason is the worst trade you can make. A late quote is a competence miss that people forgive, but a reason that turns out to be invented is an integrity miss, and those are much harder to come back from.

Before you send the message or speak in the review, check that your reply has four lines, one sentence each.

1. Say what happened as a fact anyone can check. "I didn't send the quote on Friday." Not "things got on top of me."
2. Your part. "I left it until Friday afternoon." No "but" after it, because a "but" turns the line into a defence.
3. What changes. One action you control. "I'm drafting quotes on the day of the meeting from now on." Not "I'll try harder."
4. When. "You'll have it by 11 today." A fix with no date is a wish.

Add the reason only if it helps the listener plan, and keep it to one sentence. "Our prices changed on Thursday and I waited for the new sheet" helps a client read the quote. A paragraph about your week doesn't help anyone.

Read it back once before you send it. If the reason runs longer than the four lines put together, cut it. Long reasons are where explanations turn into excuses, because the listener has to dig for the part that's yours.

Most sales excuses come down to these six. The right-hand column passes the test.

Look at the missed-target row. It blames the weak leads, because the leads really were weak. An explanation can name what wasn't yours. It just doesn't stop there.

Most of these misses start with a follow-up that had no date. Space them out and script each one with the sales follow-up process, and you'll have fewer misses to explain.

Send it before they chase you. A miss you raise yourself reads as organised. A miss they have to ask about reads as hidden.

If the fix is already done, say so in the same message:

If it isn't done yet, give a time and a backup:

When part of the miss really wasn't yours, such as a supplier delay or a price change from head office, say so in one sentence. Then own the delay if you sat on the news: "The factory pushed delivery back a week. I should have told you on Monday when I heard, not today."

Don't blame a colleague by name to a client. Say "we". They bought from you, and they want to hear that you've got it.

Start with the number. "I made 62 calls against a plan of 100" is something your manager can check, and being checkable is what makes the rest believable. "It's been a slow week" asks them to take your word for it.

Then run the four lines on the number. If you don't know where the week went, find out before you speak. Count your calls and follow-ups by day. A gap usually has a shape, like two lost mornings or follow-ups that stopped on Wednesday. Naming the shape is what turns "slow week" into an explanation.

Then put line four's date somewhere it will nag you. In ActivityTracker, every contact record carries a follow-up date, and once that date passes, the badge on the contact's card counts the days overdue. The promise in your explanation stops being a note in your head.

If the same miss keeps coming back month after month, read the sales accountability guide. It checks the numbers every Wednesday, so a dip gets fixed midweek before it turns into a miss on the 30th.

Your reps learn what to say from how you react. Call every reason an excuse and they'll stop giving reasons, and you'll hear about misses on the last day of the month.

So ask for the four lines instead of judging the first one:

• What happened? Ask for the fact, not the feeling.
• What part was yours? Accept a small one. It still counts.
• What will you change? One action, and agree that it's theirs to do.
• By when? Write the date down where you'll both see it next week.

Open with the week, not the person. "Calls were 40 short this week. What got in the way?" gets an answer. "Why didn't you make your calls?" gets an excuse, because you asked for a defence.

Check the date at the next 1:1. The one-on-one meeting template has room for it. In ActivityTracker, each rep's 1:1 notes stay on their page as one running history, and the action items you assign land in their task list, so last week's fix is the first thing you both see.

When a rep's reason really is outside their control, say so out loud. Not every miss has a part to own beyond raising it early. Treat real outside factors as excuses and the team learns to hide them, which is how a slipping deal reaches the monthly performance review as a surprise.

Usually it's the order. When the reason comes first and runs long, the listener decides you're defending yourself before you reach your part. Flip it: your part and the fix first, the reason last, in one sentence.

Two more things trip people up:

• Answering a question that wasn't really a question. "Why is this late?" from an annoyed client often means "I'm annoyed." A detailed answer to the literal question sounds like an alibi. Start with "You're right, it's late, and that's on me," then answer it.
• Flat or very detailed delivery. If you're neurodivergent, or you're someone who explains everything in full, honest reasons can come out sounding like a list of alibis. Write the four lines down before the call and say them in order. The structure does the work your tone isn't doing.

And if someone has decided in advance that every reason you give is an excuse, no wording fixes that. Put your explanation in writing, keep your records, and let the dates you hit do the arguing for you.

Pick the one promise you let slip this week, like a callback or a quote you meant to send. Write the four lines: what happened, your part, the change and the date. Send it before noon today, before they chase you. Then put the date where you'll see it, and hit it.

• Merriam-Webster, Excuse (noun), read 28 October 2026
• Merriam-Webster, Explanation, read 28 October 2026
• APA Dictionary of Psychology, Self-serving bias, read 28 October 2026
• Kim, Ferrin, Cooper and Dirks, Removing the shadow of suspicion: the effects of apology versus denial for repairing competence- versus integrity-based trust violations, Journal of Applied Psychology, 2004 (abstract), read 28 October 2026
• Ferrin, Kim, Cooper and Dirks, Silence speaks volumes: the effectiveness of reticence in comparison to apology and denial for responding to integrity- and competence-based trust violations, Journal of Applied Psychology, 2007 (abstract), read 28 October 2026
• Ohio State News, The 6 elements of an effective apology, according to science (Lewicki, Polin and Lount, Negotiation and Conflict Management Research, 2016), read 28 October 2026