Start Here

A template is the blueprint for a document: it declares fields, where each one gets its value, and where that value lands on the page. Click + New template, add fields, place them, save, then run autofill to get a finished PDF.

Three things turn a plain template into a smart one: AI instructions that steer extraction, source tabs that assemble several sources into one output, and batch fields that reference data from across many cases.

A case is the durable record for one unit of work, holding its files, extracted data, history, and generated outputs; each template field writes its value under a stable key, so renaming a field or column later never disturbs the data already saved.

A workspace is the container holding your cases, dashboard, and config; the dashboard is the view onto the active workspace, where a table of every case becomes maps, calendars, and analytics driven by your fields.

Almost everything in Document Blueprint comes down to a few core concepts: workspaces group the work, templates shape documents, cases are the durable records, and fields define what gets extracted or written. You change all of it in the UI, never in code.

Document Blueprint handles the repetitive document work a team does over and over: it reads incoming files, pulls the values you name, and fills the paperwork those values feed. Templates hold the rules, case records hold the work, and the AI reads the files.