Two lineages, deliberately separate. Raw sync versions are pre-markup internal snapshots and stay internal. Send versions carry the customer's actual document — with markup applied — plus the quoted grand total, and default to visible because they were literally just sent.
Also called: what did we send them · sent version · proof of the quote
- 1On send, the payload is hashed and compared to the latest version's signature; an unchanged send doesn't duplicate a version.
- 2The new row stores the portal snapshot and the markup snapshot together, with the customer total as quoted_price.
- 3Capture is best-effort — a version hiccup can never fail the send.
- 4The client portal only ever renders a version that carries a portal snapshot.
The versions written automatically as an estimate synced were raw, pre-markup snapshots — showing one to a customer would have printed the builder's cost as the price. A customer-facing version is now captured at the moment of sending, on the server, carrying the exact marked-up document the customer receives and the grand total quoted. Whatever gets argued about later, there is a record of precisely what left the office and when.
- No durable record of the document a customer actually received
- Internal pre-markup pricing at risk of being shown to a buyer
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →