Run autofill

Autofill resolves every field value from its source and writes it onto a document. The standard fill step is deterministic. The app uses AI at fill time for AI instruction values, From case data picks, Document reflows, page-shift rules, per-run instructions, and complex batch row orders.

Every run on a case goes through one run screen. It opens three ways: click a document name in the case Documents list to open its preview, then click Run a template; pick Run a template on this file... from a document row's menu; or pick Generate from the case menu. The run screen covers the case, and the list beside it becomes the template picker, with the case pinned at the top.

The picker lists the workspace's templates in two groups. Reads a document holds the templates that read a file. Each row shows what it reads and what it produces, and a badge says how ready the case is: ready when the case holds every file the template reads, 1 of 2 files when it holds some, and the missing file's name when it holds none. The chip above the list keeps only the templates this case can feed at least one file of; click it to see every template. Fills from case data holds the templates that read nothing and fill their pages from the case's values. Forms stay in the template editor.

Pick a template. One section per document the template reads lists the case's files in that category, newest first, and the file you came from wears On screen and is picked first. A row with several matching files starts on the newest one. A row the template reads needs a file, so when the case has none its drop zone opens on its own: drop a file there and it lands on the case when the run starts. A row the template only fills can go without a file, and the run uses the template's blank page. Upload a file at the top right swaps the files for drop zones.

The Answers for this run card asks every Form field question on the template, including a question on the same field as an Extracted input, prefilled from the case. Click Instructions for this run to type guidance for this run only, and tick Read the documents again to read the picked files again before the fill. Click Run. The screen shows the steps, and when the file disagrees with what the case holds, it asks what to keep before it continues.

The answers you changed are saved on the case before the run starts, and clearing an answer clears it on the case. If the save fails, the run does not start and your answers stay on the screen. From case data rows are the exception: what you type or clear there applies to this run only and is never saved. On the read-only dashboard of the Free and Lite plans, the run screen does not open: Run a template and Generate open the upgrade prompt and save nothing.

When the run finishes, the result shows on the screen with its file name. Click Open the file to preview it, Run another template to go back to the picker, or Back to case. On a phone, the picker is the first step: pick the template, click Continue, then check the files and run.

The preview's More actions menu holds Extract, which becomes Re-extract if the file was already extracted with the template that matches it, Share, and New template from this file... for a fillable file.

A document row in the Documents list holds Run a template on this file... in its menu, which opens the run screen above with that file picked. If a file is fillable, the row also expands to "New template from this file...".

Templates that build a deliverable from saved case values alone also sit in the list under Generate from template. This group also holds templates missing a source document. Click a row or its chevron to open its form. It asks the template's questions and lists the template's from case data rows: leave one blank and the run picks the value from the case, or type a value to use it for this run only. When a required question is empty, or the case lacks a value the source document would supply, Generate opens the form first. Type the missing values, or upload the source document to extract them, then click Generate again. The button stays off while a required question is empty. Click Answer with chat to let the AI assistant answer questions. Click Add AI instructions to guide the run. A document value you leave blank is not saved, so the document can still supply it later.

The answers you changed are saved on the case before the run starts. Nothing is saved when nothing changed.

Forms sit under Fill a form. A form is a template with questions and no document. Click a row to open its questions, prefilled from the case. Click Fill to save the answers you changed onto the case. No document is produced. Filling also derives the form's own AI instruction values: the ones your answers completed, and the ones that read an answer you changed. They follow the form's AI instructions. Values that other templates derive from those answers refresh the next time those templates run. Anyone who can edit the case can fill a form.

On the read-only dashboard of the Free and Lite plans, Generate, Extract and Fill open the upgrade prompt instead of saving or running.

The Documents list shows active runs. You see Working with a spinner and "Generating..." or "Extracting...". Failed runs show a danger message with a retry option and error details.

You can run a template directly from the editor. Click the toolbar Run button and the same run screen covers the editor, this time with the case list beside it: the template is fixed and the list picks the case. Pick where the document comes from at the top right: From a case, Upload a file or Sample document. The caret next to Run jumps straight to one of the three, or to the last file you ran on.

From a case lists the cases that hold a file this template reads; click the chip above the list to see every case. Pick a case, pick the file, and click Run. The result saves on that case, like a run from the Documents list. Each document row also takes a file of your own with Upload a file for this row; it lands on the case when the run starts. A row the template fills can go without a file, and the run uses the template's blank page; a row the template reads cannot, so the drop zone opens by itself when the case has nothing to read. Upload a file runs on a file you drop in. By default the filled document just downloads and nothing is saved; pick a case in the list instead and the file lands on it, tagged with the template's document category, with the result beside it. When a download-only run reads the template's ID field, the result screen offers to save on the case that holds that ID, or to create a case with it, and runs there with your file. Sample document runs on the pages the template was built from, with the answers from the Data tab's Form card.

