# Maintenance and ownership handoff

System / site:
Business owner:
Technical contact:
Last reviewed:

## Account register

For domain, DNS, hosting, database/storage, email, payments and analytics:
- Provider and purpose
- Business account owner
- Authorized technical contact
- Where credentials are stored (never put passwords in this document)
- Renewal date and billing owner
- Recovery contact / backup administrator

## Agreed care

Routine checks included:
Request allowance and reset rule:
Support contact / hours:
Incident response expectations (only as explicitly agreed):
Excluded work:
Provider costs and billing responsibilities:
Approval route for additional work:

## Incident record

Affected user task:
First observed date/time and timezone:
URL / system:
Expected result:
Observed result:
Evidence without customer secrets:
Incident owner:
Temporary workaround:
Recovery version and approval:
Verification after recovery:

## Repeatable checks after a change

- [ ] Read the key public pages on desktop and phone.
- [ ] Check the agreed enquiry / login / upload journey in an appropriate environment.
- [ ] Verify access restrictions with the correct test roles.
- [ ] Check failed and repeated requests without paid or customer actions.
- [ ] Verify the recovery procedure and record the result.
- [ ] Record changed provider settings and handoff information.

## Recovery evidence

Backup contents:
Location and access owner:
Last restore test (date, environment, result):
Known data-loss / recovery limits:
Next action if a restore fails:

araNET Studio — https://www.aranetsolutions.com/blog/what-website-and-software-aftercare-should-cover