A project handoff that exposes the loose ends.

Define what is being handed over

Name the responsibility and its boundaries before summarizing the history. In this example, Leo takes coordination of a pilot results brief, not control of every system used by the project. The pilot end date is unknown, so the handoff cannot promise a reporting deadline from the information supplied.

Keep the original notes in a Project and ask for a handoff brief that cites H1–H10. The fictional filenames in these notes are references for a planning exercise; their contents are not attached. The Agent should not claim it has opened or validated files merely because their names appear in a paragraph.

Identify current, draft, and historical files

A handoff is easier to trust when it explains which file to use for which purpose. pilot-brief-v2.md is the current scope reference; v1 is superseded. metric-definitions.md contains the reviewed counting rule. results-draft.md is a draft with placeholder totals. The August brief is a format example, not evidence for current results.

With real files, verify that each reference exists and open the important ones. If two files both appear current, record the conflict and ask the owner to choose. Do not rely only on a larger version number or a later modification time when the approval status is unclear.

Keep access checks in the handoff

H8 says folder access was requested for Leo. That is different from a successful sign-in and a readable source file. Include a check that Leo can reach the required location using the intended account. Never put passwords, tokens, or private access links into a broadly circulated handoff to make that step seem complete.

Workspace Project files, external services, and other people’s permissions are separate access concerns. Creating the brief does not grant another person access to its referenced systems. Use the relevant sharing and connection controls, then verify the recipient’s experience before declaring the transfer ready.

Order the first steps by what they depend on

Leo should confirm the reporting period and source delivery with Priya before calculating totals. The agreed measure is accounts with a completed session, not individual users. Duplicate account IDs need an agreed treatment before the data can support a final count. These are practical prerequisites, not optional housekeeping after writing the summary.

The expected 2026-09-15 delivery is not confirmed. Preserve that distinction in the risk register and name the person who can resolve it. An effective handoff gives the incoming owner a clear starting sequence without inventing acceptance from anyone else.

Test whether a new owner can follow it

Read the brief as if you had not attended the project meetings. Can you identify the goal, current scope, source definitions, blockers, and next useful action without guessing? Check that the important warnings are next to the relevant files, especially the placeholder totals and the historical format example.

Ask the incoming owner to flag missing context before considering the handoff accepted. Acceptance might require accessible source files, an answered question, or a walkthrough. The template can draft that checklist, but the Agent cannot establish another person’s understanding or agreement from the outgoing notes alone.

Preserve the handoff as a dated checkpoint

Save the approved brief with its date and source references. Add subsequent decisions as dated updates so the project can distinguish what was known at handoff from what changed afterward. This is particularly useful when a delivery slips or a counting rule is corrected.

If a referenced file is missing or unreadable, list it as unverified and continue only with supported facts. Do not fill gaps from an older file without saying so. A concise incomplete handoff with explicit next checks is more useful than a polished document that conceals the missing inputs.

Try it with a small example.

An illustrative result.

Fictional sample, written to show the expected structure. Your result depends on your inputs and needs review.

Fictional expected handoff excerpt

Goal: prepare a pilot results brief after an end date that remains unconfirmed (H1).
Current scope: pilot-brief-v2.md; v1 is superseded (H2).
Measure: active accounts with at least one completed session; use account counts, not users (H3, H7).
Do not report results-draft.md totals: they are placeholders (H4).

First steps: verify Leo’s folder access (H8); confirm reporting dates and Priya’s delivery (H5, H6); agree duplicate-account handling (H9); then calculate and review results.
Expected delivery: 2026-09-15, unconfirmed.
Acceptance pending: accessible files, agreed dates, resolved duplicate rule, and incoming-owner review.

Before you use the result.

• All current, draft, superseded, and historical file references have distinct roles.
• Expected delivery and requested access are not described as confirmed.
• Placeholder totals and old reporting evidence are excluded from current results.
• The next steps respect data, date, and duplicate-rule dependencies.
• The brief records pending acceptance and does not claim a permission transfer.