Who Owns Your Website? A Handover Checklist for Domains, Hosting and Admin Access

c
ceofounder
11 min read 56 views
Who Owns Your Website? A Handover Checklist for Domains, Hosting and Admin Access
Website Ownership

Who Owns Your Website? A Handover Checklist for Domains, Hosting and Admin Access

A site can look perfect and still hide a serious operational risk: nobody at the organisation knows who controls the domain, hosting, analytics, email or administrator login.

If the staff member or supplier who set it up becomes unavailable, routine changes can become urgent problems. Website ownership should therefore be part of the project scope, not an informal promise at launch.

Separate ownership from day-to-day administration

The organisation should know which accounts and assets it owns, while staff and suppliers receive only the access they need to do their work. Domain registration, hosting, website administration, analytics and email may be managed through different services.

  • Domain registration
  • Hosting
  • Website administration
  • Analytics
  • Email

Make a list of each service, its registered owner, billing contact, recovery method and the people who can grant or revoke access.

Use named accounts and strong recovery methods

Avoid relying on a shared personal email that only one former employee can open. Use organisation-controlled email addresses, a password manager where appropriate, multifactor authentication where supported, and a documented recovery contact.

Do not send passwords in a public handover document. The document should identify where credentials are stored securely and who is authorised to access them.

Request a useful handover pack

The pack should explain the domain registrar, hosting provider, renewal dates, backup process, site administration route, analytics property, Search Console property, form notification destination and any third-party integrations.

It should include what each component does, not merely a list of cryptic names. Ask for a current backup and instructions for requesting normal changes.

Agree the boundary of support

Clarify what the supplier will maintain, what the organisation must renew, how support requests are raised and which changes are outside the original scope. Confirm the notice process for ending the relationship and the way access will be transferred. These details prevent misunderstandings when a team or vendor changes.

Review access periodically

When someone leaves or responsibilities change, remove access that is no longer needed. Check billing emails and domain renewal notices still reach a monitored inbox. At least periodically, test whether the organisation can retrieve its records and reach the right support provider without depending on one individual.

Document the exit process before you need it

Even when the current relationship is healthy, agree what happens if a staff member leaves or the supplier relationship ends. Identify which assets must be transferred, how the final site backup will be delivered, who will help with DNS or hosting changes and which fees may apply. A clear exit path reduces the temptation to make hurried changes during a dispute or emergency.

Distinguish credentials from recovery access

Knowing the current administrator password is not enough if the account is tied to a former employee's phone or private email address. Check account recovery methods, billing notifications and authorised administrators. Where practical, use role-based access rather than sharing one login. Store emergency recovery instructions in a protected place that more than one authorised person can access.

✗ Credentials only

You know the password — but the account is tied to a former employee's phone or private inbox.

✓ Recovery access

Organisation-controlled recovery, role-based access and instructions more than one person can reach.

Test that backups can be restored

A backup file is not proof that the organisation can recover the website. Ask the responsible provider how restoration works, what data is included and how frequently the backup is tested. For critical sites, discuss a safe restore test in a non-production environment. Document the expected recovery steps and the person who can authorise a restoration.

Review ownership after organisational change

A merger, rebrand, new finance contact or departure of a web administrator can change who should control key accounts. Add website assets to the organisation's normal offboarding and governance checklist. Confirm that domain invoices, hosting notices and service correspondence reach monitored organisational mailboxes, and remove access when it is no longer required.

An ownership handover in four steps

1

List the domain, hosting account, website administrator, email, analytics, search tools, backups and external integrations. Identify who owns each asset and which account receives renewal notices.

2

Verify organisational recovery access and move away from accounts controlled solely by a former worker or individual supplier. Use a secure credential manager rather than putting passwords in the handover file.

3

Ask the current provider for a concise operations pack and demonstrate that an authorised employee can reach the necessary accounts. Confirm how support is requested and what happens if the supplier relationship ends.

4

Finally, schedule an annual ownership review and repeat it after staff or organisational changes.

Protect continuity when systems or suppliers change

Also consider what happens when the website is moved, a payment card expires or the organisation changes its name. The account register should identify dependencies such as DNS records, email routing and forms that deliver enquiries. Before any major change, assign a technical owner, confirm a rollback or recovery route and notify the people who depend on the service.

Ownership is not just a question of whose name appears on an account — it is the organisation's ability to make decisions, recover access and continue operating when a person or supplier is no longer available.
Example

A simple register

AssetDomain name
OwnerOrganisation
AdministratorAuthorised operations lead
RenewalAnnual
Recovery emailOrganisation-controlled mailbox
Access recordSecure password manager

Apply the same format to hosting, analytics and other important accounts.

Frequently asked questions

Should the developer own the domain?

The organisation should normally retain control of its digital assets and grant the developer appropriate administrative access.

Is a password list enough for handover?

No. Record ownership, recovery, renewals, backup and support arrangements as well as where credentials are securely stored.

Action checklist

  • The organisation's legal or designated owner controls the domain account.
  • Renewals and recovery contacts use monitored addresses.
  • Admin access follows least-privilege principles.
  • Backups, analytics and integrations are documented.
  • Supplier exit and access-revocation steps are agreed.

Final thought

The most professional website handover leaves the organisation more capable, not more dependent. Make ownership and continuity part of the project acceptance checklist.

Planning a new or rebuilt site?

Ask Stonehenge Digital KE how domain, administration and handover arrangements are handled within the website service — before launch day, not after.

Explore the Portfolio & Organisational Website Service →
Share Written by ceofounder

Interested in Portfolio & Organisational Website?

Let's build this for your business

A professional, mobile-first website that makes your business look credible and gets found on Google.

Leave a Comment

Share Your Thoughts