Put an owner beside the website's essential responsibilities
Copy this sheet into your organization's working notes. Record the person or role, provider and next action where relevant. “Unknown” is a useful answer when it identifies a gap to resolve.
Keep credentials elsewhere. This sheet is for ownership and recovery contacts, not passwords, tokens or private customer information.
| Area | Questions to answer | Record |
|---|---|---|
| Domain | Who owns the registration, receives renewal notices and can authorize changes? | Owner, registrar, notice recipient and substitute |
| Hosting | Who controls the account and approves a move or additional charge? | Provider, business owner and technical contact |
| DNS and email | Which services manage them, and are they separate from website hosting? | Providers, authorized contacts and services that must remain intact |
| Content | Who confirms business facts, approves material and decides when it appears? | Approver, editor and publication path |
| Software updates | Who reviews compatibility, installs changes and checks the affected tasks? | Maintainer, release owner and verification record |
| Recovery | What is backed up, where are copies held and who has rehearsed restoration? | Coverage, access owner, rehearsal date and open gaps |
| Enquiries | Where should requests arrive and who checks the receiving path? | Destination owner, reviewer and safe test method |
| Monitoring | What does each check detect, who receives a warning and who acts? | Check purpose, recipient and agreed response responsibility |
| Provider notices | Who assesses a service change and who can approve its cost or interruption? | Technical reviewer, decision-maker and escalation contact |
Test one handoff
Imagine the person who usually handles the website is unavailable. A provider sends a notice requiring action. Can another authorized person identify the service, determine who can assess the consequence and obtain the necessary decision?
If the answer depends on a personal inbox or undocumented login, record the missing action. Don’t solve it by circulating credentials in the sheet. Use the provider's authorized ownership and access process with an appropriate secure credential arrangement.
Make unresolved items visible
For each gap, add the next action and the person responsible for it. “Backups unknown” becomes more useful when someone is assigned to confirm the provider's coverage and arrange a controlled restore review. “Enquiries handled by the office” should identify who can confirm that a test reached its intended destination.
The sheet doesn’t create a support contract or assign obligations to a supplier without agreement. Use it to make the conversation concrete, then record the agreed coverage and response expectations separately.
Review it when responsibilities change
Revisit the sheet after a staff or supplier change, a hosting move or a new feature that changes what the site does. Keep provider notices and recovery contacts current. The purpose is a usable handoff, not a table completed once and forgotten.
Read the handover checklist, explore support planning, or discuss the gaps.
