How Do You Turn an Estimate Into a Schedule of Values?

The estimate is approved, then it keeps getting edited, and by the third pay app nobody can say what the contract was actually for.

Freeze the approved estimate as an immutable contract baseline and build the schedule of values from that snapshot, so every draw bills against a fixed contract, not a moving estimate.

What this workflow is

Turning an estimate into a schedule of values is the step that converts a priced proposal into the billing structure for the job. An estimate is the editable price you build during sales. A schedule of values, or SOV, is the fixed breakdown of the contract that progress payments bill against. The work is freezing the agreed estimate as a baseline and structuring it into billable lines.

Why it matters

The SOV is the financial spine of the whole job: every pay application, every percent complete, every retainage calculation reconciles back to it. If billing keys off the live estimate, which keeps getting edited, the contract value drifts and the billing has no fixed reference. The failure mode is a billing dispute where the contractor and owner cannot agree on what the contract was for, because the number kept moving after it was agreed.

How to do it

1. Qualify and price the scope

   The inquiry is qualified and the scope is priced in detail as an estimate, the working number through sales.
2. Reach agreement with the owner

   The owner agrees to the priced scope. This is the moment the estimate stops being a working document and becomes a contract.
3. Freeze the estimate as a baseline

   The agreed estimate is frozen as an immutable snapshot, the authoritative record of what was contracted, separate from any later editable copy.
4. Materialize the schedule of values

   The frozen baseline is broken into a schedule of values whose total is the contract authority every draw reconciles to.
5. Confirm every line has an earning trigger

   Each SOV line maps to a defined way it gets billed, so generation fails closed on any line it cannot classify rather than producing a line that stalls billing.
6. Bill progress against the SOV

   Progress draws bill against the SOV lines, always tracing back to the frozen baseline, never to the editable estimate.

Common mistakes

How Scaftra runs it

Scaftra freezes an approved estimate into an immutable estimate scope snapshot, then materializes one active schedule of values whose original contract value is the contract authority. Billing keys off the snapshot and the SOV, never the editable estimate, and SOV generation fails closed on any line it cannot classify into an earning trigger, so the contract baseline is fixed and every line is billable.

Key capabilities

• Immutable estimate snapshot: The approved estimate is frozen as a snapshot that billing reads from, so the contract baseline cannot drift even if a working copy is edited later.
• Single active schedule of values: One active SOV carries the original contract value as the authority every pay application reconciles to.
• Fail-closed generation: SOV generation fails closed on any line it cannot classify into an earning trigger, so no unbillable line slips into the billing structure.
• Contract authority: The frozen snapshot and SOV total are the contract authority, so billing always traces to what was agreed, not what was last edited.

Benefits

• Every draw bills against a fixed contract baseline that cannot drift.
• There is an authoritative record of what was contracted at the moment of agreement.
• Every SOV line has a defined way to be billed, so no line silently stalls billing.

Who runs this

• Commercial and AIA-billing GCs.Contractors who bill progress draws against a schedule of values and need the contract baseline frozen.
• Design-build firms moving from sales to billing.Teams converting an agreed estimate into a billing structure who need the handoff to be clean and fixed.

Related on Scaftra

Go deeper