> ## Documentation Index > Fetch the complete documentation index at: https://docs.go.aiinsurance.io/llms.txt > Use this file to discover all available pages before exploring further. # Binding a quote > Turn an accepted quote into a policy — where Bind lives, what the bind flow asks for, and what you get once the policy is issued. Binding is the moment a [quote](/entities/quote) becomes a [policy](/entities/policy): the quoted terms stop being a proposal and start being coverage on your book. In the app, binding is a short, dedicated flow — three steps that collect the last policy-only details (like the policy number), assemble the policy's documents, and confirm. This page follows a **new-business** quote, but the same flow — and the same **Bind Quote** entry on a completed quote's page — also binds **endorsement** and **renewal** quotes. Those servicing quotes start from the policy's page — see [Servicing a policy](/app/workflows/servicing-policies). ## Before you bind A quote is bindable when all of these are true: * **It's a new-business, endorsement, or renewal quote.** All three bind through this same flow. Cancellations and reinstatements never bind separately — their own short flows confirm directly — see [Servicing a policy](/app/workflows/servicing-policies). * **It's complete.** The Bind action appears once the quote's status is **Quote Complete** — or you can jump straight from the quote wizard's last step without the intermediate stop (see below). * **It isn't already bound.** A **Bound to Policy** quote offers **Go to Policy** instead. * **Its required fields have values.** The bind flow won't finish while required fields are missing — a **View Missing Fields** button lists exactly which ones so you can fill them in. Bind actions also follow your permissions: if your role can't update quotes and create policies, the entry points simply don't appear. ## Where the Bind action lives | From | How | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A completed quote's detail page | The standout **Bind Quote** button at the top right — also available as **Bind Quote** in the **Actions** menu. Offered on completed new-business, endorsement, and renewal quotes alike. | | The new-business quote wizard's last step | The finishing split button: pick **Bind Quote** instead of **Complete Quote** to save and enter the bind flow directly. (Endorsement and renewal wizards end with a plain **Complete Quote** — bind those from the completed quote's page.) | A quote detail page showing the quote number with a Quote Complete status tag, an Actions dropdown containing Bind Quote, Copy Quote, Cancel Quote, and Delete Quote, and a prominent purple Bind Quote button at the top right. Entering the bind flow is **not a commitment**. The quote's status doesn't change when you start binding — if you exit the flow without finishing, the quote stays exactly as it was, still ready to send or bind later. Only a completed bind advances it to **Bound to Policy**. ## The bind flow The bind flow is a small wizard with the same controls as the [quote wizard](/app/workflows/quoting#finding-your-way-around-the-wizard) — steps in the sidebar, **Exit** / **Save Quote** / **Back** / **Next** at the top right — and three steps: The details that only exist once you're issuing a policy. Out of the box the headline field is the **Policy Number**, which is required to bind. Depending on how your company is configured, you either type it here or it's generated for you and shown read-only. The **Policy Start Date** and **Policy End Date** you set while quoting are displayed for reference — the policy term is the term the quote was priced for. The bind flow's Policy Details step showing a required Policy Number text field and read-only Policy Start Date and Policy End Date values, with Exit, Save Quote, and Next buttons at the top right. The exact cards on this step come from your company's configuration — see [How your app is configured](/app/getting-started/configuration). Assemble the policy's document set — declarations pages, policy jackets, binders — from your company's **policy** form templates. The step works exactly like the quote wizard's [Forms step](/app/workflows/quoting): pick templates from the searchable list, and each form is generated with its values filled from the quote's data; edit, preview, refresh, remove, or download them individually or as a combined packet. The bind flow's Policy Forms step with a searchable policy form template picker on the left and the selected policy forms on the right, each row offering Edit, Preview, Download, Refresh Smart Tags, and Remove. A final read-through of the policy-to-be. If required fields are still missing, **Bind Policy** is disabled and **View Missing Fields** lists them. When everything's in place, select **Bind Policy**. The bind flow's Review and Confirm step showing the quote's data in read-only cards with a Bind Policy button at the top right. ## What happens when you bind Selecting **Bind Policy** does three things at once: 1. **The policy is created.** The quote's terms — insured, exposures, coverages, dates, premium — become the policy's initial state, covering the full term. This is the policy's first recorded transaction; every later change (endorsement, cancellation, and so on) is recorded on top of it. See [the Policy entity](/entities/policy) for the underlying model. 2. **The quote's status becomes "Bound to Policy"** and the quote is linked to the new policy — it stays on file as the record of what was bound. 3. **You land on the new policy's detail page**, ready to service it. That's the new-business outcome. Binding a **renewal** quote likewise creates a new policy — the next term, linked to the one it renews — while binding an **endorsement** records the change on the existing policy instead of creating one. See [Servicing a policy](/app/workflows/servicing-policies) for what each servicing bind does. A policy detail page immediately after binding, showing the policy number as the page title, an Actions menu, the Overview tab with a policy term timeline bar, a 'Version 1 · 1 segment' caption, and the policy's field cards. If the bind fails — a validation problem, a missing policy number — the error is shown and nothing is created: the quote stays unbound and you can fix the issue and try again. ## What a policy is once bound A bound policy is a different kind of record from a quote: * **It lives on the [Policies list](/app/features/policies)** with its own detail page — Overview, Activity, Quotes, Events, and Exposures tabs. * **It's history-keeping.** A policy is a ledger of dated transactions, not a single editable form. You never edit a policy's fields directly — you record changes (endorse, cancel, reinstate, renew), each effective on a date, and the app derives what the policy looked like on any day of its term. That's what powers the **View as of** date controls and the endorsement history. * **The bound quote stays attached.** The policy's **Quotes** tab lists it, and the quote's page offers **Go to Policy**. * **Billing can begin.** Written premium, invoices, and payments pick up from here — see [Billing & getting paid](/app/workflows/billing). Bound the wrong thing? A policy that shouldn't exist can be deleted from its **Actions** menu (which also removes the bound quote), and a mistaken recent change can be undone from the policy's **Activity** tab — see [Servicing a policy](/app/workflows/servicing-policies#the-activity-tab). ## Next: service it Mid-term changes, renewals, cancellations, and reinstatements all happen from the policy's page — continue to [Servicing a policy](/app/workflows/servicing-policies).