How to give a weekly status update in English
Reviewed 19 Sept 2026
A weekly update is the most common speaking task at work and one of the easiest to get wrong. Most people tell the story of their week in the order it happened. The listener wants something different: where things stand, what is in the way, and what happens next.
You do not need better vocabulary for this. You need an order that puts the conclusion first and a habit of naming dates and owners instead of saying that things are going fine.
The structure: done, blocked, next
- Headline
One sentence on where the work stands: on track, behind, or finished. Say this before anything else.
- Done
The one or two results that matter to the listener. Results, not activity: “the import now handles 50,000 rows”, not “I worked on the import”.
- Blocked
What is slowing you down, who owns it, and since when. If nothing is blocked, say so in four words and move on.
- Next
What you will finish by the next update, with a date. End with any decision or help you need from the listener.
Before and after
“So this week I was mostly working on the reporting thing, and, um, Monday I started with the export but then there was an issue with the data so I talked to Priya, and then Wednesday we had the planning so I lost some time there, but basically it's going okay I think, and next week I'll continue with that.”
- The status (“going okay I think”) comes last and is hedged, so the manager still does not know if the work is on track.
- It follows the calendar, Monday then Wednesday, instead of what matters.
- “An issue with the data” and “continue with that” give no owner, no date and nothing the manager can act on.
“The reporting work is on track for the 28th. This week I finished the export, and it now handles the full customer file. One blocker: the March data has duplicate rows. Priya's team owns the fix and expects it on Thursday. Next week I'll build the summary view and show it to you on Friday. I don't need anything from you yet.”
Phrases you can use
- “The short version is that we are on track for the 28th.”
- “We are about three days behind, and here is why.”
- “This is finished. Two small things are left.”
- “The main thing I finished is…”
- “That means the team can now…”
- “The number that matters here is…”
- “One thing is slowing us down:…”
- “It is with the data team, and they expect to fix it by Thursday.”
- “If that slips, the launch date moves by the same amount.”
- “By next week I will have…”
- “The one decision I need from you is…”
- “Nothing needed from you at the moment.”
Common mistakes
Drop the days of the week. Sort by importance to the listener, not by when it happened.
Replace “I worked on” with what is now true that was not true last week.
“Should be fine, I think” makes a manager worry. Give a date and the one condition it depends on.
If you need a decision, say it as its own sentence at the end, not inside a longer one.
A ten-minute drill
- Write four words on a note: headline, done, blocked, next. No sentences.
- Record a 60-second update on your real week using only that note.
- Listen once. Check that the first sentence tells the listener where things stand, and count the dates you named.
- Record it again with one change only.
Questions people ask
How long should a weekly update be?
For a one-to-one, 45 to 90 seconds before questions is enough for most roles. If your manager wants detail, they will ask, and answering a question is easier than guessing what they want.
What if nothing much happened this week?
Say so plainly, then say why and what changes next week: “Little visible progress this week because the review took three days. The build starts Monday.” A short honest update builds more trust than a long vague one.
Should I mention problems I already solved?
Only if the listener needs to know: for example, the problem could return, or it cost time that moves a date. Otherwise leave it out.