Chain of custody is the story of who had control of remains, when, and under what identification. Gaps in that story are liability, not just paperwork.
Minimum events to log
| Event | Capture at least |
|---|---|
| Received | Timestamp, operator, funeral home if applicable |
| Tagged | ID tag value, method (visual / scan) |
| Identity verified | Who verified, method, optional second person |
| Permit / authorization recorded | Numbers or document links |
| Cremation started | Operator, chamber if used, time |
| Cremation completed | Operator / packager, time |
| Released | Recipient, time |
Optional but valuable: refrigeration notes, container type, location in cooler, dual-person checks for high-risk steps.
Rules that prevent weak logs
- Append-only — corrections add events; they do not rewrite history
- Named actors — “system” or shared logins erase accountability
- Tag match — scanned tags should match the case tag before cremation
- No silent skips — software should block start when required steps are missing
- Exportable — counsel and inspectors need a packet, not a login
What “good” looks like in a dispute
Imagine a complaint six months later. You should be able to produce:
- The case summary and ID tag
- The ordered timeline with users and timestamps
- Documents on file for that case
- Any override with reason
- The rule or SOP version that applied
That is the standard CremateOS proof packs aim to support.
Floor workflow tips
- Put verify identity immediately before start cremation
- Use chamber boards so “in retort” is visible without radio traffic
- Share funeral-home status links so partners stop calling for basic stage updates
- Train that “green” means requirements met, not we’re in a hurry
Not legal advice
Custody practices must match your state, contracts, and counsel’s guidance. Use this as an operations baseline and harden it for your jurisdiction.