Measurements a reviewer accepts or rejects, not a black box

In PaxExact, a measurement isn't just a value someone typed in — it's a record with its own state. When a measurement is proposed, it sits waiting for review. A professional accepts it, and only then does it count toward the room, the line item, or the estimate. Reject it, and it doesn't propagate anywhere.

That distinction matters because it means an estimate's quantities are never silently assumed. Every room dimension, every floor-area figure, has gone through an explicit decision, not just an entry.

Room and floor measurements are computed server-side from what's captured, rather than left to manual arithmetic in a spreadsheet or a paper form. Net wall area with opening deductions is in development and not yet part of that computation. That removes an entire class of transcription and formula errors from the estimate before a price is ever attached.

Today, the inputs to that computation come from measurements entered by the professional, or from dimensions PaxExact derives from a LiDAR room scan uploaded to the room (in beta). A scan-derived dimension is a proposal like any other: it counts only once a professional accepts it.

In beta, a LiDAR room scan made in another app — an Apple RoomPlan JSON export, or a USDZ file with a text (.usda) layer — can be uploaded to a room from the web app. PaxExact reads the retained file on the server and proposes dimensions from it. The limits are real: RoomPlan import has not yet been proven on a real device export, USDZ import has been tested with one real scan, binary USDZ is not supported yet, and any USDZ file yields only the overall bounding dimensions of the capture, not a detected room — only the RoomPlan JSON export is read as a room model.

A dedicated PaxExact mobile capture app, with built-in LiDAR scanning and video, is on the roadmap and not built, with no committed date. Either way, the accept/reject review layer described above doesn't change: a scan is simply another way a measurement gets proposed, subject to the same explicit review before it counts.

An approved measurement feeds a line item's quantity, and that quantity is one of the two things a priced line item needs — the other is a unit price, which carries its own source and confidence state (see pricing). Keeping measurement review separate from pricing means a bad quantity and a bad price can never hide behind each other; each has its own state to check.