All topics

Project Kickoff

Category: Project Management

Project kickoff capture: scope, goals, roles, success criteria, risks, stakeholders, communication plan, and next steps.

When to use this template

Use it at the first formal alignment meeting for a new project — the conversation where the team agrees on what is being built, who is doing what, what "done" looks like, and what the risks are. For a recurring weekly status, see Status Update. When the project wraps up, use Project Closeout.

Fields captured

Project name — the working title of the project.
Objectives — what the project is trying to achieve.
Scope (in) — what is in scope.
Scope (out) — what is explicitly not in scope.
Success criteria — how the team will know it succeeded (measurable where possible).
Key milestones — name, target date, and description per milestone.
Roles & responsibilities — name, role, and responsibilities per person.
Stakeholders — name and their interest or influence on the project.
Risks & assumptions — each marked as risk or assumption, with a mitigation or note.
Constraints — hard limits the team must operate under.
Communication plan — how updates, decisions, and escalations will flow.
Next steps — tasks with optional owner and due date.
Open questions — unresolved questions to come back to.

The standard summary, attendees, and per-section summaries also apply.

Sub-views, role views, and pipeline artifacts

Sub-views: none.
Role views: Sales Engineer, Account Executive, Project Manager, Executive Sponsor.
Pipeline artifacts: Project charter (Project Kickoff only; one-click generate) and Email draft (recipient, tone, optional subject hint).
Study mode: not available.

Exports

PDF, DOCX, and Markdown include all synthesis fields. The approved project charter appears as its own appendix with project name, sponsor, objectives, scope (in/out), stakeholders, milestones, and success criteria.