Playbook › Admit and explain

Editor's example
Your manager stops by your desk. A report you owned is a day late because a data source arrived late, and you didn't flag the delay in time.
This was due yesterday. What happened?

Tone: Polite · Serious advice

○ Replies that work

You're right, it's late. The data came in Tuesday night and I should have flagged it then. It'll be with you by 3 today.
Why it works: Admitting it first, then giving one clear reason and a specific time, gives your manager what they need to plan without hearing excuses.
I'm sorry, I should have told you as soon as I saw the delay. Here's where it stands and what's left.
Why it works: Apologizing for the missing heads-up addresses what probably bothered them most, and offering the status answers their next question before they ask it.
That's on me. Next time something slips, I'll send a heads-up the same day.
Why it works: Taking ownership and naming one concrete habit you'll change shows it won't keep happening, which rebuilds trust faster than a long explanation.

× Replies to avoid

Well, nobody sent me the data.
Even if it's true, leading with blame makes the conversation about someone else and makes you look less reliable.
It's basically done.
Vague reassurance without a time gives your manager nothing to plan around and often means another delay.

Practice prompts