What a packet is
A filing packet is the whole submission as one merged PDF: fee page, cover letter, table of contents, the forms, and every exhibit in the order your firm files them — stamped and paginated, ready to print or upload. Lex assembles it and flags what needs your judgment. You review it and file it.Assembling one
The Packet tab on a client’s page shows the plan before it runs: which case type’s template it will follow, which forms it will include, how many required checklist slots are filled, and an estimated page count. Press Assemble packet and the run starts in the background — about five minutes. You can leave the page; a notification tells you when it lands. Ask Lex for it instead if you prefer:/packet checks readiness first, starts the run, and reports back.
If a run fails, nothing was filed — re-run it.
Selecting documents
Every run — the first assembly, an update, or a re-run — opens Documents in this packet before it starts. It lists the case’s uploads grouped by the exhibit they fill, with a count of how many are selected.- Everything is checked by default. Uncheck anything you want left out of the packet; Select all and Clear all do what they say.
- Your choice is remembered for the case. The next run opens on the same selection instead of quietly re-adding what you dropped. Documents uploaded since then arrive checked.
- What can’t be filed is listed too. Documents that are rejected in review, have no place in this packet, are draft translations, or didn’t finish uploading sit under Won’t be included with the reason, so a missing exhibit is explained here rather than discovered in the PDF.
- Clearing everything is allowed — the packet is assembled from the forms and generated pages alone, and any required checklist slots left empty still show up as findings.
Findings
A packet doesn’t silently paper over problems. Findings are grouped by where they came from:- Preflight — what was wrong before assembly started: incomplete forms, missing or unapproved documents.
- QA · auto-fixed — cross-checks Lex ran and resolved itself.
- QA · needs your judgment — the ones that stop at your desk.
Commenting on the packet
An assembled packet takes comments the same way a form does — switch on Comment in the toolbar and click anywhere on the PDF to start a thread pinned to that spot, with replies,@ mentions and resolve. See your team’s own comments.
Re-assembling the packet doesn’t discard the discussion: threads left on an earlier run are marked Outdated in the Comments panel, so you can tell a comment about the current PDF from one about the version it replaced.
Threads belong to the run they were left on. Opening a published version shows only the threads from the run behind it, read-only.
Packet versions
Every run replaces what the Packet tab shows. To keep a permanent record of what you filed, publish the packet. Each publish saves the latest run’s PDF, byte for byte, as a numbered version for the case — v1, v2, and so on — and the newest version is the live one. Later runs never change a published version. Publish and the version menu sit at the right end of the packet’s PDF toolbar. When a newer run has finished since the live version, the menu reads Unpublished changes.- Click Publish. The Publish vN dialog takes an optional note (up to 500 characters) and two options, both off by default:
- Click Publish. The run becomes vN and the live version. If a teammate publishes at the same moment, one of you is asked to try again — version numbers never collide or skip.
filing-packet-v<n>.pdf. Back to current packet returns to the latest run.
Editing a version. The pencil on a version’s row opens Edit vN, where you can change its note and turn Save to Documents and Visible to client on or off. The PDF and the version number never change, and versions can’t be deleted.
Your firm’s packet template
Every case type has a packet template, and every template is yours to change — in the Firm Library.- Section order is the assembly order. Drag to reorder.
- Add and remove sections. Drop a section you don’t file, or add your own note pages and document sections. Form sections follow the template’s forms.
- Instructions for Lex, per section — your template language, the points you always make. Lex follows them when drafting and QA-checking that section.
- Packet instructions, firm-wide for that packet — and you can
@mentiona teammate to route the related tasks to them. - Letterhead — logo position and whether the firm name shows, applied to every page Lex generates.