One case file, generated only after approval

A PaxExact case holds the estimate, the evidence behind it, and any commercial or contents calculations that apply — one record, not a folder of separate documents that have to be manually kept in sync. This is in production for early-access use today: when something changes on the case, the report generated from it reflects the current state, not a stale export from an earlier visit.

That matters most on a claim that runs for months, through a first estimate, a supplement, and a dispute. Instead of reconciling three versions of a spreadsheet against a folder of photos, the case holds one current state — and every prior revision stays attached rather than overwritten, so you can show what changed and when, not just where things ended up.

The case report doesn't generate until the professional approval gate has been passed. That's the same enforcement described on the estimate-review page, applied here to the output: there's no path to a case report that skips review, because the report is generated from the approved state, not from whatever happens to be on screen.

That ordering is deliberate. A report generated before approval would let an unreviewed number reach a carrier by accident — a draft mistaken for a final. Tying generation to the approval step removes that failure mode entirely instead of relying on someone to double-check before hitting export.

PDF export is in beta. The underlying workflow — pulling evidence, scope, and pricing state together into one exportable record — is real and in production. What's still being extended is the format itself: exactly what's included, how it's laid out, and how completely it represents everything on the case. Treat the workflow as solid and the specific PDF you get today as a version that will keep changing.

When a carrier or a reviewer asks where a number came from, the answer needs to be more convincing than 'trust the adjuster.' Because the case file is generated from linked, approved records rather than compiled by hand after the fact, the trace from photo to line item to total exists in the file itself — not in a person's memory of how the file was built.