Most writing about AI drafting is really about contracts - NDAs, MSAs, clause libraries. But walk into a disputes practice and count what actually gets drafted in a week: legal notices and replies, plaints and petitions, interlocutory applications, affidavits, written statements, the occasional opinion. Litigation paper is the volume business of drafting, it is deadline-driven, and it has a property contract drafting does not: most of it is addressed to a court or a counterparty who will attack its defects. This guide covers how AI drafting handles that class of document - using Judicio's Drafting feature as the working example - and where the professional lines sit. It is a companion to our precedent-to-first-draft guide, which covers the transactional side.
Litigation paper is different from contract paper
Three differences change the drafting problem. First, structure is prescribed, not preferred. A petition has parties, jurisdiction, facts, grounds, and prayer in an expected order; an affidavit deposes in numbered paragraphs with a verification; a notice under a statute must contain what the statute says it must. Get a contract's clause order wrong and it reads oddly; get litigation structure wrong and the defect is visible to the registry, the bench, and the other side.
Second, authority is load-bearing. A contract cites almost nothing; a ground in a petition stands on statute and precedent, which means a drafting tool that invents or mis-cites authority is worse than useless. Third, the deadline profile is brutal - notices with statutory reply windows, applications for tomorrow's mention. The value of automation is highest exactly where the time pressure makes unstructured chatbot output most dangerous.
Start from a brief, your files, or a template
Judicio's Drafting starts three ways. Ask Judicio takes a plain-language brief: "legal notice to a tenant for arrears of rent since January and termination of the licence, 15 days to comply". Smart Suggestions reads the matter documents you attach and proposes the documents that follow from them. Templates start from a structured pattern for the document type.
For litigation work the strongest starting point is usually a precedent from your own File Library: attach your chamber's writ format or your firm's standard notice and the draft mirrors its structure and defined terms rather than a generic form. Before generating, you set the scope with discrete chips - jurisdiction, tone, language, and length - and the draft is grounded in the files you attached: the notice recites the actual dates from the rent ledger, the petition's facts follow the record you gave it.
Structure is the hard part - and where AI drafting earns trust
The output that matters is not prose, it is a real, structured document: headings, numbered clauses and paragraphs, defined terms, a prayer where a prayer belongs. That sounds mundane and is exactly the point - the difference between a wall of text you re-type into your format and a draft you refine is the difference between a toy and a tool.
| Document | Structural spine the draft must carry |
|---|---|
| Petition / plaint | Parties and addresses; jurisdiction; chronological facts; grounds; interim relief sought; prayer; verification |
| Interlocutory application | The order sought; the specific facts justifying it; the enabling provision; urgency, if claimed |
| Affidavit | Deponent's identity and capacity; numbered depositions; personal-knowledge vs information-and-belief; verification |
| Legal notice | Sender's authority; the factual grievance with dates; the legal basis; the demand; the compliance window; consequences of default |
| Reply to notice | Paragraph-wise response; admissions and denials chosen deliberately; counter-narrative; reservation of rights |
A drafting model has to know these spines per document type and per jurisdiction - which is why "draft me a bail application" in a general-purpose chatbot produces something that reads fluently and files badly. The structured-document requirement is the quiet quality bar in this category; our explainer on legal document automation covers why template-shaped output beats free text for anything a court will read.
Legal notices and replies: the highest-volume use case
If one litigation document type justifies a drafting workflow by itself, it is the legal notice. Notices are frequent, formulaic in shape but fact-specific in content, and consequential when defective - a demand notice that misstates the amount or blows a statutory window can sink the claim it was meant to found. They are also the classic "urgent but not important enough" task that lands on the most junior person at 5 p.m.
The AI workflow inverts the economics: the structure, recitals, and standard consequence language are generated in minutes from the brief and the attached record, and the lawyer's time goes where it should - verifying the dates against the documents, choosing the demands, setting the compliance window the governing statute or contract requires, and judging tone. Replies get the same treatment with one addition: a paragraph-wise response pattern where each admission or denial is a deliberate choice, because in later proceedings the reply is evidence of what was and was not disputed.
Revision as tracked changes, cited as you draft
The first draft is never the filed draft, so the revision loop is where a drafting tool lives or dies. In Judicio, every AI revision arrives as a tracked change - the exact insertion and deletion, visible in a Redline view, which you accept or reject per change or all at once. Ask it to strengthen the ground on limitation, soften the notice's final paragraph, or renumber after dropping a prayer, and you see precisely what moved. Manual editing is always available, and Clean and Original views show the document with and without pending edits.
Authorities cited in the draft sit in a Sources tab, linked to the clause each supports - so the ground citing a limitation provision or a precedent is inspectable at the point of use. The export respects the same discipline: Word as a final copy or a tracked-changes redline, or a clean PDF. The tracked-change principle is the same one that governs our contract redlining workflow: an AI edit you cannot see is an edit you cannot be responsible for - and you are signing this document.
Jurisdiction, language, and tone
Litigation drafting is jurisdiction-shaped at every level: the court's format conventions, the governing procedural code, the language of the forum. Setting the jurisdiction chip scopes the draft's structure and framing; the language setting matters in multilingual practice - a notice may need to go in the language its recipient and the local forum actually use; and tone is a genuine drafting decision, not cosmetics - a pre-litigation notice written to preserve a commercial relationship reads differently from one written as the last step before filing.
Treat these as scoping decisions you make deliberately at the start, the way you would brief a junior. The chips make the choices explicit instead of burying them in prompt-craft - and the same brief produces a consistent house style across the team, which is half of what a drafting practice manual tries to achieve.
What AI drafting must not do
The professional lines, stated plainly. It must not invent authority - every citation in anything filed gets verified against the source first; courts have spent two years sanctioning lawyers who skipped that step, and the Sources tab exists to make the check fast, not to replace it. It must not replace the deponent - an affidavit deposes to someone's actual knowledge, and no draft changes whose oath it is. It must not decide strategy - which grounds to press, what to demand, whether to send the notice at all are judgment calls that belong to counsel and client. The draft is labour; the lawyer is the author. That allocation is not a disclaimer, it is the design.
Getting started with Judicio
Drafting is flat-priced per run - Concise for speed, Deep Mode for thoroughness, with follow-up refinements at half price and manual editing and export always free; current rates are on the pricing page. The realistic first test is this week's notice or application: start a free 7-day trial - 500 credits, no card required - attach the matter documents, brief it the way you would brief a junior, and judge the draft the way you would judge theirs: structure first, citations checked, your name on it last.