Every completed sample run lands on the Data tab. The tab shows two cards. The Values card lists every value the template captures, filled from the last run, with an AI badge on values the AI derived and the instruction that run used. The Form card holds the questions the sample run uses. Click View output to view the result. Word documents download instead of opening inline. The tab shows a freshness chip. Its chevron opens the template-level AI instructions. The Run button's caret menu holds AI instructions for this run, a separate override.

On a form, Run this form saves nothing and produces no file. It fills the Values card with your answers and any values computed from them, so you can try the form before anyone fills it on a case. A form has no documents, so its run screen has no modes, and its caret menu keeps only the run instructions.

On Pro and Scale plans, a sample run creates no case; a run from a case or an upload saves on that case. On Free and Lite plans, a sample or upload run saves as a temporary case for 14 days, a strip under the document bar links to it, and From a case opens the upgrade prompt. The Sample document pane also shows a locked Fill from your last run row for Free and Lite users.

The freshness chip reads Not run yet or Ran N ago · stale. An unanswered required question disables the sample run and names the question, for example "Fill 1 required field to run: Bid Amount", in the run screen and as a line under the Data heading. Only questions the run form asks count, so a question on the identifier field or inside a Batch table never blocks a run, and the Form card marks Required on exactly the questions that do. The run screen asks every question on the template, including one on the same field as an Extracted input, plus the From case data rows, which start blank. A template that reads several documents gets one section per document; a row you leave without a file runs on that document's stored copy. The editor canvas never replaces the preview. If you have unsaved edits, a prompt asks to Save & run or Use saved version before the run screen opens.

AI instructions for this run, in the Run button's caret menu and under Instructions for this run on the run screen, applies special instructions to the next run. Use the stale strip's Re-run with the same inputs to try again. Extracted values carry an Extracted tag and manual edits show User input. A re-extract overwrites AI values but leaves user input alone.

A Batch field holds a variable number of rows. Batch Autofill is the operation that runs it.

Select multiple cases in the dashboard. Pick a batch template in the batch action bar. Click Autofill. The app runs the template across the selected cases. It fills one row per case into a single combined file, and rows no selected case fills stay empty. The app saves this file to every selected case.

A batch run can open a source selection step first. You can override the cover file and pick appended case files. Batch autofill is included on Pro and Scale and unavailable on Free and Lite.

A field gets its value from a Value source. The options are Form field, Extracted, Static, From case, and From the delivery.

Inputs land on the case as case-data rows. Values set to From case resolve per run and are never saved.

Extraction never overwrites a value you edit by hand, and a value you remove by hand stays empty the same way. A read that finds nothing for a value keeps the value the case already holds. Values typed into a Form field persist on the case. They prefill the next time you run the template.

Fillable forms prefill boxes that match information the workspace already collects. These rows carry a From case data tag. On the run screen they start blank, and what you type there applies to that run only. In the Documents list forms they start blank: a blank row lets the run pick the value, and a typed value applies to that run only. Nothing you enter in these rows is saved.

An AI instruction output keeps its value on the case. When a value it reads changes, the next run of its template derives it again. That holds whether the change came from case details, the chat, a bulk edit, the portal or a run form, and it includes a removed value and a changed list. A value a person typed into the output itself is never replaced. An output that reads a From case value is derived on every run, because that value is picked fresh each time. An output whose derivation comes back empty is tried again on the next run.

A write zone prints the value of the input or output it belongs to. A zone under an output stays empty until that output has a value, and never prints the input's value instead. An empty value still leaves its box in the generated PDF. The boxes the app creates have no border or fill, so an empty one stays invisible until someone types in it. A field that fills a box the source PDF already has leaves that box as the source has it when the value is empty: printed text stays and a ticked box stays ticked. When two created boxes would share a name, the next one takes the name with _2, then _3, and a period in a name becomes an underscore.

Empty fields. Check the input source. For an Extracted input, confirm the write zone points at the input or transform that produces the value. A field with no value leaves an empty box. A zone under an output stays empty until that output has a value.

Shifted placements. Placement is exact by default. Content can shift between fills. Click the template's name in the editor toolbar to open template settings, and enable Document reflows in Fill. The app uses AI to find the anchor. If the anchor is missing, the value stamps at its authored position, and the app reports the fields it left there: a Check field placement warning that names them after a run from the case, a note in the chat, and a strip on the Data tab that counts them after a test run.

Missing pages. Pages require a source tab reference. Open the active tab's chevron popover. On mobile, open the settings drawer from the active row. Check the "Include pages from source" text field. Leave it empty to include all pages, or type a range like 1-3, 5.

Wrong template order. Templates order by how well they match the file. Open the template and check the document bar source tabs to see what it requires.

• Output naming
• Batch templates
• Build a template