Give a Work Update in English: Progress, Problems and What Happens Next
Practise giving a work update in English: say what changed, name the blocker and its effect, explain what happens next and ask for support only if you need it.
Say what changed, name the blocker and its effect, state the next move, then say whether you need support.
“I had three meetings, sent six emails and updated the spreadsheet” proves you were busy. It does not prove the project moved.
Update the state, not the story: Progress → Blocker → Next → Need.
Progress means what changed
Cambridge English progress-meeting material foregrounds achievements and progress. In a spoken update, the useful question is not “What did I do?” but “What is different now?”
Original practice example
The first draft is complete, and I sent it for review this morning.
This reports a changed state: the draft moved from in progress to complete and under review.
Useful when your work has reached a clear milestone.
Progress job: state change.
Replace the draft/review details with one real milestone from your work.
Explore more language-learning guides in Media-Based Language Learning.
Name the blocker and what it changes
British Council workplace material includes workload, deadline and dependency problems. A useful blocker is specific enough that the listener can understand the effect.
Original practice example
I’m waiting for the client’s data, so I can’t start the final test yet.
The blocker is the missing data; the effect is that final testing cannot start.
Useful when progress depends on an external input.
Blocker job: problem + effect.
Name one blocker and add what it currently prevents or changes.
Say what happens next—even if the blocker remains
A blocker does not always mean “nothing can happen”. State the next action you still control.
Original practice example
While I’m waiting, I’m preparing the remaining test cases.
The sentence moves from dependency to an action the speaker can still take.
Useful when one part is blocked but other useful work can continue.
Next job: controlled next action.
Say one next step that does not depend on the blocker disappearing.
Be explicit about what you need
Sometimes the update needs a decision or input. Sometimes it does not. Make that state visible instead of leaving the listener to guess.
Original practice example
I need the client to confirm the data by Wednesday if we want to keep the current schedule.
The sentence names the dependency and keeps the schedule claim conditional rather than guaranteed.
Useful when timing depends on somebody else’s input.
Need job: dependency + condition.
Replace the client/data/deadline details with a real dependency.
Original practice example
I don’t need anything from the team right now; I’ll flag it if that changes.
The speaker closes the update by making the absence of a support need explicit.
Useful when the update is informational and no action is required from others.
Need job: no support required.
Practise one version that asks for help and one version that explicitly says no help is needed.
Update Compression Lab
Turn a messy activity list into a decision-useful status update.
Messy input
Three meetings, reviewed feedback, finished first draft, sent it for review, client data still missing, final testing depends on data, test cases can be prepared now.
See one compressed update
“The first draft is complete and is now under review. I’m still waiting for the client’s data, so final testing can’t start yet. While I’m waiting, I’m preparing the remaining test cases. I’ll need the data confirmed by Wednesday if we want to keep the current schedule.”
Correction lab: keep the update accurate
“I am waiting the client’s data.”
Classification: wrong in standard English.
What a listener will probably understand: the speaker is waiting for data from the client.
Likely learner intent: explain a blocker.
Natural alternative: “I’m waiting for the client’s data.”
Context note: use wait for + noun.
“We will definitely finish on Friday.” when client data is still missing
Classification: grammatically valid but contextually overcertain.
What a listener understands: Friday completion is guaranteed.
Likely learner intent: sound confident about the schedule.
Natural alternative: “We can still finish on Friday if the data arrives by Wednesday.”
Context note: keep uncertainty visible when the outcome depends on an unresolved condition.
“There is a problem.”
Classification: grammatically valid but too vague for a useful work update on its own.
What a listener understands: something is wrong.
Likely learner intent: report a blocker.
Natural alternative: “The client data is still missing, so final testing can’t start yet.”
Context note: useful blocker language names both the issue and its effect.
“I had three meetings this week.”
Classification: grammatically valid, but it reports activity rather than progress.
What a listener understands: the speaker attended three meetings.
Likely learner intent: show that work moved forward.
Natural alternative: state what changed because of those meetings.
Context note: activity can be relevant, but it is not automatically evidence of progress.
The 30-second update
Use four sentences only: Progress → Blocker → Next → Need. If one category does not apply, say so briefly instead of inventing content.
Update the state, not the story
A useful work update is not a diary. Tell people what moved, what is stuck, what you will do next and whether you need anything from them. That is usually enough to make the next conversation much easier.