Methodology
How the numbers are computed
Technical articles on how PaxExact measures, prices, and totals a property-loss estimate — the methodology behind the platform, not marketing copy.
How PaxExact handles co-insurance and business income
PaxExact's co-insurance and business-income calculations check readiness first, then let a professional accept the result or override it with a reason.
PaxExact estimate contract v1: public vocabulary
The closed vocabularies behind every PaxExact estimate — pricing, quantity, totals, and API states — defined in one place for reference and verification.
How PaxExact computes an estimate total
PaxExact totals are computed server-side in cents with fixed rounding, state completeness explicitly, and are never recomputed by the client.
From photo to line item: PaxExact's record model
PaxExact links photos, damage observations, measurements, and line items as separate, traceable records — no photo, no proposal, never a guess.
PaxExact's human approval gate, explained
Nothing becomes a priced, reportable PaxExact estimate without a licensed professional's explicit approval — enforced in code, not policy.
Why PaxExact computes measurements server-side
PaxExact measurements are computed on the server and carry an explicit accept/reject review step, not a client-side guess a reviewer must trust blindly.
How PaxExact prices a line item
Every unit price in PaxExact carries a state, a source class, a reason when it is missing, and a confidence — a missing price is never shown as zero.