Many jurisdictions impose a minimum waiting period between death (or another defined event) and cremation. Exact hours and starting points vary by state and can change. This article is operational guidance, not legal advice — always confirm current law for your facility.
What to track on every case
- Clock start — which event starts the wait (e.g. time of death, receipt of remains)
- Required duration — hours required under your applicable rules
- Earliest cremation time — computed and visible to operators
- Who tried to start early — and whether an override was used
- Rule version — which pack or SOP version produced the wait
If those five items live only in someone’s head, you do not have a controlled process.
Why software enforcement helps
Paper charts and whiteboards fail in predictable ways:
- The wrong start time is written down
- The case is moved to “ready” because the chamber is free
- A new hire does not know the local wait applies
- After the fact, no one can show what was believed at the time
Enforcement does not replace judgment or counsel. It prevents accidental advancement when the system still believes the wait is active.
Multi-state operators
If you run more than one state, do not lead with “one national checklist.” Lead with:
- A baseline custody workflow
- State packs that add wait hours and local fields
- Clear labeling of required vs. recommended
CremateOS applies waiting periods as blockers until the due time passes (or an authorized override is recorded). Multi-state capability is secondary to getting a single facility’s floor discipline right.