Change orders land on the SOV the way the GC expects

The contract value is the sum of the lines on the Schedule of Values. Approved change orders append to the bottom, labeled. That's the standard, and STrOp now follows it in five places it didn't.

COs append labeled. Executing a change order with SOV impact used to insert the bare scope text — "Floor Prep" — indistinguishable from base contract scope. It now reads CO-002 Floor Prep, using the same number as the change order document and the CO log, so the GC reconciling your schedule against the changes it issued sees one identifier. The label travels onto the printed G703 with it.

You can see which lines came from change orders. CO-created and CO-amended lines carry a mark in the builder naming the CO behind them. STrOp has recorded that link on every execution since change management shipped — nothing had ever shown it.

Contract value has one home. It lives on the Contract tab. The project form shows it read-only with a pointer, because editing it in two places meant the SOV's balance check and NTP gate could move while the G702 cover kept printing the old figure. The awarded number stays the anchor the SOV balances to; revised value is always awarded plus executed COs, computed rather than typed.

Import from Estimate stops once a CO has landed. By then the schedule is a live billing document, not a draft — re-baselining it from the estimate would either drop the change scope or count it twice. The button refuses and names the change orders involved. Edit the lines directly instead.

A signed SOV isn't frozen out. After a revision — including one the GC asked for when it signed with changes — you can request a re-sign. The new request supersedes the old one, and the copy the GC signed before stays on file behind a View signed link.