Skip to content
QuietNoteJoin the beta

Project meeting minutes template (Word, free)

Last updated

This project meeting minutes template is built for the recurring status meeting: the one that happens every week for the life of the project. It tracks the same things in the same order each time, so the minutes from week 11 can be laid next to week 10 and the differences are obvious. Status by workstream, milestones with a red, amber or green rating, the risks and issues that changed, change requests, decisions and actions.

Download the Word file, copy the plain text, or read the example first: week eleven of an ERP implementation at a haulage company.

Word file (.docx), free and without signing up. Opens in Google Docs and Pages too.

What’s in the template

The minutes open with these details:

  • Project
  • Meeting (e.g. weekly status meeting no. 11)
  • Date
  • Time
  • Location (or video platform)
  • Chair (project manager)
  • Minutes taken by
  • Present
  • Apologies
  • Reporting period covered
  • Overall project status (green / amber / red)

Then the body follows the meeting in this order:

  1. 1. Review of open actions — Go through the action list by number. Record each as closed, open or carried with a new date. Do not re-discuss closed actions.
  2. 2. Overall status and headline — One paragraph: the overall rating, what changed since last week and the single most important thing the sponsor should know.Status this week (green / amber / red): · Status last week: · Headline:
  3. 3. Status by workstream — One block per workstream. The lead reports; the minutes record progress, plans and help needed, not the discussion.Workstream: · Lead: · Status (green / amber / red): · Progress this period: · Planned next period: · Help needed:
  4. 4. Milestones — Every milestone in the next eight weeks plus any that moved. Baseline date never changes; forecast date does.Milestone: · Baseline date: · Forecast date: · Status: · Comment:
  5. 5. Risks: new and changed — Only risks that are new, have changed rating or have an overdue response. The full register lives elsewhere.Risk no.: · Description: · Change since last meeting: · Owner: · Response:
  6. 6. Issues — Things that have already happened and need resolving. Each has an owner and a target date.Issue no.: · Description: · Impact: · Owner: · Target resolution:
  7. 7. Change requests — Any request to change scope, time or cost, with its status. Record who approves, not just that it was discussed.CR no.: · Description: · Effect on scope / time / cost: · Status (raised / assessed / approved / rejected):
  8. 8. Budget and resources — Spend to date against plan, forecast at completion, and any resourcing gap in the next period.
  9. 9. Decisions — Decisions made in this meeting, and decisions needed from someone outside it, with who and by when.Decision: · Made by: · Decisions required from steering group / sponsor:
  10. 10. Next meeting — Date, time and any change to attendees.

At the end: milestones and risks and issues log and action items, as tables you can keep across meetings.

The template

Download it as a Word file, or copy the text version into your own document.

Project Status Meeting Minutes

Project: 
Meeting (e.g. weekly status meeting no. 11): 
Date: 
Time: 
Location (or video platform): 
Chair (project manager): 
Minutes taken by: 
Present: 
Apologies: 
Reporting period covered: 
Overall project status (green / amber / red): 

1. Review of open actions
   [Go through the action list by number. Record each as closed, open or carried with a new date. Do not re-discuss closed actions.]

2. Overall status and headline
   [One paragraph: the overall rating, what changed since last week and the single most important thing the sponsor should know.]
   Status this week (green / amber / red):
   Status last week:
   Headline:

3. Status by workstream
   [One block per workstream. The lead reports; the minutes record progress, plans and help needed, not the discussion.]
   Workstream:
   Lead:
   Status (green / amber / red):
   Progress this period:
   Planned next period:
   Help needed:

4. Milestones
   [Every milestone in the next eight weeks plus any that moved. Baseline date never changes; forecast date does.]
   Milestone:
   Baseline date:
   Forecast date:
   Status:
   Comment:

5. Risks: new and changed
   [Only risks that are new, have changed rating or have an overdue response. The full register lives elsewhere.]
   Risk no.:
   Description:
   Change since last meeting:
   Owner:
   Response:

6. Issues
   [Things that have already happened and need resolving. Each has an owner and a target date.]
   Issue no.:
   Description:
   Impact:
   Owner:
   Target resolution:

7. Change requests
   [Any request to change scope, time or cost, with its status. Record who approves, not just that it was discussed.]
   CR no.:
   Description:
   Effect on scope / time / cost:
   Status (raised / assessed / approved / rejected):

8. Budget and resources
   [Spend to date against plan, forecast at completion, and any resourcing gap in the next period.]

9. Decisions
   [Decisions made in this meeting, and decisions needed from someone outside it, with who and by when.]
   Decision:
   Made by:
   Decisions required from steering group / sponsor:

10. Next meeting
   [Date, time and any change to attendees.]

