Witness statement drafting software turns your case documents into a draft statement that follows the Civil Procedure Rules. The difference between tools is not how fast they write. It is whether what comes out survives scrutiny.
We built LegalDocs-Assist because the failure we kept seeing was never a typing problem. It was a compliance problem, and it showed up at the worst possible moment.
What is witness statement drafting software?
It is software that reads your case file and produces a draft witness statement in the format a court expects.
Most tools stop at generation. You upload documents, a language model writes prose, and you are handed something that reads well and may or may not comply with anything. The drafting was never the hard part.
The hard part is the rest of it. Does the statement meet the requirements of Practice Direction 32 on format and content? Is the statement of truth in the current wording? Are exhibits referenced properly and numbered consistently? Is the chronology internally consistent with the documents it came from? Does the legal argument rest on an authority that actually exists and actually says what the statement claims?
That is what we automate. Generation is table stakes. Compliance is the product.
Why do witness statements fail?
They fail on procedure far more often than on substance.
A statement gets challenged because the statement of truth is wrong, because it contains argument dressed as evidence, because it recites documents the witness never saw, or because exhibits are referenced inconsistently. None of that is about whether your client has a good case. All of it is avoidable.
The second failure mode is newer. A statement rests on an authority that does not support the proposition, or in the worst cases does not exist at all. Courts have taken an increasingly dim view of this, and the professional consequences land on the person who signed the statement of truth, not on the software.
This is why we treat the case law library and the compliance checks as one thing rather than two. A draft that is beautifully formatted and legally wrong is not a better draft.
How does LegalDocs-Assist draft a witness statement?
You drop your case documents into named slots, and the Witness Statement Generator works from what is actually in them.
For a credit hire claim that means the call notes, the accident report, the engineer’s report and the payment pack. For housing disrepair it means the tenant complaints, the landlord letters, the surveyor reports and the repair log. The slots differ by practice area because the evidence differs by practice area, and a tool that asks a clinical negligence solicitor to upload an engineer’s report has told you something about how well it understands the work.
From there the platform builds the chronology, drafts the statement, and runs automated CPR Part 32 compliance checks against it. Anything missing comes back as a flagged placeholder rather than an invention. If a fact is not in the documents, we do not fill the gap with something plausible.
You can also apply your firm’s house style as a configurable overlay, so the output arrives in your format rather than ours.
The statement then goes to a solicitor for review and signature. That is not a limitation we are apologising for, it is the design. We set out how solicitors verify an AI-drafted statement in more detail.
Which authorities does it draw on?
Every practice area has its own library of UK authorities. These are the figures as at 6 August 2026.
| Practice area | UK authorities | Of which binding |
|---|---|---|
| RTA and credit hire | 133 | 92 |
| Housing disrepair | 46 | 28 |
| Clinical negligence | 13 | |
| Employers' liability | 10 | |
| Public liability | 10 | |
| Distinct total | 210 |
We publish these numbers because most of our competitors cannot. “Powered by AI” tells a litigator nothing. A named, countable library of authorities that a person curated and can be checked against tells them what the tool is standing on.
The libraries are practice-area specific for a reason. Impecuniosity is a credit hire concept and it has no business appearing in a disrepair statement. Bolam, Bolitho and Montgomery govern clinical negligence and nothing else. Keeping them separate is how the platform avoids importing the vocabulary of one practice area into another, which is one of the more obvious tells that a legal tool was built by people who have not done the work.
Recent decisions matter here too. Wiltshire v Aioi Nissay Dowa changed what a credit hire witness statement needs to address, and the library moved with it.
What about the statement of truth and exhibits?
Both are checked automatically, because both are where avoidable challenges come from.
The statement of truth must be in the current prescribed wording, and the consequences of signing a false one are set out in the rules. The platform checks the wording is right and that it sits in the correct place in the document.
Exhibits are checked for consistent referencing and numbering across the statement, so you do not end up with an exhibit referred to as JB1 in one paragraph and JB/1 in another. It is a small thing that creates a disproportionate amount of irritation at a hearing.
If you want the detail on the underlying requirements, we set out what CPR Part 32 requires of a witness statement in plain terms.
Is it safe to use AI for court documents?
It is safe if the architecture is built for it, and most general tools are not.
PDFs are processed inside your browser, they never reach our servers. Your data is never used to train any AI model. Those two sentences are the reason firms handling sensitive client material can use this where they could not use a consumer chatbot.
The wider point is about grounding. A general-purpose model has no curated case law library and no compliance layer. It will produce something that reads like a witness statement, with citations that may not exist, and it has no mechanism to tell you which is which. That is a materially different risk profile from a tool that draws on a fixed, curated set of authorities and flags gaps rather than filling them.
Human review remains mandatory. Software does not sign statements of truth.
Which practice areas are covered?
Five: RTA and credit hire, housing disrepair, clinical negligence, employers’ liability, and public liability.
Each has its own document slots, its own authority library, and its own compliance behaviour. Alongside the Witness Statement Generator there are practice-area tools including the Disrepair Chronology Builder, medical records pagination, Letters of Claim, and defence analysis.
The best way to judge whether the output is good enough for your firm is to look at it. You can see it in action, or get in touch and we will walk you through a statement in your own practice area.