Project Kickoff Meeting Template
A kickoff is the last meeting where everyone in the room agrees on the same picture of a project. Two months in, when someone asks "wait, was that in scope?", the only thing that saves you is what got written down in that first hour. Most kickoffs fail quietly: they turn into a presentation where one person talks and everyone else nods, and the meeting ends with goodwill and no record.
This is a project kickoff meeting template you can copy. A timed agenda, a RACI grid, and a notes format that captures decisions, owners, and open questions so the project doesn't start with a hole in it.
What a kickoff is actually for
A kickoff is not a status update and not a get-to-know-you. It's a decision meeting. By the time it's over, seven things should be written down and agreed on:
- Goal — why this project, and what "done" looks like
- Scope — what's in, and what's out
- Roles — who does the work, who signs off (a RACI grid)
- Timeline — milestones and the first deadline
- Risks — what could slip, and who's watching it
- Communication — meeting rhythm, channel, how to raise a problem
- Decisions and open questions — what was agreed, and what still needs an answer
Skip one, usually the "out" list, and that's the gap the project falls through later.
The 60-minute internal kickoff agenda
Use this when everyone works for the same company. Send a one-page brief two working days ahead so the hour goes on questions, not on reading slides aloud.
| Time | Block | Who leads | What it must produce |
|---|---|---|---|
| 0:00 | Why this project, why now | Sponsor | One sentence on the business outcome |
| 0:05 | What "done" looks like | Project lead | Measurable success criteria |
| 0:15 | Scope: in and out | Project lead | Written in and out lists |
| 0:25 | Who does what (RACI) | Project lead | One accountable owner per workstream |
| 0:35 | Timeline and milestones | Project lead | Milestones and the first deadline |
| 0:43 | Risks and open questions | Everyone | Top risks, each with an owner |
| 0:53 | How we'll work | Project lead | Cadence, channel, escalation |
| 0:57 | Recap: decisions and owners | Note-taker | Action items read back aloud |
The 75-minute client kickoff agenda
A client kickoff happens after the contract is signed and before work starts. Sales hands the relationship to the delivery team, which is why it needs 15 more minutes. The extra block is access, approvals, and how change requests work.
| Time | Block | Who leads |
|---|---|---|
| 0:00 | Introductions: name, role, what you need | Everyone |
| 0:10 | What we agreed to deliver | Sales lead |
| 0:20 | Scope: in, out, and change requests | Project lead |
| 0:30 | Who does what on both sides (RACI) | Both leads |
| 0:40 | Timeline and what we need from you | Project lead |
| 0:50 | Access, approvals, dependencies | Client lead |
| 0:58 | Risks and open questions | Everyone |
| 1:08 | Communication: status call, escalation | Both leads |
| 1:12 | Recap: decisions, owners, next steps | Note-taker |
The RACI grid: names, not departments
Listing "who's on the team" is not the same as assigning accountability. A RACI grid gives every deliverable four roles:
- R — Responsible: does the work
- A — Accountable: the one person who answers for it
- C — Consulted: gives input before the work happens
- I — Informed: kept up to date
Two rules keep the grid honest. Every deliverable gets exactly one "A"; if two people are accountable, nobody is. And if a name has no "R" anywhere, ask why they're in the project.
The kickoff notes template
General meeting notes record what was discussed. Kickoff notes need something narrower: the answers to the seven questions, in a form you can paste straight into the project plan.
| Field | What goes in it |
|---|---|
| Project, date, note-taker, attendees | Header |
| Goal (as agreed) | One sentence |
| Success measures | Measurable |
| Scope: in and out | Both lists, written live |
| Change requests go to | One name |
| RACI | Deliverable rows, one "A" each |
| Milestones | Milestone, date, owner |
| Risks | Risk, watched by, plan if it happens |
| Decisions made today | Numbered list |
| Open questions | Question, owner, answer by |
| Next meeting | Date and who runs it |
The pre-read: one page, two days ahead
The pre-read is the difference between a kickoff that decides things and one that reads slides. It's one page: the goal, the scope in and out, the draft RACI, the milestone sketch, and the three questions you most need answered. Send it two working days before. If people haven't read it, don't recap it for them. Start with the decisions and let the questions surface.
Three habits that make the notes usable
The person who knows the project best usually chairs, and they're the worst person to take notes. They're running the room. Name a note-taker who isn't chairing and put their name on the agenda. Then make three habits non-negotiable:
- Read each agenda block aloud as you open it. It feels stiff for about one meeting, then it becomes normal, and the notes come out with headings instead of a wall of text.
- Say decisions as a sentence with a name and a date. "Priya owns the pricing question, due Friday." Not "we'll circle back on pricing."
- Say the "out" list aloud. The out-of-scope list is the one people skip, and the one that saves you when someone asks for it later.
If everyone agrees, record the meeting so the note-taker can take part instead of typing. Meetbook is built for exactly this: it records from the browser tab, no bot joins the call, and it hands back a summary with action items that name an owner, where every point is backed by the quote, speaker, and timestamp. When the room disagrees about what was decided, you scroll to the moment and read what the sponsor actually said, not what someone remembers. Ask before you hit record, and add a line to the agenda saying the kickoff is being recorded.
The recap email, same day
The kickoff isn't over when the hour ends. Send a written recap within 24 hours that covers four things:
- Decisions made — every agreement, in bullets
- Action items — task, owner, deadline
- Open questions — question, owner, answer-by date
- Next meeting — when, who runs it, what to bring
Send it to everyone in the room, plus anyone who should be informed but wasn't there. Keep it somewhere shared. This document becomes the project's reference point for the first phase of delivery, and the thing you point at when someone claims the kickoff said something it didn't.