Templates

A template is the blueprint for a document — it defines fields, where they get their values, where they land on the page, and how the output file is named. Each template takes part in up to three operations: Extract, Fill, and Generate.

AI field extraction reads each ingested file and pulls structured data into the fields you defined on a template. The AI is bounded by your field schema, so extraction stays predictable.

You can guide the AI from four different places — an individual output, the template (incl. assembled-PDF guidance), a single source row, or a one-off run. Output rules win over everything else for that specific output; the rest are additive context, in order of specificity.

A template defines what a generated document looks like and where data goes on it. Create one from the Templates panel inside any workspace.

Add a field from the Fields panel of any template. Each field needs a name, a type, a source, and (usually) a placement on the canvas.

Pick a field type that matches how the value should be captured and rendered. Text is the default; number, currency, date, select, checkbox, batch, signature, address, and image are also available.

Each field has a source — question (user fills via form), extracted (AI pulls from a document or context), or static (fixed value). The field also has one or more outputs that produce the actual case-data values. Output kinds (input, static, zone, prompt, computed, binding) determine exactly how each value is produced.

Field placement is exact and deterministic. You set position, size, and page on the canvas, and autofill writes to the same spot every run.

A prefill policy controls what autofill does for a field. The three options are always_prefill, prefill_if_value, and leave_blank_for_client.

Templates can define an output filename pattern so generated files follow a consistent naming rule. Built-in tokens are {template}, {id}, {date}, {timestamp}; reference any template field by its stable id (e.g. {vendor_name}).

Source tabs assemble a template's output from ordered workspace document sources and blank pages. Each tab appears in the document bar directly above the preview canvas; the +Add menu adds more. Sources are workspace-owned, not nested inside templates — every template (and every automation) in the workspace points at the same set.