Project managers live and die by their communication. A missed update, a vague email, or a poorly worded status report can derail a timeline faster than any technical problem. If English is your second language, the pressure doubles — you are juggling deadlines and language at the same time.
This lesson focuses on one skill that most learners overlook: communicating about project progress clearly and professionally. Specifically, how to give updates, flag delays, and escalate problems without sounding either robotic or catastrophic.
The Lesson: Talking About Progress, Delays, and Problems
Project communication usually falls into three situations:
- Things are going well — you give a routine update.
- Something is slightly behind — you flag it early.
- Something has gone wrong — you escalate.
Each situation needs a different tone and different language. Let’s look at all three.
Situation 1: Routine Status Updates
Keep these factual and structured. A common format is: what is done, what is in progress, and what is next.
“The design phase is complete. We are currently in the testing stage, which is on track for the Friday deadline. Next week, we move into final review.”
Notice the verbs: is complete, are currently in, is on track. These are simple present constructions that feel calm and professional. Avoid saying “we have been doing the testing” when “we are in the testing stage” is clearer.
Situation 2: Flagging a Delay Early
This is where many non-native speakers struggle. They either say nothing until it is too late, or they over-apologise so much that the actual information gets buried.
The structure to use is: acknowledge the issue, give the reason briefly, state the impact, offer a solution or next step.
“I wanted to flag that the supplier confirmation has come in later than expected. This means the installation is likely to be pushed back by two days. We are looking at Tuesday the 14th as the revised date. I will confirm once we have rescheduled with the team.”
Short. Clear. Professional. The manager reading that knows exactly what happened, what the impact is, and what comes next. That is what good project communication looks like.
This kind of structured, real-world English practice is exactly what we work on in daily coaching sessions. If you want to practise these patterns with live feedback, here is how the coaching programme works.
Situation 3: Escalating a Serious Problem
Escalation language needs to be clear without causing panic. Avoid dramatic phrases like “this is a disaster” or “everything has fallen apart.” Use precise, measured language.
“I need to bring a risk to your attention. The third-party API integration has failed quality testing twice, and there is a possibility this will affect the go-live date. I would like to schedule a call this week to discuss mitigation options.”
Key phrases here: bring to your attention, there is a possibility, mitigation options. These signal seriousness without triggering alarm. You are telling the truth, and you are also showing you are in control of the situation.
Common Mistake: Mixing Up Tense When Describing Progress
Here is something that trips up learners at every level. When giving a project update, many people use the present perfect when the simple present is the better choice.
Incorrect: “The testing phase has been completed and we have been moving to the review stage.”
Correct: “The testing phase is complete and we are moving to the review stage.”
The present perfect suggests the action is relevant to now because of how recently it happened. In a status update, you are stating facts about where things stand. Simple present is usually cleaner and more professional in this context.
The exception: use the present perfect when you want to highlight an achievement or a change that affects the current situation. “We have identified the source of the bug, so we can now move forward with the fix.” That works because the discovery directly connects to the current action.
Practice Tips You Can Use Today
- Write a fake status update. Pick any project — a work task, a home renovation, even planning a holiday — and write a three-sentence update using the structure: done, in progress, next. Focus on clean simple present verbs.
- Practise the delay email format. Write a short email flagging a fictional delay. Use the four-part structure: issue, reason, impact, next step. Keep it under 80 words. Short emails get read.
- Record yourself speaking. Read your update or email aloud and record it on your phone. Listen back and notice if you hesitate on any specific phrases. Those hesitation points are exactly where to practise more. Fluency in project meetings comes from repetition, not inspiration.

Leave a Reply
You must be logged in to post a comment.