Combining PDFs into a matter file courts can navigate

A merged PDF is easy to produce. A matter file that judges and opponents can use without queries needs deliberate structure. Combining files is therefore less about a single button and more about how the case is presented.

Order is part of the argument

The familiar sequence - pleading, schedule of exhibits, exhibits in the order cited - looks obvious until a bundle is sorted “by scanner intake time”. Then every recipient searches. Firms should fix a default order per matter type and allow departures only with a reason (for example a chronological special file).

Exhibit numbers must still match after the merge. Number first and reshuffle later, and text and bundle diverge. Better: lock the final order, then close the schedule and numbering.

Bookmarks and filenames as navigation

From a few dozen pages upward, bookmarks or clear divider pages (“Exhibit A1”) help. The filename should carry the matter reference, content and version - not “final_final3.pdf”. Internal working names do not belong on the filing copy.

Practice check before upload

• Match final order against the exhibit schedule.
• Hunt missing or duplicate exhibits deliberately.
• Remove empty pages; fix wrong orientation.
• Set filename and version for filing.
• Hold total pages and size against portal rules.
• On large bundles: spot-test jump marks or dividers.

Technical pitfalls

Mixed page sizes (A4 and landscape plans) in one file are allowed but harder to view. Heavily protected PDFs sometimes will not merge cleanly - unlock or regenerate where lawful. OCR after a merge can be slow on very large files; with uneven quality it is often better to recognise sections before the merge and only then combine.

LexLogik supports merging in the same browser workflow as compression and quality checks. The architecture of the file remains the firm’s professional task.

Check cross-references after the merge

Spot-check pleading citations against page numbers in the pack. Exhibit numbers drift when something is inserted late. Four eyes between drafter and pack builder prevent classic swaps under pressure.

Bookmarks should mirror the schedule’s language, not internal codes. Recipients understand “Exhibit A4 - report”, not “scan_final_v3”. Keep individual files in case a sub-bundle must be rebuilt.

Upload order and receipts

Some portals number by upload time. Upload parts in intended order and keep receipts. On failure you know what arrived. Avoid identical filenames across matters in the same portal account.

Responsibility in the team

Often assistants assemble the bundle; counsel checks citations in the pleading against actual order. Make that split explicit. A short four-eyes step on deadline exhibit bundles prevents the classic swap of A3 and A4 under pressure.

Citation spot-check before upload

Pull three random exhibit citations from the pleading and jump to them in the bundle. If number, bookmark and content disagree, stop the upload. Those three minutes prevent classic exhibit swaps under deadline pressure.

Merging is file architecture, not a single button. Final order, matching exhibit numbers and clear bookmarks make the pack usable for court and opponent. Keeping individual files as well lets you rebuild a sub-bundle later without rescanning the whole matter.