What this page covers

This page explains what firms should expect from Parley’s exhibit packet workflow and what a legal team should validate before using it as part of a filing process.

Output expectations

Parley can assemble case materials into a single combined PDF with continuous pagination and an automatically generated index or table of contents.

In practical terms, firms should expect:

• one combined PDF for the packet

• continuous pagination across the full packet

• an index or table of contents aligned to exhibit order and page numbers

• bookmark behavior that can be validated if the firm requires bookmarks as part of its PDF standard

• final attorney or staff review before filing

Final review before filing

Parley is designed to reduce packet-assembly work, but filing teams should still run final QA on the exported packet.

That final review should confirm exhibit order, page references, and any firm-specific PDF requirements. If a firm applies its own bookmark rules, stamps, or other post-export formatting standards, a final PDF-tool pass may still be appropriate in some matters.

What to validate in a pilot

Run pilot checks on real packets, not only on sample files.

Recommended checks:

• late insert and reorder behavior

• pagination stability after inserts, deletions, or rebuilds

• index or table-of-contents accuracy against actual exhibit order and page starts

• bookmark behavior if the firm requires bookmarks

• file-size and high-volume packet handling

• whether the firm still wants a final PDF-tool pass for its own QA or formatting standard

Where this workflow is a strong fit

This workflow is a strong fit for evidence-heavy filings and RFE response packets where teams want faster assembly and more consistent packet structure while keeping final review inside the firm.