> ## Documentation Index
> Fetch the complete documentation index at: https://help.lexfill.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Filing packets

> One merged, stamped, QA-checked PDF in your firm's own order

## 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.

## 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.

Each finding offers the action that actually resolves it: **Accept intake value**, **Fix on form**, **Message client**, **Re-open intake slot**, or **Override & proceed** when you've decided the packet is right as it stands. Resolved findings stay on the record marked *accepted* or *overridden — proceeding*, so the decision is auditable later.

A packet that assembles clean says so.

## 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](/guides/ai-review#your-teams-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.

## Your firm's packet template

Every case type has a packet template, and every template is yours to change — in the [Firm Library](/guides/library).

* **Section order** is the assembly order. Drag to reorder.
* **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 `@mention` a teammate to route the related tasks to them.
* **Letterhead** — logo position and whether the firm name shows, applied to every page Lex generates.

Reset any template back to the Lexfill default at any time.

## Attorney-side forms

**G-28** (Notice of Entry of Appearance) and **I-907** (Premium Processing) are never asked of clients. They arrive pre-filled from your firm, attorney and client records, stay editable field by field, and are included automatically in the packets for the case types that need them.

## Litigation packages

Federal court matters produce a filing package rather than a USCIS packet — the complaint or petition plus the JS-44 civil cover sheet, AO 440 summonses, and service documents. See [Litigation](/guides/litigation).