Policy forms

Every form, filled from the record.

Quote letters, declarations, binders and invoices, assembled from your own templates against the account they belong to. One package, in the order you set, on the edition you published.

Book a demo Read the docs

Form Template

LabelForm IDSource

Form Version

VersionEditionStatus

Template Mapping

DataviewsRequiredTransform

Dataview

LabelColumns

Pipeline Document

OrderDoc Type

Pipeline

LabelDescriptionRoot Object

Property QuoteSystem

PremiumEffective DateExpiration Date+16 more attributes

Document Generation

Subject RecordMerged FileIs Test

Programs & ProductsCommercial Property PolicyAsk Riska

Commercial Property Policy

Commercial property insurance product with building and business personal property exposures

Run test

AttributesLifecycleBillingDoc GenerationFlows

Search…Mapping

Quote Package

Documents released at quote time — quote letter + declarations preview.

Quote LetterCover letter accompanying a quote — summary of premium, term, named insured.Published

Declarations PageDeclarations page rendering lines/exposures/coverages as a tabular loop.Published

InvoicePremium invoice with billing terms, due date, and remittance instructions.Published

Subject

Every dataview attached to this package is scoped to one record at run time — the object the package is rooted on, and the row you point it at.

Root objectProperty Quote

RecordCP-2026-0166

Dataviews

Each dataview attached to Invoice runs with the subject bound. All returned rows are exposed under the dataview's label, and the template's tags resolve against them.

Invoice — BillingLabel · Premium · Effective Date

Invoice — IdentifierExternal ID · Created At

Form Template

LabelForm IDSource

Form Version

VersionEditionStatus

Template Mapping

DataviewsRequiredTransform

Dataview

LabelColumns

Pipeline Document

OrderDoc Type

Pipeline

LabelDescriptionRoot Object

Property QuoteSystem

PremiumEffective DateExpiration Date+16 more attributes

Document Generation

Subject RecordMerged FileIs Test

Programs & ProductsCommercial Property PolicyAsk Riska

Commercial Property Policy

Commercial property insurance product with building and business personal property exposures

Run test

AttributesLifecycleBillingDoc GenerationFlows

Search…Mapping

Issuance Package

Documents released at policy issuance — declarations, binder, invoice.

Quote LetterCover letter accompanying a quote — summary of premium, term, named insured.Published

Declarations PageDeclarations page rendering lines/exposures/coverages as a tabular loop.Published

BinderTemporary evidence of coverage issued at bind.Published

InvoicePremium invoice with billing terms, due date, and remittance instructions.Published

Subject

Every dataview attached to this package is scoped to one record at run time — the object the package is rooted on, and the row you point it at.

Root objectProperty Quote

RecordCP-2026-0166

Dataviews

Each dataview attached to Binder runs with the subject bound. All returned rows are exposed under the dataview's label, and the template's tags resolve against them.

Binder — Coverage WindowLabel · Effective Date · Expiration Date

From the Word file you already use. Four steps to turn a document you retype every week into one the system produces.

[01]

Bring the document.

Upload the .docx with a form ID and an edition. ISO wordings and the letters you wrote sit in one library.

[02]

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.

[03]

Ask Riska

Which property renewals are out of appetite?

Working

record_search640ms

task_search210ms

render_gui95ms

Three of the fourteen renewals score into the referral band. Sable Ridge Energy is the largest at $2,110,000, and catastrophe exposure is what pulls its score down.

Sable Ridge EnergyHalstead MarineWinnow Grocers

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.

[04]

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 leadProgram 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.

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 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.