Skip to main content
EasyPalmCards

Presentation10 cardsAbout 20 min to speakIntermediateWork

Project kickoff meeting script

Cue cards for running a project kickoff meeting: why the project exists, goals and scope, roles, timeline, ways of working, risks and the first actions, so everyone leaves aligned.

Use this template

Free to use, edit, print and study. No account needed: your set stays on this device.

The cards

  1. 1

    Welcome and purpose

    Thanks for joining. The aim of today is to make sure we all understand [project name], agree how we will work together, and leave with clear first steps.

    Quick round of names and roles: [prompt each person for name, role and one thing they hope to get from the project].

  2. 2

    Why this project

    We are doing this because [problem or opportunity].

    If it goes well, [who benefits] will be able to [outcome].

    The sponsor is [name or role], and success matters to them because [reason].

  3. 3

    Goals and success measures

    1. [Goal] – measured by [metric]
    2. [Goal] – measured by [metric]

    We will know we are done when [clear finish line].

  4. 4

    Scope

    In scope: [list]

    Out of scope: [list]

    Changes to scope go to [person or group] and are decided by [process].

  5. 5

    Roles

    • Project lead: [name]
    • Decision maker: [name]
    • Doing the work: [names and areas]
    • Consulted: [names]
    • Kept informed: [names or groups]
  6. 6

    Timeline and milestones

    • [Milestone] – [date]
    • [Milestone] – [date]
    • [Milestone] – [date]
    • Finish: [date]

    Fixed dates we cannot move: [list and reason].

  7. 7

    Ways of working

    • Check-ins: [frequency, length, day]
    • Where work lives: [tool or shared folder]
    • Quick questions: [channel]
    • Decisions recorded in: [place]
    • Response times we agree on: [e.g. within one working day]
  8. 8

    Risks and assumptions

    What could slow us down?

    • [Risk] – owner [name] – plan [step]
    • [Assumption we are making] – check by [date]

    Ask the room: What worries you about this project?

  9. 9

    Questions and parking lot

    Before we wrap up: what is still unclear?

    • Open question: [question] – owner [name] – answer by [date]
    • Parked for later: [topic too big for today]

    Write them where everyone can see.

  10. 10

    First actions

    1. [Action] – [owner] – [due]
    2. [Action] – [owner] – [due]
    3. [Action] – [owner] – [due]

    Next meeting: [date and time]. I will send notes by [day].

How to use this template

A kickoff meeting is where a project either starts aligned or starts with quiet confusion that surfaces weeks later. This template gives the project lead a running order for a 20 to 45 minute kickoff with the core team and key stakeholders. It moves from why the project exists to what success looks like, what is in and out of scope, who does what and when, and how the team will communicate. A risk card invites people to share worries early, when they are cheap to fix. The last card makes sure everyone leaves with named actions and dates. Share the cards as the agenda beforehand so people arrive with their questions ready.

Tips

  • Invite the sponsor to give the 'why' in their own words; it shows the project has real support.
  • Write the out-of-scope list carefully. It prevents more arguments later than anything else in the meeting.
  • Ask quieter team members directly for their view on risks; the best warnings often come from the people doing the detailed work.
  • Agree on one place for documents and one place for decisions, and stick to them from day one.
  • Capture actions on screen during the meeting so owners can confirm them before people leave.
  • Send the notes within a day while everyone still remembers what was agreed.
  • Leave the last five minutes free; kickoffs nearly always run over, and rushing the first actions defeats the purpose of the meeting.

Make it fit

  • For a small internal project, combine scope with goals and roles with ways of working, and run it in 15 minutes.
  • For a client project, add a card on how the client will review and approve work, and who signs off.
  • For a team across countries, rotate meeting times so the same people are not always joining early or late, and record the session.
  • For agile or sprint-based work, replace the timeline card with the first sprint goal and the date of the first review.
  • For community or volunteer projects, add a card on how much time each person can realistically give.

Updated October 28, 2026