The Pandoc Pleading
Captions, tables of authorities, and signature blocks — driven by a firm reference template.
The open-source practice
A practitioner’s guide to replacing proprietary software with free, scriptable tools — drafting in Markdown, turning PDF productions into searchable data, and automating the grind.
Focus areas
Most of the repetitive grind in legal work comes down to two things: producing documents, and working through the other side’s papers.
Focus 01 — The drafting desk
Pleadings, briefs, and letters live in Markdown — a format you can read in 1999 or 2099. One command turns the draft into a court-ready Word document, formatted by your firm’s reference template.
Focus 02 — The document mill
The other side’s production arrives as three thousand scanned pages. You leave with a full-text index, searchable Bates cites, and clean PDFs for the client — in an afternoon, not a summer.
Live demos
Two working simulations of the core pipelines. No install, no account — just the idea, executable.
Simulated preview — the real pipeline runs pandoc with your firm’s reference template.
Court-ready document
Simulated against an 8-document sample production — the real pipeline searches thousands of OCR’d pages via SQLite FTS5.
The toolbox
Everything used in the workflows here is open source, free, and runs on your own machine. Nothing phones home.
The universal document converter — Markdown to court-ready Word, PDF, and more.
The OCR engine that turns scanned pages into searchable text.
Split, merge, repair, and renumber PDF files from the command line.
Version control for every draft — a full, defensible history of how a document evolved.
A local, full-text-searchable index of your document production. One file, no server.
The glue that automates the repetitive work between the other tools.
The workflow
A simple, repeatable pipeline that keeps documents clean and consistent every single time.
Write in Markdown. Plain text — fast to edit, easy to review, and under version control.
Pandoc turns the draft into a formatted Word document using your firm’s template.
OCR and index the other side’s production. Find every page that matters in seconds.
Clean, consistent, court-ready documents — every single time.
Why open source
Documents live in plain text and open formats. No subscriptions, no proprietary files, and no vendor holding your own work hostage.
Every tool in the stack costs nothing. The only expense is a little time to learn — time you get back many times over.
If a task takes more than a few clicks, it can be automated. One command can process a thousand pages exactly the way you would.
| Proprietary suite | Open source stack | |
|---|---|---|
| Licensing | Per seat, per year | $0, forever |
| Your files | Proprietary formats | Plain text + open formats |
| Automation | Clicks and macros | One command, any number of documents |
| If the vendor folds | Your files are ransom | The tools live on |
Plain text is a legal right.
Anything you can read without software can’t be held hostage.
If it repeats, automate it.
A task that takes more than a few clicks deserves a script.
Boring is a feature.
The tools you never think about are the ones that work.
The library
Step-by-step walkthroughs written for practicing lawyers — templates, scripts, and checklists. Each one ships complete.
Captions, tables of authorities, and signature blocks — driven by a firm reference template.
The full Tesseract pipeline: extraction, quality checks, and a searchable full-text index.
Numbering, segmentation, and Bates maps for compilations and disclosure sets.
Versioning drafts, diffing revisions, and keeping an audit trail the court would accept.
Questions
No. The guides are written for lawyers, not engineers. Every workflow is a handful of copy-paste commands; the Python appears only where it saves real time, and it’s always optional.
Courts accept Word and PDF — and that’s what you file. Markdown is your working format: the place where the document is fast, diff-able, and future-proof. The conversion step exists precisely so the court sees the format it expects.
Everything runs locally on your machine. No cloud, no telemetry, no account. Your matter never leaves your hardware — which, for a privileged document, is the whole point.
Every tool in the stack is open source with no cost. The guides on this site are free, too. If a workflow ever needs a paid service, the guide will say so up front and show you the free alternative.
It runs on Windows, macOS, and Linux — including ARM laptops — and everything is local, so there’s no network access to block. The guides start from a clean install, so they double as your IT request sheet.
Four guides are in production now. Each ships complete — templates, scripts, and checklists included.
See what’s coming