The estimate becomes part of the claim

Claim Adjustment is built for public adjusters, for roofing and restoration contractors who work insurance claims rather than pure repair jobs, and for claim-oriented estimating organizations — anyone whose estimate will be read by a carrier, an appraiser, or a court, and needs to hold up under that reading. If that's not your work, this module adds cost without adding value: a general contractor scoping a repair job for the homeowner directly doesn't need an approval gate built for adversarial review, and shouldn't be sold one.

Say it plainly: if you only need to produce and hand off an estimate, stay on the base product. Claim Adjustment earns its place when the estimate has to survive scrutiny from someone whose interests aren't aligned with yours.

This is the module's most mature piece. Unapproved scope is excluded from totals and reports by the platform itself, not by a policy someone might skip under deadline pressure. Every line item carries its own review state through revisions, and a line that's gone stale is blocked from silent edits — you reconcile it explicitly instead of letting an old approval quietly carry forward.

AI-assisted damage observations sit inside that same gate. A photo can be analyzed into a proposed observation tied to that exact image — this is in beta, real and in production, but deliberately narrow: no photo means no proposal, and nothing an AI proposes counts toward the estimate until a professional accepts it.

Once scope is approved, PaxExact holds the estimate, its evidence, and any commercial or contents calculations together on one case — that case structure is live today — and generates a report only after that approval step, never before. Case-file PDF export is in beta: the underlying workflow that pulls evidence, scope, and pricing state together is real and in production; the exact format of the export itself is still being extended, so expect it to keep changing.

Two pieces of this module are not ready to rely on. Contents valuation — replacement cost and actual cash value with documented depreciation — is designed but not built; every total today stays RCV-only and says so rather than implying a depreciated figure. A case-file audit log, a chronological record of every change to a case, is partially built: each case records five lifecycle events — creation, step advances, estimate linking, professional approval and report generation — but not every change, and the log cannot yet be exported or viewed in the application. The estimate's own revision history is live and separate.

Both matter for defending a claim over months of back-and-forth with a carrier, and both are being built with that use in mind — but neither is something to rely on today.

Claim Adjustment doesn't replace anything in PaxExact Estimate — it adds the approval gate, the case file, and (eventually) contents valuation and an audit log on top of the same rooms, line items, and server-computed totals you already build in the base product. A firm that starts on Estimate alone and later takes on claim work can add this module without re-entering anything; the estimate that already exists becomes the estimate the case file is built from.