← All playbooks
Tier 4: Total Clusterfuck

What do you do if you told your manager something was finished and it wasn't?

The short answer

Correct it before the next status meeting, not during it. Say plainly that your earlier update was wrong, give the true current state, and give a date you're confident in rather than the one you wish were true. Then over-communicate for two weeks — trust is rebuilt by frequency, not by eloquence.

What's actually at stake

  • 01One wrong status is a mistake; discovering it independently makes it a credibility problem.
  • 02Optimistic dates are what created this, so a conservative date is the actual apology.
  • 03Two weeks of unprompted updates resets the default assumption about your reporting.

Do

  • · Correct it proactively and in writing.
  • · Give a date with buffer you can beat.
  • · Send unprompted progress notes until trust resets.

Don't

  • · Do not blame 'scope changes' unless you can name them.
  • · Do not bury the correction in a long update.
  • · Do not let it be discovered in a demo.

A draft you can send now

Correcting my last update: [item] is not done — it's at [true state]. I called it early and I shouldn't have. Realistic completion is [date], and I'll send you a short note every [Tue/Thu] until it lands.
Tailor this to my exact disaster →

Questions people actually ask

What if the deadline was impossible anyway?
That's a separate conversation and it lands much better once your reporting is accurate.
How bad is this?
Recoverable once. Career-defining if it happens twice on the same project.
Should I tell the client too?
If they were told the same thing, yes — and before your manager has to.

Take it further

Related incidents

All CYABot tools →