A Contract Change Order can modify both the contract (billing-side / Schedule of Values) and the budget (cost-side / estimate) from a single Change Request record — they're separate tabs on the same record. For the concepts behind all this, see Change Order Management.
The grid shows each line's original units, current units, scheduled value, the change you're proposing, and the resulting New Current Units / New Scheduled Value so you can see the effect before approving. It also surfaces other pending and approved changes from separate change orders, so overlapping changes are visible.
The unit columns (Original Units, Current Units, Inc/Dec Units, and New Current Units) display and save up to five decimal places, with at least two always shown, so fractional quantities such as 0.125 tons are kept exactly rather than rounded. Money columns stay at two decimals.
Line numbers are validated as billing lines are saved: a line number that already exists on the contract — or on another line of the same change request — is rejected, so your Schedule of Values numbering stays unambiguous even with several change orders in flight.
Several change requests can be open on the same contract at once, and they can be approved in any order; there is no need to approve them in the sequence they were created.
After approval: if a change order was approved prematurely or with the wrong values, it can be unapproved, or corrected and re-approved in a single atomic step — see Unapproving an Approved Change Order.
Multiple contracts: if a project has more than one Sales Order, a contract filter appears above the grid and lines are grouped by contract. Select a contract before adding a new line.
To help keep unit-price lines complete, the grid watches for a mismatch between a line's dollar change and its units. If a line has a Proposed Changes amount but zero Inc/Dec Units (or units entered with no matching dollar change), those cells turn red so they're easy to spot.
When you click Save with any of these lines still in place, a confirmation appears listing the affected lines, with two options:
This is just a prompt, not a block — it gives you a chance to add the units you meant to enter while still letting an intentional zero through. Deliberate zero-quantity lines are fully supported through save and approval, which comes in handy when a change is purely a dollar adjustment on a unit-price line. A line also only falls back to Pending Approval when both its Inc/Dec Units and Proposed Changes are zero, so zeroing one side of a change doesn't quietly reset the line's status.
The reverse case works too: a line with a quantity change in Inc/Dec Units but a $0 Proposed Changes amount can be approved, which is handy when you need to move units on a line without changing its value. Two cases are still blocked at approval with the message "Change requests cannot approve proposed changes of 0": a line with no amount and no quantity change, and a lump-sum line with a $0 proposed change (lump-sum lines change by dollar amount only, so $0 leaves nothing to apply).
Each cost line shows Original Budget, Current Estimate, Actual Costs (with a link to the underlying transactions), Committed Costs (with a link to the open POs), and the resulting New Current Estimate — so you can weigh a proposed change against what's already been spent and committed.
The New Current Estimate, New Current Hours, and New Current Units columns appear only while the change request is pending. Once it is approved, the current values already include the change, so those columns are hidden.
Because Sales Orders aren't natively aware of credit memos, the preferred way to reduce a contract after billing is a negative change order while the standalone credit memo option is off (the default): reduce the contract value with a negative change order, then invoice that amount netted against positive line billings. With the option on, a standalone credit memo can reduce the contract directly. See Correcting Invoices with Credit Memos for the full picture.