1997 Studio
← All articles

Operations·1 min read·1997 Studio

Website handover is more than sending a link.

Clarify the accounts, documentation and tasks needed to operate the website after handover.

Editorial draft awaiting approval.

Hand-drawn illustration of the article topic

Clarify access and responsibilities

List the domain, hosting, admin area and integrated services. For each item, identify the management account, responsible person and access recovery process.

Transfer access securely rather than putting passwords in shared documents. The scope of source code and design assets to be handed over should be agreed in the project terms.

Try the tasks you will do every week

Ask the operator to publish an article, replace an image and review a contact enquiry. Real tasks reveal where guidance is missing.

Keep documentation concise and organised by task. A step-by-step image replacement guide is often easier to consult than a long document describing every feature at once.

Agree on how to handle issues

Clarify the support channel, contact person, coverage and the difference between defects and additional development. Do not wait for a problem to discuss these points.

Check backup and recovery procedures within the agreed scope. Having a backup is not the same as having successfully tested restoration.

Facing a similar challenge?

Clarify your idea with Studio ↗