How to run a project kickoff meeting: agenda, checklist and example

What a kickoff meeting is for

A kickoff meeting turns an approved idea into a shared plan. Before it, the project lives in a charter, a budget line and a few people's heads. After it, everyone who will do the work has heard the same story and knows their part.

A good kickoff does four jobs:

• Purpose: explain the problem the project solves and what success looks like, in measurable terms.
• Scope: state what is in, what is out, and the main deliverables.
• People: introduce the team, the sponsor and the key stakeholders, and confirm who decides what.
• Ways of working: agree how you will plan, report, raise issues and approve changes.

There are often two kickoffs. The internal kickoff is for the delivery team. The client or sponsor kickoff is for the people paying for or receiving the result. Small projects can combine them. Large ones usually hold the internal one first, so the team arrives at the client meeting aligned.

Before the meeting: preparation checklist

Most of the value of a kickoff is created before anyone enters the room. Work through this list in the week before:

1. Confirm the sponsor will attend and open the meeting, even for ten minutes.
2. Finalise the invite list: core team, sponsor, key stakeholders. Keep it under about 15 people so discussion is still possible.
3. Prepare a short deck or document: goals, scope, milestones, team and roles, risks, ways of working.
4. Draft a high-level timeline with the main milestones. It does not need to be final, but it must exist.
5. Draft a first responsibility split (a RACI or a simple owner list) for the main deliverables.
6. List the top five known risks and open questions.
7. Send the agenda and materials at least two working days ahead, and ask people to read them.
8. Book the room or video link, and name a note-taker who is not the facilitator.

A 60-minute kickoff meeting agenda

Use this agenda as a starting point. Stretch it to 90 minutes for larger projects by giving more time to scope and risks.

Time	Item	Led by	Output
0 to 5 min	Welcome and purpose of the meeting	Project manager	Everyone knows why they are here
5 to 10 min	Why this project matters	Sponsor	Business case in plain words
10 to 20 min	Goals, success criteria, scope in and out	Project manager	Agreed scope boundaries
20 to 30 min	Timeline and key milestones	Project manager	Milestone dates people accept
30 to 40 min	Team, roles and decision rights	Project manager	Confirmed owners for each deliverable
40 to 48 min	Risks, assumptions and open questions	All	First entries for the risk register
48 to 55 min	Ways of working: meetings, reports, tools, changes	Project manager	Agreed cadence and channels
55 to 60 min	Actions, owners, dates and next meeting	Note-taker	Action list read back to the room

How to run the meeting, step by step

1. Start on time and state the goal. Say what the meeting must produce: agreed scope, accepted milestones, named owners.
2. Let the sponsor speak first. Hearing the reason from the person who funds the work gives it weight that a slide cannot.
3. Make scope concrete. Show an "in scope" and an "out of scope" list side by side. The out-of-scope list prevents more arguments later than any other single item.
4. Walk the timeline, not the task list. Show five to ten milestones. Ask "what would stop us hitting this date?" and capture every answer as a risk or question.
5. Confirm roles out loud. For each deliverable, name one accountable person and ask them to confirm in the room.
6. Agree the rhythm. Weekly team check-in, status report frequency, where tasks live, how a change request is raised and who approves it.
7. Close with actions. Read every action back with an owner and a date. Anything without an owner is not an action.

Worked example: an office move kickoff

A company of 80 people is moving to a new floor in 16 weeks, with a budget of $150,000. The project manager sends a four-page pack two days before the kickoff. In the meeting:

• The sponsor (the operations director) explains the reason: the current lease ends, and the new floor must be ready for the first working day after it does.
• Scope in: fit-out, furniture, network and phones, the physical move. Scope out: new laptops, which belong to a separate IT refresh.
• Milestones: design signed off in week 3, fit-out complete in week 11, network live in week 13, move weekend in week 15, snag list closed in week 16.
• Owners: facilities lead for fit-out, IT lead for network, HR for staff communication, the project manager for the move plan.
• Risks raised: landlord approval for cabling could slip; furniture lead time could exceed eight weeks. Both go into the risk register with owners.

The meeting ends with nine actions, each with an owner and a date, and a weekly 30-minute check-in on the calendar.

Common kickoff mistakes

• Presenting for 60 minutes. A kickoff is a working session. If nobody asks a question, people have not engaged.
• No sponsor. Without the sponsor, the team hears the project manager's view of why it matters, which carries less weight.
• Skipping out of scope. Unspoken assumptions about scope become change requests later.
• Shared ownership. "Marketing and IT will handle it" means nobody will. Name one person.
• No written follow-up. If the notes and actions are not sent within a day, the meeting fades from memory.

After the meeting: follow-up checklist

• Send notes, decisions and the action list within 24 hours.
• Turn the milestones into a schedule with dependencies, so dates are calculated rather than typed.
• Enter the risks raised in the meeting into the risk register with owners and response dates. The project risk management guide explains the columns.
• Set up the task board or project space and invite everyone.
• Book the recurring check-in and the first status report date.

How to do this in Critova

In Critova you can create the project from a template (office move, product launch, client onboarding and others), so the kickoff pack starts from a sensible task list instead of a blank page. Add milestones on the timeline, assign owners to tasks, and log the risks raised in the meeting in the risk register, each with an owner and a response date. After the meeting, team members update their own progress from the My Work page, which also works on a phone. Browse the project templates to find a starting point.