The value of a kickoff meeting template is that you never have to figure out how to run a kickoff from scratch. You start each new project engagement with a consistent structure, ask the same essential questions, and produce the same written output. What changes is the content — not the process.
Here’s a complete, usable template for the entire kickoff meeting process.
Part 1: Pre-meeting prep (send 24–48 hours before)
Email subject: [Project Name] Kickoff — Agenda
Body:
Hi [Client name],
Looking forward to our kickoff call on [day] at [time]. Here’s what we’ll cover:
- Project overview and goals
- Scope and deliverables confirmation
- Timeline and milestones
- What I’ll need from you
- Communication and feedback process
- Open questions
Please bring anything you want to clarify on the scope or timeline. If there’s anything specific you’d like to discuss that isn’t on this list, send it over and I’ll add it.
See you [day].
Part 2: The meeting template (45–60 minutes)
Use this as a running document during the call. Fill it in as the conversation happens.
[PROJECT NAME] — KICKOFF NOTES
Date: ___________ Attendees: ___________
1. Project overview
- Stated goal: ___________
- Success criteria (how we’ll know this worked): ___________
- Any unstated constraints or priorities that came up: ___________
2. Scope confirmation
- Deliverables confirmed: ___________
- Anything added or clarified from the proposal: ___________
- Explicitly out of scope: ___________
- Change order process confirmed: Yes / No
3. Timeline
| Milestone | Target Date | Dependencies / “Due from client by” |
|---|---|---|
| _____ | _____ | _____ |
| _____ | _____ | _____ |
- Hard deadline (if any): ___________
- Client feedback windows (how many days per milestone): ___________
4. Client responsibilities
- Primary point of contact: ___________
- Who approves deliverables: ___________
- Stakeholders who will review: ___________
- Assets to be provided: ___________
- Access credentials needed: ___________
- Due from client by: ___________
5. Communication
- Primary channel for messages and feedback: ___________
- Update frequency: ___________
- Best way to reach me for urgent questions: ___________
- File delivery method: ___________
6. Open questions and decisions made
Next steps:
| Action | Owner | Date |
|---|---|---|
| _____ | _____ | _____ |
| _____ | _____ | _____ |
Part 3: Post-kickoff summary (send within 24 hours)
Email subject: [Project Name] — Kickoff Summary
Body:
Hi [Client name],
Thanks for the call today. Here’s a summary of what we confirmed:
Project goal: [One sentence]
Deliverables:
- [Deliverable 1]
- [Deliverable 2] Not included: [Short list]
Timeline:
What I need from you:
- [Asset/access] by [Date]
- [Feedback on milestone 1] within [X] days of delivery
Communication:
- I’ll send [weekly updates / milestone updates] via [channel]
- Please send feedback to [email/tool]
Clarifications from the call:
- [Any changes or additions to what was in the proposal]
Please reply to confirm this looks right. I’ll start on [first task] and you’ll hear from me by [date].
Paste the post-kickoff summary into a project folder and keep it for the life of the engagement. It’s your reference document if any scope question comes up mid-project.
How to adapt this for different project types
For smaller projects (under 2 weeks), condense the timeline section to key dates only and skip the formal milestone table. The scope confirmation and communication sections always stay.
For larger projects with multiple stakeholders, add a stakeholder map to section 4: who needs to approve what, in what order, and who has final say when there are conflicting opinions.
For retainer engagements, replace the one-time timeline with a recurring deliverables schedule (what’s delivered each month, by when, with what review process).
Where this fits in your workflow
The kickoff meeting template is the third document in your project workflow, after the proposal and the contract. If you use a proposal tool like Waco3 to send and sign the proposal, the kickoff is the conversation where you confirm that what both parties signed off on is understood the same way by everyone.
Running the same template for every kickoff takes the cognitive load out of the process — you’re not reinventing it each time, you’re executing a proven structure. The specific decisions you make in each meeting are different; the process for capturing them isn’t.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
