Built around the job you already do: document, scope, price, defend

The job starts with what's actually at the property, not a narrative written afterward. Photo capture is live: photos attach to specific rooms and damage records from a web browser, and an AI-assisted damage observation can be proposed from a photo — always tied to that exact image, always requiring your review before it counts toward anything. There's no dedicated mobile app yet, so plan around browser-based capture in the field today.

Line items, measurements, and photos are separate, linked records — live today — so a scope you build isn't a set of assertions, it's a set of claims each backed by a specific piece of evidence. Measurements are computed server-side and carry their own accept/reject state, so quantities are decided deliberately rather than assumed.

That structure is what lets you build a scope quickly without giving up the trail back to the evidence — you're not choosing between speed and defensibility, because the linking happens automatically as you work, not as a separate step you have to remember afterward.

This is the part of the workflow furthest from finished, and it's worth saying plainly: PaxExact's pricing architecture — source-tracked, confidence-scored unit costs — is built, but no production pricing catalog is loaded behind it. Treat PaxExact today as a place to build and review scope, not yet a source of priced numbers you can hand to a carrier unchecked. A missing price is never shown as zero; the total says it's incomplete instead.

Once you approve the scope, PaxExact generates a case file that carries the evidence, the scope, and the pricing state together — live today, with PDF export in beta as the output format keeps being extended. The approval gate that produces it is enforced in code: nothing you haven't explicitly signed off on ends up in a report a carrier sees.

That's the file you'd actually hand to a carrier reviewer or reference later in a dispute — built from linked, approved records rather than assembled by hand the night before a deadline, and traceable back through the scope to the specific evidence behind each number.

Most public adjusters start with PaxExact Estimate, the base product, plus Claim Adjustment, which adds the approval gate and case file this page describes. Estimate is live. Claim Adjustment is a mix: its approval gate and case-file workflow are live and its PDF export and AI-assisted observations are in beta, while the case audit log is coming soon and contents valuation is planned — so the module as a whole is listed as planned, its least mature part. Commercial losses typically add the Commercial module (coverage records and co-insurance in beta; the business-income calculation coming soon), and a contents-heavy claim adds the Contents module (itemization is coming soon — stored by the platform but with no screen in the app yet; valuation with depreciation is planned, not built).

Beyond that core set, a few modules are optional depending on how you run your practice: LiDAR & Advanced Capture (scan upload in beta; a native capture app is planned, not built), Back Office if you don't already run an operating platform (mostly planned, with organization roles coming soon), Client Portal if you want clients to see status directly (coming soon), and Agreements for client agreements and e-signature (coming soon). None of these optional modules are required to use Estimate or Claim Adjustment.