Trusted by teams turning documents into production data
Real Estate
Inspection reports — home inspections, property condition reports, commercial PCAs, and 4-point inspections — arrive as long narrative PDFs with embedded photos. Carriers, lenders, and acquirers need structured deficiency lists, not 40-page reports. Sensible converts any inspection format into actionable JSON for underwriting and claims diligence.
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
Inspection reports bury findings in long narrative, and every firm orders sections differently and grades severity in its own words. We parse the narrative and classify each finding against your severity schema.
01
Roof, electrical, plumbing, HVAC, foundation, and structural sections each contain free-text findings mixed with photos and bullet lists. Sensible parses each section into discrete deficiency records with severity, location, and recommendation.
02
One inspector calls it "monitor," another calls it "marginal," another writes "needs further evaluation." Sensible classifies findings against your underwriting severity schema so downstream rules behave consistently across reports.
03
InterNACHI templates, ASHI reports, carrier-specific 4-point forms, and commercial PCAs all look different. Each layout needs its own configuration, and SenseML makes each one repeatable.
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 inspection report is different, so we build the config around your exact schema rather than a fixed list. These are the fields teams request most; we map whatever else your underwriting, claims, or acquisition pipeline needs.
01
Property identity
Property address, inspection date, inspector name, license number, inspection type, client name, square footage, year built
02
System conditions
Roof, electrical, plumbing, HVAC, foundation, structural, exterior, interior — overall condition and age per system
03
Deficiencies
Item, location, severity, description, recommended action, estimated cost, page reference for source citation
config.json
SenseML
{ /* SenseML: inspection report extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "property_address", "description": "subject property address" },
{ "id": "inspection_date", "description": "inspection date, date of inspection" },
{ "id": "deficiencies", "description": "deficiencies, defects, issues found" },
{ "id": "roof_condition", "description": "roof condition, roof rating" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes inspection reports from any inspector or template system.
InterNACHI, ASHI, Spectora, HomeGauge, Horizon — pre-built configurations for each major inspection-software template.
Insurance-carrier-specific 4-point inspections, wind mitigation forms, and commercial property condition assessments.
Answers about deficiency parsing, severity classification, and inspector format variation.
Yes. Insurance-carrier 4-point inspections, wind mitigation forms, and commercial property condition assessments each have their own configuration. The output schema can be tailored per use case.
Yes. Roof, electrical, plumbing, HVAC, foundation, and structural sections get parsed into discrete deficiency records with severity, location, recommendation, and source-page citation preserved.
Inspector-specific language ("monitor," "marginal," "needs further evaluation") gets classified against your underwriting severity schema. Downstream rules behave consistently across reports from different inspectors.
Any inspector or template system. The library ships configs for InterNACHI, ASHI, Spectora, HomeGauge, and Horizon, and the output schema is yours to tailor per use case. Carrier-specific 4-point inspections, commercial PCAs, and report formats we haven't built yet all get configured in SenseML.
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.