Milestones
Milestone | Baseline | Forecast | Status | Owner

Risks and issues log
No. | Type (risk / issue) | Description | Owner | Status

Action items
No. | Action | Owner | Raised | Due | Status

What project meeting minutes are for

Status minutes exist for continuity. A project runs for months; people join and leave; the sponsor attends one meeting in four. The minutes let anyone reconstruct where the project was in any given week, which milestone slipped when, and who agreed to what. They are also the audit trail behind the change requests and the budget.

Keep the same section order every week. The reader should be able to find the data migration workstream in the same place in every set of minutes without searching.

What green, amber and red should mean in writing

Most projects rate status with a traffic light. The colours are only useful if the minutes say what they mean, so write it once at the top of the project and keep it. A workable definition: green means on plan with no help needed; amber means a milestone or the budget is at risk but the workstream has a recovery plan it can carry out itself; red means a milestone or the budget will be missed without a decision or resource from outside the workstream.

The common failure is the watermelon: green on the outside, red inside. It happens when leads are reluctant to report amber. The minutes help by recording the reason for each rating, not just the colour.

Risks, issues and change requests are three different lists

  • A risk is something that might happen. It has a likelihood, an impact and a planned response. It is numbered R-nn.
  • An issue is something that has happened and is now affecting the project. It has an impact and a target resolution date. It is numbered I-nn. When a risk materialises, close the risk and open an issue.
  • A change request asks to alter the agreed scope, dates or budget. It is numbered CR-nn and has a status. A change request is not approved by being discussed in the status meeting; record who has the authority and whether they have used it.

What to leave out

  • The full status report. Attach it or link to it; the minutes record what changed and what was decided.
  • Discussion of why something slipped, beyond one sentence of cause. The lessons go in a retrospective or post mortem.
  • Actions that reset every week. Keep one numbered action list for the whole project and carry open items forward with their original number and date raised.
  • Opinions on the rating. If the lead says amber and the project manager thinks red, record the agreed rating and, if it was escalated, that it was escalated.

One log for the life of the project

Number actions, risks, issues, change requests and decisions once, in sequence, from the kickoff to closure. Many teams keep these in a single RAID log (risks, assumptions, issues, dependencies) and paste the changed rows into the minutes. That way the minutes stay short and the log stays complete. Whatever tool you use, the minutes should name the item by its number so that "CR-07" means the same thing in week 11 and week 30.

Example: filled-in project meeting minutes

What the template looks like once it’s been used. The organisation and people are made up.

Minutes of weekly status meeting no. 11, Merriwether Logistics ERP implementation

Project: ERP implementation (finance, dispatch and fleet modules)
Date: Wednesday 4 March 2026

Time: 10:00 am to 10:55 am

Location: Depot meeting room and by video

Chair: Ingrid Halvorsen, project manager

Minutes taken by: Ingrid Halvorsen

Present: Ingrid Halvorsen, Rohan Mehta (finance workstream), Beth Callaghan (dispatch workstream), Luis Carvalho (data migration), Aisha Rahman (training and change), Kevin O'Dowd (Stratus Partners, implementation partner)

Apologies: Margaret Sweeney, CFO and sponsor

Reporting period: 25 February to 3 March 2026

Overall status: Amber (last week: green)

1. Review of open actions

