Batch & quick autofill
Batch templates fill one row-repeating document against many cases at once. A Run with your documents… run fills a template against ad-hoc PDFs. Both reuse the standard single-case fill engine.
Batch handles cyclical work. You turn a known set of cases into rows on one summary document. An own-documents run generates a quick PDF. You use it to test field placements or validate a field mapping.
Batch templates
A template becomes multi-case automatically. You add a Batch field to the template. The app removes the batch capability when you delete the field. There is no separate toggle. Only batch templates appear in the batch bar dropdown.
Batch autofill requires a specific plan. Pro and Scale include it. Free and Lite require an upgrade to Pro.
A batch run accepts one to 24 selected cases. You select cases using the row checkboxes. A numbered badge shows the selection order. It reads Selected {case identifier}, position {number}. Click to deselect. You click Select All to grab every visible case in the current order.
In the Select Files for Batch dialog, you can pick a cover override. The dialog only offers PDF-like files from selected cases matching the output category. The app uses this cover as-is. It does not run autofill on it.
For appended files, the dialog automatically selects the newest eligible PDF per case. It filters these files by input category. You cannot choose a no-file option for a case with eligible files.
The template fills once. Each selected case becomes one row. The per-case files merge after the generated document. The app saves the combined PDF to every selected case. It tags the file with the output category. The UI shows a generic Some files failed to save error for failures. Cases with a successful save keep the file.
A batch template holds a fixed number of rows. The run rejects if you select more cases than the template capacity. You must split the runs or increase the template row count.
Row order
Rows follow your selection order. Select All uses the current visible sort order. You can override this in the Batch field. You enter a plain language instruction in the Row order (optional) box. The placeholder reads e.g. order rows by amount, highest first.
Simple single-field sorts run without an AI call. Complex instructions use AI at generation. The app falls back to selection order when it cannot resolve the instruction. Leaving the box blank preserves selection order.
Run with your documents
An own-documents run generates a filled PDF. The run bypasses the normal case-autofill flow. It assembles template source tabs from the document bar into one PDF. It hides blank and dangling rows. The run uses the full cloud autofill pipeline. This includes AI extraction.
The Run split button sits in two places. On a source tab, you use the editor toolbar button. On the Data tab, you use its own Run split button. The toolbar button disappears on the Data tab.
The run modal shows a Documents section. It lists each source document. You click Replace to upload your own PDF. Unreplaced rows use the stored copy.
You fill any required form questions. These block the run. You optionally enter Special AI instructions. These apply to this run only. A blank box uses default template logic.
The editor prompts you to save unsaved edits first. You can also run against the last saved version. Clicking the main Run button runs a Test & Preview. This uses stored sample documents without uploads.
The finished PDF downloads automatically. The editor navigates to the Data tab. It refreshes the last-run values. You click View output to open the output modal. The preview pane does not show the output.
The run persists a value snapshot on the template. It has no activity timeline. On Pro and Scale, no case hosts the result. On Free and Lite, the app saves a temporary case. These last 14 days. The app caps them at 50 live cases. It purges the oldest cases over the cap. You run autofill on a real case for a permanent record.