Taking over a website: what should you receive?
The login is only the beginning. Find out who owns the domain, where the backups live, and how the next person will maintain the site.
This checklist is intended for a supplier change, staff departure or completed support project. Use the parts relevant to the website and identify unknowns as actions to resolve.
Provider ownership and recovery
List the domain registrar, DNS service, host, email provider and relevant application vendors. Record the organizational owner, account identifier where appropriate and authorized recovery contact. Confirm who receives billing, renewal and service notices.
Keep passwords, tokens and recovery codes in the agreed secure system. The handover should tell an authorized person how to obtain appropriate access, not expose credentials to everyone who receives the document. Named permissions can help distinguish access needed for maintenance from ownership of the provider account.
Test an absence scenario: can another authorized person identify the provider and start the appropriate recovery or support process if the usual contact is unavailable? A table that names only a departed employee has not completed that responsibility.
Application and content inventory
Record the platform, significant components, custom modifications and licenses that affect operation. Explain which responsibilities they support. A new maintainer should know which component supplies the enquiry path or protected downloads before deciding it’s unnecessary.
Identify content owners and the approved publishing process. Include related documents, repeated business details and any temporary notices with a future review date. The next editor needs to understand which facts require approval and where a coordinated change must be made.
Data and recovery material
Describe the records, uploads, storage and configuration needed for the site. Identify backup coverage, schedule, retention and access. Keep the latest relevant restore-rehearsal record, including the snapshot, environment, tasks checked and limitations.
The recovery instructions should distinguish files, database content and external services. They should identify who can authorize returning to an older state and how newer records will be considered. A backup archive with no usable restoration path leaves a major handover gap.
Changes, releases and representative checks
Explain where the editable source or configuration lives and how an authorized maintainer makes a change. Identify the test environment, release owner and recovery route. Record important differences between preview and production.
Provide a small set of task checks that represents the website's responsibilities. For example, a service site may need its enquiry destination and downloads checked, while an account-based system needs appropriate access behavior. Include how tests avoid creating real customer work.
Don’t represent a successful rehearsal as a guarantee that every feature has been tested. State which checks were performed and what remains outside that evidence.
Notifications and support boundaries
List monitoring checks, their purpose, destination and owner. Explain which failures they can detect and where they are limited. Record how to recognize and update a check that no longer matches the site.
Keep the support arrangement available: reporting channel, included work, coverage, approval and provider escalation. If a project is ending without continuing support, say who becomes responsible. A friendly handover message shouldn’t leave an implied permanent service obligation.
Open findings and retirement decisions
Transfer unresolved faults, unsupported components, approaching renewals and deferred improvements with their evidence and next decision. Avoid a generic “known issues” list that nobody owns. The business should know which items need approval and which belong with another provider.
If an old host, plugin or temporary account remains, document why and when it can be retired. Remove access through the appropriate authorized process when it’s no longer required. Don’t cancel a provider simply because the new public homepage appears to work.
Verify the handover through a small task
Ask the receiving maintainer to locate a provider record, explain the publishing path and follow one representative check using suitable access. This can reveal missing context before the former maintainer becomes unavailable.
A good handover leaves the business able to continue ordinary care and make informed decisions about the next change. The responsibility sheet offers a compact ownership record; support planning defines the continuing arrangement.
