Claims / Diary and deadlines
Nothing ages out unseen
Statutory deadlines computed per jurisdiction from the loss and report dates, surfaced on the claim and across the whole book — plus a diary with owners and due dates.
A missed acknowledgment is not usually a knowledge failure. It is a visibility failure, and it is fixable structurally.
See the book-wide clockWho is responsible for knowing the deadline?
The platform computes it, so nobody has to remember the statute for a jurisdiction they handle twice a year. Acknowledgment, contact and decision dates derive from the loss and report dates per jurisdiction, and appear both on the file and on a page showing every clock in the operation.
Computed, not typed
Two surfaces, one clock
- 01
Claim compliance computes the dates
Per jurisdiction, from the loss and report dates. Not entered by whoever opened the file and not inherited from a template.
- 02
Compliance deadlines shows the book
Every claim’s clock across the operation on one page, so aging files are a queue rather than a quarterly surprise.
- 03
Diary carries owners
Entries have a due date, an assignee and a claim — raised by hand or automatically by platform events.
- 04
Notes are the narrative record
Encrypted, attributed, timestamped and not editable after the fact. A file defended two years later reads as it read the day it was written.
What drives a clock
Inputs the computation uses
Because these are the inputs, a correction to any of them re-computes the dates — and the change is recorded rather than silently replacing the old schedule.
Jurisdiction
Selects the applicable statutory requirements
Line of business
Workers’ compensation carries its own reporting obligations
Loss date
Anchors periods measured from occurrence
Report date
Anchors acknowledgment and contact windows
Claim status
Closure with an open SIU referral is refused, so a clock cannot be escaped by closing
Where you still configure
The platform computes from rules. The rules for your jurisdictions have to be right, and that is a shared responsibility.
Jurisdiction rules need loading
Statutory periods are configuration, per jurisdiction and line. Same principle as delinquency: we ship no guessed periods.
Not legal advice
The platform enforces the periods you configure. Determining your obligations is your counsel’s work.
A visible deadline is still a deadline
Surfacing an aging clock does not do the work. It converts a compliance failure into a staffing decision, which is the most a system can honestly do.