Documenting your estate so you can hand it over
The test of an estate record is simple: could a competent stranger, holding only that document, keep every property alive for a month without asking you one question? Most estates fail, and the gap is never the clever technical detail. It is the bookkeeping. What exists, who gets billed, which date it lapses on, and what stops working when one entry expires.
Three triggers, one document
People write this record for three different reasons, then discover the reasons want identical fields.
- You become unavailable. An accident, an illness, a family emergency. Nothing technical fails. A card declines, nobody knows which card, and properties go dark one renewal at a time.
- You sell a property. Diligence asks what is included, where it runs, what moves with it, and what silently stays behind: a shared address, a certificate covering several hostnames, an analytics property under your personal login. Every ambiguity gets priced against you.
- You bring somebody in. A contractor with no map either interrupts you daily or guesses. Guessing is how a live zone gets edited in the wrong panel at the wrong hour.
Fields the register needs
One row per property. Assume the identifier itself is already fixed by whatever convention you settled on.
| Field | Why a successor cannot work without it |
|---|---|
| Domain, registrar, expiry date, auto-renew flag | The commonest cause of an avoidable outage |
| Legal owner vs day-to-day operator | These differ more often than people admit, and a sale turns on it |
| Where authoritative DNS actually answers | Frequently neither the registrar nor the host |
| Account, plan and region the site runs on | Tells a successor which panel to open |
| Address it resolves to, shared or not | Decides whether the property can leave on its own |
| Certificate issuer, coverage, renewal method | Manual renewals are the ones that get missed |
| Mail routing and mailbox host | Mail often lives apart and survives a host change |
| Application, major version, code repository | Separates a patchable site from a rewrite |
| Backup target, date of last verified restore | An untested backup is a claim, not a record |
| Monitoring check and where alerts arrive | Alerts aimed at an abandoned inbox are common |
| Payment instrument, billed entity, renewal cadence | The bus scenario lives or dies here |
| Attached third parties: search console, analytics, CDN, gateway, forms | The assets buyers forget to ask for |
| Dependencies on other rows | See below |
| Where credentials live, who holds emergency access | A pointer only, never the secret |
| Date this row was last verified | Turns a guess into evidence |
Write the dependencies down explicitly
Take one row, imagine deleting it, list what goes dark. That finds couplings you stopped noticing years ago.
us-01 / address A
serves: shop, blog, docs
cert: covers shop + blog only, docs renews separately
mail: hosted elsewhere, unaffected by a host change
registrar: notices route to one mailbox that is also on this box
That last line is the classic trap: the mailbox receiving renewal warnings sits on the very machine whose lapse it is meant to warn you about. If a property may be sold, note now what has to be untangled before a transfer completes cleanly.
Keep the keys out of the map
No passwords, tokens, private keys, recovery codes or card numbers belong in this file. The register is the one document you deliberately copy: to a buyer, an accountant, a contractor, a folder your family can open. Every copy would become a copy of the keys, and a copy cannot be revoked. Record where each secret is stored and who can reach it in an emergency, then grant access per person and withdraw it when they leave.
Stale is worse than missing
An absent register makes people check reality. A wrong one makes them act with confidence. Attach updates to events that already happen: a launch, a cancellation, a registrar move, a renewal. Once a year, pull the real inventory from the registrar, host and billing accounts and diff it against the register both ways. Anything present in one and absent in the other is the finding. Then run the drill: hand the document to someone else and ask what renews next and who pays for it. If they can answer, it works. Upkeep habits sit under running your estate.
Still not sure which way to go?
Tell us what you are building. If it needs less than you think, we will say so.