Let every person be quick to hear, slow to speak, slow to anger.James 1:19
A project can be finished enough to publish and still be difficult for another person to maintain. The original builder knows which file matters, which link is temporary, and which promise was deliberately left small. The next person sees a folder, a live page, and an unanswered question. A useful handover makes the operating knowledge inspectable before the original builder steps away.
This is an original, lightweight handover method for small, low-risk resources and projects. It is useful when a collaborator takes over a resource page, a workshop kit, or a recurring internal task. It does not replace specialist operational, security, legal, or safety review where those responsibilities apply. The aim is a bounded transfer with visible gaps, not an impressive document that declares everything complete. The example below is invented, not a SIX33 result.
1. Define what is being handed over, and what is not.
Name the project, version, location, and date of the transfer. Describe the useful promise in one sentence: who should be able to do what with this resource? List the assets included, such as the current source file, published page, approved images, and maintenance instructions. Distinguish the current version from an archive or a draft. A folder called final is not an adequate version record when several people can edit its contents.
Write the boundary beside the promise. A dated list of local workshops is not a live booking system. Handing over the list does not automatically transfer responsibility for workshop delivery, payment, or support from another organisation. Record the dependencies and the commitments you are explicitly excluding. Link the project brief and important decision records so the incoming owner can understand the constraints without reconstructing the whole project history from chat messages.
2. Agree on ownership, authority, and a realistic support boundary.
Name an incoming owner and ask whether they have agreed to the responsibility. Sending someone a link, adding their name to a checklist, or assuming a volunteer will keep helping is not acceptance. Separate the person who maintains the resource from the person authorised to approve spending, change its promise, or publish information on behalf of a team. A handover should make those decisions easier to route, rather than silently granting authority.
Describe the routine work, its likely cadence, the available capacity, and the escalation route when the owner is unavailable. State support hours or response arrangements only if somebody has actually agreed to them. GOV.UK describes the live phase of a digital service as sustainable support and continued improvement. That is a useful reminder to plan beyond publication; it is not a requirement that a small voluntary project promise continuous support or adopt a government service process.
3. Check access and write instructions someone else can follow.
List where the source, publishing controls, approved assets, and working instructions live. Check that the incoming owner can use the access they are authorised to have. Keep credentials in the team's approved access system; the handover should point to that process, never contain passwords, recovery codes, or secret keys. Distinguish a request for access from confirmed access. If an account remains under a departing person's control, record the unresolved dependency and responsible owner instead of treating the transfer as complete.
Write one ordinary maintenance task as a short sequence: starting point, required permission, steps, expected result, and how to check the result. Include an example of what could go wrong and the agreed response. For a resource page, the task might be replacing an expired listing, checking the public page, and recording the source date. An inventory of tools is useful, but it is not a runbook. The next person needs to know what to do and how to recognise whether it worked.
4. Keep open issues, recovery steps, and review triggers visible.
Separate known issues from untested assumptions. Give each consequential gap an owner, a next action, and a condition or date for review. An issue such as the last update was not checked on a phone is different from a verified failure on a specific device. Preserve that distinction. If an unresolved issue makes the promise unreliable, narrow the promise or delay that part of the transfer; do not hide it in a long appendix marked future improvements.
Describe how to pause, correct, restore, or retire the resource if its ordinary operation fails. The appropriate response may be as simple as removing stale information and directing visitors to a verified source. GOV.UK's reliable-service guidance connects monitoring to a sustainable response plan. AWS recommends operational readiness reviews before launch and periodically afterward. Those references concern digital services and workloads; this worksheet borrows the discipline of reviewing operation, not their formal assurance or certification status.
5. Run a short walkthrough and record the actual result.
Ask the incoming owner to perform an ordinary task using the instructions, then explain or demonstrate the agreed recovery step in a safe setting. Do not make an unnecessary production change just to create a tick in the checklist. Use an appropriate draft, test copy, or walkthrough and state its limits. Record whether each check was demonstrated, blocked, or not checked, with its date and evidence location. A demonstration establishes something about that task and setting; it does not establish that every future problem can be handled.
Consider a hypothetical handover of a workshop resource page. The incoming owner can open the approved source and replace a date in a test copy, but cannot publish because access approval is pending. The team records the editing task as demonstrated and publication as blocked. A named coordinator retains publishing responsibility until authorised access is confirmed. The temporary arrangement includes a review date and the instruction to remove an expired listing rather than imply that its availability is live. None of these invented checks represents a real SIX33 outcome.
After the missing access is resolved, repeat the relevant check rather than rewriting the earlier blocked entry as if it never happened. Ask the incoming owner to confirm what they are accepting and from when. If they accept only part of the work, keep the remaining responsibility explicit. A sent document, a checked task, and an accepted responsibility are three different records. Keeping them separate makes the handover more honest and more useful when something later changes.
6. Set the next review and keep the document current.
Leave with one current handover record, not a new stack of competing copies. Put the version date, document owner, and next review near the top. Agree how changes to instructions, access, dependencies, or the public promise will be recorded. Keep sensitive details in the appropriate restricted location. A shareable summary can describe the resource and responsible role without publishing private contact details, participant records, or internal recovery arrangements.
Use the first review to ask what the incoming owner actually needed, which instructions were unclear, and what remains blocked. Revise the procedure when the evidence calls for it. Acceptance of a handover means an agreed responsibility has transferred within a stated boundary. It does not prove demand, long-term sustainability, or impact. If the project cannot be maintained responsibly, consider reducing its scope, arranging another owner, or retiring the unsupported promise rather than leaving visitors to discover the gap.
The short versionHand over a bounded responsibility, demonstrate the ordinary work, and keep the unresolved parts visible.
Put the guide to work
Project handover and maintenance worksheet
Copy or download the blank template. Edit it in your own document, keep participant details private, and replace every bracketed prompt before sharing.
Read or select the full template
This downloads the public blank template only. It does not include your private journal notes or tool drafts.
Direct answers
Questions about this guide.
What should a project handover document include?
Include the current version and scope, incoming owner and approval authority, asset and access locations, ordinary maintenance instructions, common failure and recovery steps, open issues with owners, walkthrough results, acceptance boundaries, and a next review date. Keep credentials and personal records outside the document.
When is a project handover complete?
A handover is complete within its agreed boundary when the incoming owner has accepted the responsibility, required access and operating tasks have been checked, and outstanding issues have an explicit arrangement. Sending a file or adding a person's name is not acceptance. Keep blocked and unchecked items visible.
What is the difference between a project brief and a handover?
A brief agrees what work should be done, for whom, and within what scope. A handover explains how the current version will be owned and maintained after responsibility changes. Link the brief and decision records rather than copying their entire history into the handover.
Should a handover include passwords or private participant records?
No. Point to approved access and restricted source locations instead. Confirm authorised access through the appropriate process, and keep passwords, secret keys, recovery codes, participant details, and unnecessary personal information out of the handover and any public summary.
Can I use this checklist for a volunteer or community project?
Yes, for an appropriate small, low-risk resource or task. Agree the actual capacity, responsibility, and support boundary with the incoming owner. The worksheet is an original working aid, not a consent form, professional approval, operational certification, or a substitute for specialist review.
Receipts
Sources and further reading.
- GOV.UK Service Manual — How the live phase works ↗ — Sustainable support and improvement of a live digital service; a reference for planning beyond publication, not a prescribed process for every small project.
- GOV.UK Service Standard — Operate a reliable service ↗ — Connects service monitoring, quality assurance, and a sustainable response to problems.
- AWS Well-Architected — Ensure a consistent review of operational readiness ↗ — Readiness reviews before launch and throughout the workload lifecycle. The worksheet here is not an AWS readiness assessment or certification.