Template

Project Kickoff Meeting Template

A kickoff meeting exists to remove ambiguity before work starts. This template forces the four answers projects usually skip: why, what's in scope, who owns it, and what done looks like.

When to use this template

  • • Starting a new project, initiative, or client engagement.
  • • Restarting a stalled project with a new team or new scope.
  • • Onboarding a vendor or agency into an existing workstream.

The template

**Project:** [Name]
**Date:** [YYYY-MM-DD]
**Sponsor:** [Name]
**Project lead:** [Name]
**Attendees:** [Names + roles]

**1. Why this project exists**
Problem: [what is broken today]
Business outcome: [what changes if we succeed]

**2. Goals & success metrics**
- Goal: [goal] — Measured by: [metric, target, date]

**3. Scope**
In scope: [items]
Out of scope: [items]

**4. Roles & owners**
- [Workstream] — Owner: [name] — Backup: [name]

**5. Timeline & milestones**
- [Milestone] — [date]

**6. Risks, dependencies, assumptions**
- Risk: [risk] — Mitigation: [plan] — Owner: [name]

**7. Communication plan**
Status update: [cadence, channel]
Escalation path: [who, when]

**8. Definition of done**
[Explicit finish line]

**9. Action items**
- [ ] Owner — Task — Due date

Copy the block above and paste it into your notes app.

Filled-in example

**Project:** Customer portal redesign
**Date:** 2026-03-04
**Sponsor:** Dana Reyes (VP Product)
**Project lead:** Kofi Mensah
**Attendees:** Kofi (lead), Lin (design), Marcus (eng), Sarah (support)

**1. Why this project exists**
Problem: 38% of support tickets are portal navigation questions.
Business outcome: cut portal-related tickets in half.

**2. Goals & success metrics**
- Reduce portal support tickets — Measured by: tickets/month, 400 → 200 by Sep 30.
- Improve task completion — Measured by: usability test pass rate, 61% → 85%.

**3. Scope**
In scope: navigation, billing page, account settings.
Out of scope: mobile app, SSO migration.

**4. Roles & owners**
- Design — Owner: Lin — Backup: Kofi
- Frontend — Owner: Marcus — Backup: Priya

**5. Timeline & milestones**
- Design review — Apr 10
- Beta with 20 accounts — Jun 5
- Full rollout — Aug 20

**6. Risks, dependencies, assumptions**
- Risk: billing API rewrite slips — Mitigation: ship navigation first — Owner: Marcus

**7. Communication plan**
Status update: Friday async post in #portal-redesign.
Escalation path: Kofi → Dana within one business day.

**8. Definition of done**
All three pages live for 100% of accounts with ticket volume tracked for 30 days.

**9. Action items**
- [ ] Lin — Share wireframes — Mar 13
- [ ] Marcus — Confirm billing API timeline — Mar 11

Tips that make it work

  • • Send the draft scope 24 hours before the meeting so debate happens live, not afterwards.
  • • Write the out-of-scope list explicitly — it prevents most scope creep.
  • • Every workstream gets one accountable owner, never two.
  • • End by reading the action items aloud with owners and dates.

FAQ

How long should a project kickoff meeting be?

Sixty minutes is enough for most projects: fifteen on context and goals, twenty on scope and roles, fifteen on timeline and risks, ten on next steps.

Who should attend a kickoff?

The sponsor, the project lead, one representative per delivery function, and anyone whose sign-off can block the work. Keep it under ten people.

What is the single most important kickoff output?

A written definition of done plus a named owner for each workstream. Without both, scope drifts within two weeks.

Related reading