How do I close out my part of a project when another team will continue it?

Prepare a continuation brief, not a full history of everything you did. The goal is to help the next team understand the current state and act without reconstructing it from scattered messages.

Include:

1. The purpose and current scope of the work.
2. What you completed, with references to relevant materials if your workplace uses them.
3. What is still open, blocked, or waiting for a decision.
4. Important decisions already made and the reason, if known.
5. Dependencies, upcoming dates, and people or teams the next owner may need to coordinate with.

Mark uncertain details as questions or assumptions rather than presenting them as settled. For example: “Assumption to confirm: the review still needs to happen before the draft is shared.” If ownership has not been agreed, say so plainly. A clear unknown is more useful than an invented answer.

Describe each open item in terms of status, next action, dependency, and consequence of waiting. Avoid vague entries such as “follow up on launch.” Instead, specify what needs to happen and what information is missing. Don’t label something urgent unless you can explain the deadline or impact; let the receiving team weigh it against its own workload.

Here is a copyable example using hypothetical project details:

“Open item: Confirm whether the draft can include the revised reporting fields. Status: Waiting for a decision from [team or role]. Next action: Ask [owner, if agreed] to confirm the fields by [date, if set]. Dependency: The draft cannot be finalized until this is settled. If delayed: The review date may need to move; confirm with the project coordinator. Ownership: Not yet agreed.”

Use one entry per meaningful task or decision. If a date is only a suggestion, label it as proposed rather than treating it as a commitment.

Record the decisions that constrain or explain the next steps, not every discussion. For each one, note the decision, who or what group made it if you know, when it was made if useful, and the rationale that was actually given. Link to the relevant record where appropriate, but include enough context that the brief makes sense on its own.

Separate three things: confirmed decisions, proposals that were discussed but not approved, and questions that remain open. For example:

“Confirmed: Use the current draft structure for the next review. Reason recorded: it matches the agreed review scope. Not confirmed: whether the later phase will use the same structure. Open question: receiving team to decide whether that matters for its next milestone.”

This helps prevent an old suggestion from being mistaken for a commitment. It cannot guarantee that nobody will revisit a decision; the receiving team may have new information or authority to change direction. Make the earlier context easy to find without implying a decision can never change.

Use the meeting to check understanding and agree the transition, rather than reading the brief aloud. Walk through the current state, pause at open items and dependencies, and ask the receiving team what is unclear or missing. Confirm which tasks it accepts, who will coordinate unresolved ownership, and what communication or review point comes next. Record any changes to the brief after the discussion.

A closeout is clearer when everyone can answer these questions: What did I finish? What remains? Which details are confirmed versus uncertain? What has the receiving team agreed to take on? What still needs an owner or decision? If an item has no agreed owner, keep it visible and raise it with the relevant project coordinator or manager rather than silently treating it as transferred.

You can close with: “I’ve documented my completed work and the remaining items. We’ve confirmed [agreed items] will move to [team or role]; [unassigned item] still needs an owner. I’ll update the brief with today’s clarifications.” This states the boundary of your contribution without implying that you control the next team’s priorities.