Tier 3 · Lifecycle
A recorded date is not a managed date. A managed date has an owner, a reminder, and an escalation path. This audit separates the two — surfacing the overdue-limitation triage queue and the key-date types that exist without anyone being warned.
Every 'planned' limitation date now past its due date, ranked as a triage queue and grouped by practice area so the concentration is obvious.
Key-date types with no reminder configured — dates that exist in the system but warn no one before they fall due.
Key-date types with no owner or responsible role — a date nobody is accountable for.
Whether limitation patterns reflect the relevant jurisdictions, or a single generic rule is applied everywhere.
A side-by-side of dates that are merely stored against dates that carry a reminder, an owner, and an escalation — the gap between the two is the risk.
Key-date definitions are captured from configuration; instance dates are queried live (guards and allocations are not held in snapshots, so they are read from the live instance). Overdue status is computed against the snapshot date and concentration is analysed by practice area.
886 'planned' limitation dates sat past their due date, and 66% of them were concentrated in a single practice area (Workplace injury) — exactly where a triage queue is most useful.
A dated, ranked triage queue partners can action on Monday morning, and a reminder-and-ownership gap list that turns recorded dates into managed dates.