How to Tell Your Manager About a Mistake or Delay in English

You realise you have made a mistake, or a task is going to be late, and your stomach drops (an idiom for a sudden feeling of worry). So you wait until it is fixed, or send a short, vague message. If you are learning how to tell your manager about a mistake, this is very common, and it is usually about timing and structure, not your English level.

Why telling your manager about a mistake feels so hard

Here are three common reasons people hold back.

Worrying about how it will look

Many people worry a mistake will make them look less competent, especially when they already work hard to prove themselves in a second language.

Softening the message too much

Soft words like “a small issue” or “might be a bit late” can hide how serious a problem is, like calling a two-week delay “a small delay”.

Waiting until you have a solution

Wanting to fix a problem first comes from a good place, but waiting often makes it bigger: your manager loses time to adjust plans.

Why early, clear bad news builds trust

In many Western workplaces, managers prefer “no surprises”: they want to hear about problems early, not be surprised later. Reporting a problem early and clearly is often seen as ownership, which means taking responsibility for your work. For a related situation, see How to Say No to a Deadline Without Sounding Difficult.

A real story: the engineer who waited too long

Steve once coached a software engineer on an integration project for an important client. A week before the deadline, he realised a change on the client’s side would delay his work by several days. He tried to fix it alone first, and in the daily standup only said there “might be some small issues”. Two days before the deadline, his manager heard about the delay from the client. The delay was manageable, the manager said, but hearing about it so late was a real problem.

Steve saw two things: the engineer waited for a full solution before reporting, and softened the message until it did not sound serious. His work was good; the problem was timing and clarity.

They practised a simple bad-news structure: main news first, clear words instead of “maybe”, and speaking up early.

Months later, on a different project, he hit another delay. He told his manager that day, with a clear explanation and a plan. His manager thanked him for the early warning, and they agreed a new date with the client in good time.

Steve, AptSpeak’s coach, puts it this way:

“People often think the mistake is the problem. Usually, the real problem is the silence around it. Managers can handle bad news. What they find hard is hearing it late, or not understanding it when they do hear it. When you say it early and clearly, with a plan, you build trust, even on a bad day.”

— Steve, AptSpeak coach

A simple structure for telling your manager about a mistake or delay

To deliver bad news at work, use this four-part formula: What happened → The impact → The fix → The next step. Always put the main news in your first sentence. If you do not have a full fix yet, say what you are doing to find one.

A software engineer reporting a bug:

“I need to flag a bug that reached customers this morning: some users can’t download invoices. I’m testing a fix and will update you by 2 p.m.”

An operations coordinator reporting a delayed shipment:

“I wanted to let you know early: the client’s shipment will be three days late due to a supplier problem. I’m checking if our own stock can cover part of it, and I’ll update you by 5 p.m.”

Too vague, too dramatic, or clear?

Aim for the middle.

A mistake in a report

Too vague: “There might be a small issue with the report.” Too dramatic: “I’ve ruined the whole report, I’m so sorry.” Clear and calm: “I found an error in yesterday’s figures. A corrected version is coming by 3 p.m.”

A delayed release

Too vague: “The release could be a bit late.” Too dramatic: “The release is a disaster.” Clear and calm: “The release will move from Friday to Tuesday to fix two bugs.”

A late supplier

Too vague: “We have some supplier challenges.” Too dramatic: “The supplier has let us down completely.” Clear and calm: “The supplier will deliver five days late. I’m checking other options today.” Useful phrases for delivering bad news at work

Pick the ones that feel natural.

Starting the conversation

To flag something means to point out a problem so others notice it.

“I need to flag something.” “I wanted to let you know early that…” Explaining what happened and owning your part “I made a mistake in…” “I should have raised this earlier.” Describing the impact and the fix “This means the release will move from Friday to Tuesday.” “Here’s what I suggest…”

To apologise for a mistake at work, say “I’m sorry about this” once, sincerely. Then move to the fix: repeating “sorry” makes it about your feelings, not the solution.

Saying it in person or in writing

Raise serious problems in a quick call first, then confirm in writing. Small issues can go in a message. Here is a short project delay email:

Subject: Q3 dashboard: new date Wednesday

Hi Anna,

As discussed, the Q3 dashboard will be ready on Wednesday, not Monday, because the finance data arrived late. I’ve started the other sections and will update you on Monday.

Best,

Wei

Need to explain it to a client too? See How to Explain a Technical Problem to a Non-Technical Client.

Frequently asked questions Should I tell my manager about a mistake before I fix it?

Usually, yes. Tell them as soon as you understand it, and say how you are working on a fix.

Should I tell my manager in person or by email?

Start with a quick call for serious problems, then follow up in writing. Small issues can go in a message.

What if the delay is not my fault?

Describe the cause factually, without blaming anyone: “The supplier’s delivery is five days late,” not “The supplier ruined our plan.” Then focus on the impact and next step. See also How to Push Back at Work Without Sounding Rude.

Practise difficult conversations with an AptSpeak coach

At AptSpeak, we offer communication training for international professionals and corporate teams. Steve, our interview and communication coach from Arizona, USA, has 13 years of experience teaching and mentoring professionals and has coached hundreds of people. He helps you practise difficult conversations with managers and clients, such as reporting problems, delays, and mistakes, with clear, constructive feedback. His focus is building your confidence, not just your grammar. You can start with a trial session.