Project handoff meeting notes template
A handoff is complete when someone can take responsibility—not when a document has been sent. Keep outstanding work and acceptance visible.
Free template + filled example. No account required. How to use the Skill
- Made for
- Project delivery
- Suggested conversation
- 30–60 minutes
- Take it with you
- Markdown · Prismical Skill
See the finished note.
Use this when work moves between teams or owners. The fictional reporting dashboard is ready for a receiving team to inspect, but an unresolved permission check means acceptance is still conditional.
Notes / worked exampleProject handoff · Reporting dashboard
What is being transferred
Reporting dashboard v2 and its maintenance runbook are moving from the delivery team to operations.
Current state & known gaps
The delivery team has demonstrated the weekly refresh. Operations has not yet run it independently.
Receiving owner & acceptance
Ren is the receiving owner. Acceptance requires a successful independent refresh and verified access.
Access & reference material
Runbook location was shared in the project workspace. Operations service-account access remains unverified.
Open risks & support window
Unverified access could block the first refresh. No support window or response-time commitment was agreed.
Transfer actions
Lee will verify service-account access by Tuesday. Ren will try the refresh after access is confirmed; no completion date stated.
Read the source dialogue for this example
- Lee: We are handing reporting dashboard v2 and its maintenance runbook to operations. The runbook is in the project workspace.
- Lee: We demonstrated the weekly refresh, but operations has not run it independently.
- Ren: I will be the receiving owner. Acceptance needs a successful independent refresh and verified access.
- Lee: Service-account access is still unverified. I will check it by Tuesday.
- Ren: I will try the refresh once access is confirmed.
- Lee: We have not agreed a support window or response-time commitment.
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.
What is being transferred
Define the deliverable and the version or location. Distinguish operational responsibility from access to a document.
Current state & known gaps
Record what works, what remains incomplete, and what has been tested. Do not present a demo as production acceptance.
Receiving owner & acceptance
Name the receiving owner and the conditions for accepting responsibility. Silence or an email attachment is not acceptance.
Access & reference material
List the runbook, escalation path, and required access without placing secrets in the note. Mark permissions that still need verification.
Open risks & support window
Make unresolved risks explicit and record any agreed support period. Do not invent service-level commitments.
Transfer actions
Capture the next action on each side and the review point. Keep project ownership with the current owner until acceptance conditions are satisfied.
# Project handoff meeting notes template Date: [add date] Participants: [add names] Purpose: [add purpose] ## What is being transferred [Define the deliverable and the version or location. Distinguish operational responsibility from access to a document.] ## Current state & known gaps [Record what works, what remains incomplete, and what has been tested. Do not present a demo as production acceptance.] ## Receiving owner & acceptance [Name the receiving owner and the conditions for accepting responsibility. Silence or an email attachment is not acceptance.] ## Access & reference material [List the runbook, escalation path, and required access without placing secrets in the note. Mark permissions that still need verification.] ## Open risks & support window [Make unresolved risks explicit and record any agreed support period. Do not invent service-level commitments.] ## Transfer actions [Capture the next action on each side and the review point. Keep project ownership with the current owner until acceptance conditions are satisfied.]
Make it part of the meeting.
Before · prepare the receiving path
Ask the receiving owner what they need to operate the deliverable. Gather the relevant runbook, open issues, and access checklist before the meeting.
During · walk through a real task
Have the receiving team explain or perform a representative operation. Record gaps exposed by the walkthrough rather than treating the presentation itself as acceptance.
After · confirm responsibility explicitly
Check the acceptance conditions and record the transfer decision. Keep unresolved work assigned and make support boundaries clear instead of relying on informal availability.
What to watch for
- Marking a project handed over because the files were sent.
- Including access tokens or passwords in the runbook note.
- Assuming the delivery team has promised indefinite support.
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.
Who owns the project during a conditional handoff?
Make that explicit in the meeting and follow your team’s governance. This template keeps acceptance conditions visible so a transfer does not create a gap where both teams assume the other is responsible.
What should go in a handoff checklist?
Include a representative task, required access, references, unresolved issues, the receiving owner, and acceptance conditions. Add operational or contractual requirements specific to your project rather than relying on a generic checklist alone.
Keep the work moving.
Useful next steps for the conversation you are preparing for.
Project kickoff meeting notes template
Align a project around outcomes, scope, decision owners, dependencies, and first actions. Free kickoff notes template, worked example, and Prismical Skill.
Explore resource TemplatesCustomer onboarding meeting notes template
Align onboarding around the customer’s first outcome, setup owners, dependencies, and success check. Free notes template with an example and Skill download.
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 meeting minutes generator
Turn pasted meeting text into a reviewable minutes draft with discussion excerpts, decision candidates, and actions. Free browser-only tool; no account needed.
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.