Project kickoff meeting agenda template (60 minutes)

By Admin · Published 6 October 2026

A kickoff meeting has one job: to leave everyone with the same picture of what the project is for, what is in it, who does what and what happens next. Most project trouble traces back to people holding different pictures. This agenda gets them into the open in an hour.

The agenda

Total time: 60 minutes. Adjust the times to fit your meeting; the order is what matters.

1. Welcome and introductions (8 min). Each person says who they are, their role on the project and one thing they bring. For people who have not met, add one light question.
2. Why this project (10 min). The problem it solves, who it is for and what success looks like. Use plain outcomes, not activities.
3. Scope and what is out (10 min). What the project includes and, just as important, what it does not. Write the exclusions on the page.
4. Roles and responsibilities (10 min). Who decides, who does the work, who must be consulted and who is kept informed. Check there is one owner for each area.
5. Timeline and milestones (10 min). The key dates, what depends on what, and who owns each milestone. Agree the next checkpoint.
6. Risks and open questions (8 min). What could go wrong, what is not yet known and who will find out. Capture them without solving them all now.
7. How we work and next steps (4 min). Where updates live, how often the team meets, and the first three actions with owners and dates.

Project kickoff meeting agenda (60 minutes)
1. Welcome and introductions (8 min): Each person says who they are, their role on the project and one thing they bring. For people who have not met, add one light question.
2. Why this project (10 min): The problem it solves, who it is for and what success looks like. Use plain outcomes, not activities.
3. Scope and what is out (10 min): What the project includes and, just as important, what it does not. Write the exclusions on the page.
4. Roles and responsibilities (10 min): Who decides, who does the work, who must be consulted and who is kept informed. Check there is one owner for each area.
5. Timeline and milestones (10 min): The key dates, what depends on what, and who owns each milestone. Agree the next checkpoint.
6. Risks and open questions (8 min): What could go wrong, what is not yet known and who will find out. Capture them without solving them all now.
7. How we work and next steps (4 min): Where updates live, how often the team meets, and the first three actions with owners and dates.

An example

An illustration for a team of seven moving a company's help centre to a new platform. It is an example, not a real project.

• Welcome and introductions (8 min): each person gives their role and one thing the old help centre does that must not be lost.
• Why this project (10 min): customers cannot find answers, so support gets repeat questions. Success is fewer repeat tickets and faster search.
• Scope and what is out (10 min): in are article migration and search; out are redesigning the product pages and translating the content.
• Roles and responsibilities (10 min): one owner for content, one for the platform setup, one for search quality, with the head of support deciding priorities.
• Timeline and milestones (10 min): content audit first, then migration, then a two week trial with support staff before launch.
• Risks and open questions (8 min): old links may break, and nobody knows how many articles are out of date. Two people take these away.
• How we work and next steps (4 min): a weekly 20 minute check-in and a shared project page. Three first actions assigned.

Do the thinking before the meeting

A kickoff is not the place to work out the goals for the first time. Draft the purpose, a first scope and a rough timeline beforehand, and send them a day ahead. The meeting is then for testing the draft with the people who will do the work, which is where the corrections come from.

Say what is out of scope

Scope arguments in the middle of a project usually start with something nobody wrote down as excluded. Listing exclusions takes a few minutes and saves weeks of disagreement. Keep the list visible for the whole project and add to it when new requests arrive.

Be clear about who decides

Roles are the part teams skip, and the part that causes the most friction later. For each area, name one person who is accountable. If two people both think they own a decision, or neither does, it will stall. A simple table of who decides, who does, who is consulted and who is informed is enough.

Make people comfortable early

People who have not worked together are more careful about raising risks and questions in front of strangers. A short, easy opener helps. Try a question from the icebreakers for new teams, and use a random turn order for the introductions so nobody is singled out to start.

Cost matters too. Seven people in a 60 minute meeting at an average of 50 an hour is 350 of working time, which is well spent if everyone leaves with the same picture. The meeting cost calculator works it out for your own team.

More templates

• Weekly team meeting agendaA 30 minute weekly meeting: check-in, last week's actions, priorities, blockers and decisions.
• One-on-one meeting agendaA 30 minute one-on-one: check-in, their topics first, priorities, feedback and next steps.
• Sprint retrospective agendaA 60 minute retrospective in five steps: set the stage, gather data, insights, decisions and close.