Start with an account and asset register.

A website depends on more than the CMS. The domain registration, DNS, hosting, source repository, analytics, search verification, media files, forms and service integrations may each have a different administrator. Record the agency’s accountable role, approved administrators, recovery route and the evidence that access has been checked.

Keep credentials in the approved credential system, not in the project brief or a shared content spreadsheet. A register should reference the controlled location and responsible role. Use organization-managed accounts where the agency’s process supports them, with an access review when staff or suppliers change.

Ask what is delivered and what is licensed.

ItemQuestion to settleEvidence to inspect
Content and mediaWhat may the agency use, edit and take to another system?Usable exports and a record of third-party licenses.
Custom source filesWhat source, configuration and documentation are included?Repository access and a documented build or handover procedure.
CMS and hostingWhich accounts are controlled by the agency or provider?Admin roles, recovery contacts and account responsibility.
Extensions and servicesWhich licenses end or change if the support arrangement ends?License holder, renewal owner and replacement options.

On a small screen, scroll the table sideways to see every column.

Ownership and usage rights depend on the actual agreement and licenses. Have the authorized procurement or legal reviewer settle those terms. A source-code handover does not automatically transfer third-party rights, hosted services or support obligations.

Define the work hidden inside “maintenance.”

Split technical operation from content upkeep. Technical work can include updates, backup checks, restoration, monitoring and fault diagnosis. Content work can include revised service facts, document replacements, new pages, accessibility review and expired notices. A hosting fee does not explain which of those activities is included.

Record support hours, how an issue is submitted, how urgency is assessed, the expected initial response and who communicates progress. An initial response target is different from a resolution commitment. State any exclusions and the process for approving additional work.

Use the website cost guide to separate recurring responsibilities from initial implementation. For editorial upkeep, the content governance model identifies the owner and reviewer roles.

Test a restoration and a routine staff change.

Ask how backups are created, who can access them, what they contain and how a restoration is verified. Agree on the recovery objectives appropriate to the service and test evidence. A successful backup job is not the same thing as a demonstrated recovery.

Include a normal staff departure in handover practice. Revoke the departing account, confirm a remaining authorized administrator can still work and check that automated processes do not rely on the departed person’s access. Record follow-up for any unmanaged dependency.

A technician checking a website restoration on a laptop beside an ordinary external backup drive, a colleague observing the result in a calm office.
Practicing website backup restoration.

Make provider transition a practical scenario.

Before accepting a support arrangement, ask the team to describe a hypothetical exit: export content, transfer the agreed source and configuration, identify active licenses, hand over account administration and explain how redirects or external integrations remain supported. Establish what transition assistance is included or separately priced.

Test an export with representative pages, attachments and content relationships. Confirm that another authorized team could interpret it. If data cannot leave a platform in a usable form, make that constraint visible during CMS selection, not only at the end of the contract.

Keep the register alive after acceptance.

Assign an owner to review account control, licenses, supplier contacts and maintenance responsibilities after material changes. Connect it to the change log so new forms or integrations do not become ownerless services.

The GOV.UK open-standards guidance (opens in a new tab) provides context on interoperability. Its UK policy requirements are not a local-government contract template. The asset and handover register here is a practical discussion aid for your agency’s reviewers.

Bring the agreed responsibilities into the requirements brief and the migration plan. Explore website design and handover support for the implementation scope.

Prepare editors through practice, then verify the handover.

Editor training should leave staff able to complete ordinary work using their actual permissions. List the roles that will draft, review, publish, manage documents and administer access. A recorded presentation can support practice, but attendance alone does not establish readiness.

Use an approved training area and representative sample content. Ask an editor to revise office hours, replace a superseded file, correct a service instruction and preview a page on mobile. Ask a reviewer to return a draft with a reason, then approve the corrected version. Test the route when the usual approver is absent.

Practice taskEvidence of readinessIf the task fails
Revise a pageCorrect source revision, preview and approved publicationClarify the field, role or instruction and repeat.
Replace a documentCorrect edition and usable old-link handlingResolve file ownership and migration behavior.
Correct a live errorAffected versions identified and checkedPractice the correction path and backup access.
Transfer ownershipPending drafts and reviews reassignedUpdate responsibilities before removing access.

On a small screen, scroll the table sideways to see every column.

Record the participant role, task, independent or assisted completion, unresolved issue and next practice date. Do not use training as a workaround for a confusing interface that several editors cannot operate. Feed those issues back into configuration or design.

Handover also needs account control, a permissions list, support instructions, known issues and the owner for outstanding work. Use the content governance model for approval authority and the CMS comparison to evaluate editing before procurement.

An editor practices a page update during one-to-one staff training at a laptop, another staff member checks the source information beside them.
Practicing a publishing handover.