Run autofill

Open a file in the case review modal, pick a template in the right-side Autofill rail, click Autofill, and the finished PDF lands in the case Documents section under Files Generated, tagged with the template output category.

Updated 4 min read

Autofill takes a case and a template, resolves every field value from its source, then writes the values onto the template to produce a finished PDF. The fill step is deterministic: same case + same template + same source data = the same PDF, every time. Extraction (the AI step) is non-deterministic; the fill that follows is not. (One exception: templates with Document reflows enabled add an AI placement step at fill time, covered under Troubleshooting.)

Diagram of a source document with highlighted regions on the left, value tiles traveling through a drafting lens, and a pen inking those values into a target form's boxes on the right
Fig. 01Extract, then fill. Values are read from highlighted regions of the source, resolved per field, and inked into the exact write zones on the output.

How values flow

Each field's inputs (Question, Extracted, or Static) resolve into case.data; its outputs then act, a write zone stamping a value onto the PDF or a transform deriving a new one. The full field model lives in Build a template. What matters at fill time: each write zone reads case.data[placement.dataKey] and stamps it; source tabs (workspace document sources, blank pages, template references) set page order, with pages from referenced case files stitched in; and named PDF form fields are placed by name and never move.

The five modes share one resolver and renderer, differing only in steps run: Extract Only (ingest or Re-extract, no PDF), Fill Only (fill from existing data; a Generate <template> row builds the deliverable with no incoming file), Extract + Fill, Update Case (write extracted values back), and Batch Fill (one batch template across many selected cases, each filling one row into a single combined PDF saved to every case, no extraction). Two "batch" terms meet here: a batch field is a field type holding a variable number of rows, while Batch Fill is the operation, one run across many selected cases each filling one row of that field.

Run it on a case

1Open the case2Open a file3Pick template in rail4Click Autofill5Run AutofillDownload from Files

The review modal pins an Autofill rail to the right of the preview, the canonical entry point, holding the template picker and one Autofill button. Clicking it swaps the preview to a prompt: form questions, an optional Special AI Instructions textarea (this run only), and Run Autofill (if the template has no form questions, the prompt is just the textarea and the button, which you can leave blank to run the template's default logic). The output PDF appears in Documents → Files Generated, tagged with the template's output category. The kebab (...) menu owns Re-extract and Share.

On mobile, the kebab opens a bottom drawer with the picker plus Autofill, Extract/Re-extract, and Share.

You can also trigger runs from the case's Documents section: expand a received file for per-template Autofill or Update case, use a Run a template row for templates not yet run, or a Generate <template> row to build a deliverable with no incoming file (an amber Needs N badge flags missing data). See Cases and data for the full Documents layout.

To run without creating a case, the template editor toolbar's split Run button tests against the template's stored sample documents, while its dropdown's Run with your documents… option fills against PDFs you upload (the filled PDF downloads automatically and appears in the preview pane): use it to test a new template or generate a one-off. For bulk runs, select multiple cases in the dashboard, pick a batch template in the batch action bar, and click Autofill.

An autofill run
TemplateVendor Cover Sheet
Source caseINV-2026-0412
Fields resolved12 of 12
OutputAcme-Supply-Co-INV-2026-0412.pdf

Troubleshooting

Fields empty despite case values: check the input source. Question must be typed at run time; for Extracted, confirm the write zone points at the input or transform that produces the value (a write zone stamps whatever value its key points at in case data).

"No template available": templates appear only when the case has a file in a category the template accepts. Check the file's categories against the template's input categories.

Fields in the wrong place: placement is exact by default. If content shifts between fills (variable-length sections pushing fields around, a paragraph growing, a signature block moving onto the next page), enable Document reflows in the template's details dropdown (click the template name in the editor toolbar) so write zones re-find their anchor with AI. If an anchor can't be found, the value stamps at its authored position rather than guessing.

Missing pages: pages aren't included unless a source tab references them. Open the document bar above the editor preview, then the active tab's chevron popover (multi-source layout) or menu (single-source layout) and check the "Include pages from source" boxes.

We use cookies to keep you signed in and improve the product. See our Cookie Policy.
Manage preferences