How to Build an Indexed Court Bundle

An index that sends the reader to page 214 for a document that actually sits on page 231 does more damage than a plain stack of paper, because it invites confident reliance and then fails at the worst moment. Bundles slip out of alignment for a dull, predictable reason: the index gets built against draft files, then documents are added, re-scanned, or reordered, and nobody re-checks the page numbers before the bundle is served. The fix is discipline about sequence.

Paginate first, index last

Never number the index against a folder of separate files you still intend to merge. Assemble the complete bundle, run pagination across the whole document as a single continuous file, and only then write the index against those final numbers. If you index early and combine late, every insertion after that point shifts the pages beneath it and silently invalidates everything below.

Group documents in a sequence a reader expects

A bundle is a reading tool, not a filing cabinet. Order it so the reader can move through the dispute logically:

• Pleadings and applications in the order they were filed
• Orders and directions in date sequence
• Correspondence grouped by thread, chronological within each
• Supporting documents, agreements, and annexures, clearly labelled

Keep filed material visibly separate from internal working notes, and never let a draft or a privileged note wander into the served copy.

Label so each entry is unmistakable

An index line that reads "Letter" helps no one. Give each entry a date, the parties or author, and enough description to identify it without opening the page: "Notice under Section X from A to B, dated 12 March." Consistent labelling lets counsel call for a document by its index description mid-argument and get the right page first time.

Test the references before anyone relies on them

Sampling is the step most people skip and most regret. Open a spread of index entries and confirm each lands on the document it names, at the top of the right page. Pagination often survives on screen but breaks on export or when printed on a machine that scales the page, so check the format the bundle will actually be used in. If the advocate will work from a printout, test the printout; if from a tablet, test the file at reading size.

Freeze the version and record what was served

Once the bundle is finalised, treat it as fixed. Note which version went to the court, which to the other side, and which the advocate is carrying, because a late correction that produces a second pagination is how one side ends up citing page numbers the bench cannot find. If a genuine correction is unavoidable, reissue the whole bundle with a clear version marker rather than patching a few pages.

Keep the build repeatable

Bundles are assembled under time pressure, often late the night before, and a workflow that keeps the index tied to the final paginated file removes most of the risk. Producing a clean, consistently labelled bundle with references that survive export is the sort of task Juniorlawyer is designed to take off the last-minute pile so the person building it is checking accuracy rather than fighting page numbers.

The test of a bundle is simple: pick any line in the index at random, and the reader should land exactly where it promised. Build against the final file, label every entry so it identifies itself, sample the references in the format that will be used, and fix the version before it leaves your hands. An index that can be trusted is worth more than a bundle that merely looks complete.