Free Project Kickoff Meeting Agenda Template
A project kickoff agenda that leaves the team aligned on what they’re building and who owns what.
Part of our free meeting agenda templates.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
1.Meeting Information
| Date | {{Date}} |
|---|---|
| Time | {{Start – End time}} |
| Location | {{Location or video link}} |
| Facilitator | {{Facilitator}} |
| Note-taker | {{Note-taker}} |
| Attendees | {{Attendees / required vs optional}} |
Fill this block before you send the invite so everyone knows when, where, and who is expected. Name a facilitator and a note-taker — meetings without both tend to drift.
2.Objectives
- Align everyone on the project’s purpose, goals, and success criteria
- Agree the scope, the roles, and how the team will work together
- Leave with owned next steps and the date of the next checkpoint
State one to three outcomes this meeting must produce — a decision, a plan, an aligned team. If you cannot name an objective, the meeting can probably be an email.
3.Agenda
| Topic | Lead | Time | Type |
|---|---|---|---|
| Welcome & introductions (who’s who, and their role) | {{Facilitator}} | 10 min | Inform |
| Why this project — background & business case | {{Sponsor}} | 10 min | Inform |
| Objectives & success criteria | {{Project manager}} | 10 min | Discuss |
| Scope: what’s in and what’s explicitly out | {{Project manager}} | 15 min | Decide |
| Roles, responsibilities & decision-making | {{Project manager}} | 10 min | Discuss |
| High-level timeline & milestones | {{Project manager}} | 10 min | Inform |
| Risks, assumptions & open questions | All | 10 min | Discuss |
| Ways of working: tools, meetings, communication | {{Facilitator}} | 5 min | Inform |
| Next steps & action items | {{Facilitator}} | 10 min | Decide |
Give every item an owner, a time box, and a type — Inform, Discuss, or Decide — so people come prepared and you protect time for the decisions that matter. Put the most important item first, not last.
4.Decisions & Notes
| Topic | Decision / key note | Follow-up |
|---|---|---|
| {{Scope question}} | {{What was decided}} | {{Follow-up}} |
Capture decisions as they happen, in the room. A one-line record of what was decided prevents the same debate from reopening next week.
5.Action Items
| Action | Owner | Due date |
|---|---|---|
| {{First task — start with a verb}} | {{Owner}} | {{Due date}} |
| {{Action}} | {{Owner}} | {{Due date}} |
Every action needs a single owner and a date — “we” is not an owner. Read these back aloud before you close the meeting so nobody leaves surprised.
6.Parking Lot
- {{Important question raised but not for this meeting}}
Park anything important that is off-agenda here instead of letting it derail the meeting. Review the parking lot when you plan the next agenda.
7.Next Meeting
| Date & time | {{Date and time}} |
|---|---|
| Focus | {{Main focus for next time}} |
Set the next meeting before everyone leaves — it is far harder to schedule afterward. Note the main focus so the next agenda almost writes itself.
A worked example for the kickoff of a company-wide CRM implementation project.
1.Meeting Information
| Date | Tuesday, June 16, 2026 |
|---|---|
| Time | 1:00 – 2:30 PM |
| Location | Main conference room + Zoom for remote stakeholders |
| Facilitator | Dana Reyes, Project Manager |
| Note-taker | Tom Becker, Business Analyst |
| Attendees | Sponsor (VP Sales), Sales Ops, Marketing, IT, Finance, the implementation partner |
2.Objectives
- Align all departments on why we are replacing the legacy CRM and what success looks like
- Confirm the scope of phase 1 and what is deferred to a later phase
- Agree the core team, the decision-making process, and the next milestone date
3.Agenda
| Topic | Lead | Time | Type |
|---|---|---|---|
| Welcome & introductions — name, team, and role on the project | Dana Reyes | 10 min | Inform |
| Why now — the business case for replacing the legacy CRM | VP Sales (Sponsor) | 10 min | Inform |
| Objectives & success metrics (adoption, data quality, reporting) | Dana Reyes | 10 min | Discuss |
| Phase-1 scope: migration + sales module; out: marketing automation | Dana Reyes | 20 min | Decide |
| Roles: PM, system owner, data lead, partner, and approvers | Dana Reyes | 10 min | Discuss |
| Timeline: discovery → build → UAT → go-live (target Sept 30) | Dana Reyes | 10 min | Inform |
| Top risks: data quality, user adoption, integration with billing | All | 15 min | Discuss |
| Ways of working: weekly status, Jira board, shared drive | Tom Becker | 5 min | Inform |
| Next steps & action items | Dana Reyes | 10 min | Decide |
4.Decisions & Notes
| Topic | Decision / key note | Follow-up |
|---|---|---|
| Phase-1 scope | Phase 1 covers data migration and the sales module only; marketing automation moves to phase 2 | Dana to update the scope doc and charter |
| Go-live target | Target go-live is September 30, with UAT starting September 1 | Partner to confirm the build timeline fits |
| Decision-making | Day-to-day decisions: PM; scope/budget changes: Sponsor sign-off via change request | Dana to circulate the change-request process |
5.Action Items
| Action | Owner | Due date |
|---|---|---|
| Share the project charter and phase-1 scope for sign-off | Dana Reyes | Fri Jun 19 |
| Pull a data-quality report from the legacy CRM for assessment | Sales Ops (Priya) | Wed Jun 24 |
| Confirm the billing-system integration approach with IT | IT Lead (Sam) | Tue Jun 23 |
| Set up the Jira project and shared drive and invite the team | Tom Becker | Mon Jun 22 |
| Book the weekly status meeting series through go-live | Dana Reyes | Mon Jun 22 |
6.Parking Lot
- Whether to retire the old reporting tool after go-live (decide in discovery)
- Territory restructure that may overlap with this project — raise with Sales leadership
7.Next Meeting
| Date & time | Tuesday, June 23, 2026 · 1:00 PM |
|---|---|
| Focus | Discovery kickoff: data assessment findings and integration approach |
What to put on a project kickoff meeting agenda
A kickoff is where a project goes from approved to actually understood. The agenda should spend its time on the parts teams most often leave fuzzy — the why, the scope, and who owns what — not on status, of which there is none yet. Put the highest-stakes item, usually scope, early while attention is fresh.
This template lays the agenda out in the order a kickoff naturally flows, so you can walk the room from introductions to owned next steps without losing the thread.
- Introductions and roles — who is in the room and what each person owns
- The why — background, business case, and the problem being solved
- Objectives and success criteria — how you will know it worked
- Scope — what is in, what is out, and the known constraints
- Timeline and milestones — the major dates and dependencies
- Risks and assumptions — what could derail the work, surfaced early
- Next steps — action items with an owner and date, plus the next checkpoint
Who to invite and how long to run it
Invite the core team who will do the work, the project sponsor, and the stakeholders the project affects — plus any vendor or partner. Keep the room to the people who need to agree on scope and decisions; everyone else can read the summary afterward.
Most kickoffs run 60–90 minutes. Time-box each item, send the charter or scope as pre-reading, and protect the scope and next-steps blocks from being squeezed at the end — those parts decide whether the project starts aligned.
How it works
- Fill the meeting information and the objectives this kickoff must achieve.
- Walk the team through the why, the scope, roles, timeline, and risks — capturing decisions as you go.
- Agree next steps with an owner and date for each, then download as Word or PDF.
Frequently asked questions
What should a project kickoff meeting agenda include?
A kickoff agenda should cover introductions and roles, the business case (the why), the objectives and success criteria, the scope (in and out), the high-level timeline and milestones, the main risks and assumptions, how the team will work together, and clear next steps. This template includes each of those, plus space for decisions and action items.
What is the purpose of a project kickoff meeting?
A kickoff aligns everyone on what the project is, why it matters, and who does what before the work starts. It is where you confirm scope, set expectations, surface risks early, and agree how the team will communicate — so the project begins with shared understanding instead of assumptions.
Who should attend a project kickoff?
Invite the core team who will do the work, the project sponsor, and the key stakeholders or department leads affected by the project — plus any vendor or partner. Keep it to the people who need to agree on scope and decisions; others can get the summary afterward.
How long should a kickoff meeting be?
Most kickoffs run 60–90 minutes. Bigger or cross-team projects may need longer for scope and risk discussion. Time-box each agenda item, send pre-reading (the charter or scope) ahead, and protect time for the scope and next-steps sections, which matter most.