For accident management companies
The operating system behind a modern accident management company.
Intake, credit hire, storage, recovery, engineering, documents, signatures, correspondence and claim finance — running on one record, for the whole operation.
The day job
Four questions, asked constantly.
“What is this claim worth?”
Charges derive from the workstreams — hire days by rate, storage days by rate, recovery, CDW — so the number is on the claim, and every figure is reproducible from the dates and rates that made it.
“What is holding it up?”
The claim shows what it is waiting for: a signature, an engineer, a solicitor, a third-party insurer. Not derived from a note somebody left three weeks ago.
“Did anyone chase that?”
Milestones raise their own follow-ups on your SLA timings and close them when the thing arrives. Nobody has to remember.
“Where is the signed authority?”
On the claim, with a certificate recording who signed it, from where, when, and what wording they agreed to.
Chasing
The work that disappears.
Referred to a solicitor, VD in, engineer instructed, pack sent — each raises the follow-up it needs, and closes it when the wait ends.
- Chase solicitor for VD AuthorityOpen
- Chase engineer reportOpen
- Off-hire — payment sent to clientOpen
- Chase payment packOpen
Every task above was raised by a milestone, not by a person — and closed by the event it was waiting for.
Questions people ask
What software do accident management companies use?
Most run a legal case management system adapted for motor work, a spreadsheet for the hire fleet and its costs, a shared drive for documents, and email for everything else. It works until volume rises or someone asks what a given claim is worth, at which point the answer has to be assembled by hand from four places.
Is this a CRM?
No. A CRM is organised around a contact and a pipeline of opportunities. Accident management is organised around a claim, and a claim has parallel workstreams with their own dates, rates and running costs. Bending a CRM into that shape is possible and generally regretted.
We are small. Is this over-engineered for us?
The parts that matter at low volume are the parts that stop things being forgotten: intake that does not let unverified data into your records, chases that raise and close themselves, and documents attached to the claim rather than to a person. Those help a team of three as much as a team of thirty.
Can our referrers and solicitors see their claims?
Not yet. Partner and customer portals are planned, not built. Today, solicitor correspondence is filed automatically against the right claim and documents are shared by email from within the system, which covers most of what the portal would do — but we would rather say what is missing than let you discover it in the demo.
What about credit hire specifically?
Hire periods, day rates, storage and recovery are shipped and feed the claim's value. The deeper credit hire work — vehicle groups, rate tables on the annual cycle, extensions with reason codes, and need and impecuniosity captured at deployment rather than reconstructed for a dispute — is in build. It is the next major module.
Bring the claim that went wrong.
The interesting demo is not the clean file. Pick the one that got disputed, or sat too long, and we will show you where the system would have caught it.