Closing Meeting Minutes Template (Project Closeout)
Use this template to write minutes for a project closeout. It records what was delivered, who signed off, what is still open and who owns it, so the record holds up after the team moves on.
Used by 300,000+ individuals and teams. Free trial, no credit card required.
Closing meeting minutes: the template
Seven sections cover everything a closeout record needs. Each one shows an example entry so you can see the level of detail to aim for.
Closing meeting minutes
- Project: [Project name]
- Date and time: [Date, start and end time]
- Location or link: [Room or video link]
- Chair: [Name]
- Minutes taken by: [Name]
- Present: [Names and roles]
- Apologies: [Names]
Purpose and scope of the meeting
One sentence on why the meeting was held and what the project set out to deliver.
Delivery against scope
What was delivered, changed or dropped, with dates.
Results and measures
Outcomes against the targets agreed at the start. Use numbers.
Lessons learned
One point to repeat and one to change, per person or per team.
Decisions and sign-off
Each decision on its own line, with who made it and any conditions.
Open items and handover
Everything still open, with a named owner and a date. Who supports it after the team stands down.
Next meeting and distribution
Whether a follow-up is needed, and who receives the minutes.
Akcijske točke
| Task | Lastnik | Due |
|---|---|---|
| Close the two open defects | Dev lead | 21 March |
| Move project files to the archive folder | Project coordinator | 28 March |
| Send the signed-off minutes to the PMO | Minute taker | Next working day |
Copy-ready minutes text
Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].
CLOSING MEETING MINUTES Project: [Project name] Date and time: [Date, start and end time] Location or link: [Room or video link] Chair: [Name] Minutes taken by: [Name] Present: [Names and roles] Apologies: [Names] PURPOSE AND SCOPE OF THE MEETING [One sentence on why the meeting was held and what the project set out to deliver.] DELIVERY AGAINST SCOPE [What was delivered, changed or dropped, with dates.] RESULTS AND MEASURES [Outcomes against the targets agreed at the start. Use numbers.] LESSONS LEARNED [One point to repeat and one to change, per person or per team.] DECISIONS AND SIGN-OFF [Each decision on its own line, with who made it and any conditions.] OPEN ITEMS AND HANDOVER [Everything still open, with a named owner and a date. Who supports it after the team stands down.] NEXT MEETING AND DISTRIBUTION [Whether a follow-up is needed, and who receives the minutes.] ACTION ITEMS Task | Owner | Due [Task] | [Name] | [Date] Next meeting: [Date, time] Minutes prepared by: [Name]
How to run this meeting
-
Decide who takes minutes before the meeting
Name the minute taker in the invite. The chair should not do it, because chairing a closeout and writing it down are two full jobs.
-
Record decisions, not conversation
Minutes are the record of what was decided and who does what. Write each decision as a short sentence with the owner and the date, and skip who said what unless it matters.
-
Capture sign-off in the sponsor's own words
If sign-off has conditions, write the condition exactly and name who checks it. This is the line people will look for later.
-
Send the minutes within one working day
Ask attendees to reply with corrections within 48 hours. After that, treat the minutes as accepted and file them with the project record.
Let the minutes write themselves from the recording
Closeout minutes need accurate decisions, owners and dates, which are the details that get lost when someone types and chairs at the same time. Record the call with Speak AI and the draft minutes are ready when it ends.
- Record the closing meeting on Zoom, Google Meet or Microsoft Teams, or upload a recording.
- Get a full transcript with speakers labelled, so the sign-off is easy to find and quote.
- Get an automatic summary you can paste under Results, Decisions and Lessons learned.
- Get action items with owners and due dates pulled from the conversation, ready for your task tracker.
See how the Pomočnik za sestanke z umetno inteligenco in Beležnik z umetno inteligenco work, or start with a free account.
Pogosto zastavljena vprašanja
What should closing meeting minutes include?
The project name, date, attendees, what was delivered against scope, the results against targets, lessons learned, each decision and the sign-off, open items with owners and dates, and who receives the minutes.
How are closing meeting minutes different from regular minutes?
Regular minutes track a discussion and the next steps. Closing minutes are a final record: they confirm what was delivered, capture formal sign-off, and hand over open items, so they are often filed as part of the project record.
How long should meeting minutes be?
One to two pages is enough for most closeouts. Aim for short sentences that capture decisions, owners and dates, not a transcript of the conversation.
Who should take the minutes at a closing meeting?
Someone other than the chair, agreed before the meeting. A project coordinator or a team member from outside the main discussion works well, or you can record the meeting and use an AI notetaker to draft them.
How soon should closing meeting minutes be sent?
Within one working day, while attendees still remember the discussion. Ask for corrections within 48 hours and then file the minutes as final.
Get closeout minutes without typing them
Book a demo to see Speak AI draft the minutes, decisions and action items from your recorded meeting, or try it free on your next call.
English 
Español 
Français 
Italiano 
العربية 
Português do Brasil 
Nederlands 
Deutsch 
עִבְרִית 
Русский 
日本語 
Polski 
Čeština 
Українська 
Slovenščina 
Svenska 
Ελληνικά 
Norsk bokmål 
简体中文 
Türkçe 
Català 
Magyar 
한국어 
Slovenčina 
Suomi