Onboarding & Teamwork
Hand Over a Project You Are Leaving Without Losing Decisions or Ownership
Transfer a continuing project with decision rationale, usable access routes, recipient checks, and an explicit acceptance record with unresolved exceptions.
Hand over a project by agreeing who will own each responsibility, preserving the reasons behind important decisions, and checking that the recipient can use the relevant information and access routes. Finish with an explicit acceptance record that names remaining exceptions. A shared folder and a farewell walkthrough establish that material exists; they do not establish that someone has accepted responsibility.
This LandOffer.ai guide covers a lasting transfer when you leave a project, rather than temporary holiday cover or a weekly status update. The completed example is fictional. Its documents, walkthrough results, and acceptance messages illustrate a method; no real workplace transfer or system-access test was performed.

Define the transfer before collecting documents
Agree the transfer with the manager or other person authorized to assign continuing responsibility. Agree what is moving, to whom, when, and with what authority. A new project lead may coordinate delivery without being allowed to approve spending, accept a security exception, or change a customer commitment. Keep those decisions with their actual approvers.
Separate the project's continuing work from your departure tasks. The project may remain active after you leave. Closing your involvement does not mean its deliverables are complete, its risks have disappeared, or its operating team has accepted an unfinished release.
The Association for Project Management's handover research summary recommends an incremental transfer and documentation shaped around recipients' needs. Its context includes transition into ongoing operations. Applying that principle to a colleague taking over active work means checking what they need to decide and do, rather than copying every historical file into a new folder.
Ask the recipient which upcoming activities would be hardest without you. Those questions identify the most valuable knowledge to transfer. If a replacement has not been appointed, escalate that gap to the assigning manager. You can prepare evidence and explain the risks; you cannot make an unconsulted colleague the accountable owner by placing their name in a table.
Preserve decisions as well as the current plan
A project summary tells the recipient where work stands. A decision record tells them why it stands there. Together they help the recipient judge whether a proposed change would reopen a constraint the team has already investigated.
For each consequential choice, record the decision, rationale, alternatives considered, approver, evidence location, and conditions that would justify reconsideration. Mark an assumption as an assumption. A preference in a chat thread should not become an approved requirement merely because it appears in the handover document.
Salesforce's guidance on taking over an existing project recommends reviewing project records and understanding stakeholders and approval processes. Use that recipient perspective: could someone distinguish an active commitment from an abandoned idea without asking you to interpret every discussion?
Maintain an index pointing to the current plan, decision log, risk register, and access-request routes instead of creating competing copies. Identify the maintained plan, current issue list, and approved decision log. If a convenient summary becomes outdated, the recipient needs to know which underlying record controls. Include the date you last checked each important reference.
Completed handover package: an active search project
In this fictional case, Owen is leaving the Maple museum-collection search upgrade at the end of Week 4. Imani will become delivery lead, with manager Rafi approving the transfer. Curator Beatrice approves vocabulary changes; the platform duty team controls production index rebuilds. Imani can prioritize the agreed backlog but cannot approve new collection-data policy or execute production rebuilds independently.
The project is mid-delivery. A pilot search experience exists, and the next milestone is a curator review of the remaining synonym list. Owen's departure does not convert that pilot into an accepted public launch.
Here is the filled handover index, revision 2, prepared before the Week 3 recipient recheck. The locations are illustrative internal routes, not real links or instructions to access a museum system.
| Record | Completed handover content | Continuing owner and boundary |
|---|---|---|
| Project charter and plan | Search upgrade covers the public collection catalog; staff-only acquisition records remain excluded. Curator review is due Thursday of Week 4. | Imani maintains delivery plan; Rafi approves milestone changes. |
| Decision D-07 | Curators review synonyms before activation because an ambiguous term could merge distinct collection concepts. Bulk automatic activation was rejected. Revisit only with Beatrice's approval and documented review evidence. | Beatrice owns vocabulary approval; Imani tracks its delivery dependency. |
| Current work | Pilot complete for the agreed sample collection; 18 proposed synonyms reviewed, six awaiting curator review. Public launch remains unapproved. | Imani coordinates remaining review and the later launch-readiness decision. |
| Access register | Team workspace contains the plan, decision log, and issue queue. Request access through the service desk using the Maple project group. Production actions use the platform duty queue. No passwords are stored here. | Workspace administrator grants access; platform duty retains production execution. |
| Risks and exceptions | R-03: unresolved synonyms may affect relevance. R-04: the retired rebuild-queue alias has been corrected in revision 2; recipient recheck is pending at this point. | Beatrice owns R-03's content decision; platform duty owns R-04's execution route. Imani tracks both. |
| Responsibility and contacts | Rafi approves the Week 4 transfer; Imani is incoming lead; Beatrice is content approver; the platform duty role handles operational requests. Owen's support ends Friday of Week 4. | Team roles and maintained internal directory replace reliance on Owen's personal availability. |
The package gives Imani a usable starting point while preserving two unresolved items. It does not describe either risk as solved. It also distinguishes tracking a risk from having authority to accept it: Imani can maintain R-03 in the plan without overruling Beatrice's vocabulary decision.
An access register should describe where to request a capability and who approves it. Do not paste a departing person's token into a handover file. For a concrete product example, Atlassian's project permissions documentation distinguishes access levels and explains that sharing a link does not itself provide access. Your actual systems may use different roles and approval routes.
Ask the recipient to perform the next task
A walkthrough may leave an access or navigation gap undiscovered if the recipient only watches. Agree a few representative checks with the recipient. Have them find a decision, interpret a pending risk, locate the next work item, and identify how an authorized action would be requested. Use an approved non-production exercise where appropriate; a handover is not permission to alter a live system.
Imani's Week 2 walkthrough uses three checks. First, she finds D-07 and explains why automatic synonym activation remains excluded. Second, she identifies the six pending terms and Beatrice's approval role. Third, she attempts to locate the documented production-rebuild request queue without asking Owen for a private shortcut.
The first two checks pass within the fictional case. The third fails: the queue alias in the runbook is retired. Owen can still remember the replacement, but that memory is precisely the dependency the handover must remove. The failure becomes an assigned correction rather than a verbal assurance that “the team knows.”
In the fictional case, revision 2 replaces the obsolete alias with the maintained platform-duty entry point and names its role owner. In Week 3, Imani repeats the lookup and locates the correct request route. This verifies navigation in the example, not execution authority or rebuild success. The package records that distinction so nobody interprets a successful lookup as permission to operate production.
Run the transfer over four weeks, with a fallback
The following four-week sequence is filled for the Maple case. It is an editorial example, not a universal notice period or minimum handover duration. If less time is available, prioritize consequential responsibilities and gaps with the assigning manager rather than pretending the same checks have happened.

