Free Template · Word · Updated March 2026
Free Project Kickoff Agenda Template
Word Download
The kickoff meeting sets the tone for everything that follows. A structured agenda ensures you cover objectives, scope, milestones, roles, risks and ways of working — in 60 minutes, with energy, without running over. This template gives you a timed 12-slot agenda, pre-reading list, meeting objectives and an action items section.
Timed 12-slot agenda
Each agenda item has a start time, duration and named presenter — so the meeting has structure and accountability.
Meeting objectives section
Six pre-written meeting objectives — what attendees should know, agree and commit to by the end of the session.
Actions & pre-reading
Pre-reading materials list and an action items table for capturing follow-ups during the meeting itself.
Kickoff Meeting Agenda
Free Word template — instant download
Format
Word (.docx)
Agenda slots
12 timed items
Duration
60-minute structured meeting
Objectives
6 meeting objectives
Compatible
Word, Google Docs, LibreOffice
Price
Free — no signup needed
No email required. Instant Word download.
01 — The Agenda
The 60-Minute Kickoff Agenda — All 12 Items
The template uses a 60-minute structure. Times are starting points — adjust durations to your project's complexity. The key constraint is keeping the meeting to 90 minutes maximum: beyond that, energy drops and the room stops absorbing information.
09:00
5 min
Welcome and Introduction
Facilitator: Project Manager
Welcome attendees, confirm the meeting objectives and agenda. Set the tone — energetic and purposeful. Confirm how the meeting will run (timekeeping, parking lot for out-of-scope questions).
09:05
10 min
Round-Table Introductions
All attendees
Name, role and what you are bringing to the project. Keep to 30–45 seconds each. For large groups, ask people to introduce themselves as they speak rather than going around the room.
09:15
10 min
Project Background and Strategic Context
Presenter: Project Sponsor
Why this project exists and why it matters now. Connects the team's daily work to organisational strategy. This slot belongs to the sponsor — hearing the "why" from a senior leader creates commitment that no PM presentation can replicate.
09:25
15 min
Project Objectives and Success Criteria
Presenter: Project Manager
What the project must achieve and how success will be measured. Walk through each objective with its KPI. Check for alignment — if team members are unclear or have different expectations here, better to surface it now than in Week 6.
09:40
10 min
Scope — In and Out
Presenter: Project Manager
Explicitly confirm what is in scope and what is out. Reading the out-of-scope list often generates the most useful discussion in the whole meeting — if something you expected to be included is out of scope, now is the right time to raise it.
09:50
10 min
Key Milestones and Timeline Overview
Presenter: Project Manager
High-level schedule showing the major milestones and delivery dates. Do not attempt to walk through every task — show the shape and rhythm of the project. Highlight any hard deadlines driven by external factors (regulatory, contractual, seasonal).
10:00
10 min
Roles and Responsibilities (RACI Walkthrough)
Presenter: Project Manager
Walk through the RACI matrix for key decisions and deliverables. Clarify who is Responsible, Accountable, Consulted and Informed. Ask explicitly: "Is there anyone who expected a different role on this?" Ambiguous accountability here causes delays later.
10:10
10 min
Top Risks and Assumptions
Presenter: Project Manager
Present the 3–5 highest risks and the key assumptions the project is built on. Ask the team to identify any risks you have missed. The kickoff meeting is often where the best risk intelligence surfaces — the people in the room know things the PM does not.
10:20
10 min
Ways of Working
Presenter: Project Manager
Tools (project management, communication, document storage), meeting cadence (weekly status, sprint reviews), escalation path and how decisions will be made. Getting explicit agreement here prevents passive-aggressive behaviour around tools and processes later.
10:30
15 min
Questions and Open Discussion
All attendees
Structured open floor. Work through the parking lot items first. Encourage questions — silence is not necessarily agreement. If a question cannot be answered in the meeting, name who will answer it and by when.
10:45
10 min
Actions and Next Steps
Presenter: Project Manager
Confirm every action arising from the meeting: what, who, by when. Read them back out loud. If an action does not have a named owner and a due date, it is not an action — it is a hope. Confirm the date of the next project meeting.
10:55
5 min
Close
Facilitator: Project Manager
Thank attendees. Re-state the project's importance and the team's collective role. End on time — finishing early or on the dot sends the signal that you respect people's time and run a tight ship. That signal matters.
02 — Preparation
Kickoff Preparation Checklist — 48 Hours Before
The meeting is won or lost in the preparation. A PM who walks in with a prepared agenda, pre-aligned sponsor, distributed pre-reading and confirmed logistics runs a qualitatively different meeting from one who improvises.
✓
Brief the sponsor before the meeting. Agree what they will say in the Project Background slot. They should speak from strategic conviction — not read from your slides. 15 minutes of pre-alignment saves 30 minutes of confusion in the room.
✓
Send pre-reading 48 hours in advance. Distribute the Project Charter, draft plan and initial RACI so attendees arrive with context. The meeting should focus on discussion and alignment — not on reading documents aloud.
✓
Prepare a 5-slide deck maximum. Welcome/objectives, strategic context, scope, milestones and RACI. That is enough. More slides signal you do not trust the discussion to carry the meeting.
✓
Confirm all attendees have accepted the invite. Chase anyone who has not responded. A key stakeholder who does not attend the kickoff will feel unaligned from the start — and will act accordingly.
✓
Test the technology. Screen sharing, video conferencing, whiteboard tools — test all of it the day before. A 15-minute technical setup at the start of a kickoff kills momentum before it has started.
✓
Prepare a parking lot. Create a visible space (whiteboard, shared doc, chat thread) for questions and items that arise but are out of scope for the current agenda item. This keeps the meeting on time without dismissing valid concerns.
✓
Have the action items table open and visible. Use the action items section of the template (or the Action Item Tracker) on a shared screen so everyone can see actions being captured in real time. This improves accountability instantly.
03 — Best Practice
Kickoff Meeting — What Works and What Doesn't
The most common kickoff mistakes are structural — too long, too passive, too focused on presenting rather than aligning. These two lists are drawn from real project experience.
✓ What Works Well
Send pre-reading 48 hours before — the meeting is for discussion, not delivery
Let the sponsor open — "why this matters" lands differently from the right person
Read the out-of-scope list aloud — it generates the most useful discussion
Ask explicitly about role expectations — silence is not agreement
Capture actions on a visible shared screen in real time
End on time — it signals professionalism and respect
Send minutes and actions within 24 hours while context is fresh
✗ What Goes Wrong
Running over 90 minutes — energy and retention collapse after this point
Reading slides aloud to people who can read them faster than you speak
Skipping the out-of-scope section — "assumed included" becomes the PM's problem
No sponsor presence — the team assumes the project is low priority
Vague actions: "someone will look into that" — not an action
Inviting everyone — 25 people cannot have a focused alignment conversation
No follow-up — half the attendees will forget the meeting within 48 hours
The single most impactful preparation: Walk through the agenda with the sponsor one-to-one before the meeting. Agree exactly what they will say and for how long. A sponsor who understands their role in the meeting — and arrives prepared to play it — transforms the energy in the room in ways that no slide deck can match.
04 — After the Meeting
What to Do Immediately After the Kickoff
A great kickoff meeting that is not followed up within 24 hours loses most of its value within a week. The energy and alignment created in the meeting has a short half-life — the follow-up is what converts it into lasting momentum.
Within 24 Hours
Send the meeting minutes and action items to all attendees. Use the Meeting Minutes template and the Action Item Tracker alongside this agenda. Include a summary of what was agreed on scope, roles and ways of working — not just the action list. This becomes the reference document for the first few weeks of the project.
Within 48 Hours
Publish the action items in the shared project space (Teams, SharePoint, Confluence — wherever the team agreed to work). Set up any recurring meeting invites agreed in the ways of working discussion. Ensure the Risk Register is updated with any risks surfaced during the meeting.
First Status Meeting
Open the first project status meeting by reviewing actions from the kickoff. This reinforces that actions from meetings are taken seriously from the very first session — a behaviour that pays dividends for the entire project lifecycle.
PMP exam note: In the PMBOK framework, the kickoff meeting is an output of the Develop Project Management Plan process and marks the transition from planning to execution. The PMP exam may test whether you know that the kickoff meeting comes after the project management plan is approved — not before. It is also tested in the context of stakeholder engagement: the kickoff meeting is the primary tool for communicating the project plan to the team and aligning expectations at project start. See our 200 PMP practice questions for scenario questions on project initiation and kickoff.
05 — FAQ
Kickoff Meeting — 4 Common Questions
A project kickoff meeting is the first formal meeting of the project team and key stakeholders after the project has been approved. Its purpose is to introduce the team, align on objectives and scope, confirm roles and responsibilities, review the high-level schedule and risks, agree on ways of working, and generate the commitment needed to start the project effectively. A well-run kickoff prevents many misunderstandings that would otherwise surface — and derail — the project weeks or months later.
A complete kickoff agenda should cover: welcome and introductions; project background and strategic context (from the sponsor); project objectives and success criteria; scope — what is in and out of scope; key milestones and the high-level timeline; roles and responsibilities (RACI walkthrough); top risks and assumptions; ways of working — tools, communication channels, meeting cadence; open Q&A; and action items from the meeting. The meeting should not exceed 90 minutes — 60 minutes is achievable with strong preparation.
The kickoff should include all core project team members, the project sponsor or their representative, key stakeholders significantly affected by the project, and any major suppliers or vendors who are part of the delivery team from day one. It should not include every stakeholder — people with minor or tangential involvement do not need to attend and their presence can make focused alignment harder. For large programmes, separate workstream kickoffs are more effective than one large meeting.
For most projects, 60–90 minutes is the right length. Shorter risks leaving important topics uncovered; longer risks losing the room's attention. The key is preparation: a PM who has prepared the agenda, pre-aligned the sponsor and distributed pre-reading 48 hours before can cover all essential topics in 60 minutes focused on discussion and alignment rather than information delivery. Sending a project charter, draft plan and RACI as pre-reading means attendees arrive with context — not questions.
Explore More Free PM Resources