← All resources

Launch and hand over

Digital project handover

Transfer the ability to operate the project, not just its URL.

When to use it
Before launch, a supplier change or completion of an agreed stage.
What you will have
An inventory of assets, owners and checks that lets another team continue the work.
When not to use it
Delivering files does not replace acceptance or transfer intellectual property rights. Those matters are agreed separately.
View the worked example

The example is fictional. It demonstrates completion, not the outcome of an actual project.

Release being handed over

The Russian promotional website with three routes. An English version is outside this release.

Source and assets

Code in the client’s repository, editable designs, copy and build instructions. Another team member should verify the documented build.

Accounts and access

The client owns the domain and hosting. The supplier has a separate role. Verify access after handover and revoke roles no longer needed.

Deployment and recovery

Instructions cover build, deployment and rollback. Test recovery at a non-production address before closing the stage.

Third-party assets and rights

Attach sources and licences for photos and fonts. Reference the agreed document covering rights to commissioned assets.

Operation after handover

Marketing owns content; an appointed administrator owns publishing and payment. Support and its terms must be agreed separately.

Download example (.md)

Fill in the template

If an answer is unknown, say so. You do not need to complete every field before a first conversation.

Version, URLs, deliverables, acceptance evidence and known limitations.

Repository, design files, content, build instructions, dependencies, tool versions and a backup.

Who owns the domain, hosting and services? Which roles are transferred and who verifies access? Do not record passwords here.

How do you deploy, verify, roll back and restore a backup? Who approves launch?

List fonts, images, libraries and external services with their terms. Unclear rights require separate review.

Who updates content, pays for services, responds to incidents and approves new work?

Fields work in your browser. Your text is not sent to us or saved after the page closes. Download the document to continue later.

Sources and adaptation

A Keiss Media checklist informed by GOV.UK guidance on documentation and knowledge transfer. It adapts guidance, not a contract or acceptance certificate.

Contains public sector information licensed under the Open Government Licence v3.0.

Version 1.0 · 15 October 2026