Page 147 has moved again
The bundle is due. A caseworker has spent the afternoon exporting documents from the case file, merging them in a PDF editor, stamping page numbers and typing an index in Word. Then the adviser adds a witness statement near the front. Every page number after it shifts, the index is now wrong, and the skeleton argument refers to pages that no longer say what it claims.
So the merge is done again, the stamps are redone, the index is retyped. At eleven at night, someone notices one document is in twice and another scanned upside down. Nobody is doing legal work at this point. They are fighting a PDF.
Bundles are built from scratch every time
The documents already exist on the matter. The problem is that there is no link between the file and the bundle. Each bundle starts as a manual export, and each change means redoing the steps that follow it, because pagination and the index depend on everything before them.
Firms often have a template for bundle layout and a style for indexes, but they live in people's heads and old examples. Different caseworkers produce different-looking bundles, and the quality depends on who is on duty the night before.
Some firms have tried general PDF tools with a merge feature. These help with joining files but not with the index, the sections or the rebuild when things change late.
What manual bundling costs
| Problem | Effect |
|---|---|
| Late changes | Pagination and index redone by hand, often more than once |
| Index and pages out of step | References in submissions point to the wrong page |
| Duplicated or missing documents | Embarrassing corrections after service |
| Poor scans | Illegible or rotated pages in a formal document |
| Senior staff involved | Advisers checking page numbers instead of preparing the case |
How the bundle tool works
- The tool reads the documents already stored on the matter, through your case management system's API or a linked document folder, so nothing is exported by hand.
- The caseworker builds the bundle by placing documents into sections from your firm's template, drag and drop, with a short description for each entry.
- On build, every document is converted to PDF, rotated upright where the scan is sideways, and checked for blank or unreadable pages, which are flagged rather than silently included.
- The tool merges everything, stamps page numbers in the position and format your firm uses, adds PDF bookmarks per document, and produces an index with matching page references.
- When a document is added, removed or moved, the whole bundle is rebuilt in one click, with the index updated to match.
- Each version is saved with a date and a list of what changed, so the adviser can see which version went where.
Any specific format required by a tribunal or court is set up by your firm in the template. We build what you specify and do not decide what the rules require.
Evenings back
Late additions stop being a crisis. The index always matches the pages. Bundles look the same whichever caseworker built them. Advisers review the content and the order, not the page numbers, and the version history shows exactly what was served.
The same tool usually ends up used for other compiled documents too, such as application bundles and evidence packs for clients.
Junior staff can build a first draft confidently because the template guides the structure, and the adviser's review focuses on whether the right documents are in the right order, which is where their time is best spent.
Does this sound familiar?
- Bundles are merged and paginated by hand
- A late document means redoing the index
- Different caseworkers produce different-looking bundles
- Page references in submissions have been wrong before
- Bundle preparation often runs into the evening