Group litigation · Housing disrepair
The back office for
housing disrepair claims.
A disrepair file gathers all inbound info before becoming a case: tenant account, surveyor report, medical records, repair logs, and claim responses. Claim Inbox reads, classifies, extracts key facts, and manages the wait for disclosure and expert evidence within your existing case system.
What firms running Claim Inbox are seeing
- More files per handler
- 27×
- Less hands‑on time per file
- 96%
- Team time spent waiting
- 0 hrs
The work is heavy. The
waiting is heavier.
High‑volume disrepair runs on paralegal reading hours, and then on patience. A file is a stack of inbound to read and index, and then weeks or months of waiting on the landlord, the surveyor and the other side’s solicitors. Through all of it, a handler still owns the file: chasing, checking, keeping it alive.
The reading is hard work; the waiting is what quietly costs you.
The inbound never stops
Intake enquiries, the tenant’s repair history, single‑joint‑expert surveyor reports, medical evidence and the landlord’s disclosure: every file is a heterogeneous stack of inbound before it’s a case, read and indexed by hand.
Then the file waits for everyone
Disclosure, the single‑joint‑expert report, the landlord’s solicitors: weeks or months per step. And a handler still owns the file the whole time, chasing and re‑checking, whether or not anything has actually moved.
The protocol won’t wait
The Pre‑Action Protocol front‑loads disclosure, expert evidence and deadlines before a claim is even issued. Miss a date and the file slips, and there’s no single view of what’s due across the book.
Housing disrepair claim manual workflow
A paralegal
- Opens the shared inbox
- Reads the email
- Find the question set
- Add questions to email
- Send to client
- Wait for the reply
- Key reply into BMS
- Move to the next one
How it works
The whole disrepair
workflow, on one
canvas.
The same capabilities, configured to a disrepair claim, with a person approving every action, on top of the case system you already run.
Read the surveyor report
Single‑joint‑expert reports and schedules of condition read for the disrepair items, severity and works needed, extracted and anchored to the page it came from.
Powered by Document IntelligenceClassify the landlord’s disclosure
Repair logs, tenancy files and complaint histories disclosed under the protocol, sorted against the right matter and the facts that carry the claim pulled out.
Powered by Correspondence ProcessingRead the medical evidence
GP and medical records screened for the conditions the damp‑ and mould‑related claim turns on, with the source page noted for every finding.
Powered by Document IntelligenceChase and carry the wait
Every outstanding disclosure, expert report or landlord response chased automatically and actioned the moment it lands: the file kept moving through the wait, with no one sitting on it.
Powered by Book IntelligenceDraft the letter of claim
The letter of claim and protocol correspondence drafted from the file, deadlines tracked against the protocol clock, with a fee earner signing off before anything leaves.
Powered by Document IntelligenceKeep the client updated
Acknowledgements, updates and query answers drafted and sent, with the thread kept on the matter, not scattered across individual inboxes.
Powered by Client Communications
Built once for disrepair, run on every file, on top of Proclaim, Leap, Visualfiles or Clio. Saber sits around your case system; it doesn’t replace it.
- DSARs
- Docs
- Emails
- CSV
- Queries
Approves
Where the cost really goes
You pay for the wait,
not the work.
A disrepair claim spends most of its life waiting: on the landlord’s disclosure, the surveyor’s report, the other side’s solicitors. Weeks, often months, per file. And through all of it a handler still owns the file: chasing, checking, keeping it moving. That waiting is where the cost quietly sits.
Saber carries the file through the wait and acts the moment a counterparty responds (on demand, around the clock) so your people aren’t tied up minding files that are simply waiting on someone else. The same team carries a far bigger book, and the cost of each file falls, because no one is paid to sit on it.
Built for FCA‑ and SRA‑regulated redress
A human approves every action, with a full audit trail and page‑anchored citations. ISO 27001 and ISO 42001 certified, UK‑only data residency, your data never used to train our models.
- Conduct trail
- Page-anchored
- ISO 27001
- ISO 42001
- UK data residency
Automate your book
with Saber.
Send us one workflow you run today: a DSAR, a batch of lender mail, a round of client updates. By the end of the week we’ll show it read, actioned and ready for a paralegal to approve, on your data. No fee, no commitment.
AI suggests. A human decides.
Claim Inbox handles the rest.
