Claims Start as Events.

Claims management is on the roadmap. What exists now is the thing a claim depends on: every event, investigation, corrective action and closure captured as a timestamped, attributable record, so if a claim ever arrives, the file is already built.

What We Are Building

A claims module that tracks a claim as its own object from notice through reserve, defense and resolution, linked to the event that caused it, so the incident record, the investigation and the claim file are one chain rather than three systems. We are building it. It is not here yet.

True Today

The File Is Already Being Built

A claim arrives two years after the event, when the people who were there have left. The investigation you actually did is the best evidence you have. Here is what the platform is keeping for you in the meantime.

A Complete Activity Trail

Every event carries a complete, timestamped activity trail: who reported it, who investigated, what they found, what was done, when it closed. That is the file a claim would need, and it is being built as you work.

One Chain, Not Three Systems

An investigation is linked to the event that triggered it and to the corrective actions it produced, so the chain that answers "what did you do about it" is one click, not one archaeology project.

Records Are Versioned

An edit does not overwrite history; it adds to it. What the record said in March is still recoverable in the following March.

Access Follows Your Roles

Access follows the roles you configure, so a case with potential exposure can be restricted without being removed from the workflow.

Dated and Attributed Decisions

Reportability determinations, harm scores and closure decisions are dated and attributed to a person, which is the difference between a defensible record and a reconstruction.

Related