A project handover should let the next owner find the current work, understand its state and take the next action. Start with the handover date, the person receiving it and a short description of what is being transferred.

Keep the handover alongside the actual deliverables. A local DOCX or Markdown file in Ulet is a practical place to write it.

A handover package lists current files, open issues and a receiving owner, with checks for access and follow-up.

Make the package usable without reconstructing the project. Original instructional illustration.

List what the new owner receives

Deliverable

Location

Current state

Next action

Review draft

handover/report-v03.docx

Two comments remain

Maya resolves comments by 12 November

Source table

handover/source.xlsx

Ready for review

Receiving owner checks the cited rows

Replace these sample entries with real locations the receiving owner can use. A folder name on your computer is only helpful if the other person can locate the corresponding folder.

Explain the open work

Record unfinished tasks, dependencies and decisions still needed. Give each one an owner and a next checkpoint. If a deadline depends on someone else, name that dependency so the new owner knows what to follow up.

Keep a distinction between the last confirmed state and an assumption. “Waiting for two comments” is clearer when you include who owes those comments and when they were requested.

The report draft has two reviewer comments left. Maya resolves them by 12 November and the new owner checks the revised draft.

Illustrative handover record for a report. Original instructional illustration.

Provide the smallest useful background

Explain the objective, the decisions that shape the current work and the important constraints. Link to detailed notes when the receiving owner may need them. A short decision log can provide the reasoning behind an earlier choice.

Run a handover check together

  1. Ask the receiving owner to find and open the required files.

  2. Confirm which copies are current.

  3. Review the next deadline and open issue.

  4. Agree who handles the first action after transfer.

  5. Record the handover date and any remaining questions.

Save the issued handover with a clear filename. The version-naming guide can help keep working and sent copies identifiable. Prepare the document in Ulet.