One published playbook per outcome. A case copies the steps when it starts, so editing here never changes a live case; publish a new version and new cases pick it up. Each panel shows the playbook’s name, outcome, status and version, then its steps with the action type, a family badge for steps the family owns, an approval badge for steps that always need a person, and what each step waits for. Edit, Publish and Archive are at the bottom; New playbook at the top.

​
The editor

A playbook has a name, an outcome and a description, then one panel per step with ↑ ↓ Remove to reorder. Every step has a key (what other steps refer to), a title, an action, instructions for the operator, an owner (operator, family or system), the evidence completion needs (none, note, reference, file), which steps it runs after (blank means the previous one) and expected days.

​
Step types

Strings are templates: {{deceased.name}}, {{executor.email}}, {{case.reference}} and the rest listed under Settings → Automation. Email, webhook and API steps have a switch, Always needs approval, whatever the rules say. Save as v(n+1) (or Create draft) validates the steps first: keys must be unique, dependencies must exist, every type’s required fields must be present.

​
Publishing

Publish makes this the playbook new cases use for that outcome; a previously published one for the same outcome is superseded. Archive withdraws it. The provider itself must be published for any of its playbooks to reach a case.