Project Kickoff Meeting
The why, the what, scope and non-goals, risks, and working agreements. Run this well and the project doesn't drift.
Free, no sign-up. Editable, copy as Markdown, plain text, or calendar.
Pick a duration
Before the meeting
- Sponsor shares a one-page project brief 48 hours ahead
- Everyone reads the brief before the meeting
- Hiring manager or PM invites only the people with a role to play, not passive observers
After the meeting
- Publish kickoff notes and the risk register to a shared location
- Schedule the first working meeting while it's still fresh
- Send a three-line summary to stakeholders who weren't in the room
More agenda templates
About the project kickoff agenda
A project kickoff is a one-shot meeting that sets the trajectory of everything that comes after. A kickoff that skips the why produces teams that lose motivation halfway through. A kickoff that skips non-goals produces projects that scope-creep into oblivion. A kickoff that skips working agreements produces weeks of friction over decisions that should have taken five minutes in the kickoff. The agenda below is opinionated about all three because those are the blocks teams skip most often.
What is the goal of a project kickoff meeting?
The goal is shared understanding, not information transfer. By the end of the meeting, every person in the room should be able to describe the project in one sentence, know their role, and agree on what is explicitly out of scope. If you do not leave with those three things, the kickoff has failed its primary purpose.
How long should a kickoff meeting be?
Sixty minutes is the right default for most projects. Large cross-functional projects deserve ninety minutes so you can actually work through risks and non-goals rather than racing past them. Kickoffs under forty-five minutes almost always skip the hard conversations, which is why projects then have those conversations in week three instead.
Who should be in a project kickoff?
The people who will do the work, the sponsor, and any stakeholder whose decision could reshape the project. Passive observers should read the kickoff notes after, not sit in the room. Oversized kickoffs train the room to defer to the loudest voice and make it hard for the core team to actually commit to anything.
What should a kickoff produce?
A written project brief (updated after the meeting with anything new), a list of non-goals, a risk register, a RACI or equivalent responsibility chart, and a meeting cadence on everyone's calendar. If the kickoff ends without those artefacts written down, the next meeting is going to re-do the kickoff.
Frequently asked
- What should a project kickoff meeting agenda include?
- The why (business case), the what (goals and success criteria), scope and non-goals, timeline and milestones, risks and unknowns, working agreements, and commitments. Non-goals and working agreements are the two blocks teams skip most often and regret most later.
- How long should a project kickoff be?
- Sixty minutes is the right default. Complex cross-functional projects earn ninety. Under forty-five minutes you almost always skip the hard conversations on scope and risk, which the team then has to have anyway, just later and under pressure.
- Who should run the project kickoff?
- Usually the project manager or the person who will own delivery. The sponsor presents the why, then hands over to the delivery owner. If the sponsor runs the whole meeting, the team becomes an audience rather than the owners of the project.
- What is the difference between a project kickoff and a project plan?
- A kickoff is a meeting that aligns the team. A plan is a document that guides execution. Good kickoffs produce the first version of a plan, but the plan is not the kickoff. If you try to review a 20-slide plan during the kickoff, you will run out of time before you reach non-goals.
When to use this template
Every time a new project starts. Even on small projects, a 30-minute kickoff pays for itself in the first week. Skip only when the team has run the exact same play many times before.