Keeping Change Orders Under Control
A change order is simply a written amendment to the agreed scope and price. Used properly it is the mechanism that keeps a project honest while conditions change. Used poorly, which mostly means used late or not at all, it becomes the reason a project finishes well over budget with both parties feeling wronged.
The Two Kinds, and Why the Distinction Matters
Changes fall into discoveries and elections. A discovery is a condition nobody could have priced: rot behind a shower surround, wiring that fails inspection, a floor that turns out to be two inches out of level. An election is a decision you made, whether that is upgrading a fixture or moving a wall you had originally planned to keep.
Keeping these separate does real work. Discoveries draw against the contingency reserve, which exists for exactly this. Elections should be funded separately, because they are choices and treating them as unforeseen conditions quietly consumes the reserve you will need when an actual discovery arrives. Projects that fail financially often fail this way, with the contingency spent on upgrades before the first real surprise appears.
Price It Before the Work Happens
The single most valuable rule is that no change proceeds until it is priced and signed. This feels bureaucratic on a small item and it is precisely the small items that erode a budget, because each one individually seems too minor to formalize. A verbal yes on a Tuesday becomes a line item of unknown size on a final invoice, and by then the work is installed and the negotiation is over.
A change order should state what changed, why, the cost impact, and the schedule impact. That last one gets omitted constantly and matters more than people expect. A change requiring an additional inspection or a re-order of a long lead item can add weeks that never appeared in the conversation about price.
Keep a Running Ledger
Both parties should be able to see the same number at any moment: original contract, approved changes to date, remaining contingency. Keeping that visible converts the end of a project from a reckoning into a formality. It also changes behavior during the project, because a homeowner watching the reserve deplete makes different decisions about upgrades than one who will see the total for the first time at the end.
When to Push Back
Not every proposed change is legitimate. Work that should have been foreseen by a competent estimator visiting the site is arguably part of the original scope, and it is fair to say so. The distinction is between conditions that were genuinely concealed and conditions that were merely unexamined. A contractor who priced without looking in the crawlspace is in a weaker position than one who found something behind a wall that no inspection could have reached.