The heading is the provider’s name; the line under it lists its domains, the record’s version and when it was verified and is next due. Five tabs: Policy, Playbooks, AI research, Sources, History.

​
Header actions

Badges beside them show the status and whether the record needs review or a source changed. A banner above the tabs reports a pipeline in flight (scanning, analysing, drafting), a failed automatic run, results held for a person, or a prompt to choose outcomes.

​
The Policy tab

The service: name, category, domains, website, and a one-paragraph summary an operator reads first. What happens after a death: the provider’s terms in our words (who may ask, what proof, what options, timelines, what they refuse), the policy and help page URLs, the typical turnaround, the review interval, and jurisdiction notes. Contact channels: web form, email, phone, post, API or in-app, each with a label, the address and when to use it. Supported outcomes: the outcomes this provider can deliver. When the latest analysis suggests outcomes not yet ticked, Use suggested applies them. Saving with a new outcome drafts its playbook when AI research is configured. Documents the provider asks for: death certificate, proof of relationship, executor’s photo ID, probate, and so on. Document steps in playbooks draw on this. Source pages: where the policy was read. Checked weekly and read by AI research. Save as v(n+1) writes a revision with an optional change note. Only operators and above can edit; viewers and reviewers see the fields disabled.