Apology FRAMEWORK

People often say “I’m sorry for that” or “I’m sorry for everything” without naming the behaviour.
It’s easier, but it hides the real issue.

Name it.
Identify the specific behaviour.
No vague “sorry” - be precise.

I’m sorry I didn’t inform you…
I’m sorry I kept you waiting…

Own it.
Show that you understand the impact on the other person.

…I realise this held you back.
…I know this meant losing the session.

Drop the excuses.

I was overwhelmed. Things got crazy.

Owning the impact is what actually repairs trust.

Show what happens next.
A real apology ends with direction.
​No action, no repair.

Fix it.
State the forward action — what you’re doing now or next time.

…I’ll update you earlier next time.
…Here’s the corrected version.

​Scenario
You were supposed to send a report to a colleague earlier today.
They reminded you several times.
You kept thinking you’d do it “in a moment,” but the day exploded, you got buried, and you completely forgot.
Now it’s late afternoon.
You finally notice three missed messages from them: short, polite, increasingly urgent.
You know they were waiting for your file to move their part of the project forward.
You need to apologise. Properly.

Apology (Using Name it · Own it · Fix it)

Name it.
“I’m sorry I didn’t send the report as agreed.”
(No excuses. No softeners. You name the behaviour directly.)

Own it.
“I realise this held you up and created unnecessary pressure on your side.”
(This shows you understand the impact; not your chaos.)

Fix it.
“I’ve attached the report now, and I’ll set a reminder so this doesn’t happen again.”
(This shows forward direction and reliability.)