Preparing hearing bundles with AI help: indexing, paginating, checking
By the ChamberOne team 4 minute read
Nobody enjoys the night before a bundle is due. The work is repetitive, the deadline is fixed and a single missing page can embarrass the team in front of the court. That mix makes bundle preparation a good test of where AI helps and where it does not. This article walks through the job in stages, marks the steps a machine can do well, and keeps a human check on the steps where a mistake costs the most.
Key points
- Read the court's directions first; the tool should follow them, not the other way round.
- Automate naming, duplicate spotting, draft indexing and date ordering, and review each result.
- Selection, privilege and index descriptions remain lawyer decisions.
- Check page counts, section edges and the electronic copy, ideally by someone who did not build the bundle.
Start with the court's directions, not the tool
Courts and tribunals set their own requirements for bundles: how documents are ordered, how pages are numbered, whether an electronic copy is needed and in what format. These differ between courts and change over time. Check the practice direction, local rules or registry instructions for the forum before you design the workflow, and keep them beside you while you work.
Automation will do whatever you tell it. If the instruction is wrong, you will produce a wrong bundle quickly. The directions come first, the tool second.
Where automation earns its keep
Four tasks suit software well because they are mechanical, tedious and easy to check afterwards.
- Naming and sorting: converting a folder of files with names like 'scan0042' into consistent titles with a date, a document type and a party.
- Duplicate detection: finding the same email or exhibit saved three times under different names, including near-duplicates with a small difference.
- Draft indexing: producing a first index with a description and date for each document, which a person then edits.
- Date ordering: arranging correspondence and notes chronologically, and flagging items with no readable date.
Where a person must stay in control
Selection is a legal judgment. Which documents belong in the bundle, which are privileged, which have been agreed with the other side: none of that should be decided by a tool. A model can suggest, but it does not know what has been agreed, what the judge asked for, or what the client has said must stay out.
Descriptions need the same care. An index entry that mischaracterises a document is a small error with large consequences, because the court relies on the index to find things. Read every entry against its document.
- Name and sort files consistently
- Detect duplicates and near-duplicates
- Produce a draft index for a person to edit
- Order documents by date and flag missing dates
- Which documents belong in the bundle
- What is privileged or already agreed
- Whether each index entry fits its document
The missing-page problem
The worst bundle errors are not clever. They are a page that did not scan, a document that lost its reverse side, a page numbered twice, or an exhibit that fell out when two files were merged. Software can cause these quietly, for example by dropping blank-looking pages or by failing on a corrupted file while carrying on with the rest.
Build in a check that does not depend on the tool being right. Compare the page count of each source document with the page count of its section in the bundle. Compare the final total with the sum of the parts. Spot-check the first and last page of every section. Do this by a person who did not assemble the bundle, if you can spare one.
A staged workflow
Here is one way to run it, with the checks marked.
- 1
Collect all candidate documents in one place and keep the originals untouched.
- 2
Run duplicate detection and have a lawyer decide which version stays.
- 3
Rename and classify documents, then review the classifications for errors.
- 4
Lawyer selects and orders the documents, guided by the court's directions.
- 5
Generate the draft index and paginate the bundle.
- 6
Check page counts, the first and last page of each section, and every index entry against its page.
- 7
Test the electronic copy: open it on a different device, follow the links, search for a known phrase.
- 8
Keep a record of what was checked and by whom.
Searchable text and its limits
Many courts and judges like a searchable electronic bundle. Making scans searchable depends on character recognition, which can misread poor copies, handwriting and stamps. A search that finds nothing is not proof that a phrase is absent. Do not tell a judge that a document 'does not mention' something on the strength of a search of an unchecked scan.
Where a document is critical, read the page itself. Where the copy is poor, consider whether a better one can be obtained before the bundle is finalised.
Who does what in a small team
Suppose a three-person litigation team has two days to produce a bundle. The paralegal collects, renames and de-duplicates, using software for the first pass. The associate selects and orders, and drafts the index descriptions from the tool's suggestions. The partner reads the index and a sample of documents, and signs off on what is left out. A different person, perhaps a secretary or a trainee, does the final page-count check with fresh eyes.
The point of splitting the work is not hierarchy. It is that the person who built something is the worst person to check it, because they read what they meant to see.
Confidential material and the last hour
A bundle often contains sensitive client material, medical records or documents covered by confidentiality orders. If you use an outside tool for naming or indexing, check where the files go and who can access them, and follow the firm's policy and any order that applies. Where there is doubt, do the sensitive sections by hand.
Finally, keep the last hour free. Late changes are normal: an agreed document arrives, a page is withdrawn. Every change after pagination can break cross-references. Re-run the checks after the final change, not before it. Tell everyone who holds a copy, including counsel and the other side, when a corrected version replaces an earlier one, so that nobody argues from a page that has moved. Keep a short note of what changed and when, because the question of which version a judge was given is easier to answer with a record.
This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.
Read next
AI in Witness Bundle and Proof of Evidence Preparation: What to Automate and What Not To
A practical guide for litigators on which parts of witness bundle and proof of evidence preparation AI can handle, and which parts it must not touch.
6 minute readHallucinated citations: what court sanctions teach about checking AI output
The patterns behind fake authorities reaching courts, and the supervision and checking controls that would have caught them.
5 minute readBuilding a litigation chronology with AI
Extract dated events, link each to its source page and check for conflicts before the chronology is used.
5 minute read