Issuing a Policy

After a bind is approved, the policy exists but isn’t yet complete. Issuance is the process of assembling the policy packet — all the forms, endorsements, and declarations — and getting it delivered.

Policy detail page

Navigate to the bound policy from the submission detail (click the policy number link) or find it on the Policies page. The Policy Detail page is organized into tabs:

Tab	Contents
Insured	Name, address, contact, entity type
Coverages	Line-by-line limits, deductibles, modifiers
Rate Result	Final premium calculation with full audit trail
Drivers	Driver list, records, usage (commercial auto)
Operations	Fleet size, territory, operating authority
Equipment	Scheduled equipment (specialty lines)
Billing	Premium breakdown, payment terms
Filings	State filing status
Requirements	Compliance checklist
History	Complete activity timeline
Packet	Document assembly and delivery

Policy Packet Builder

The Packet tab contains the Policy Packet Builder — a multi-step workflow for assembling and delivering the policy documents.

Step 1: Select Forms

The builder loads the form catalog for the policy’s line of business and pre-selects all active forms. You can:

• Search forms by code, title, or category
• Filter by category (declarations, coverage form, endorsement, schedule, notice, etc.)
• Select/deselect individual forms using the checkboxes
• Use Select All or Clear to manage bulk selections

Each form shows its form code, title, category badge, bureau (if not proprietary), edition date, and page count.

Tip

The Forms Library includes uploaded blank PDFs and forms generated by the doc factory at bind time. Generated-at-bind forms can be previewed with sample policy data, but they do not have a stored blank PDF to download because the final PDF depends on the policy state, selected drivers, additional interests, or other bind-time data.

When ready, click Assemble Packet to build the manifest.

Step 2: Review & Finalize

After assembly, the manifest table shows every form in the packet:

• Form Code — The filing identifier
• Title — Human-readable form name
• Category — Color-coded badge (policy jacket, declarations, coverage form, conditions, endorsement, schedule, notice, application)
• Type — Mandatory or Optional

Review the manifest to confirm all required forms are present.

• If the packet is in draft status, click Finalize Packet to lock it
• If you need to adjust forms, click Back to form selection to return to Step 1

Caution

Finalization locks the packet version. If changes are needed after finalization, you’ll need to issue an endorsement.

Step 3: Send Packet

Once finalized, click Send via Email to open the delivery form:

1. Enter the To address(es) — comma-separated (producer, agent)
2. Optionally add CC recipients (insured, operations)
3. Add an optional personal message
4. Review the email preview showing subject line, recipients, and included content
5. Click Send Packet Email

The email includes the policy details, form count, and a secure PDF download link.

Step 4: Delivered

After sending, a confirmation screen shows:

• Delivery recipients
• Message ID
• Email subject

From here you can Send to Another Recipient or go Back to Packet to review.

Common issues

No forms in catalog

• Verify that forms have been loaded for the policy’s line of business and state
• Check the Form Library or API to confirm form availability
• If the missing item is a generated-at-bind form, confirm the triggering data exists on the policy and that the generated form appears in the Form Library preview list

Missing mandatory forms

• The manifest marks forms as Mandatory or Optional — ensure all mandatory forms are present before finalizing
• Contact operations if a required form hasn’t been filed yet

Post-issuance changes

If the insured needs changes after the policy is issued:

• Minor changes: Issue an endorsement from the policy detail page
• Major changes: May require cancellation and re-issuance depending on the nature of the change

Out-of-sequence endorsements

If the endorsement’s effective date is earlier than the most recent processed endorsement, the system flags it as out-of-sequence. OpenInsure handles this automatically:

1. The timeline engine re-derives all premium segments from the insertion point forward
2. Downstream endorsement premiums are recalculated (cascade)
3. The endorsement detail shows past-period and future-period premium adjustments separately
4. A warning badge appears in the workbench so the underwriter can review the ordering

Tip

If a pending endorsement with an earlier effective date exists, the system requires it to be issued first to prevent cascade conflicts.

Lifecycle complete

Once the packet is finalized and delivered:

Received → Incomplete → Rated → Quoted → Bound → Issued

The policy is now active. From here, the lifecycle continues with renewals, endorsements, and claims — but those are separate workflows.

Back to: Quote to Policy overview