Project Kickoff Meeting Agenda and Notes Template

Five weeks into a warehouse software rollout, Rosa's project stalls on one sentence: "I thought label printing was part of this." Half the room remembers the kickoff saying yes. The other half remembers no. Nobody wrote it down, so the next hour goes on arguing about a meeting from a month ago.

A good project kickoff meeting agenda prevents that argument. Everyone knows a kickoff covers goals, scope and roles. The hard part is leaving the room with those answers in writing.

Below are two timed agendas (internal and client), a notes template for decisions, owners and open questions, a filled example, and the recap email.

If you'd rather not scribble while you chair, try ParrotNotes free. Record the kickoff on your phone and get a transcript, a summary and action items afterwards.

What a project kickoff meeting agenda has to settle

A kickoff is the one time the sponsor, the project lead and the people doing the work agree on the same picture before anyone starts. The University of Waterloo's project management office puts it plainly in its kickoff guidance: "Most of this information presented at the kick off meeting will come from the Project Charter." It suggests one to two hours, led by the project manager.

So you confirm the project out loud; you don't invent it. By the end, seven things should be written down:

1. Goal: why this project, and what "done" looks like
2. Scope: what's in, and what's out
3. Roles: who does the work, who signs off, who is consulted, who is kept informed (a RACI grid)
4. Timeline: milestones and the first deadline, each with an owner
5. Risks: what could slip, and who watches it
6. Communication: meeting rhythm, channel and how to raise a problem
7. Decisions and open questions: what was agreed, and what still needs an answer

Internal project kickoff meeting agenda template (60 minutes)

Use this when everyone works for the same organization. Send a one-page brief two working days ahead, so the hour goes on questions, not on reading slides aloud.

INTERNAL PROJECT KICKOFF (60 minutes)
Project:          Sponsor:          Project lead:
Note-taker:       Pre-read: one-page brief, sent 2 days ahead

0:00  Why this project, and why now? (5 min, sponsor)
0:05  What does "done" look like? Goal and success measures (10 min, lead)
0:15  Scope: what's in, and what's out? (10 min, lead)
0:25  Who does what? Walk through the RACI grid (10 min, lead)
0:35  Timeline: milestones and the first deadline (8 min, lead)
0:43  Risks and open questions (10 min, everyone)
0:53  How we'll work: check-in rhythm, channel, escalation (4 min, lead)
0:57  Recap: decisions, owners, next meeting (3 min, note-taker)

Scope gets its own 10 minutes on purpose. The "out" list is the part people skip.

Picture Dana, a sales operations lead rolling out a new CRM to 30 field reps. In her scope block she says: "In: contacts, deals and call logging on mobile. Out: quoting, which stays in the ERP until next year." Two regional managers had assumed quoting was coming. They found out at minute 17, not in month three.

Client kickoff meeting agenda template (75 minutes)

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.

CLIENT PROJECT KICKOFF (75 minutes)
Project:          Client sponsor:     Our project lead:
Client lead:      Note-taker:         Pre-read: signed scope + draft plan

0:00  Introductions: name, role, what you need from this project (10 min, all)
0:10  What we agreed to deliver, and why it matters to you (10 min, sales lead)
0:20  Scope: in, out, and how changes get requested (10 min, our lead)
0:30  Who does what on both sides: the RACI grid (10 min, both leads)
0:40  Timeline, milestones and what we need from you, by when (10 min, our lead)
0:50  Access, approvals and dependencies (8 min, client lead)
0:58  Risks and open questions (10 min, everyone)
1:08  Communication: status call, channel, escalation path (4 min, both leads)
1:12  Recap: decisions, owners, next meeting (3 min, note-taker)

The second block matters most. The sales lead restates what was sold while the delivery team listens. If a promise from the sales cycle isn't in the signed scope, this is the cheapest moment to find out. A mutual action plan keeps those commitments visible before the deal closes.

Internal vs client kickoff: what changes

Before you fill in a client grid, a stakeholder map tells you who really holds sign-off.

The kickoff notes template: decisions, owners and open questions

General meeting notes templates record what was discussed. Kickoff notes need something narrower: the answers to the seven questions, in a form you can paste into the project plan.

KICKOFF NOTES
Project:            Date:           Note-taker:
Attendees:

GOAL (as agreed):
Success measures:

SCOPE   In:
        Out:
        Change requests go to:

ROLES (R = does the work, A = signs off, C = consulted, I = informed)
Deliverable          | Name | Name | Name | Name

MILESTONES           Milestone | Date | Owner
RISKS                Risk | Watched by | Plan if it happens
DECISIONS MADE TODAY
OPEN QUESTIONS       Question | Owner | Answer by
PARKING LOT
NEXT MEETING:

Two rules keep the grid honest. Give each deliverable exactly one "A". And if a name has no "R" anywhere, ask why they're in the project.

A filled example: the Line 3 case packer kickoff

