Retention Triggering

Retention schedules fail at the start rather than the end. A schedule specifies a period from a triggering event — contract expiry, employment termination, case closure — and if the event date was never captured, the clock never starts and the record is retained indefinitely by default. Capturing it manually is unreliable at volume, which is why most estates have a retention policy and an estate that grows forever. Deriving the trigger from the content itself is the only approach that scales.

Because Centralpoint infers record type and triggering dates during ingestion, retention clocks start without a user selecting a category. Disposition then operates on records with their version lineage and derived artefacts, so executing the schedule covers interaction logs, cached answers and index membership rather than stopping at the document.