> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useunderflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bind and policy paper

> Turn an accepted quote into coverage, a binder, and an invoice.

Binding starts when the agency accepts one quote option. Underflow withdraws the sibling options, checks the bind conditions, and prepares the selected terms for execution.

## Before bind

Blocking subjectivities must be satisfied before coverage can bind. Each subjectivity shows its status on the file and can point to the document that satisfied it. Each state form the placement state wants signed is its own subjectivity under the state's code for the form; it cannot be waived and is marked Received only with its own signed copy, so one upload never stands in for another form. Nonblocking subjectivities remain visible after bind until they are closed.

A quote is an offer on the application as it stood when the quote was cut. If any answer changes afterwards, whether a correction from the broker or a scan that found something new, the quote is stale: the letter is not sent and the bind is refused until the underwriter withdraws it and quotes again from the current answers.

The selected program supplies the carrier, capacity, forms schedule, cancellation method, and state-specific requirements. Surplus-lines business requires a home state with verified state figures. Before bind, Underflow screens the insured's names; a possible sanctions match or an incomplete sanctions lookup holds the bind for review. When the bind executes, it locks the quote, freezes the application, and takes the desk's ledger lock, then checks binding authority against the book as it will stand when the bind commits, so two binds at a program's capacity run in turn and the second is refused rather than both slipping past the cap. On an approved bind those results are compared with what was approved: a bind whose premium, authority, sanctions result, or home state has moved since approval does not run; it has to be proposed again.

> [!WARNING]
>
> Underflow resolves carrier forms from the program schedule. It does not invent policy forms.

## Bind

The bind action creates:

* The policy record and policy number
* The selected coverage terms and premium
* The premium transaction and invoice
* The resolved forms schedule
* The state-filing obligation on eligible surplus-lines business with a home state

The file moves to Bound and the application is frozen as the record that was underwritten. After the bind commits, Underflow generates the binder and attaches it to the policy. Aurora can then propose the bound notice with the binder attached.

> [!NOTE]
>
> The policy stays Bound even if binder rendering fails. If the policy row has no binder link after bind, contact
> Underflow rather than binding the quote again.

## Issuance

The current workbench does not expose an operator action to move a Bound policy to Issued. Underflow has an issuance service that changes the status and renders a declarations page, but no production workflow invokes it today. The resolved forms schedule is stored on the Bound policy; it is not assembled into a final carrier-form package in the workbench.

## What follows

> **[Service the policy](https://docs.useunderflow.com/policy-servicing/overview.md)**
>
> Handle renewals, endorsements, cancellations, certificates, and claims.

> **[Track the invoice](https://docs.useunderflow.com/accounting/invoices.md)**
>
> Follow delivery, aging, payment, and reconciliation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.