Project Kickoff Checklist

Most projects that go sideways were set up wrong, not run wrong — unclear scope, a missing decision-maker, or a team that never agreed on what done means. This checklist walks the kickoff in order so everyone starts aligned. Work through it before you write a line of the plan, and see the rest of our work and onboarding checklists.

Curated by the Gisti team · Updated

Project Kickoff Checklist · 16 items

  1. Define the project goal, scope, and success criteria

    Write down what's explicitly out of scope, too — that's where scope creep starts.

  2. Identify the stakeholders and, crucially, the single decision-maker

    One clear owner of the final call prevents deadlock later.

  3. Confirm the budget and the resources you actually have
  4. Assemble the team and confirm each person's availability
  5. Define roles and responsibilities so ownership is unambiguous

    A simple RACI (who's responsible, accountable, consulted, informed) works well.

  6. Gather and document the requirements
  7. Break the work into milestones and a realistic timeline
  8. Identify dependencies and risks, and note a mitigation for each
  9. Choose your tools for tracking, docs, and communication
  10. Set up the project workspace: the board, repo, or shared folder
  11. Agree on a communication cadence and how status gets reported
  12. Define what done looks like for the first milestone
  13. Schedule the kickoff meeting and send an agenda in advance
  14. Run the kickoff: align on goals, plan, roles, and next steps

    Leave the room only when everyone can state the goal in one sentence.

  15. Document the decisions made and share the notes with everyone
  16. Confirm the first tasks and their owners before you close the kickoff

Make it yours in Gisti

Open this checklist in Gisti to tick items off, add your own, set reminders, and keep it in sync across Android and the web. AI can tailor every item to your exact situation.

Open Gisti

Open this checklist in Gisti

Free to start · Works on Android & the web · Not affiliated with GitHub Gist.

Related checklists

Frequently asked questions

What is a project kickoff meeting?

A kickoff meeting is the first formal meeting of a project where the team and stakeholders align on the goal, scope, roles, timeline, and next steps. Its purpose is to make sure everyone leaves with the same understanding of what's being built, who owns what, and how success will be measured.

What should a project kickoff cover?

A strong kickoff covers the goal and success criteria, the scope (including what's out of scope), the stakeholders and decision-maker, roles and responsibilities, the timeline and milestones, the main risks and dependencies, and how the team will communicate. It should end with agreed first tasks and owners.

Who should be in a project kickoff meeting?

Invite the core team who'll do the work, the project sponsor or decision-maker, and any key stakeholders whose input shapes the outcome. Keep it to people who genuinely need to align — anyone who only needs the outcome can be sent the notes afterward instead of attending.