Pro free for 30 days.No card.Start free →

Project Status Meetings and Updates: How to Run Them Well

Most status meetings waste time. Learn how to decide between a meeting and a message, run a 15 to 30 minute agenda focused on blockers and decisions, assign owners and dates, and send short written updates that clients and managers will read.

By WorkBOS Content Desk5 min read
Notebook and pen on a table during a team meeting (Photo by sarahblocks on Pixabay)
Photo: sarahblocks / Pixabay

Few things drain a small team faster than a status meeting where everyone reads out what they did last week while the rest check their phones. The meeting runs long, nobody decides anything and the real problems come up in the corridor afterwards.

A good status routine does the opposite. It takes minutes, surfaces problems early and leaves everyone clear on what happens next. This guide shows how to run status meetings and written updates that small teams and clients actually value.

Decide what the meeting is for

University meeting guidance from North Dakota State University suggests deciding whether a meeting is meant to decide, discuss or inform, and notes that if it is only informing, an email may be enough. That is the single most useful test for status updates.

Meeting or message?

| Situation | Best format | |---|---| | Routine progress, nothing blocked | Written update in chat or the project | | A decision is needed from several people | Short meeting | | A problem needs discussion | Short meeting, with the right people only | | Client wants reassurance | Brief written summary, plus a call at milestones |

Duke University's project guidance makes a related point about channels: short-term general updates work well asynchronously, long-term reference material belongs in documents, and real-time conversation is best for building relationships and resolving problems. Use the meeting for talking, not for reading out lists.

Build a simple status agenda

For a weekly team check of 15 to 30 minutes, a structure like this works:

  1. Wins and finished work (2 minutes). Only what was completed.
  2. Blockers and risks (8 minutes). The main reason to meet. What is stuck and who can unblock it?
  3. Decisions needed (5 minutes). Get them made or assign an owner and a date.
  4. Next week's priorities (3 minutes). Top items per person.
  5. Recap (2 minutes). Read back decisions and actions.

NDSU's example for a 30-minute meeting also allots time to each item, including follow-up on previous actions, discussion, decision and a closing check. Time boxes keep you honest.

Prepare in advance

  • Send the agenda early with a clear question for each item.
  • Ask people to update their tasks before the meeting, so the board already shows progress. Nobody needs to narrate what is visible.
  • Invite those who decide or are affected; send a summary to everyone else.

Roles that keep it moving

NDSU recommends assigning a note taker and having a facilitator who stays neutral and keeps discussion on task. In a small team, rotate these so it is not always the owner.

  • Facilitator: keeps time, redirects side conversations, makes sure quieter people speak.
  • Note taker: records decisions and actions, not a transcript.
  • Everyone: comes with updates already entered and focuses on blockers.

The same guidance lists common problems to watch for: circular discussion, one person dominating, silence and inability to reach agreement. If a topic goes round in circles, park it and book a separate conversation with the two or three people who matter.

End with owners and dates

A meeting without actions is a conversation. Before closing, make sure every action has:

  • A named owner.
  • A due date.
  • A clear definition of done.

NDSU advises assigning owners and deadlines before closing and sending a summary of decisions and action items within a couple of days, while details are fresh. Start the next meeting by checking those actions first.

Write status updates people will read

For clients, managers and absent teammates, a short written update beats a long meeting. Keep a consistent format so readers know where to look. A reader who gets the same five headings every week learns to scan for the one that matters, and soon only reads the "at risk" line when something is wrong.

A five-line update template

  1. Overall status: on track, at risk or off track, in one word.
  2. Done since last update: two to four bullets.
  3. Coming next: two to four bullets.
  4. Risks and blockers: what you need and from whom.
  5. Budget and dates: spent versus planned; any change to milestones.

Be honest about "at risk". Clients forgive early warnings far more readily than late surprises. If a date will slip, say so as soon as you know, with the reason and your proposed fix.

Match frequency to the project

  • Small, fast project: short update twice a week.
  • Typical project: weekly.
  • Long, slow-moving project: every two weeks plus milestone reviews.

Common mistakes

  • Reading out task lists. If the board is current, skip it and discuss blockers.
  • Inviting everyone, every time. Only invite people who decide or are affected.
  • Hiding bad news. Problems found early are cheap; late ones are not.
  • No written follow-up. Memory of who agreed to what fades within days.
  • Never evaluating the meeting. NDSU suggests asking whether a meeting was worth holding. If not, shorten or cancel it.
  • Status theater. If nobody acts on the update, stop sending it.

Status updates in WorkBOS

WorkBOS keeps tasks, owners and due dates in projects, so progress is visible before a meeting starts. You can chat with your team and use the calendar for scheduling, and compare project budgets against actuals for the budget line of your update. For client-facing projects, a branded client portal can give customers a place to see shared information. Automations can help with routine, repeatable steps. Documentation is in the docs, short lessons are in the Academy and plans are on the pricing page. Browse everything under features. A solid project plan makes status updates much easier, because milestones and owners are already defined.

Frequently asked questions

Q: How long should a weekly status meeting be? A: Fifteen to thirty minutes is enough for most small teams. If it regularly runs longer, move detailed discussions into separate meetings with only the people who need to attend.

Q: Can we replace status meetings with written updates? A: Often yes, when work is on track. Keep a meeting for decisions, blockers and relationship-building, and use written updates for routine progress.

Q: What should a client status update include? A: Overall status, what was completed, what is next, risks or blockers, and any change to budget or dates. Keep it short and consistent.

Q: How do I stop one person dominating? A: Use a facilitator, time boxes and a round where everyone speaks briefly. Park long debates for a separate conversation.

Q: Who should take notes? A: Rotate the role. Record decisions and action items with owners and dates, then send them out within a day or two.

Sources are linked in the text above: North Dakota State University, Duke University Bass Connections.

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →