Extract policies and endorsements to structured JSON
Insurance policies contain the full terms of coverage: insuring agreements, conditions, exclusions, and endorsement modifications. These documents run dozens to hundreds of pages. Sensible extracts policy data into validated JSON for administration, compliance review, and coverage analysis.
Why insurance policies challenge extraction tools
Long-form legal text, nested coverage structures, and modifying endorsements make policies deeply complex.
Policies contain declarations, agreements, conditions, and exclusions. Sensible identifies each section and extracts its data.
Endorsements modify, add, or restrict base coverage. Sensible extracts each form number, effective date, and terms changed.
Occurrence vs. claims-made, named perils vs. open perils. Sensible identifies the form type and extracts the relevant terms.
Fields we extract
Extract any data you need from policies and endorsements into your desired output schema
Named insured, policy number, effective/expiration dates, policy form, territory, classification, premium basis
Insuring agreement type, per-occurrence limit, aggregate limit, deductible/SIR, sublimits, coverage triggers, retroactive date
Endorsement form number, effective date, description, premium impact, additional insured provisions, waiver of subrogation
Additional insured endorsement naming a specific certificate holder.
Full CGL policy document with coverage forms, conditions, and exclusions.
Commercial property policy covering buildings, contents, and business income.
Mid-term policy change adding, removing, or modifying coverage.
Supported policy types
Sensible processes insurance policies across all major lines and coverage forms. No template needed. Any new policy format can be configured to your output schema in hours.
CGL, commercial property, workers comp, commercial auto, umbrella/excess, professional liability, cyber, D&O, EPL
Homeowners, personal auto, renters, umbrella, flood, earthquake
Common Questions
Specific details about our policy extraction engine.
Yes. Sensible extracts endorsement form numbers, effective dates, description of changes, and premium adjustments as separate items linked to the base policy.
Sensible extracts renewal terms, premium changes, and coverage modifications. You can compare renewal data against the prior term programmatically.
Sensible processes policies with multiple coverage forms, conditions, and exclusions. Each section is identified and extracted with its specific fields and terms.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.