Status Update Meeting Template

A status update meeting keeps a project or initiative honest. It is a focused checkpoint to compare progress against the plan, flag risks early, and make the decisions that keep work moving. This status update meeting template helps you run it in 30 minutes instead of letting it sprawl into a recurring time sink.

When to use it

Use it for any project with a deadline, a budget, or stakeholders who need visibility. It works for software releases, marketing campaigns, operational rollouts, and anything else where progress and risk need a regular pulse. Skip it when a written update would do the same job.

Who attends

The project team plus the stakeholders who need the information or must make decisions. Keep the room tight. People who only need to be informed can read the recap instead of attending live.

How to run it

Start by restating the objective and timeline so progress has a yardstick. Walk through what is done, in progress, and not started against the plan, keeping it factual. Spend real time on risks and blockers, deciding how to respond rather than just noting them. Raise any decisions that need stakeholder input, then close with clear next steps, owners, and the date of the next update.

Facilitator tips

• Send the data in advance so the meeting is for decisions, not reading slides aloud.
• Use a simple red, yellow, green health signal so status is scannable.
• Focus on risk and decisions, the two things a live meeting is actually good for.
• Capture decisions, not just discussion, so they are not relitigated next week.

Common mistakes

• Reading a status report out loud that everyone could have read faster on their own.
• Glossing over risks to keep the update positive, then being surprised later.
• Inviting people who only need to be informed, not consulted.
• Ending without owners, so progress stalls until the next meeting.

Track project status and risks in one place. Run it in OrgTP.