Free meeting tools
Free Project Kickoff Meeting Template
Give the project a shared starting point. Agree on success, scope and responsibilities before turning the first milestone into an owned action.
No signup. Edit in your browser. Download Word .docx, text or Markdown.
Edit this templateA clear agenda. A useful record.
2. Add meeting details
All fields are optional. Apply your details when ready. Your latest edited draft stays available to restore.
Your notes stay in this tab.
Entries and drafts are kept in browser memory. Reloading or leaving this page clears them. Download a copy to keep your work.
3. Edit, copy or download
Ready to make your ownReplace the prompts in square brackets. Add notes during the meeting, then confirm decisions, owners and deadlines.
Word .docx opens in Microsoft Word and can be uploaded to Google Docs. .txt is plain text; .md adds Markdown headings. No document is uploaded automatically.
When to use this template
Use this template when the people delivering and approving a project need to agree how it will work. Bring the brief and known constraints. Use the meeting to resolve unclear responsibilities and decisions, then keep assumptions visible until they are checked.
Make it useful for your meeting
1. Agree what success will look like
Name the outcome and the evidence the project owner will use to accept it. Link the brief so participants can compare the goal with the original request.
2. Draw the scope boundary
List deliverables and exclusions in plain language. Distinguish agreed requirements from assumptions. Decide how a proposed change will be reviewed and who can approve it.
3. Connect milestones to dependencies
Give each milestone an owner, a target date and any prerequisite. Record risks with an action to investigate or reduce them. Check dates with the people expected to deliver the work.
4. Confirm how the team will work
Choose the update channel, review cadence and decision owner. Finish with the first actions and the next review date. Share the agreed document where contributors can find it.
A filled-in example
Fictional team example. Use it to see the level of detail, then adapt the editor above for your meeting.
Account setup guide kickoff Attendees: Alex (project owner), Sam (writer), Jordan (reviewer) Outcome: Publish a guide that explains invitations and first account setup. Acceptance: Jordan can follow the steps using a test account without clarification. In scope: Desktop guide, screenshots and review. Out of scope: A video walkthrough and translated versions. Milestone: Sam shares the outline by Tuesday. Dependency: Alex provides a test account before screenshot work starts. Risk: The invitation screen may change; Jordan will check it before approval. First action: Alex confirms account access on Monday. Next review: Thursday, with scope changes recorded for Alex to decide.
Common questions
What should happen before a kickoff?
Share the brief, the proposed outcome and known constraints. Ask participants to read them and bring open questions. If basic scope or sponsorship is still undecided, make that decision an explicit agenda item.
Who should attend a project kickoff?
Include the people needed to agree the outcome, do the work and approve key decisions. Add a dependency owner when their input is needed. Share the reviewed record with other contributors afterward.
Is this a full project plan?
It is a starting record for scope, responsibilities, milestones and risks. Move detailed tasks and ongoing status into the tools your team uses, then keep decisions and changes connected to this agreed starting point.
Your document stays in this tab. Copy or download it before leaving. The editor does not record a call, send your notes or save them to an account.