Draft v0.0.1

HomeHudl Property Repair Record (HPRR)

Open, vendor-neutral data standard for property restoration and insurance claims

Overview

The HomeHudl Property Repair Record (HPRR) is the open standard. An individual record for a given property is called a Property Repair Record (PRR).

HPRR is an open, portable, vendor-neutral standard for representing the full repair history of a property, including damage events, insurance claims, contractor involvement, documents, and timeline events.

HPRR solves the core problem in the property insurance ecosystem: no shared language between homeowners, contractors, insurers, CRMs, and estimating platforms.

Think of it like FHIR for property restoration: HPRR plays a similar role for property restoration that HL7 FHIR plays for healthcare records: a simple, open resource model that different systems can agree on.

Why now? Verisk's consolidation of Xactimate + AccuLynx + ISO + Snowflake creates a single point of control. HPRR establishes the open alternative.

This is v0.0.1, a minimal draft intended to plant the flag, define the category, and create a foundation to iterate on.

Who is HPRR for?

Insurance carriers and MGAs

Contractor CRMs and job-management tools

Estimating platforms

Homeowner apps and portals

HPRR & AI

HPRR is intentionally designed to be AI-ready.

By standardizing the core objects in a property repair record (Property, Claim, Contractor, Insurer, TimelineEvent, and Document), HPRR enables:

•Clean, structured training data across carriers, contractors, and platforms
•Safer, auditable AI models for claims, underwriting, and routing
•More accurate predictions for delays, disputes, costs, and satisfaction
•Vendor-neutral AI innovation, because everyone trains on the same resource model
•A shared ecosystem, instead of siloed proprietary datasets

This mirrors how HL7 FHIR unlocked healthcare AI innovation by standardizing clinical resources. HPRR does the same for property restoration and insurance claims.

HPRR does not prescribe scoring, modeling, routing, or workflows. It only defines the canonical structure that enables those systems to safely evolve.

Principles

Property-centric

The record belongs to the property — not the insurer, not the contractor, not the software vendor.

Open & vendor-neutral

Anyone can implement PRR without permission.

Simple first, extensible later

v0.0.1 includes only essential objects. Scoring, disputes, and complex workflows come in later versions.

Portable

A PRR should move easily between systems (CRMs, insurers, adjusters, homeowner apps).

Minimal commitment

The draft is intentionally small to avoid freezing early design decisions.

Core Objects (v0.0.1)

HPRR v0.0.1 defines six objects and intentionally excludes scoring, disputes, workflows, routing logic, and other complex features. Those come later.

NOT in v0.0.1: scoring, disputes, delay categories, workflows, routing logic, insurer preferences, or CIE logic.

Object Definitions

Property

Represents a real-world address.

Key Fields:

property_id (string, required)
address (full structured address)
geo (optional lat/lng)
year_built (optional)
structure_type
metadata

Claim

Represents one damage event + insurer interaction.

Key Fields:

claim_id (string, required)
property_id (string, required)
insurer_id (optional)
contractor_id (optional)
cause_of_loss (hail, wind, water, fire)
date_of_loss (required)
status (open, in_review, approved, etc.)
coverage (deductible, ACV, RCV, SoL)
timeline[] (references TimelineEvents)
documents[] (references Documents)
metadata

Contractor

Represents the contractor performing the work.

Key Fields:

contractor_id
legal_name
trade (roofing, GC, restoration)
service_regions
contact (phone, email, website)
metadata

Insurer

Represents the carrier or MGA.

Key Fields:

insurer_id
legal_name
brand_name
naic_code
preferred_scope_platform
contact
metadata

TimelineEvent

Atomic event describing what happened and when.

Key Fields:

event_id
claim_id
occurred_at (timestamp)
event_type (inspection_scheduled, etc.)
actor_type (homeowner, contractor, etc.)
actor_id (optional)
related_document (optional)
metadata

Document

Photos, PDFs, SoLs, invoices, receipts, permits.

Key Fields:

document_id
claim_id or property_id
document_type
url (or object reference)
uploaded_at
metadata

Minimal Example

Here's a tiny example showing how a Property Repair Record (PRR) looks in practice:

Property:
  id: PROP-1234EXAMPLE
  address: 123 Example St, Anytown, WI
  year_built: 1995

Claim:
  id: CLAIM-20240701-01
  property_id: PROP-1234EXAMPLE
  cause_of_loss: hail
  date_of_loss: 2024-07-01
  status: approved
  coverage:
    deductible_amount: 1000
    acv_paid: 8000
    rcv_total: 15500

Contractor:
  id: CTR-001
  legal_name: "Example Roofing Co."
  trade: roofing

TimelineEvents:
  - event_id: EVT-1
    occurred_at: 2024-07-02T10:30:00Z
    event_type: inspection_completed
    actor_type: contractor

Documents:
  - doc_id: DOC-1
    type: photo
    url: https://example.com/photo1.jpg

Roadmap: What Comes Later

These features are not in v0.0.1 yet — they're future extensions:

v0.1

Standardized delay categories and dispute categories.

v0.2

Permitting event types and mortgage endorsement flow.

v0.3

Contractor-insurer performance relationships, plus pre-inspection and inspection results.

v1.0 (Major Milestone)

When HomeHudl has traction: CIE scoring extension, contractor efficiency profiles, insurer preference profiles, AI-driven event prediction, standardized PRR bundles, and signature framework.

Governance & Stewardship

Steward:

HomeHudl

License:

MIT (open, permissive; see repository for full text)

Model:

Open draft with public feedback, versioned drafts

Process:

HPRR evolves through versioned drafts, not committees

Goal:

Become the neutral, open standard for property repair data globally

HPRR v0.0.1 — Draft standard by HomeHudl

Questions or feedback? Contact us at info@homehudl.io