The platform
One record. Everything hangs off it.
ClaimCore is organised around the claim, not around a matter, a contact or a ticket. Every workstream, document, message and charge belongs to one record and is reachable from it.
M. Okonkwo
- Accident
- 04/07/2026
- Liability
- Non-fault
- TP insurer
- Admiral
Credit hire
42 days
£3,570.00
Storage
18 days
£450.00
Recovery
Complete
£285.00
Engineering
Total loss
PAV £8,950
Claim value
£4,305.00
Activity
- 14:22VD Authority signed by clientClient
- 11:05Engineer's report forwarded to solicitorSystem
- 09:41Valuation confirmed with clientR. Whitfield
- YesterdayStage — Engineering → Valuation confirmedSystem
How it fits together
Six things, connected.
An integrity boundary at intake
Claims arrive from a public form, an agent or an API into a verification queue. Client, vehicle and claim records are written in exactly one place in the code, inside one transaction, after a human has checked the submission. Unverified data cannot reach your records — not by convention, by construction.
A pipeline you own
Stages live in a table, not an enum. Rename them, reorder them, add your own, retire the ones you never use. Stage moves are recorded with who moved them and when.
Workstreams with their own clocks
Hire, storage, recovery and engineering hold their own dates, rates and status, and each feeds the claim’s value directly. The claim total is derived, never typed.
Documents and signatures
Documents are typed, permissioned and scoped to the claim. Signature requests are single-use links; the sealed PDF carries a certificate page recording signer, IP, timestamps, consent wording and a SHA-256 of the document itself.
Correspondence on the file
Inbound solicitor email is matched to a claim on your reference or on the firm’s own matter reference, which the system learns the first time you file one. Attachments are reviewed before they land.
Money that reconciles
Charge lines derive from the workstreams. Invoices and payment packs are built from those lines, and every figure is reproducible from the stored rates and dates that produced it.
The pipeline
Configurable, not hard-coded.
These are the stages ClaimCore ships with. They are a starting point — every one of them is yours to change.
- FNOLCaptured and verified
- OnboardingDocuments signed
- Hire & storageClock running
- EngineeringReport received
- ValuationConfirmed with client
- Disclosed to TPInsurer notified
- Authority & fundsVD in
- Off-hireExposure closed
- Payment packSent to solicitor
- RecoveredMoney in
Modules
What is shipped, and what is not.
ClaimCore is in active development, and this table is the honest state of it. A demo will show you the shipped column working on your own data.
| Module | What it means for the business | Status |
|---|---|---|
| First notification of loss | Capture a claim from the public, an agent or an API — nothing reaches your records unverified. | Shipped |
| Claim record | Claimant, vehicle, third party, every workstream and the full history on one screen. | Shipped |
| Configurable pipeline | Your stages, your names, your order — changed in the admin screen, not by us. | Shipped |
| Credit hire & storage | Hire and storage periods, day rates and recovery charges feeding the claim's value. | Shipped |
| Engineering & total loss | Reports, pre-accident value, salvage and the total-loss decision, sent on to the solicitor. | Shipped |
| Documents | Typed, permissioned, tied to the claim, and served only to people entitled to see them. | Shipped |
| E-signature | Send, sign, seal. Every signature carries a certificate — signer, IP, timestamps, consent text and a SHA-256 of the sealed document. | Shipped |
| Solicitor correspondence | Inbound email filed against the right claim, matched on your reference or theirs. | Shipped |
| Claim finance | Charges derived from the workstreams, invoices, payment packs and commission — reproducible from stored rates and dates. | Shipped |
| Chase & SLA | Milestones raise their own follow-ups and close them when the wait ends. | Shipped |
| Finance ledger | Receipts allocated to the invoices they settle, part payments with real figures, aged debt and write-off with a reason. | Shipped |
| Fleet compliance | MOT, tax, insurance and servicing chased before they fall due, with utilisation measured two ways. | Shipped |
| Analytics | Where claims stall, what happened to each month's cohort, and every figure against the same period last time. | Shipped |
| Public API & webhooks | A versioned API scoped by keys you issue, and signed webhooks your systems can trust. | Shipped |
| Migration Centre | Bring your existing book across: map, validate, rehearse without changing anything, then commit. | Shipped |
| GTA-grade credit hire | Vehicle groups, rate tables on the annual cycle, extensions with reason codes, and need and impecuniosity captured at deployment rather than reconstructed later — plus a check that names the evidence still missing while there is time to get it. | Shipped |
| Liability | Decisions, apportionment, evidence and the third-party insurer's position, tracked properly — and the split flows through to the invoice. | Shipped |
| Repairs | Repairer, estimate, authorised and final cost, against the total-loss threshold. | Shipped |
| Workflow automation | Build the rules yourself: trigger, condition, action, delay — without waiting for a developer. | Shipped |
| Customer & partner portals | Claimants, referrers, engineers, repairers and solicitors self-serve, so your handlers stop fielding status calls. | Shipped |
| Guided vehicle inspections | Nine required views on a phone, walked in the order you go round the car. It refuses to submit while one is missing, and names which — so the photograph a defendant asks about eight months later was taken. | Shipped |
| ClaimCore AI | Reads a document and proposes claim field values, each shown beside the exact words it was read from — checked against the document before you see it. Nothing is written until somebody accepts it. | Shipped |
| Cited credit-hire assistant | Would cite a named authority with a link, or decline. Not built: it needs a corpus of UK authorities, and in a litigated domain a citation the product cannot verify is worse than no answer. | Planned |
Multi-tenancy, permissions and the audit trail are foundational rather than modular — see how ClaimCore handles your data.
See it against one of your real claims.
Thirty minutes, no slides. Bring a live file and we will run it through the system end to end.