A point-in-time record
A structured snapshot of the website, its connected services, account owners, and known renewal responsibilities.
Documented website ownership
Website Owner Kit — know what you own, where it lives, and what happens next.
I prepare a clear record of the accounts, responsibilities, renewals, update process, and handover contacts around a website. It can support a new Locriva build or help organise an existing site before maintenance or a provider change.
Need a quick answer? Email me directly.
01 — What it is
Documentation that makes a website easier to own.
The exact contents depend on the site. Before work starts, we agree which accounts, providers, responsibilities, and workflows need to be documented.
A reusable request brief
A simple format for asking a developer or support provider for changes with fewer missing details and assumptions.
A handover aid
A record that helps a client, future provider, or internal contact understand who controls what and where to begin.
02 — What it is not
Clear limits keep the kit useful and safer.
I prepare documentation. I don't take control of your accounts or make promises about systems I can't verify.
Not a password vault
Plain-text passwords, backup codes, card details, and private security answers do not belong in the kit.
Not ongoing maintenance
The kit records the current setup. Monitoring, updates, fixes, and response times require a separate care scope.
Not control of third parties
Registrars, hosts, email providers, and other platforms keep their own terms, pricing, security, and availability.
03 — Possible contents
Six practical records, selected to fit the website.
Not every client needs every record. The written scope identifies what can be verified and what the client must confirm before the final handover.
Control map
Site platform, account owner, access role, recovery contact, and the responsible person for each service.
Domain and DNS record
Registrar, nameservers, renewal responsibility, known DNS purpose, and where approved changes must be made.
Hosting and service inventory
Hosting, email, forms, analytics, backups, and other connected services that can be verified.
Change-request brief
A repeatable way to describe the page, current problem, requested outcome, content, files, and deadline.
Renewal and review checklist
A calendar-ready list of known renewals, ownership checks, content reviews, and maintenance decisions.
Handover contacts
Who to contact for content, technical work, billing, recovery, and emergencies covered by an existing provider.
04 — Information safety
I record ownership, not your passwords.
The kit is designed to help a client understand access without becoming a dangerous list of credentials. Sensitive credentials should stay in an appropriate password manager controlled by the client.
- No plain-text passwords, payment card details, backup codes, or private security answers
- Client confirms account ownership, billing responsibility, and recovery contacts
- I mark unknown or inaccessible services as unverified rather than guess
- I cannot control third-party terms, prices or service availability
- The final scope states the delivery format, retention approach, and deletion expectations
05 — Common questions
Questions before an Owner Kit project starts.
Anything unclear should be resolved in the written scope before account information is reviewed.
Can this be prepared for an existing website?
Yes. I can prepare it as a standalone documentation project if you can authorise access and confirm which services I should review.
Does the kit include website fixes?
Not automatically. I may identify missing access, expired services, broken links or unclear ownership while preparing the documentation. I'll quote any repairs separately.
Will you keep my passwords?
I won't record plain-text passwords in the kit. We'll agree temporary access and secure credential handling before work begins.
Does it replace a maintenance plan?
No. The kit documents the setup and process. A care plan covers agreed recurring checks, small updates, support limits, and response windows.
How much does it cost?
I don't publish a fixed price yet. The work depends on the number of providers, accounts, unknowns and records needed. I'll confirm the scope and fee with you in writing first.
06 — Start with the current setup
Tell me what you know about the website and where ownership becomes unclear.
A first message should include the website address, the known provider or platform, who currently handles updates, and the main ownership or handover problem. Do not email passwords.