WHY CHANGE ORDERS
ALWAYS LOSE MONEY.
Change orders should be some of the most profitable work on a job — you already have the crew mobilized, the equipment on site, and the overhead running. But most change orders lose money. Not because the scope is wrong. Because the billing protocol is broken. Work starts before a price is agreed. Overhead isn't included in the price. Billing gets delayed past the leverage window. Costs code to the wrong place. Four failures, all preventable.
HOW APPROVED SCOPE BECOMES
UNRECOVERED REVENUE.
The impact: a $5M subcontractor running 15 jobs with an average of 4 change orders per job. If each change order averages $8,000 and recovers at 70% instead of 100% due to these four failures, that's $24,000 per job, $360,000 per year in preventable under-recovery. Every year.
THE CHANGE ORDER PROTOCOL
THAT RECOVERS THE MARGIN.
NO WORK WITHOUT A WRITTEN DIRECTION OR PRICE AGREEMENT
The PM's standing instruction: verbal "just get it done" is not authorization. Every scope change requires either a written direction to proceed (which preserves your right to price it) or a price agreement in writing before work starts. The PM communicates this to the GC as a professional standard, not a confrontation. Most GCs who work with structured subs respect this. Those who don't are teaching you something about the relationship.
PRICE WITH FULL OVERHEAD AND IMPACT COSTS
Change order pricing formula: direct labor (fully burdened) + direct material + equipment at cost basis rate + overhead allocation at current overhead rate + profit at target margin + any impact costs (standby time, re-sequencing, added mobilization). Build a change order pricing template that calculates each line. The PM fills in the scope quantities. The template calculates the rest.
BILL WITHIN 5 DAYS OF COMPLETION — CFO TRACKS THE LOG
Every completed change order gets billed within 5 days. The CFO maintains a change order log for every active job. Monthly, the CFO reviews the log: any change order with costs hitting the job but no billing event gets escalated to the PM that week. The log is the enforcement mechanism. Without it, billing timing is entirely dependent on the PM remembering — which is how 60-day delays happen.