Project kickoff meeting template (free, with example)
Last updated
This project kickoff meeting template records what a project needs agreed before work starts: why it exists, what is in and out of scope, who does what, the milestones, how the team will communicate, and the risks already visible. Kickoff minutes differ from a weekly status meeting because they become the baseline every later meeting is measured against.
Download it as a Word file, copy the plain-text version, or read the example first: a kickoff for a company moving its head office across town.
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 name
- Project sponsor
- Project manager
- Date
- Time
- Location (or video platform)
- Present (name, organisation, role on the project)
- Absent
- Minutes taken by
- Distribution list
Then the body follows the meeting in this order:
- 1. Welcome and introductions — Who is in the room and their role on this project, not their job title. One line per person.
- 2. Why the project exists — The sponsor's statement of the problem or opportunity, in their words. One paragraph.Background: · Business objective: · What success looks like (measurable where possible):
- 3. Scope — List what is out of scope as carefully as what is in. The out-of-scope items are the ones that cause arguments later.In scope: · Out of scope: · Assumptions: · Constraints (budget, date, regulation, systems):
- 4. Deliverables — The tangible things the project hands over. Name each one and who accepts it.Deliverable: · Accepted by: · Acceptance criteria:
- 5. Roles and responsibilities — For each major piece of work: who does it, who is accountable for it, who must be consulted and who is kept informed. One accountable person per item.Sponsor: · Project manager: · Workstream leads: · Subject-matter experts: · Steering group:
- 6. Timeline and milestones — Key dates only. The detailed plan lives in the schedule; the minutes record the milestones everyone in the room just agreed to.Milestone: · Target date: · Owner:
- 7. Budget and resources — Approved budget, how spend is authorised, and any people, space or equipment already committed.
- 8. Communication plan — Which meetings happen at what rhythm, where documents live, how decisions are escalated and who signs off.Status meeting (frequency, attendees): · Steering group (frequency): · Reporting (what, to whom, how often): · Document location: · Escalation path:
- 9. Known risks and open questions — Risks the team already sees, each with a first owner. These become the first rows of the risk register.Risk: · Likelihood / impact: · Owner: · First response:
- 10. Decisions made today — Anything agreed in the room that later meetings will rely on.
- 11. Actions and next steps — Including the date of the first status meeting.
At the end: decisions 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 Kickoff Meeting Minutes Project name: Project sponsor: Project manager: Date: Time: Location (or video platform): Present (name, organisation, role on the project): Absent: Minutes taken by: Distribution list: 1. Welcome and introductions [Who is in the room and their role on this project, not their job title. One line per person.] 2. Why the project exists [The sponsor's statement of the problem or opportunity, in their words. One paragraph.] Background: Business objective: What success looks like (measurable where possible): 3. Scope [List what is out of scope as carefully as what is in. The out-of-scope items are the ones that cause arguments later.] In scope: Out of scope: Assumptions: Constraints (budget, date, regulation, systems): 4. Deliverables [The tangible things the project hands over. Name each one and who accepts it.] Deliverable: Accepted by: Acceptance criteria: 5. Roles and responsibilities [For each major piece of work: who does it, who is accountable for it, who must be consulted and who is kept informed. One accountable person per item.] Sponsor: Project manager: Workstream leads: Subject-matter experts: Steering group: 6. Timeline and milestones [Key dates only. The detailed plan lives in the schedule; the minutes record the milestones everyone in the room just agreed to.] Milestone: Target date: Owner: 7. Budget and resources [Approved budget, how spend is authorised, and any people, space or equipment already committed.] 8. Communication plan [Which meetings happen at what rhythm, where documents live, how decisions are escalated and who signs off.] Status meeting (frequency, attendees): Steering group (frequency): Reporting (what, to whom, how often): Document location: Escalation path: 9. Known risks and open questions [Risks the team already sees, each with a first owner. These become the first rows of the risk register.] Risk: Likelihood / impact: Owner: First response: 10. Decisions made today [Anything agreed in the room that later meetings will rely on.] 11. Actions and next steps [Including the date of the first status meeting.] Decisions No. | Decision | Made by | Date Action items No. | Action | Owner | Due | Status
What kickoff minutes are for
A kickoff is the only meeting where everyone involved in a project hears the same description of it at the same time. The minutes capture that shared description: the objective, the scope boundary, the roles and the dates. Six weeks later, when someone asks whether the new phone system was ever part of the move, the kickoff minutes are where the answer lives.
That makes them different from status minutes. Status minutes record change; kickoff minutes record the starting point. Write them so they can be read on their own by someone who joins the project in month three.
Record the scope boundary in both directions
- In scope: the work the project will do, in enough detail that a reasonable person could not read something extra into it.
- Out of scope: the things people might assume are included and are not. Say them plainly, and name who raised each one if it was contested.
- Assumptions: anything the plan depends on that nobody has confirmed yet, such as a landlord's access dates or a supplier's lead time.
- Constraints: the fixed things, usually the end date, the budget ceiling and anything regulatory.
Write the roles in sentences, not a grid
Many project managers use a RACI chart: for each piece of work, who is responsible for doing it, who is accountable for the result, who is consulted and who is informed. The chart is useful, but in minutes it is clearer to write a sentence per workstream: "Jenna Kowalski leads the fit-out workstream and is accountable for it; Chloe Dunbar at Northgate Interiors is responsible for the works; Felix Brandt is consulted on cabling; all staff are informed through the fortnightly update." The common mistake is two accountable people for one item, which in practice means none.
What to leave out
- The full schedule. Record the milestones and where the schedule is kept.
- Enthusiasm. "The team is excited to begin" tells a future reader nothing.
- Risks without owners. A risk nobody owns is a worry, not a risk register entry.
- Detailed design or technical discussion. If the kickoff turns into a working session, note that a separate session was agreed and minute that separately.
- Status. A kickoff has none yet. If the project has already started informally, record what has been done as background, not as progress.
Internal and client kickoffs
For an internal project, the sponsor's statement and the roles matter most. For a kickoff with a client or external contractor, add the contract or statement-of-work reference, how changes to scope will be requested and priced, and the acceptance criteria for each deliverable. Those three items are where client projects most often go wrong, and the kickoff is the cheapest moment to write them down.
Example: filled-in project kickoff meeting
What the template looks like once it’s been used. The organisation and people are made up.
Minutes of the kickoff meeting for the Halden & Pike head office relocation project
Project: Head office relocation to 40 Marsh Lane
Sponsor: Rebecca Mallory, Chief Operating Officer
Project manager: Omar Haddad
Date: Thursday 5 February 2026
Time: 9:30 am to 11:15 am
Location: Boardroom, 12 Chandler Street
Present: Rebecca Mallory (sponsor), Omar Haddad (project manager), Jenna Kowalski (facilities), Felix Brandt (IT), Nadia Sørensen (HR), Patrick Quinn (finance), Chloe Dunbar (Northgate Interiors, fit-out contractor)
Absent: None
Minutes taken by: Omar Haddad
2. Why the project exists
Rebecca Mallory: the lease at Chandler Street ends on 31 August 2026 and the building cannot accommodate the planned growth to 140 staff. The firm has signed a ten-year lease at 40 Marsh Lane. The objective is to move all staff and operations to Marsh Lane with no loss of client service. Success means every desk, phone line and system working on the first Monday in the new building, and the Chandler Street lease surrendered on time with no dilapidations dispute.
3. Scope
In scope: fit-out of floors 3 and 4 at Marsh Lane; new desks, chairs and meeting-room furniture; network, Wi-Fi and telephony at the new site; physical move of staff, files and equipment; decommissioning and handover of Chandler Street; staff communication and welcome pack.
Out of scope: replacement of the policy administration system (separate project, Felix Brandt); rebranding of signage beyond the reception sign; any change to working-from-home policy (Nadia Sørensen noted this is being reviewed separately and must not be tied to the move).
Assumptions: landlord gives access for fit-out from 2 March 2026; existing laptops are reused; the archive at Chandler Street can be reduced by at least half before the move.
Constraints: move must complete by 31 August 2026; budget ceiling $1.15 million including contingency; the client contact centre cannot be offline during business hours.
5. Roles and responsibilities
Jenna Kowalski leads the fit-out and move workstream and is accountable for it. Chloe Dunbar is responsible for the fit-out works under the Northgate contract. Felix Brandt leads and is accountable for the IT and telephony workstream. Nadia Sørensen leads staff communication and the desk allocation. Patrick Quinn controls the budget and approves spend above $10,000. Rebecca Mallory chairs the steering group and is the escalation point. Omar Haddad coordinates all workstreams and reports to the steering group.
6. Timeline and milestones
Fit-out design signed off: 27 February 2026 (Jenna Kowalski). Fit-out starts on site: 2 March 2026 (Chloe Dunbar). Network and telephony live at Marsh Lane: 26 June 2026 (Felix Brandt). Fit-out practical completion: 10 July 2026 (Chloe Dunbar). Main move weekend: 18 and 19 July 2026 (Jenna Kowalski). Chandler Street handed back: 21 August 2026 (Jenna Kowalski).
7. Budget and resources
Approved budget $1.15 million, of which $95,000 is contingency held by the sponsor. Spend above $10,000 needs Patrick Quinn's approval; above $50,000 needs the steering group. Two facilities staff are assigned half-time from March.
8. Communication plan
Weekly status meeting, Tuesdays 9:00 am, workstream leads and project manager. Steering group monthly, first Thursday, chaired by Rebecca Mallory. One-page status report to the steering group every Friday. All documents in the Relocation folder on the shared drive; the schedule is the single source for dates. Staff update by email every second Friday from Nadia Sørensen. Escalation: workstream lead to Omar Haddad to Rebecca Mallory.
9. Known risks and open questions
R1: landlord access date slips (medium likelihood, high impact). Owner Jenna Kowalski. First response: confirm access in writing with the landlord by 13 February.
R2: telecoms provider lead time for the new fibre circuit exceeds 12 weeks (medium / high). Owner Felix Brandt. First response: place the order this week, before the design is final.
R3: staff resistance to allocated seating (high / medium). Owner Nadia Sørensen. First response: desk allocation principles to be agreed with department heads before any plan is published.
Open question: whether the archive can be scanned rather than moved. Patrick Quinn to cost both options.
10. Decisions made today
The move weekend is 18 and 19 July 2026. Working-from-home policy is out of scope. Spend approval thresholds as recorded under item 7.
Decisions
| No. | Decision | Outcome |
|---|---|---|
| 1 | Move weekend fixed as 18 and 19 July 2026 | Agreed, steering group |
| 2 | Working-from-home policy excluded from scope | Agreed, sponsor |
| 3 | Spend approval: over $10,000 finance, over $50,000 steering group | Agreed, sponsor |
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | Confirm landlord access date for fit-out in writing | Jenna Kowalski | 13 February 2026 |
| 2 | Order fibre circuit for 40 Marsh Lane | Felix Brandt | 9 February 2026 |
| 3 | Cost scanning versus moving the archive and report to the next status meeting | Patrick Quinn | 17 February 2026 |
| 4 | Circulate the kickoff minutes and the schedule link to all attendees | Omar Haddad | 6 February 2026 |
Tips for project kickoff meeting
- Send the sponsor's objective statement to them for sign-off before you circulate the minutes. If they would word it differently, better to find out now.
- Give every milestone an owner in the minutes, even when the schedule already has one. The minutes are what people actually read.
- Write the out-of-scope list from the questions people asked in the room; those are the assumptions that needed correcting.
- Put the link to the schedule and the document folder in the minutes themselves, so the minutes are the one bookmark a new team member needs.
- Number the risks from R1 and the decisions from D1 at the kickoff and keep that numbering for the whole project.
Related templates
- Project meeting minutes template — The weekly status record: where each workstream stands, which milestones moved, what changed on the risk log and what was decided.
- Sprint planning template — The sprint goal, the team's real capacity, the items pulled in, and what each of them depends on.
- Client meeting notes template — For agencies, consultants and advisers: a record of what the client asked for and what each side agreed to, written so it can be sent back to them.
- Meeting notes with action items template — Notes built around a running action register, for recurring meetings where last week's actions are this week's first agenda item.
- All meeting minutes 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 is discussed in a project kickoff meeting?
The reason the project exists, its objective and what success looks like; what is in and out of scope; the deliverables; who is responsible and accountable for each workstream; the milestones; the budget; how the team will meet, report and escalate; and the risks already known. The kickoff ends with the first actions and the date of the first status meeting.
Who should attend a project kickoff meeting?
The sponsor, the project manager, every workstream lead and anyone whose agreement the plan depends on, such as a key supplier or the head of a department that will be disrupted. People who only need to know the project is happening can be told afterwards; a kickoff with thirty people in it rarely agrees anything.
How long should a kickoff meeting be?
Sixty to ninety minutes is typical for an internal project with a few workstreams. Larger programmes sometimes run a half-day kickoff with workshops, but the decisions still fit in an hour of minutes. If the meeting is running long, it is usually because scope is being designed in the room rather than confirmed.
What is the difference between a project charter and kickoff minutes?
A charter is the document that authorises the project, usually written by the sponsor or project manager before the kickoff. The kickoff minutes record that the team heard it, what was clarified or changed in the room, and the actions that followed. Where there is a charter, the minutes should reference it rather than repeat it.
Should a kickoff meeting have minutes?
Yes, and they are among the most useful minutes a project produces, because they are referred back to when scope is disputed. Keep them factual and send them within a day or two, with the schedule link, so that the baseline is agreed while everyone still remembers what they heard.
Can an AI note taker take kickoff meeting notes?
It can draft the discussion, the questions raised and the action list, which helps in a long session where the project manager is also presenting. The scope boundary, the role assignments and the milestone dates should be checked by the project manager word for word before the minutes go out, since those lines are the ones that will be quoted later.