Project template
Project Kickoff Brief Template for Small Teams
A one-page kickoff brief for agreeing on the outcome, scope, owner, milestones and first action before work begins.
Why use a kickoff brief?
Small projects often begin with a conversation or a message. A short kickoff brief makes sure people leave with the same understanding of the goal, scope, deadline and owner. It is a shared reference, not a full project plan.
Copyable one-page project kickoff brief
Agree before work starts
Project name and approval date: Business outcome: Observable success measure: Scope included: Scope excluded: Single accountable owner: Contributors and approver: Milestones and target dates: Dependencies and assumptions: Risks and risk owner: Definition of done: First next action / owner / due date:
| Brief section | Questions to answer |
|---|---|
| Outcome | What should be different when the project is complete? |
| Success measure | What observable evidence will show that the outcome was reached? |
| Scope and exclusions | What is included, and what is explicitly outside this project? |
| Ownership | Who is accountable, who contributes and who approves the result? |
| Milestones and dependencies | What are the key checkpoints and what must happen first? |
| Definition of done | What must be true for the work to be accepted and closed? |
| First next action | What is the first step, who owns it and when is it due? |
Filled example (fictional)
Project: Launch a customer onboarding email sequence · Owner: Operations lead
- Outcome: New customers receive first-week information in a consistent order.
- Success measure: The sequence is approved, tested and ready for the defined customer group.
- Included: Draft the sequence, review it, configure the order and run a test.
- Excluded: Redesigning the website or changing the billing process.
- Approver: Customer operations manager.
- Milestones: Draft review Monday; approval Thursday; test Friday.
- Dependency: Support confirms the common first-week questions.
- Risk: Late support input may require another review cycle.
- First action: Operations lead collects support input by Tuesday.
The people and dates in this example are fictional.
How to agree on scope and ownership
- Send a draft before the kickoff so participants can spot missing assumptions.
- Agree on the outcome before listing tasks.
- Write down exclusions to make boundaries visible.
- Name one accountable owner and identify who approves the result.
- Confirm the first action, its owner and its due date before ending the conversation.
First-week follow-through
Keep the approved brief near the project work. Check whether the first action happened, whether a dependency changed and whether the milestones still make sense. Revisit the brief when the goal, scope, key date or approver changes. Record who agreed to a material change and when.
Frequently asked questions
Is a kickoff brief the same as a project charter?
They overlap. A kickoff brief is a lightweight alignment document for a small team. A formal charter may include additional governance and authorization details.
Who writes the project kickoff brief?
The project owner can draft it. The sponsor or approver and key contributors should confirm the goal, scope and acceptance criteria.
How long should a kickoff brief be?
For a small project, aim for one page. Add detail only when it helps someone make a decision or complete the work.
Can a brief change after kickoff?
Yes. Record material changes to scope, dates or success measures, including who approved them and when.
Connect the brief to the project work
A project brief is easier to use when the owner, milestones and next actions stay close to the work. See Clarityy’s project management workspace, the small-team week-one setup guide and how to manage projects without a project manager.