| Week | Work performed in the fictional case | Recorded result and next responsibility |
|---|---|---|
| 1: agree and inventory | Rafi confirms Imani as incoming delivery lead. Owen and Imani select the plan, D-07, current review queue, access routes, and two risks for the package. | Scope and Friday Week 4 support cutoff agreed; Imani accepts participation in the transfer, not full project ownership yet. |
| 2: demonstrate and challenge | Imani completes the three walkthrough checks; production-request navigation fails because the alias is retired. | R-04 remains open. Owen documents the mismatch; platform duty confirms the maintained route for the revision. |
| 3: revise and repeat | Owen publishes revision 2; Imani repeats the failed lookup and locates the maintained queue. No production action is executed. | R-04's documentation correction accepted. Production rebuild execution remains with platform duty. R-03 remains unresolved. |
| 4: lead and accept | Imani leads the planning review using revision 2. Thursday's curator review approves four of the six pending synonyms and leaves two unresolved. Rafi confirms the continuing delivery assignment. | Imani accepts delivery coordination from Friday 16:00 with R-03 still open; Beatrice retains the content decision. Owen's support ends at that same cutoff. |
Define an unavailable-person fallback before the final week. For Maple, if Owen becomes unavailable before the transfer is accepted, Rafi becomes interim delivery coordinator. Imani maintains the documented backlog within existing scope; production rebuilds wait for the established platform-duty process. Rafi uses the maintained records and role directory to resolve gaps instead of assuming Owen will answer later.
After Friday's cutoff, questions follow the new ownership map. Any additional help from Owen would require a separate, explicitly agreed arrangement; it is not part of the transfer's operating assumption. If no one can accept a critical duty by the cutoff, Rafi must allocate it or decide how the affected work is limited. A gap recorded in a document remains a gap.
Write an acceptance receipt with explicit exceptions
A receipt should state what the recipient accepted, the effective time, what they could verify, and what remains with someone else. “Thanks, received” establishes receipt of material. It may be insufficient evidence of an agreement to take responsibility for continuing work.
Here is the completed fictional receipt after the Week 4 review:
Maple handover acceptance — revision 2
Imani: I accept delivery coordination for the agreed collection-search upgrade from Friday, Week 4, at 16:00. I can locate the maintained plan, decision D-07, pending-review queue, and platform-duty request route. I led this week's planning review using those records.
Two synonyms remain unresolved under R-03. Beatrice retains vocabulary approval; I will track that dependency and bring any resulting milestone change to Rafi. Production rebuild execution remains with platform duty. This receipt does not approve a public launch or expand my production permissions.
Rafi: Confirmed. Imani owns continuing delivery coordination from the stated cutoff. Beatrice and platform duty retain the decisions and actions listed above. Owen's scheduled support ends at the cutoff; future work uses the maintained ownership routes.
The receipt does not require every project issue to disappear. It requires those issues to stay visible with continuing owners and agreed consequences. Retain any evidence required by the organization's own process; this example is not a prescribed contractual form.
If the recipient declines part of the transfer, record the declined responsibility and the reason. Ask the authorized manager to resolve the assignment, capacity, or access gap. Keep partial acceptance explicit until the authorized manager resolves the remaining responsibility.
Leave a record that survives your account
Before leaving, check whether important records depend on your personal workspace, ownership, notifications, or private bookmarks. Coordinate necessary changes through the approved administrators. Transferring a file, changing a project-owner field, and assigning a continuing operational duty may be separate actions with different permissions.
Preserve the decision history alongside the maintained current plan. Label superseded notes and retain records according to the team's policy; do not delete the evidence behind an inconvenient constraint. Make the main entry point discoverable to the people who will need it after your access ends.
A final check should answer: who owns the next decision, where can they find its context, how do they obtain the necessary access, and what happens if a named person is unavailable? Record the effective transfer time, accepted responsibilities, and unresolved assignments before closing your involvement. For more guidance on workplace transitions, return to LandOffer.ai after recording the accepted scope and the remaining exceptions in your team's own system.


