Product
Nothing becomes a priced estimate without human approval
PaxExact enforces an explicit approval gate in code: unapproved scope is excluded from totals and reports, and every line item carries its own review state through revisions.
What's real today
- The professional approval gate is live and enforced in code — not a policy note.
- Estimate review and revisions are live: each line item has a review state, and stale lines are blocked from silent edits.
- Server-computed totals are live, reporting completeness and RCV state rather than assuming a number is final.
- A missing price is never shown as zero; totals mark themselves partial or incomplete instead.
The approval gate is a code path, not a checklist
It would be easy to describe an approval step as a best practice and leave enforcement to habit. PaxExact doesn't: unapproved scope is excluded from totals and reports by the platform itself. There's no configuration that lets an unreviewed line item quietly count toward a number a carrier will see.
This is one of the most mature pieces of the platform — it's live, it's enforced, and it doesn't change based on who's using it or how busy they are.
That consistency matters most under deadline pressure, exactly when a manual checklist is most likely to get skipped. Because the gate lives in the platform rather than in a habit, a rushed afternoon doesn't produce a different outcome than a careful one.
Revisions, and a stale line can't be quietly edited
Every line item carries its own review state, separate from the estimate's overall status. When an estimate is revised, PaxExact tracks that as a revision rather than overwriting history, and a line item that's gone stale — because something upstream changed — is blocked from being silently edited. You have to reconcile it explicitly rather than have an old approval quietly carry forward onto new numbers.
Totals that admit what they don't know
Totals are computed by the platform, not assembled from figures typed elsewhere, and they report their own completeness. If any line is unpriced, the total says so rather than presenting a number that looks finished. Sales tax appears only when the professional enters a rate, and the total says whether it was applied, instead of quietly leaving it out with no explanation.
A total that isn't finished yet
Why the gate exists
An estimate that reaches a carrier is a professional's name on a number. The approval gate exists so that number always reflects a deliberate decision by that professional — not an AI proposal, not a stale revision, not an unpriced line rounding invisibly to zero. It's the single piece of the platform built to make sure nothing gets ahead of the person accountable for it.
It also means the review layer is where every other unresolved state in PaxExact ends up: an AI-proposed observation, an unpriced line, an RCV-only contents total — none of it matters unless it eventually passes through a person who decides what to do with it. The gate is what makes that decision unavoidable rather than optional.
FAQ
Frequently asked
Can an unapproved line item show up in my total?
No. Unapproved scope is excluded from totals and reports by the platform itself, not just by convention.
What happens if I try to edit a stale line item?
It's blocked. Stale lines can't be silently edited; they carry a state that forces you to reconcile them explicitly.
Does PaxExact model tax in its totals?
Partly. You can enter one sales-tax rate on the estimate, and the platform applies it to the subtotal and reports tax_state APPLIED; with no rate, the total reports NOT_APPLIED rather than guessing. There is no taxable-base split, rate lookup or jurisdiction model yet. Overhead & profit is applied server-side, separately.
Related