The platform
One system for the whole life of a case
Intake, case management, client communication, documents and settlement — on a single record, in one place, with the routine work handled in the background.
What's inside
Seven surfaces, one case record
Each of these is a view onto the same case, not a separate tool with its own copy of the truth. Nothing is retyped and nothing needs reconciling at the end of the month.
Case management
Phases, deadlines and documents on one timeline, so where a case stands is a fact rather than a question for whoever last touched it.
Client communications
Calls, texts and email attach themselves to the case as they happen — no forwarding, no pasting, no separate inbox to search later.
AI workflows
Medical records and bills are read and catalogued as they arrive, with provider and lien values extracted for a person to confirm.
Document automation
Demand packages, letters and retainers assemble from the case record, so the figures in them cannot drift from the figures in the file.
Reporting
Where cases stall, which deadlines are close, and what the pipeline is worth — read off the same record the work happens on.
Team collaboration
Assignments and handoffs are explicit, so a case never depends on one person remembering how it moves.
Client portal
Clients see progress and send documents themselves, which is most of what the update calls were for.
How a case moves
The phases are the system, not a status field
A personal injury case runs a known course. OneCounsel models that course directly, so the next action on a case is something the system can name rather than something a senior paralegal has to be asked.
- 01
Intake
Facts captured once, checked for the things that decide whether a case is viable, and turned into a file rather than a note.
- 02
Treatment
Records and bills gather against the case as they arrive, with gaps visible while there is still time to chase them.
- 03
Demand
The package assembles from what is already in the file — specials, records, liens — instead of being rebuilt by hand.
- 04
Negotiate
Offers, counters and authority tracked against the case, so the history of a negotiation is not in somebody's memory.
- 05
Litigate
Deadlines and filings carried on the same record, for the cases that do not settle.
- 06
Finalize
Disbursement, liens and closing handled against the numbers the file already holds.
Built for the data you hold
Medical records are the hard part, so they set the bar
- Tenant isolation in the database
- Every query runs under row-level security tied to the firm, enforced by Postgres rather than by application code remembering to filter.
- Permission on every endpoint
- Access is checked per action and per record against an authorization policy, not inferred from which screen someone reached.
- PHI treated as PHI
- Protected health information is masked in logs and kept out of error messages, because that is where it usually escapes.
- An audit trail you can read
- Who saw what and who changed what, recorded as events on the case rather than reconstructed from server logs.
See it on your own caseload
Thirty minutes with someone who knows personal injury practice. We will tell you plainly if it is not a fit.
Request a Demo