How PaxExact works

A claim starts with what's actually documented at the property — photos and measurements attached to specific rooms and damage, not a narrative summary written after the fact. That evidence is what everything downstream in PaxExact references back to.

Photo and measurement capture attached to a claim's rooms and line items works today, from a web browser. A LiDAR room scan made in another app can be uploaded to a room, in beta, and turns into proposed measurements a reviewer accepts. A dedicated mobile capture app is planned, not built.

Damage is recorded as discrete, evidence-linked observations rather than a single freeform scope narrative, so every line item in the resulting estimate can be traced back to a specific photo or measurement — not just asserted.

AI-assisted damage observations are in beta: when a vision provider is configured, a photo can be analyzed and turned into a proposed observation, always tied to that specific photo and always requiring human review before it counts toward anything. That analysis fails safely — no photo, no proposal, never a guess — rather than substituting a generic answer when it isn't available. An accepted observation can then be turned into suggested line items (in beta) — specific repair operations for water damage to walls, ceilings, floors and baseboards, and smoke, soot or mold damage to walls, ceilings and floors — each counting only after a professional approves it; other line items are entered by the estimator.

PaxExact is built around an explicit approval gate: a licensed professional reviews and approves the scope before it becomes a priced estimate. The platform assembles and links evidence; the professional decides.

The approval gate is real and enforced in the code, not aspirational: a scope cannot become a priced, reportable estimate without an explicit professional approval step.

The pricing architecture is built to track where every unit cost came from and how confident that figure is, rather than presenting a single number with no lineage. This is one of the areas furthest from general availability today — see the current status on the capabilities page.

The pricing architecture (source-tracked, confidence-scored unit costs) is built, but no real pricing data has been loaded behind it yet. The one connected pricing source today is an explicitly sandboxed vendor feed, not a licensed production catalog. Treat pricing as not yet a source of real numbers.

Once approved, PaxExact generates a case file that carries the evidence, scope, and estimate together — built to be traced from photo through scope through price, not assembled from three disconnected documents after the fact.

A computed, evidence-linked case file is real and generated today, gated on the same professional approval step. Its output format is being extended; treat the workflow as real and the output format as still evolving.