The platform

Demand packages built from the file, not beside it

Demand packages, letters and retainers generated from the case record.

What this looks like today

The demand is assembled by hand from records, bills and the case file. Every figure in it is retyped, which means every figure in it can be wrong.

What it does

  • Assembled from the case record

    Specials, records, treatment history and liens come from the file itself, so the package cannot disagree with the case it describes.

  • Letters and retainers from templates

    Coverage letters, representation letters and retainers generate with the case's own details filled in.

  • One place to change wording

    Firm language lives in the template, so improving a paragraph improves every document that uses it from then on.

  • Reviewed before it goes

    Generation produces a draft for a person to approve. Nothing leaves the firm without a human reading it.

The numbers cannot drift

A demand assembled from the case record is arithmetically the same as the case record. That is the whole point — the failure being removed is not slowness, it is a package that quietly disagrees with the file it came from.

What it does not do

Templates are for the documents a PI case produces repeatedly. Bespoke pleadings and one-off drafting are still drafting.

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

We'd like to measure how this site is doing

Analytics helps us see which pages actually help firms evaluate OneCounsel. You can refuse, and the site works exactly the same. How we handle data