How it works
Funeral Sentry goes live by location, not by feature toggle. Most independent homes are fully migrated inside three weeks. Multi-location groups roll out one region at a time, on a schedule we set with you.
01The 30-day shape
Each phase has a deliverable. By day 30 you have a working compliance system of record per location — not a project plan that says you started one.
We import your existing GPLs, scan your staff records, configure your state license overlays, and assign roles. One location at a time, or all at once for groups.
Define your disclosure workflows, renewal cadences, retention periods, and escalation paths. Every funeral home runs slightly differently — the platform adapts.
From the day you go live, every arrangement generates a record. Every staff member’s training is tracked. Every regulatory change flows to your obligations.
Whether it’s an FTC inquiry, a state board review, or a plaintiff’s discovery request — your records are sealed, signed, and exportable in minutes, not days.
02What the platform refuses to do
A compliance product that uses cheerful language is a compliance product you can't take into a deposition. We chose the boring, evidentiary path on purpose.
Every AI finding cites a specific price item or disclosure key from your GPL. If the citation doesn’t match the source, the finding is downgraded to ESCALATE and waits for a human.
LOW and MEDIUM risk flags auto-resolve when the underlying data is corrected. HIGH and CRITICAL flags require a human to acknowledge and close — even after the data passes.
A published GPL version cannot be silently changed. Corrections create a new version with a full diff against the prior. The historical record is the legal record.
03What the system actually does
A document folder is not an audit trail. A spreadsheet is not a versioned price list. Here is what the platform writes to disk on a normal Tuesday.
Actor, action, entity, organization, location, request id, IP, user-agent. Append-only — the platform itself never deletes or updates an audit row.
Evidence files stored under tenant-prefixed keys. Audit packet exports include the document hash so receipt can be proven without trusting our database.
Each published version stores its parent. The diff (price additions, removals, percentage changes) is preserved separately so reviewers can audit deltas, not just snapshots.
A finding cites a specific price item by ID or a disclosure by FTC section. Reviewers click through to the original record, not a paraphrase.
Service-layer guards reject any query that lacks an organization id. A misdirected read returns 404 with zero information leak about whether the row exists in another tenant.
Full export at any time — JSON, CSV, sealed PDF. Cancellation does not gate your records. Compliance data follows the funeral home, not the vendor.
Start with one location
Load one location. We'll audit the GPL, score every disclosure, surface the gaps, and hand back a readiness report. Keep the report whether you continue or not.