# Document Generation (https://riska.io/platform/policy-forms)

_Document Generation_

## Every form, filled from the record.

Quote letters, declarations, binders and invoices, assembled from your own templates in seconds. One package, in the order you set, on the edition you published, with nobody retyping the quote into Word.

## The paperwork, off the underwriter’s desk.

Upload a template, tag it against your data model, and the documents you owe go out filled from the record they describe. Binders, policy forms, quotes and notices come off the same Data Mesh that captured the submission.

### Tag it once.

Upload your own template and mark the places your data belongs, editing it in the browser. An agent reads the document first and proposes where each token and each repeating section should go, and why. You accept the suggestions you want.

### Any attribute on your model.

A token can pull any attribute you have, followed across relationships, and a loop expands a list row by row. The mapping is resolved and validated against the template before a run ever reaches a customer.

### Generated where the work is.

Pick the record, and the templates that apply to it are the ones you are offered. The finished document is filed against that record and audited like everything else, or produced by a workflow at the moment the policy binds.

## From the Word file you already use.

Four steps to turn a document you retype every week into one the system produces, and give those hours back to underwriting.

- **Bring the document.**: Upload the .docx with a form ID and an edition. ISO wordings and the letters you wrote sit in one library.
- **Tag it where it needs data.**: Open the real document in the app and click a field to drop it at the cursor. No conversion, no separate template language.
- **Or auto-tag it.**: The document is read end to end and each placement comes back with a reason and a confidence. Nothing is written until you accept it.
- **Publish and lock.**: A published edition is immutable. Later changes fork a new draft, so the form a policy was issued on never moves.

> "“We were rebuilding the same quote letter in Word for every account. Now it comes out of the system with the right edition on it.”" — Policy services lead, Program manager · four states

## Packages, not one-off documents.

A package is an ordered list of templates. Each one carries a document type, and a form joins the package only when the risk calls for it.

### Quote package.

The quote letter and a declarations preview. Drag to reorder, and the merged file follows the same order.

### Issuance package.

Declarations, binder and invoice, rendered in parallel, merged into one file and turned into a PDF preview as soon as it lands.

### Endorsement package.

The endorsement wording, a revised declarations page and the premium change, built from the same library rather than a second one.

## Nothing goes out on an unknown form.

Every document records the configuration and the edition that produced it.

- **Editions are immutable**: Publishing locks a version. A form that has been issued is never edited underneath you.
- **Every run is on the record**: Who started it, when, how long it took, and which file each template produced.
- **Forms ride the release**: Templates, mappings and packages are versioned with the rest of the product and cut together.

## The data comes from the record.

There is no merge file to export and no spreadsheet to keep in step. A package is bound to one record and reads from there.

### Bind the subject.

Every package is rooted on an object. Pick the policy, the account or the endorsement, and every template in the package reads from that one record.

### Pull the fields.

Each template declares the views of the record it needs. A single row reads as one value in the letter, and a schedule of locations reads as rows a table repeats over.

### Check the output.

Before anything renders, every slot the document expects is marked matched, missing or the wrong shape, with an expected row shown for a repeating section the data left empty.

## The paper is the last step.

One configuration, one record graph, one release. Everything the document says was decided somewhere else in the platform.

## Bring the form you retype every week.

Send a quote letter or a declarations page you rebuild by hand. We will tag it live and generate it against a real policy.