Project Status Meeting Agenda
A project status meeting is a recurring 30-minute check-in, usually weekly, where the project lead and workstream owners review progress against milestones, risks and the decisions the project needs. This project status meeting agenda skips updates that could be written down and ends with decisions made and an owner for every next step.
Agenda
30 min · 5 parts
- 0:00Wins3 minWhat finished since the last meeting
- 3:00Milestones8 minEach milestone: on track, at risk or late
- 11:00Risks and blockers8 minNew and changed risks, blockers and what we're doing about them
- 19:00Decisions needed6 minWhat needs a decision, from whom and by when
- 25:00Action items5 minAn owner and a date for each action, and last week's actions checked
Free to start. Guests join from a link, no account needed.
- Length
- 30 min
- How often
- Weekly on most projects, every two weeks on long and steady ones, and more often in the weeks before a launch.
- Who attends
- The project manager and workstream leads, plus the sponsor or stakeholders when a decision needs them.
- You leave with
- A shared view of where the project stands, decisions made or escalated, and an owner and date for every next step.
The agenda, part by part
How to run a project status meeting
1. Wins
3 minName what finished since last time, in one line each. On a long project, seeing progress keeps morale up, and it shows stakeholders what changed. Keep it to finished work, not activity.
Ask: What did we finish this week that we can show?
2. Milestones
8 minGo through each milestone with a simple status: on track, at risk or late. Ask leads to share a written update before the meeting, so the call covers only what changed or slipped. For anything at risk, ask what would bring it back on track and who needs to know.
Ask: Which milestone are you least confident about, and why?
3. Risks and blockers
8 minReview the risk list: what's new, what got worse and what can be closed. Blockers that need help from outside the team go here too. Agree on a next step and an owner for each, and move long problem-solving to a separate conversation.
Ask: What has changed since last week that could put a date at risk?
4. Decisions needed
6 minList the decisions the project is waiting on, who can make them and when they are needed. Make the ones the people in the room can make, and escalate the others with a clear recommendation. Write each decision down so it doesn't get reopened.
Ask: Which decision, made today, would unblock the most work?
5. Action items
5 minRead back each action with one owner and a due date. Start the next meeting by checking them, so the list stays honest. Send the notes and the updated status the same day.
Ask: Who owns this, and when will it be done?
Project status meeting questions
- What did we finish since the last meeting?
- Are we on track for the next milestone?
- What's at risk, and what would bring it back on track?
- What are we waiting on from other teams?
- Has anything changed in scope, budget or dates?
- Which decision do we need, and from whom?
- What should stakeholders hear from us this week?
Example: a weekly status meeting before a launch
A team is four weeks from launching its online store in two new countries.
Notes
- Wins: payment provider approved for both countries.
- Milestones: translations on track; product photos for the new catalog at risk.
- Risk: the legal review of the terms may take two weeks instead of one.
- Decision: launch both countries together or a week apart. The sponsor chose a week apart.
- Last week's actions: four of five done; the returns page moved to next week.
Action items
- Hana: get the remaining product photos approved, by Thursday.
- Luis: ask legal for a firm review date, by tomorrow.
- Sophie: update the launch plan with the new dates, by Friday.
Ways to adapt it
Written updates, shorter meeting
Keep the same weekly status meeting agenda, but ask leads to post a written update the day before. The meeting drops to 15 minutes and covers only risks and decisions.
Stakeholder status meeting
For sponsors and executives, meet every two weeks or monthly. Send a one-page status report first and spend most of the time on risks and decisions that need their help.
Several projects at once
Run one review for the whole portfolio. Give each project a short slot, discuss only what's at risk or needs a decision, and use one status scale that everyone applies the same way.
Common mistakes
Going around the room for updates.
Instead: Collect updates in writing beforehand and talk only about what changed, slipped or needs help.
Calling everything on track until it's suddenly late.
Instead: Agree on what at risk means, and thank people who raise problems early.
Discussing problems without deciding anything.
Instead: End each risk with a next step, and each decision with a name and a date, or escalate it.
Inviting everyone, every week.
Instead: Invite the people who own milestones or make decisions. Everyone else gets the notes.
Run it in Edworking
Your agenda keeps the meeting on time
Start a video meeting from any template. Edworking turns the agenda into the structure of the call, so nobody has to watch the clock.
Live agenda
A timer for every part
Everyone sees the agenda and how long is left in each part, with a clear moment when the meeting moves on.
AI notes
Notes that follow the agenda
AI takes the notes part by part and writes the summary and action items when the call ends.
Tabs in the call
Your work on screen, no sharing
Open docs, tasks and files as tabs in the call. Everyone sees the same thing without anyone sharing a screen.
Guests
Anyone can join from a link
Free to start. Clients, candidates and guests join from a link, with no account needed.
Frequently asked questions
30 minutes for a weekly meeting on most projects. If updates are shared in writing first, 15 to 20 minutes can be enough.
Weekly works for most active projects. Move to every two weeks on long, stable projects, and to short daily check-ins in the last days before a launch.
Wins, progress against milestones, risks and blockers, decisions needed and action items with owners. Keep the updates short so most of the time goes to risks and decisions.
A status report is a written summary of progress, risks and dates. A status meeting is for what needs a conversation: risks, trade-offs and decisions. Sending the report first keeps the meeting short.
Skip updates nobody needs to discuss, start on time and end early when there's nothing to decide. Rotate who leads it now and then. A status meeting that produces decisions is one people want to attend.
More meeting agenda templates
Project Kickoff Meeting Agenda
Start a project with a shared goal, a clear scope, named owners and a first deadline.
7 parts
Weekly Team Meeting Agenda
Wins, key numbers and the top three priorities for the week, with blockers cleared in 30 minutes.
6 parts
Daily Standup Meeting Agenda
A 15-minute daily check-in on what moved, what's next and what's in the way.
3 parts