Project kickoff meeting notes template
Start with a shared definition of success. Make the project’s scope, decision rights, and unresolved dependencies easy to revisit after the kickoff.
Free template + filled example. No account required. How to use the Skill
- Made for
- Project delivery
- Suggested conversation
- 45–60 minutes
- Take it with you
- Markdown · Prismical Skill
See the finished note.
Use this when a project moves from an idea into coordinated work. This fictional kickoff covers a customer onboarding refresh. A target date appears alongside its dependency so it cannot be mistaken for an unconditional promise.
Notes / worked exampleProject kickoff · Customer onboarding refresh
Outcome & success signal
Improve completion of the first workspace setup. The team will establish a baseline before choosing a completion-rate target.
Scope & exclusions
Refresh the setup checklist and invitation guidance. Billing changes are outside the project.
Roles & decision rights
Taylor owns delivery. Morgan approves changes to the onboarding flow.
Milestones & dependencies
A prototype is targeted for September 12, subject to access to the current setup analytics.
Risks & open decisions
Analytics access is not confirmed. The team has not decided whether invitation guidance needs a separate screen.
First actions
Taylor will request analytics access by Monday. Morgan will review the scope document; no review date was agreed.
Read the source dialogue for this example
- Taylor: We want more people to finish the first workspace setup, but we need a baseline before choosing a target.
- Morgan: Scope is the setup checklist and invitation guidance. Billing stays out.
- Taylor: I will own delivery. Morgan, can you approve onboarding-flow changes?
- Morgan: Yes. September 12 is a prototype target if we can get the setup analytics.
- Taylor: I will request analytics access by Monday. We have not decided whether invitation guidance gets a separate screen.
- Morgan: I will review the scope document.
Start with a blank page.
Keep the useful structure.
Each field earns its place. Use the prompts as reminders, then replace them with your own meeting evidence.
Outcome & success signal
Describe what should change and how the team will judge it. Separate a measurable target from an aspiration when no baseline exists.
Scope & exclusions
Name what is included and what is deliberately excluded. Record a change-control question if the boundary is not settled.
Roles & decision rights
Distinguish the person doing the work from the person making the final decision. Confirm responsibility rather than assuming it from seniority.
Milestones & dependencies
List the target milestone and its condition. Use explicit tentative language for dates the group did not commit to.
Risks & open decisions
Capture the uncertainty, its consequence, and the next step to resolve it. Do not mark a risk as resolved because it was discussed.
First actions
End with accepted actions, named owners, and stated dates. Leave missing dates visible rather than filling them with the project milestone.
# Project kickoff meeting notes template Date: [add date] Participants: [add names] Purpose: [add purpose] ## Outcome & success signal [Describe what should change and how the team will judge it. Separate a measurable target from an aspiration when no baseline exists.] ## Scope & exclusions [Name what is included and what is deliberately excluded. Record a change-control question if the boundary is not settled.] ## Roles & decision rights [Distinguish the person doing the work from the person making the final decision. Confirm responsibility rather than assuming it from seniority.] ## Milestones & dependencies [List the target milestone and its condition. Use explicit tentative language for dates the group did not commit to.] ## Risks & open decisions [Capture the uncertainty, its consequence, and the next step to resolve it. Do not mark a risk as resolved because it was discussed.] ## First actions [End with accepted actions, named owners, and stated dates. Leave missing dates visible rather than filling them with the project milestone.]
Make it part of the meeting.
Before · circulate the proposed boundary
Write a draft outcome, scope, and decision list so the meeting can resolve disagreements. Mark unknowns instead of presenting the draft as a finished project plan.
During · test shared understanding
Ask different participants to describe success and exclusions in their own words. Capture where those descriptions differ, especially around approval authority and milestone conditions.
After · circulate decisions and open items
Share a reviewed kickoff note with explicit unresolved questions. Revisit the scope when new work is requested; preserve the original decision and record the change rather than silently editing history.
What to watch for
- Assigning a target date to every action without agreement.
- Leaving the final decision-maker implicit.
- Treating an aspirational success metric as an established baseline.
Turn the template
into a Prismical Skill.
Import the file
Download the Skill JSON above. In Prismical, open Settings → Skills → Import and select the file. This downloads a file; it does not install anything automatically.
Run it on a note
Open the note with your meeting transcript. Run the imported Skill from the note dock. It asks for this template’s sections and appends the result for review.
Check before sharing
Verify quotes, owners, dates, and missing context against the transcript. AI can make mistakes. Keep the original note and follow your team’s sharing policy.
A few useful answers.
Practical details before you use this resource.
Is this a project charter?
It can inform one, but it is a meeting record. A charter may require additional approvals, commercial terms, or governance fields. Preserve the kickoff’s decisions and use your organization’s formal process where needed.
What if scope is still uncertain?
Write the uncertainty down and identify how it will be resolved. A kickoff can produce a discovery plan or a bounded first milestone without pretending that the whole project is already defined.
Keep the work moving.
Useful next steps for the conversation you are preparing for.
Stakeholder update meeting notes template
Write stakeholder updates with evidence of progress, changes to the forecast, risks, and clear decision requests. Free template and reusable Prismical Skill.
Explore resource TemplatesProject handoff meeting notes template
Transfer a project with clear status, receiving owners, open risks, access checks, and acceptance criteria. Free handoff template with a worked example.
Explore resource WorkflowsAI meeting notes for consultants
Build clearer client records with Prismical: kickoff scope, check-in decisions, and handoff acceptance. Includes reusable consulting meeting templates.
Explore resource Free toolsFree action items extractor
Find explicit action candidates in meeting text, with source lines and owner or timing hints. Review and copy the result. Free tool that runs in your browser.
Explore resourceBring your next conversation
into Prismical.
Capture the conversation, keep the transcript beside your notes, and reuse a Skill for the output you need. Review the result before you share it.