How to Give a Clear Update in a Team Meeting (With Examples)

Give your update in three parts: what you finished, what you're doing next, and what's blocking you or what you need, in that order and in under 60 seconds. Lead with the one thing the team most needs to know, use names and dates instead of vague progress words, and say blockers as a clear request so someone can act on them.

The three-part update

PartThe question it answersLengthExample
DoneWhat changed since last time?1–2 sentences"I finished moving the blog pages to the new site."
NextWhat will be different by next time?1 sentence"Today I'm starting on the product pages."
Blocked / needWhat's in the way, and who can help?1 sentence, or "nothing blocking""I need the new product photos from Ana by Thursday."

That's often 20–40 seconds. In a daily standup, it should be. In a weekly meeting, you might have up to two minutes, but the same order still works: the extra time goes on one important detail, not on more items.

Lead with what matters most

If one thing on your list affects other people, say it first. This is the idea behind BLUF, bottom line up front.

"Main thing: the launch date is at risk, because the payment provider hasn't approved us yet. Otherwise, I finished the checkout tests, and next I'm writing the help articles."

The team hears the one thing they need in the first five seconds, even if their attention drifts after.

Before and after: rewrites

Vague words like "working on", "progressing" and "looking into" tell people nothing. Replace them with a fact, a name or a date.

BeforeAfter
"I'm still working on the report, it's going well, should be done soon hopefully.""The report is drafted. I'm checking the numbers with finance today and will send it Wednesday."
"I had a lot of meetings this week, and did some stuff with the client, and some emails.""I met the client twice. They've agreed the new scope, and I'll send the revised quote tomorrow."
"I'm kind of stuck on the API thing, not sure what's going on, I've been looking into it.""I'm blocked on the API: it rejects our test requests. Raj, could you look at it with me for 15 minutes after this?"
"Nothing much to report.""No change on the vendor contract; it's with legal. Next, I'm starting the Q4 budget draft."

Examples by role

Made-up examples, each under 40 seconds spoken.

Software developer at standup:

"Yesterday I fixed the login timeout bug; it's in review. Today I'm picking up the password reset ticket. No blockers."

Marketing coordinator, weekly meeting:

"The October newsletter went out Tuesday. Open rate was about the same as September. This week I'm drafting the webinar invitation. I need the speaker's bio from Leo by Friday to keep the send date."

Nurse at a shift huddle:

"Bed 4 has a new fall-risk assessment, so please check in hourly. Bed 7 is due for discharge after the 2 p.m. review. I'm short one set of dressing supplies for the afternoon; I've asked stores."

Project manager, weekly status:

"We're on track for the March 3 go-live, with one risk. Training has slipped a week because the trainer is off sick. Next, I'm confirming a replacement by Thursday. If that doesn't work, I'll bring options to this meeting next week."

Saying a blocker so someone acts on it

A blocker said vaguely gets a nod and no help. Say:

  1. What's blocked. "The data migration."
  2. Why. "We don't have access to the old database."
  3. Who can unblock it, and by when. "Maria, can you approve the access request today?"

If you don't know who can help, ask: "Who's the right person for database access?"

Sharing bad news in an update

Don't bury it in the middle. Say it first, say what you're doing about it, and say what you need.

"Bad news first: the supplier has delayed the shipment by two weeks. I've asked for partial delivery, which would cover the first two stores. I'll know by Wednesday. If that's a no, we'll need to decide whether to move the opening."

Keep your tone flat and factual. The team takes its cue from you.

When someone asks a follow-up

Answer in one sentence, then stop. If it needs a longer discussion, offer to take it offline: "Short answer: yes, we can. Happy to go through the details after the meeting." This keeps standups short and respects everyone else's time.

How to prepare in two minutes

  1. Before the meeting, write three lines: done, next, blocked.
  2. Underline the most important one and move it to the front.
  3. Replace any vague word with a fact or a date.
  4. Say it out loud once, quietly. If it takes more than 60 seconds, cut.

If speaking up in meetings is hard for you, Speaking Coach's "Give a clear work update" scene lets you practice with a manager who follows up on what you said. More general advice is in how to speak up in meetings.

Questions people ask

How long should a standup update be?

About 30–60 seconds per person. If something needs longer, flag it and discuss it after the standup with the people involved.

What do I say if I did nothing new?

Say what's still in progress and when it will change: "Still on the budget draft; I'll have it ready Thursday." That's useful information.

Should I list everything I did?

No. Mention only what affects the team or what they need to know. Your full task list is for your own notes.

How do I give an update when I'm nervous?

Write the three lines down and read them if you need to. A clear, short update read from notes is better than a long one improvised. The guide on stopping rambling helps too.

How do I update my boss one-to-one?

Use the same order, but start with anything they need to decide or know about first, and bring options, not just problems.