Project Handover Checklist

A clear plan to transfer a project to a new owner or team without losing knowledge.

Published June 27, 2026

Download PDF

Prepare the Handover

Confirm the incoming owner and the handover date
Agree on an overlap period for questions and support
Even a week of overlap reduces costly gaps.
Tell stakeholders who their new point of contact will be
List everything that needs to transfer
Schedule the knowledge-transfer sessions in advance

Document the Project

Write a current status summary with open items
List active tasks, deadlines, and dependencies
Document known risks, issues, and workarounds
Highlight active blockers and recurring technical glitches so the incoming lead is not blindsided.
Record key decisions and the reasons behind them
Create a directory of key contacts and vendors
Note where all files and systems are located

Transfer Access and Credentials

List all systems, tools, and accounts in use
Grant the new owner the access they need
Transfer or reset shared passwords securely
Use a password manager, never plain email.
Reassign ownership of files, repos, and folders
Update licenses and subscriptions to the new owner
Confirm the incoming owner can log in to everything
Have them test every tool while you are still available to troubleshoot permissions or 2FA issues.

Run Knowledge Transfer

Walk the new owner through the project end to end
Demonstrate recurring tasks and routine processes
Explain stakeholder relationships and expectations
Cover common problems and how to handle them
Record sessions or notes the owner can revisit
Recordings help when questions surface later.

Verify the Handover

Have the new owner complete a key task on their own
Shadowing while they execute a real task confirms true comprehension far better than passive listening.
Review the handover document together for gaps
Confirm all access works as expected
Answer any remaining questions before stepping back
Agree on who to contact for follow-up issues

Sign Off and Close

Confirm both owners agree the handover is complete
Get written sign-off from the manager or sponsor
Formal sign-off establishes clear accountability and confirms the transition period has officially ended.
Revoke the outgoing owner's access where appropriate
Remove old access promptly to keep systems secure.
Send a final note announcing the new owner
Archive the handover documents for reference

0 / 32 done

A project handover checklist is the task list you use to transfer a project, system, or role to a new owner or team. It covers documentation, access and credentials, knowledge transfer, and a formal sign-off so the incoming owner can take over without gaps.

Handovers fail when key knowledge lives only in one person's head. A structured handover moves that knowledge into documents, sessions, and shared access before the original owner steps away.

This checklist suits managers transitioning a project, teams onboarding a new owner, or anyone leaving a role and passing it on.

Download the printable PDF, work through it with both the outgoing and incoming owners, and check off each item as it transfers. The result is a clean handover where the new owner is confident and nothing falls through the cracks.

FAQ

What is a project handover?

It is the transfer of a project, system, or role from one owner to another. It moves documentation, access, and knowledge so the new owner can continue the work smoothly.

What should a handover document include?

Project status, key contacts, open tasks and risks, system access, recurring duties, and where files live. The goal is a single reference the new owner can rely on from day one.

How do I do a good knowledge transfer?

Combine clear documentation with live sessions. Walk the new owner through the work, answer questions, and overlap for a period so they can ask while you are still available.

Who should be involved in a handover?

The outgoing owner, the incoming owner, and the manager or sponsor who confirms the transfer. Key stakeholders should also be told who their new contact is.

Who needs to approve and sign off on the project handover?

It depends on your organization, but sign-off usually involves the outgoing project lead, who confirms documentation and access are handed over, and the incoming owner, who confirms they have what they need. Many teams also ask the project sponsor or a manager to approve the transfer of responsibility.

How should unresolved issues and ongoing risks be managed during handover?

Document all active risks, technical debt, and pending blockers in a dedicated section of the handover register. For each item, record its current status, potential impact, temporary workarounds, and planned next steps. The incoming owner should explicitly review and accept these items so no lingering problems are overlooked or dropped once the transition concludes.

Built from public guidance and kept up to date — how we write our checklists. Spotted a mistake? Tell us.