Captive Insurance
An insurer owned by the businesses it covers, the forms it takes, and what separates a captive from simply retaining the risk.
The three steps that turn an enquiry into a live policy, where cover actually attaches, and what a referral does to the sequence.
Quote-bind-issue, often shortened to QBI, is the process of turning an insurance application into an agreed insurance contract and its formal policy documents. It connects pricing, acceptance of coverage, and policy issuance.
The three stages may happen within one online journey or involve separate work by a broker, underwriter, and policy administration team. Each stage answers a different question: what coverage is being offered, whether the parties have committed to it, and whether the documents have been issued.
| Stage | Main purpose | Typical result |
|---|---|---|
| Quote | Calculate and present proposed coverage and price | An offer or estimate with terms and conditions |
| Bind | Commit to the agreed insurance contract through an authorized party | Confirmation of the agreed coverage and its effective date |
| Issue | Produce and deliver the formal policy documents | The policy schedule or declarations, wording, and applicable endorsements |
Binding and issuing are distinct actions even when a system completes them together. Guidewire describes binding as making the agreed policy legally binding, while issuance produces and sends the documents defining the policy. Guidewire’s explanation of binding and issuing.
This distinction helps explain why a quoted application, a bound policy awaiting documents, and an issued policy need different statuses.
A quote starts with information about the applicant and the risk. The required details depend on the product. A commercial property application might need the building’s location, construction, use, insured values, and requested deductible. An auto application uses a different set of information.
The insurer checks eligibility, applies rating rules, and presents the available coverage and premium. An insurance rating engine can perform the calculations, while underwriting rules determine whether the risk can proceed automatically or needs review.
A useful quote makes the proposed arrangement clear:
An indicative price may still require further information before a firm offer is available. A quote should not be treated as confirmation that coverage has already been bound. Guidewire’s business glossary similarly distinguishes a premium quotation from the later binding of a policy. Guidewire’s insurance business terms.
If the applicant changes a material detail, such as the insured value or business activity, the quote may need recalculation and another underwriting check.
Binding records the commitment to the agreed coverage. The person or organization binding it must have the necessary authority. A producer’s involvement in a sale does not by itself establish that they can bind every risk on the insurer’s behalf.
Before binding, the workflow resolves the requirements relevant to that transaction. These may include customer acceptance, underwriting approval, signed information, and any required payment arrangements. The exact conditions depend on the product and insurer.
The effective date and time are particularly significant. A policy can be bound today with coverage scheduled to begin on a future date. The date someone clicks “bind” is therefore not automatically the date coverage starts.
A binder provides temporary evidence of coverage before the formal policy is issued. Washington’s insurance regulator describes a binder as proof of coverage for a specified period pending issuance or a required premium payment. Its form and duration depend on the applicable arrangements. Washington Office of the Insurance Commissioner’s glossary.
The binder should communicate the agreed coverage accurately. Issuing a price illustration or sending an application for review is a different action.
Issuance turns the agreed policy information into the formal document set and completes the related administration. This can include producing the declarations or schedule, attaching the correct wording and endorsements, delivering the documents, and updating policy and billing records. Guidewire’s definition of policy issuance.
An endorsement changes or adds to policy terms. That makes correct document selection important: the policy package needs to reflect the terms actually agreed at binding.
Document production can fail after binding succeeds. For example, the customer might have an agreed contract while a document service is unavailable. The remaining task is then to complete and verify issuance. Repeating the purchase as a new sale could create a duplicate transaction.
Consider a fictional business buying property insurance for new premises.
In this example, quoting, binding, issuing, and the start of coverage have different dates. A record that stores only “policy created” would leave several of those events unclear.
Some applications can move through QBI automatically. Others need an underwriter or another authorized reviewer to resolve an exception.
A referral means the application requires that review. It does not necessarily mean the risk has been declined. The pending item might concern an unusual activity, requested limit, missing information, or a price outside an automated authority range.
Requirements can also differ by stage. Guidewire’s product configuration distinguishes information required for quoting, binding, and issuing. This supports collecting data when it becomes necessary while retaining the appropriate checks before each action. Guidewire’s stage-specific data requirements.
For example, an application might have enough information for a preliminary quote but still need a document before binding. The system should show that requirement and who needs to resolve it.
A policy administration system can maintain the policy record as it moves through the process. It connects the application to pricing, approvals, documents, and subsequent policy changes.
Useful records include the accepted quote version, the binding confirmation, the effective date, and the issued document set. Together, they allow a team to trace which terms were accepted and what the customer received.
Operational measures can then identify specific delays: time to first quote, time awaiting underwriting review, quote-to-bind conversion, and time from binding to successful document delivery. Keeping these stages separate makes it easier to see whether a delay comes from pricing, a decision, or policy production.

An insurer owned by the businesses it covers, the forms it takes, and what separates a captive from simply retaining the risk.

What a case reserve represents, how the first estimate is set, and why it moves every time new information reaches the file.

The money paid out above what the claim should have cost, why it is measured by file review, and what separates it from fraud.
Book a live, personalized demo with our product team - tell us your use case and see the platform work with your data. No commitment.