Build a project handover pack people can use

Define what is being handed over and to whom

Start with the scope of the transfer, the outgoing owner, the incoming owner and the intended handover date. Identify who can accept the handover on behalf of the business. That may be different from the person who will use the records day to day. Make the distinction clear before arranging the final review.

State whether the project is complete or whether live work is changing hands. A completed event pack moving into the archive needs different attention from a supplier coordination project with several outstanding commitments. Where only part of a project is transferring, describe the boundary and name the person retaining the other responsibilities.

Put an orientation page before the file list

The first page should give the recipient a quick but accurate view of the work. Summarise the purpose, agreed scope, current stage and next significant milestone. Record the date the summary was checked. Avoid describing an optimistic future position as though it has already happened.

Explain the few decisions that shaped the project and any constraints the next owner needs to respect. A short decision summary is more useful than expecting them to reconstruct the reasoning from months of messages. Refer to the underlying records where necessary, and flag assumptions that have not yet been confirmed.

• Purpose and agreed scope reference.
• Current position, checked on a stated date.
• Completed and accepted outputs, distinguished from drafts.
• Next milestone and immediate priorities.
• Important decisions, constraints and unresolved assumptions.

Index the records the next owner will actually use

Provide a concise index of current records and explain what each is for. Include the active tracker, approved outputs, relevant correspondence, process notes and the source documents needed for continuing work. Keep old drafts out of the normal route while preserving records the business needs under its own arrangements.

Check access with the incoming owner. A working link on your computer does not establish that the recipient can open the file or use the required system. Arrange appropriate access through the system owner; do not put passwords into the handover pack. Include who to contact if access fails and who is responsible for reviewing access after the transfer.

Give every open item an explicit next action

List unfinished tasks, outstanding decisions and dependencies separately from completed outputs. For each, include its owner, next action, due date or review point, and the consequence of delay. “Supplier outstanding” is insufficient. Say which confirmation is missing, the latest position and who will follow up.

In a fictional office-move coordination handover, the furniture delivery date is confirmed but building access is still awaiting the site contact. The incoming coordinator needs the contact, the last response, the next follow-up date and the decision route if access cannot be confirmed. A copy of the furniture order alone would not give them that context.

Identify commitments already made to other people, including updates that have been promised. Transfer those communication obligations explicitly so a customer or supplier is not left waiting because both coordinators assume the other will respond.

Use a walkthrough to test whether the pack works

Give the recipient time to read the pack, then use the review to work through a realistic next task. Ask them to find the current tracker, explain the next priority and locate the evidence for an important approval. This checks whether the structure supports action rather than merely looking complete.

Record questions and gaps as actions with owners. Some can be fixed before acceptance; others may be accepted as known limitations if the authorised person agrees. Do not describe a missing approval or inaccessible system as a minor note when it prevents the next owner from carrying out the responsibilities being transferred.

Record acceptance and the remaining responsibilities

Use a short acceptance record stating the scope transferred, pack version, date and accepting person. Note any exceptions, their owners and the agreed resolution. Confirm where new questions should go after handover and whether any further clarification is included in the arrangement. Availability after the transfer should be agreed, not assumed.

Update the live records so they show the new ownership. Tell relevant people through the agreed channels, remove superseded instructions from active use and arrange any access changes with the responsible system owner. Keep the accepted pack as the reference point. The transfer is complete when responsibility, information and practical access line up.