Here's the template filled in for a fictional client kickoff. Marco is a project manager at a packaging machinery supplier that has sold an automatic case packer to a mid-sized bakery. The sales rep, Priya, joins to hand over.

At minute 12, Priya restates the order: one case packer for Line 3, installed and running two carton sizes. The bakery's plant engineer asks about a guarding upgrade on Line 2. It came up on a site visit but never reached the quote. Marco doesn't argue. He writes it under "Out" and gives Priya an open question to price it separately.

KICKOFF NOTES
Project: Line 3 case packer installation      Date: October 6
Attendees: Marco (PM), Priya (sales), Ken (service tech); bakery:
Joan (plant manager, sponsor), Luis (plant engineer), Mei (maintenance)

GOAL: Line 3 packs both carton sizes at rated speed by December 4,
with two maintenance staff trained on changeovers.

SCOPE   In: case packer, install, conveyor integration, site
            acceptance test, training for 2 maintenance staff
        Out: Line 2 guarding upgrade; palletizer changes
        Change requests go to: Marco, in writing, copying Joan

ROLES                  | Marco | Ken | Joan | Luis | Mei
Installation plan      |   A   |  R  |  I   |  C   |  C
Conveyor integration   |   A   |  R  |  I   |  R   |  I
Site acceptance test   |   R   |  R  |  A   |  C   |  I
Maintenance training   |   A   |  R  |  I   |  I   |  R

MILESTONES   Site survey Oct 20 (Ken); delivery Nov 10 (Marco);
             acceptance test Dec 1 (Joan)
RISKS        Holiday peak blocks downtime (Luis): install on the
             weekend of Nov 14. Carton samples late (Mei): ship by Oct 17
DECISIONS    1. Install the weekend of Nov 14
             2. Status call Thursdays 8:30, 20 minutes
OPEN         1. Price for Line 2 guarding (Priya, by Oct 13)
             2. Who approves install-weekend overtime? (Joan, by Oct 9)
PARKING LOT  Palletizer speed issue (separate visit)
NEXT MEETING Thursday October 9, 8:30

Six weeks later, when someone asks whether guarding was included, the answer takes 10 seconds.

The kickoff recap email

Send the recap the next working morning, while memories still match the notes. In Microsoft's 2023 Work Trend Index, a survey of 31,000 workers in 31 markets, 55% said next steps at the end of a meeting are unclear, and 56% said it's hard to summarize what happened. Here's Marco's, built straight from the notes:

Subject: Line 3 case packer kickoff: decisions and next steps

Hi Joan, Luis and Mei,

Thanks for yesterday. Here's what we agreed.

Goal: Line 3 packing both carton sizes at rated speed by December 4.

Decisions: install the weekend of November 14; status call
Thursdays at 8:30.

Not in this project: the Line 2 guarding upgrade. Priya will send
a separate price by October 13.

Next steps
- Ken: site survey by October 20
- Mei: carton samples to our plant by October 17
- Joan: confirm who approves install-weekend overtime by October 9

Notes and the RACI grid are attached. If anything doesn't match
your memory of the meeting, reply by Thursday and I'll correct it.

Marco

The last line turns the email into the agreed record, not just your version. For follow-ups that get replies, see our guide to the follow-up email after a sales call.

Record the kickoff so the notes fill themselves

The person who knows the project best is usually chairing, and can't take notes too. A recording fixes that, as long as you ask first. Add a line to the agenda: "This kickoff will be recorded for notes. Tell the chair if you object." Recording rules vary by location, and a client kickoff means asking the client too.

With ParrotNotes on a phone in the middle of the table, the kickoff becomes a transcript, an AI summary and action items, with no meeting bot joining. Three habits make the output match your template:

• Read each agenda block aloud as you open it, so the transcript gets your headings
• Say decisions as sentences with a name and a date: "Ken owns the survey, due October 20."
• Say the "out" list aloud, so it's in the record word for word

Kickoffs often run past an hour, which suits ParrotNotes Pro: up to 3 hours per recording, 3,000 minutes a month, speaker identification, and custom insight templates you can set up with your kickoff headings. ParrotNotes also drafts a follow-up email from what was said, a head start on the recap. Pro is $19.99 a month, or $14.99 a month billed annually.

The free plan gives you 100 minutes a month and an AI summary on every recording. Download ParrotNotes free and try it on your next project check-in.

Run your next kickoff from this project kickoff meeting agenda

A kickoff works when the answers leave the room in writing:

• Pick the variant: 60 minutes internal, 75 minutes with a client
• Give scope its own block, and say the "out" list aloud
• Give every deliverable one person who signs off
• Capture decisions, owners and open questions in the notes template
• Send the recap the next morning and ask for corrections

One line under "Out", read back at minute 57, would have settled Rosa's label-printing argument in 10 seconds.

For the meetings after the kickoff, our meeting agenda template guide covers the weekly check-in, and the meeting minutes template covers the formal record. Copy this project kickoff meeting agenda into your invite today, then download ParrotNotes free so the notes are ready before you leave the room.