A-38 (confirm bank file format with Westfield Bank, Rohan Mehta): closed. A-41 (publish training calendar, Aisha Rahman): closed. A-43 (resolve duplicate customer codes, Luis Carvalho): open, carried to 11 March, see item 3. A-44 (agree test environment refresh schedule, Kevin O'Dowd): open, due 6 March.

2. Overall status and headline

Status moved from green to amber. The second trial data load found 3,400 customer records with duplicate codes, which puts the start of user acceptance testing at risk. Go-live on 1 June 2026 is still forecast as achievable if UAT starts by 20 April.

3. Status by workstream

Finance (Rohan Mehta): green. Chart of accounts loaded and reconciled to the current ledger. Next period: configure fuel surcharge invoicing, see CR-07. No help needed.

Dispatch (Beth Callaghan): green. Depot and vehicle master data signed off. Next period: dispatcher workflow walkthrough with Stratus on 10 March. Help needed: two dispatchers released for a full day.

Data migration (Luis Carvalho): amber. Trial load 2 completed; 3,400 of 18,200 customer records have duplicate codes from the two legacy systems. A de-duplication rule has been drafted. Next period: apply the rule and run trial load 3 by 18 March. Help needed: a decision from finance on which code survives where the two systems disagree.

Training and change (Aisha Rahman): green. Training calendar published; 62 of 70 users booked. Next period: super-user sessions start 16 March.

4. Milestones

Trial load 3 complete: baseline 11 March, forecast 18 March, amber. UAT start: baseline 13 April, forecast 20 April, amber. UAT complete: baseline 15 May, forecast 15 May, green (contingency absorbed). Go-live: baseline 1 June, forecast 1 June, green.

5. Risks: new and changed

R-09 (legacy data quality worse than assumed): likelihood raised from medium to high; now partly realised as I-06. R-14 (new): dispatcher availability during harvest season in May may limit UAT participation. Owner Beth Callaghan. Response: agree named UAT testers with the operations manager by 20 March.

6. Issues

I-06 (new): 3,400 duplicate customer codes. Impact: trial load 3 and UAT start delayed one week. Owner Luis Carvalho. Target resolution 18 March.

7. Change requests

CR-07: add fuel surcharge calculation to invoicing. Stratus estimate $42,000 and three weeks of configuration, no effect on go-live if approved by 13 March. Status: assessed; to be put to the steering group on 12 March. CR-05 (additional reporting licences): approved by the sponsor on 27 February, $8,600.

8. Budget and resources

Spend to date $611,000 against a plan of $598,000 for this point; forecast at completion $1.34 million against a budget of $1.38 million, before CR-07.

9. Decisions

Decided: UAT start moves to 20 April; the go-live date is not changed. Decided: where the two legacy systems disagree on a customer code, the finance system's code survives (Rohan Mehta, on behalf of the sponsor). Required from the steering group on 12 March: approval or rejection of CR-07.

10. Next meeting

Wednesday 11 March 2026 at 10:00 am.

Milestones

Milestones
No.DecisionOutcome
1UAT start moved from 13 April to 20 April 2026; go-live unchangedAgreed, project manager
2Finance system code survives where legacy customer codes conflictAgreed, on behalf of sponsor
3CR-07 fuel surcharge moduleReferred to steering group, 12 March

Action items

Action items
No.ActionOwnerDue
1Apply de-duplication rule and run trial load 3Luis Carvalho18 March 2026
2Agree named UAT testers from dispatch with the operations managerBeth Callaghan20 March 2026
3Present CR-07 with Stratus estimate to the steering groupIngrid Halvorsen12 March 2026
4Confirm test environment refresh schedule (A-44, carried)Kevin O'Dowd6 March 2026

Tips for project meeting minutes

  • Record last week's rating next to this week's. The change is more informative than the colour.
  • Keep the baseline date in the milestone table even after it has been missed. A forecast that moves every week while the baseline stays still is the clearest picture of a slipping project.
  • Write one line of cause for each amber or red, in the lead's words. Next quarter nobody will remember why week 11 went amber.
  • Carry open actions forward with the date they were raised. An action raised in week 3 and still open in week 11 is itself an issue.
  • Send the minutes the same day. A status meeting's minutes lose most of their value by the time the next one happens.
  • If the sponsor sends apologies, write the headline paragraph for them specifically; it is the only part of the minutes they will read.

Related templates

Or let the notes write themselves

A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.

Questions

What should project meeting minutes include?

The overall status and why, progress by workstream, milestones with baseline and forecast dates, risks and issues that are new or changed, change requests and their status, budget position, decisions made and required, and a numbered action list carried over from previous meetings. Attendance and the reporting period go at the top.

How detailed should project status meeting minutes be?

Detailed enough that a sponsor who missed the meeting knows what changed and what they need to decide; short enough to read in five minutes. A page or two for a weekly meeting is normal. Put the detail in the status report and the RAID log and keep the minutes to changes, decisions and actions.

What is the difference between a risk and an issue in project minutes?

A risk is something that might happen and would affect the project if it did; you record its likelihood, impact and the planned response. An issue is something that has already happened and needs resolving now; you record its impact, owner and target date. When a risk occurs, it is closed and reopened as an issue.

What does RAG status mean in a project meeting?

RAG stands for red, amber, green. Green usually means on plan, amber means at risk with a recovery plan the team can carry out itself, and red means a milestone or budget will be missed without a decision or resource from outside the team. Definitions vary between organisations, so write yours in the first set of minutes and keep to it.

Who should write project meeting minutes?

Usually the project manager or a project coordinator, because they already hold the action list, the milestone schedule and the RAID log, and the minutes are largely an extract from those. On larger programmes a project management office takes the minutes so the project manager can chair without writing.

Can an AI note taker write project status meeting minutes?

It can draft the workstream updates and the action list from the discussion, which saves the project manager typing while chairing. The ratings, milestone dates and change request statuses should come from the project's log rather than from the transcript, and the project manager should confirm the decisions section before circulating.

Notes without the bot.

QuietNote captures meetings from your own computer, so nothing joins the call. It’s in private beta — join to help shape the first version.

Private beta. No credit card.