/

Templates / Projects and agile

Project kickoff meeting

Project kickoff meeting template

A project kickoff meeting gets everyone who will work on or approve a project to agree on five things: why it exists, what is in and out of scope, who does and signs off what, the key dates, and the known risks. Kickoff notes should record those agreements plus every open question with an owner, so nobody has to rely on memory a month later.

Best forProject managers starting an internal or client project with a new team

Meeting length60 to 90 minutes, once at the start of the project

SectionsGoal, scope in and out, success measures, roles, milestones, risks and assumptions, ways of working, open questions, next steps

FormatsGoogle Docs, Word, Notion, Markdown

Word Markdown

Project kickoff notes: [project name].docx

Project kickoff notes: [project name]

Project Date Sponsor Project manager Attendees Absent Notes by

Why we're doing this

Business reason and the one goal, in the sponsor's words

In scope

Out of scope

Say it plainly, including things people might assume are included

Success measures

Measure	Target	Checked by	When

Roles

Person	Role	Signs off
	Sponsor / Project manager / Does the work / Consulted / Informed	Which deliverables, or none

Milestones

Milestone	Date	Fixed or estimate	Depends on

Risks and assumptions

Risk or assumption	Type	Owner	Next step
	Risk / Assumption / Dependency

Ways of working

Status meeting:
Files and decisions live in:
Scope changes approved by:
Expected reply time:

Open questions

Question	Owner	Answer by

Next steps

ID	Item	Owner	Due	Done looks like

Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact.

Word Markdown

Project kickoff meeting agenda.docx

Project kickoff meeting agenda

Project Date Time60 to 90 minFacilitatorProject managerNotes by Pre-readOne-page project brief, sent 2 or 3 days before

Item	Owner	Time	What we need to leave with
Introductions and roles	Project manager	10 min	Everyone knows who decides, who builds and who signs off
Why this project, and the goal	Sponsor	10 min	One goal everyone can repeat
Scope: in and out	Project manager	15 min	An agreed out-of-scope list
Success measures	Sponsor	5 min	What gets measured, by whom and when
Milestones and key dates	Project manager	10 min	Fixed dates and estimates marked as such
Risks, assumptions and dependencies	Everyone	10 min	An owner for each risk and each unchecked assumption
Ways of working	Project manager	5 min	Status meeting time, file location, how scope changes are approved
Open questions and next steps	Notes taker	5 min	Every question and action has one owner and a date

Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact.

Pinewick Supply Co. dealer reorder portal, project kickoff

Filled-in example

Pinewick Supply Co. dealer reorder portal, project kickoff

ProjectDealer reorder portalDateMonday, November 2, 2026, 9:00 to 10:15 amSponsorDana Kessler, VP SalesProject managerMarcus IlungaAttendeesDana Kessler, Marcus Ilunga, Ruth Ambrose (sales desk lead), Tomas Vega (developer), Hana Sato (warehouse systems), Owen Price (Brightfold Design, contract designer)AbsentGil Fraser (finance), will read the notesNotes byRuth Ambrose

Why we're doing this

Most dealer orders are repeat orders of the same items, and they arrive by phone or email. The sales desk spends most mornings keying them in. Goal: dealers place repeat orders themselves, so phone and email reorders drop by half by the end of March 2027.

In scope

Dealer login using existing account numbers
Reorder from order history, with quantities editable
Stock levels from the warehouse system, refreshed every 15 minutes
Order confirmation email to the dealer and the sales desk

Out of scope

New dealer sign-up. The sales desk keeps setting up accounts as it does today.
Card payments. Dealers stay on net-30 terms.
A mobile app
Promotions or price changes in the portal (possible phase 2, not scheduled)

Success measures

Measure	Target	Checked by	When
Phone and email reorders	Down 50% from the October baseline of about 420 a month	Ruth	End of March 2027
Dealers using the portal	40 of the top 60 dealers have placed at least one order	Dana	End of February 2027
Order errors	No higher than today. Baseline not pulled yet, needs confirming.	Hana	Baseline by Nov 13

Roles

Person	Role	Signs off
Dana Kessler	Sponsor, final call on scope and dates	Launch go or no-go
Marcus Ilunga	Project manager	Project plan, weekly status
Tomas Vega	Does the work: builds the portal	Technical design
Hana Sato	Does the work: stock feed from the warehouse system	Stock feed test results
Owen Price	Does the work: screen designs	None. Ruth signs off designs.
Ruth Ambrose	Consulted, speaks for the sales desk	Screen designs, dealer instructions
Gil Fraser	Informed, credit terms and holds	None

Milestones

Milestone	Date	Fixed or estimate	Depends on
Screen designs approved	Nov 20	Estimate	Ruth's review time
Stock feed working in test	Dec 4	Estimate	Warehouse system vendor opening API access
Pilot with 5 dealers	Jan 11, 2027	Fixed	Sales desk picks pilot dealers by Dec 14
Launch to all dealers	Feb 1, 2027	Fixed, announced at the dealer meeting	Pilot sign-off by Jan 25

