Free Project Status Meeting Agenda Template
A project status agenda that keeps stakeholders informed and unblocks the project.
Part of our free meeting agenda templates.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
1.Meeting Information
| Date | {{Date}} |
|---|---|
| Time | {{Start – End time}} |
| Location | {{Location or video link}} |
| Facilitator | {{Facilitator}} |
| Note-taker | {{Note-taker}} |
| Attendees | {{Attendees / required vs optional}} |
Fill this block before you send the invite so everyone knows when, where, and who is expected. Name a facilitator and a note-taker — meetings without both tend to drift.
2.Objectives
- Give stakeholders a clear, honest read on status against the plan
- Get the decisions and approvals the project needs to keep moving
- Agree the next steps and who owns each before the next check-in
State one to three outcomes this meeting must produce — a decision, a plan, an aligned team. If you cannot name an objective, the meeting can probably be an email.
3.Agenda
| Topic | Lead | Time | Type |
|---|---|---|---|
| Status summary: on track / at risk / off track | {{Project manager}} | 5 min | Inform |
| Progress since last meeting & upcoming milestones | {{Project manager}} | 10 min | Inform |
| Risks & issues — what could derail us | {{PM / owners}} | 10 min | Discuss |
| Decisions & approvals needed today | {{Sponsor}} | 10 min | Decide |
| Budget & resource check | {{PM / Finance}} | 5 min | Inform |
| Next steps & action items | {{Project manager}} | 5 min | Decide |
Give every item an owner, a time box, and a type — Inform, Discuss, or Decide — so people come prepared and you protect time for the decisions that matter. Put the most important item first, not last.
4.Decisions & Notes
| Topic | Decision / key note | Follow-up |
|---|---|---|
| {{Decision needed}} | {{What was decided}} | {{Follow-up}} |
Capture decisions as they happen, in the room. A one-line record of what was decided prevents the same debate from reopening next week.
5.Action Items
| Action | Owner | Due date |
|---|---|---|
| {{Action — start with a verb}} | {{Owner}} | {{Due date}} |
| {{Action}} | {{Owner}} | {{Due date}} |
Every action needs a single owner and a date — “we” is not an owner. Read these back aloud before you close the meeting so nobody leaves surprised.
6.Parking Lot
- {{Issue raised that needs a separate working session}}
Park anything important that is off-agenda here instead of letting it derail the meeting. Review the parking lot when you plan the next agenda.
7.Next Meeting
| Date & time | {{Date and time}} |
|---|---|
| Focus | {{Main focus for next time}} |
Set the next meeting before everyone leaves — it is far harder to schedule afterward. Note the main focus so the next agenda almost writes itself.
A worked example for a weekly status meeting on a company-wide CRM implementation.
1.Meeting Information
| Date | Tuesday, August 18, 2026 |
|---|---|
| Time | 1:00 – 1:45 PM |
| Location | Conference room + Zoom for the sponsor and partner |
| Facilitator | Dana Reyes, Project Manager |
| Note-taker | Tom Becker, Business Analyst |
| Attendees | Sponsor (VP Sales), Sales Ops, IT, the implementation partner |
2.Objectives
- Confirm whether we still hit the Sep 30 go-live after the data-quality findings
- Get a decision on the billing-integration scope so build can finish
- Approve two extra weeks of partner hours, or agree what to cut
3.Agenda
| Topic | Lead | Time | Type |
|---|---|---|---|
| Status: AT RISK — data quality is worse than expected | Dana Reyes | 5 min | Inform |
| Progress: build 70% done; UAT prep started; migration dry-run done | Dana Reyes | 10 min | Inform |
| Risks: dirty legacy data, billing API gaps, UAT tester availability | Dana / IT | 10 min | Discuss |
| Decision: billing integration — full sync vs read-only for phase 1 | Sponsor | 10 min | Decide |
| Budget: partner hours tracking 15% over; options | Dana Reyes | 5 min | Inform |
| Next steps & action items | Dana Reyes | 5 min | Decide |
4.Decisions & Notes
| Topic | Decision / key note | Follow-up |
|---|---|---|
| Billing integration scope | Phase 1 ships read-only billing sync; full two-way sync moves to phase 2 | Partner to re-estimate the build by Thu |
| Go-live date | Hold Sep 30 but add a one-week hypercare buffer; decide go/no-go at UAT exit (Sep 22) | Dana to update the plan and stakeholders |
| Budget | Approve 80 extra partner hours from contingency to fix data quality | Sponsor approved; Dana to issue the change order |
5.Action Items
| Action | Owner | Due date |
|---|---|---|
| Run the data-cleanup scripts on the top 3 dirty fields | Sales Ops (Priya) | Fri Aug 21 |
| Re-estimate the read-only billing build and confirm the date | Partner (Raj) | Thu Aug 20 |
| Confirm five UAT testers and book the UAT sessions | Dana Reyes | Wed Aug 19 |
| Issue the change order for 80 additional partner hours | Dana Reyes | Wed Aug 19 |
6.Parking Lot
- Reporting-tool retirement after go-live — schedule a separate decision session
- Territory restructure overlap — raise with Sales leadership outside this meeting
7.Next Meeting
| Date & time | Tuesday, August 25, 2026 · 1:00 PM |
|---|---|
| Focus | Data-cleanup results and UAT readiness ahead of the Sep 22 go/no-go |
How it works
- Open with an honest status — on track, at risk, or off track — and progress since last time.
- Walk milestones, risks and issues, then get the decisions and approvals the project needs.
- Agree next steps with an owner and date for each, then download as Word or PDF.
Frequently asked questions
What should a project status meeting agenda include?
A project status agenda should open with a clear status (on track / at risk / off track), then cover progress since the last meeting and upcoming milestones, the risks and issues, any decisions or approvals needed, a budget and resource check, and next steps with owners. This template lays out exactly that flow.
How do you run an effective status meeting?
Lead with the headline status, not a task-by-task dump; focus the time on risks, blockers, and the decisions you need from the people in the room; and end with clear, owned action items. Send a written status update ahead so the meeting is for discussion and decisions, not reading.
What is the difference between a status meeting and a standup?
A status meeting reports progress to stakeholders and sponsors and is where project-level decisions and approvals happen, usually weekly or biweekly. A standup is a short daily sync within the delivery team focused on blockers. Use this template for stakeholder status and the standup template for the daily team sync.
How often should you hold project status meetings?
Weekly is common for active projects; larger or slower projects may do biweekly. Match the cadence to how fast things change and how much decision-making the project needs. Keep it to 30–45 minutes by sending the detailed status in writing beforehand.