Trusted by teams turning documents into production data
Insurance
Declaration pages summarize who is covered, what is covered, for how much, and for how long. Every carrier formats them differently, with unique layouts and field structures. Use Sensible to get structured dec page data for policy management, renewals, and coverage verification.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data
No two carriers build a dec page the same way, and coverage schedules and endorsement riders shift with every policy. Hybrid extraction reads each carrier's layout; schema enforcement makes the JSON identical no matter who issued it.
01
Travelers, Hartford, Chubb: each produces dec pages with unique field placement, terminology, and page structure. The hybrid engine reads each layout with LLM flexibility, then validates against your target schema with deterministic rules.
02
Coverage tables list limits, deductibles, and premiums in structures that vary across carriers. Horizontal tables, vertical tables, nested tables: Sensible extracts each line with its coverage type and amounts intact.
03
Each endorsement form number, description, and premium adjustment modifies the base policy in a specific way. The extraction captures every endorsement as a separate structured item, linked to the underlying policy data.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
Every dec page is different, so we build the config around your exact schema rather than a fixed list. These are the fields insurance teams request most; we map whatever else your policy-admin system needs.
01
Policy information
Policy number, named insured, mailing address, effective date, expiration date, carrier name, producer/agency, policy form
02
Coverage details
Coverage type, limit per occurrence, aggregate limit, deductible, premium per coverage, total premium, retroactive date
03
Endorsements and conditions
Endorsement form numbers, endorsement descriptions, additional insureds, mortgagee/loss payee, vehicle/property schedules
config.json
SenseML
{ /* SenseML: declaration page extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "policy_number", "description": "policy number, policy #" },
{ "id": "named_insured", "description": "named insured, insured name, policyholder" },
{ "id": "total_premium", "description": "total premium, total annual premium, policy premium" },
{ "id": "expiration_date", "description": "expiration date, policy period to, policy end date" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible's insurance template library includes dec page configurations across all major lines of business. New carrier formats can be added using SenseML without starting from scratch.
Personal auto, homeowners, commercial property, general liability, workers compensation, umbrella/excess, professional liability
All major carriers including Hartford, Travelers, Liberty Mutual, Chubb, AIG, Zurich, Nationwide, State Farm, and any specialty carrier
Answers about dec page extraction across carriers and lines of business.
Yes. Every carrier formats dec pages differently. Sensible's hybrid extraction adapts to each carrier's layout while outputting a consistent schema.
Yes. Sensible identifies endorsement sections and extracts endorsement form numbers, descriptions, and any premium charges associated with each endorsement.
Yes. Package policies with property, liability, auto, and umbrella on separate dec pages are each extracted with line-specific field configurations.
Coverage types, limits, deductibles, premium per coverage, endorsement list, named insureds, and additional insureds come back by default. Dec pages differ by carrier and line of business, so the fields are defined in configuration and shaped to the coverages you write. Add or reshape what gets extracted to match your schema.
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.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. 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 PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.