Risks and assumptions

Risk or assumption	Type	Owner	Next step
Warehouse system vendor hasn't confirmed API access	Dependency	Hana	Call the vendor's account manager by Nov 4. Escalate to Dana if there's no date by Nov 9.
Dealers keep phoning out of habit	Risk	Ruth	Write a short script for the desk to walk callers through the portal
Dealer account numbers in billing are clean	Assumption	Tomas	Spot check 50 accounts
Holidays slow reviews in late December	Risk	Marcus	No sign-offs scheduled Dec 21 to Jan 1

Ways of working

Status meeting: Thursdays 2:00 to 2:30 pm, starting Nov 5
Files and decisions live in: the shared project folder, decision log tab
Scope changes approved by: written request to Marcus. Dana approves anything that moves a fixed date.
Expected reply time: same business day for blockers, two business days for reviews

Open questions

Question	Owner	Answer by
Do dealers on credit hold see the portal, or get stopped at checkout?	Gil (absent, Marcus will ask)	Nov 13
Who answers dealer questions about the portal after launch, sales desk or IT?	No owner yet. Dana to assign.	Nov 9
Do we need Spanish screens at launch?	Ruth	Nov 20

Next steps

ID	Item	Owner	Due	Done looks like
K1	Send kickoff notes and the out-of-scope list to attendees and Gil	Marcus	Nov 3	Notes in the project folder, Gil has replied
K2	Get an API access date from the warehouse system vendor	Hana	Nov 4	A date in writing from the vendor
K3	Spot check 50 dealer account numbers	Tomas	Nov 11	List of mismatches, or "none found"
K4	First screen drafts	Owen	Nov 13	Drafts in the folder, review booked with Ruth
K5	Book the weekly status meeting	Marcus	Nov 3	Invite sent for Thursdays 2:00 pm

Pinewick Supply Co., Brightfold Design and everyone named here are a fictional sample.

Best forProject managers starting an internal or client project with a new team

Meeting length60 to 90 minutes, once at the start of the project

SectionsGoal, scope in and out, success measures, roles, milestones, risks and assumptions, ways of working, open questions, next steps

FormatsGoogle Docs, Word, Notion, Markdown

What to write in each section

Why we're doing this

The business reason and the one goal the project will be judged on, in two or three sentences. The sponsor should say this out loud, not the project manager.

"Cut phone and email reorders by half so the sales desk can look after new accounts" beats "build a reorder portal".

In scope and out of scope

List what is in, then list what is out just as clearly. The out-of-scope list prevents more arguments later than anything else on the page.

Success measures

How you'll know at the end that it worked: a number, a date and the person who checks it. If you don't have a baseline yet, say so and give someone the job of getting it.

Roles

Who decides, who does the work, who must be consulted and who just needs to be told. Name one person who signs off each deliverable.

Milestones

The handful of dates that matter, including ones that depend on someone outside the room. Mark which are fixed and which are estimates.

Risks and assumptions

What could knock the plan over, and what everyone is assuming without having checked. Each one gets an owner and a next step.

Ways of working

When the status meeting is, where files and decisions live, how scope changes get approved, and how fast people should expect a reply.

Open questions and next steps

Kickoffs always raise questions nobody can answer on the spot. Write each one down with an owner and a date, then list the first week's action items in an action items tracker.

When to use this template

The project has been approved and the people doing the work are meeting together for the first time.
Half the team heard about the project in passing and each person has a different idea of the deadline.
You're starting work with a client or vendor and need to agree who approves what before the first deliverable is due.

Questions people ask

Who should attend a project kickoff meeting?: The sponsor, everyone who will do the work, and anyone who signs off a deliverable. People who only need updates can read the notes. If the sponsor can't make it, ask them to confirm the goal beforehand and name who can decide for them in the room. If a key trade-off comes up that nobody present can decide, move that part, or the whole kickoff, to a date the sponsor can make.
How is a client kickoff different from an internal one?: A client kickoff spends more time on contacts, approvals and how change requests are handled, and less on internal staffing. Hold a short internal kickoff first so your own team agrees on scope and dates before the client hears them.
What should I send before a kickoff meeting?: A one-page brief with the goal, draft scope, draft milestones and the team list, two or three days ahead. People then spend the kickoff correcting and agreeing to it instead of hearing it for the first time. Send it with the agenda (see how to write a meeting agenda).

Related templates

Project status meeting templateProject teams and stakeholders, weekly or every two weeksAgenda · Template · Example

Project meeting notes templateProject teams of 3 to 8 working through tasks together, weekly or as neededAgenda · Template · Example

Planning meeting agenda template for quarterly team planningTeam leads and managers planning a quarter, season or half yearAgenda · Template · Example