# Digital project handover

Keiss Media · Version 1.0 · 15 October 2026

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.

## Sources and adaptation

- Civil Service, UK Government: [Contract Management Training & Accreditation Foundation level: takeaway guide, Exit and transition](https://www.gov.uk/government/publications/civil-service-helping-you-with-managing-suppliers-and-contracts/contract-management-training-accreditation-foundation-level-takeaway-guide-html#exit-and-transition). Open Government Licence v3.0.
- Technology community (web operations), Government Digital Service: [Monitoring the status of your service](https://www.gov.uk/service-manual/technology/monitoring-the-status-of-your-service). Open Government Licence v3.0.

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.
https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/