The kickoff meeting is the first meeting that brings together every actor of a project: sponsor, project manager, team, business owners and, when relevant, the client. Its purpose is easy to state and hard to achieve: everyone leaves with the same understanding of the objectives, the scope, the roles and the next steps. A project that starts without a kickoff almost never catches up on the implicit expectations nobody wrote down. This guide gives the definition of a project kickoff meeting, its objectives, who to invite, a 60 to 90 minute model agenda, the preparation from D-15 to D-day, the content of the presentation, the minutes, the common mistakes and a reusable checklist.
Kickoff meeting: definition and objectives
A kickoff meeting is the official start meeting of a project. It takes place once the project has been approved — scoping done, budget and project manager named — and before production work begins. It is neither a scoping meeting (the objectives are already set) nor a design workshop (the detail comes later). The kickoff aims at four results:
- Align: everyone knows why the project exists, what is expected and what is not.
- Organise: roles, responsibilities and decision paths are named and accepted.
- Commit: participants make visible commitments in front of the others, starting with the sponsor.
- Launch: the meeting ends with a macro schedule, first dated actions and a date for the next checkpoint.
Who to invite to the kickoff meeting, and why
A kickoff gathers eight to fifteen people depending on the size of the project. The rule: invite everyone whose absence would force you to hold the meeting again, and only them. Each invitee must know what is expected of them during the session.
| Role | Why they are there | What is expected of them in the meeting |
|---|---|---|
| Sponsor | Carries the project with senior management | Opens the meeting, restates the stakes, confirms the budget and the priorities |
| Project manager | Runs the project day to day | Prepares and facilitates, presents scope, schedule and organisation, writes the minutes |
| Project team (key contributors) | Does the work | Understands scope and schedule, raises constraints and risks |
| Business owners | Own the need | Validate the objectives and the scope, name their points of contact |
| Resource managers | Lend the people | Commit to the availability of their teams on the planned dates |
| Client or end users (external kickoff) | Receive the deliverable | Confirm expectations, acceptance criteria and the approval path |
| PMO (optional) | Guardian of the method | Restates the reporting rules and the portfolio governance bodies |
Internal kickoff or client kickoff: two different meetings
On a project delivered for a client (agency, IT services, consulting), the launch happens in two steps: an internal kickoff, then a client kickoff. Mixing them means negotiating internal questions in front of the client, or discovering their expectations after having planned.
| Internal kickoff | Client kickoff (external) | |
|---|---|---|
| When | Before the client kickoff | One to two weeks after the internal kickoff |
| Participants | Team, project manager, management, sales | Client, client-side sponsor, project manager, team leads |
| Objective | Assign roles, check feasibility and margin, prepare the questions for the client | Align expectations, validate the contractual scope, set up the shared governance |
| Sensitive topics | Real workload, internal risks, sales history | Scope and out of scope, acceptance criteria, approval path |
| Tone | Frank, operational | Reassuring, structured, formal |
| Output | Team plan and list of questions | Minutes approved or signed by the client |
Preparing the kickoff: from D-15 to D-day
The quality of a kickoff meeting is decided before the session. A five-step preparation fits in two weeks.
- D-15: set the date with the sponsor and the indispensable decision-makers, book the room or the video call, block the calendars. A kickoff without a sponsor gets postponed.
- D-10: re-read the project charter, list the points still open (fuzzy scope, unconfirmed resource) and settle them beforehand, one to one.
- D-7: build the kickoff presentation (see below), the macro schedule and the roles matrix; review them with the sponsor.
- D-3: send the invitation with the timed agenda, the presentation and a clear instruction: what each participant must prepare or validate.
- D-1: rehearse the facilitation, test the video call and screen sharing, appoint a note taker, prepare the action table.
Model kickoff meeting agenda (60 to 90 minutes)
A kickoff lasts between one hour and one hour and a half. Beyond that, attention drops and decisions get diluted. The model agenda below is calibrated for 75 minutes; adjust the durations, not the order.
- Opening by the sponsor (5 min): why this project, why now, what will change at the end.
- Round table (5 min): name, role in the project, availability. Short, but essential for teams that do not know each other.
- Objectives and success criteria (10 min): three to five measurable objectives, and how you will know the project succeeded.
- Scope and out of scope (10 min): the expected deliverables and, just as important, what will not be done.
- Macro schedule and milestones (10 min): the main phases, the dated milestones, the known dependencies.
- Organisation, roles and governance (10 min): who does what, who decides, which committees at which frequency.
- Risks and constraints (10 min): the risks already identified, the resource, budget or calendar constraints.
- Ground rules (5 min): tools, recurring meetings, approval path, where the documents live.
- Questions, next steps and actions (10 min): answers to questions, the first five actions with owner and date, next meeting.
What a kickoff presentation contains
The kickoff presentation is the document that will remain: absentees will read it, newcomers will refer to it. Fifteen slides are enough. One slide per section, one message per slide, the details in an appendix.
- Context: where the project comes from, which problem it addresses, what has already been decided.
- Objectives: three to five measurable objectives and their success criteria.
- Scope: deliverables included, excluded, and the assumptions the estimate relies on.
- Macro schedule and milestones: the phases, the dated milestones, the target end date.
- Organisation and roles (RACI): the project org chart and, for each major deliverable, who is responsible, who approves, who is consulted, who is informed.
- Governance and committees: weekly project committee, monthly steering committee, who sits on them, what is decided there.
- Identified risks: the five major risks, their impact and the planned response.
- Ground rules: tracking tools, rituals, document management, expected response times.
- Next steps: the actions of the next two weeks and the date of the first project committee.
After the kickoff: minutes and the first five actions
The kickoff produces nothing until its minutes are sent. Send them within 48 hours, two pages at most: participants, decisions taken, open questions with their owner, and the list of actions. The first five actions of a project are almost always the same:
- Create the project in the tracking tool with its members, their roles and the macro schedule.
- Schedule the governance bodies: first project committee and first steering committee in the calendars.
- Record the risks raised in the meeting, with an owner and a response.
- Close the open questions: every point left fuzzy has an owner and an answer date.
- Confirm the resources: each manager confirms in writing the availability announced in the meeting.
Common kickoff meeting mistakes
Kickoffs that fall flat almost always make one of these mistakes:
- Launching without the sponsor: the meeting loses its authority, and the commitments made do not hold.
- Turning the kickoff into a workshop: the discussion dives into the detail of one feature and never reaches roles or schedule.
- Presenting a scope without an out of scope: everything not explicitly excluded will be requested later.
- Forgetting the resources: a schedule presented without the managers having confirmed their teams’ availability is a wish.
- Delivering a monologue: ninety minutes of slides without a round table or questions; nobody commits.
- Not concluding: the meeting ends without actions, owners or a date for the next checkpoint.
- Not recording anything: the minutes arrive ten days later, or never; the decisions get reopened at the first committee.
Reusable kickoff checklist template
The checklist below covers the whole cycle. Copy it into your tracking tool and tick it project after project.
- Before: date validated by the sponsor; indispensable participants confirmed; project charter re-read; presentation built and reviewed; macro schedule and milestones ready; invitation sent with agenda and instructions; note taker appointed.
- During: sponsor opens the session; round table done; objectives and success criteria validated; out of scope made explicit; roles and governance accepted; risks listed; ground rules set; actions recorded with owner and date; next meeting scheduled.
- After: minutes sent within 48 hours; project created in the tool with members and schedule; committees scheduled; risks and actions recorded; presentation and minutes archived; availability confirmed in writing.
The kickoff in FoxPlan
In FoxPlan, the outcomes of the kickoff become the working project directly: the project is created with its members and their roles, the macro schedule and the milestones are laid out in the Gantt chart, the committees (project committee, steering committee) are scheduled as recurring sessions with their agenda, and the risks and actions raised in the meeting are recorded from day one, attached to the project. The kickoff presentation and the minutes are attached to the project as files, available to the whole team. The momentum of the first day is not lost in transcription.
See how to do it in the FoxPlan documentation ↗
Frequently asked questions
What is a kickoff meeting?
A kickoff meeting is the official start meeting of a project. It brings together the sponsor, the project manager, the team, the business owners and sometimes the client to share the objectives, the scope, the schedule, the roles and the ground rules, so that everyone starts with the same understanding.
Who should attend a project kickoff meeting?
The sponsor, who opens the meeting; the project manager, who prepares and facilitates; the key contributors; the business owners; the managers who lend the resources; and, for an external project, the client. Eight to fifteen people, each with a defined role during the session.
How long should a kickoff meeting be?
Between 60 and 90 minutes. Shorter, there is no time for questions and commitments; longer, attention drops. A timed agenda of nine items, with 5 to 10 minutes each, fits in 75 minutes.
How do you prepare a kickoff meeting?
Set the date with the sponsor fifteen days ahead, re-read the project charter and settle the open points one to one, build the presentation and the macro schedule a week ahead, send the invitation with a timed agenda three days ahead, and rehearse the day before.
What should a kickoff presentation include?
Nine sections: context, objectives and success criteria, scope and out of scope, macro schedule and milestones, organisation and RACI roles, governance and committees, identified risks, ground rules, next steps. About fifteen slides, one message per slide.
What is the difference between an internal kickoff and a client kickoff?
The internal kickoff, held first, assigns roles within the team, checks feasibility and margin and prepares the questions for the client. The client kickoff, one to two weeks later, aligns expectations, validates the contractual scope and sets up the shared governance. Internal topics such as real workload or margin are never discussed in front of the client.
