Esc

↑↓ move↵ openIndex · Pagefind

Signing the change order is the halfway point. For the change to be real everywhere, four more things have to happen: the cost budget is revised for the new scope, the matching sub change order (a commitment change) is issued, a new SOV line is added so the work can be billed, and the forecast and WIP pick up the new contract value and cost.

Sample data: on Riverside, CO #14 adds $86,400 to the contract. Summit Mechanical's subcontract gets a $68,000 change order (CCO-03). CO #14 becomes SOV line 10 and is billed on Pay App #9 at 80% (60% installed plus 20% stored), $69,120 before retainage. Then the WIP catches up.

When those steps live in different systems, each one is a chance to drift: an owner CO approved but no sub CO issued, a sub CO issued against the wrong code, a change billed before it was executed. A change order log that tracks each change through every step, with dates and amounts, is the simplest control.

The question to ask every month: for each executed change order, is it in the budget, the commitments, the SOV and the forecast?

Do it · Template

Change order log (CSV)

Open the log and read the CO-14 sample row: requested vs approved amount, schedule days, sub COs issued and the pay app it was billed on. Add one change from a current job and fill in every column. Any blank you cannot fill is a gap in your loop.

Download the template

Check yourself

Three questions, instant feedback. Get all three right to check off this lesson.

Q1After an owner change order is executed, which step is most often missed?

Q2Sample data: CO #14 is billed on Pay App #9 at 80%. Before retainage, that is:

Q3Why add an executed change order as its own SOV line?

0 of 3 correct

Key terms

Go further

Open file