Universal Form Data Model

One canonical schema underlying every Insurance Blueprint form. All form types share a single data model, so one integration handles every line of business.

Insurance Blueprint Universal Form Data Model

A single, unified schema that captures the data underlying all Insurance Blueprint forms — from Personal Auto Proof of Insurance to Commercial Certificate of Insurance and every form to follow.

Top-Level Fields

Field Type Notes
form_id string IBP form identifier
form_type enum POI, COI, GL_APP, HO_APP…
schema_version string SemVer (e.g. 1.0.0)
effective_date date Policy start date
expiration_date date Policy end date
issuer PartyModel Carrier or insurer
named_insured InsuredEntity Primary insured party
additional_insureds AdditionalInsured[] Optional; used on COI
certificate_holder PartyModel Optional; COI only
policy_number string Carrier policy number
coverages Coverage[] One or more coverages
vehicles Vehicle[] Auto form types only
locations Location[] Property form types
endorsements string[] IBP endorsement codes
signature SignatureModel Optional e-signature block

Coverage

coverage_type: enum // BI, PD, COMP, COLL, GL, BI_PD…
limit_per_occurrence: decimal
limit_aggregate: decimal?
deductible: decimal?
premium: decimal?

InsuredEntity

name: string
entity_type: enum // INDIVIDUAL, BUSINESS
address: AddressModel
dob: date? // individuals only
fein: string? // businesses only

Vehicle (auto forms)

year: integer
make: string
model: string
vin: string
garaging_address: AddressModel

PartyModel

name: string
address: AddressModel
naic_code: string? // carriers
contact_email: string?
contact_phone: string?
IBP-DM-001 — Universal Form Data Model
v1.0.0 • JSON Schema, XML Schema • Full field documentation included
JSON Schema (Member) XML Schema (Member) Full Docs (Member)

Why one model for all forms

One Integration

Integrate once and handle every form type. Adding a new line of business to your system means adding a new form_type value, not a new schema.

Sparse by Design

Fields not applicable to a form type are simply absent or null. A Proof of Insurance card omits locations. A COI omits vehicles. No artificial field inflation.

Versioned Uniformly

All forms draw from the same versioned schema. A MAJOR bump affects every form type at once, keeping your integrations predictable and synchronized.

Human-Readable

Every field ships with plain-English documentation, optionality rules, and form-type applicability notes. Developers and underwriters can read the same spec.

Semantic versioning with migration guides

The Universal Form Data Model uses semantic versioning (MAJOR.MINOR.PATCH). Breaking changes increment the major version and ship with a migration guide.

MAJOR
Breaking changes.
Migration guide required.
MINOR
New fields added.
Backward compatible.
PATCH
Doc fixes only.
No schema change.
Current version: 1.0.0 • Released 2026-08-21