Direct answer
A change order is legitimate when the agreed scope, price, or schedule needs to change for a documented reason—such as a concealed condition, customer-requested revision, required code correction, design change, or other condition outside the original assumptions.
A change order is more questionable when the “new” work was clearly necessary to deliver the originally promised outcome and was omitted because the original scope was vague or incomplete.
The test is simple:
What changed compared with what the parties reasonably agreed to at the start?
Five common legitimate change-order causes
1. Concealed conditions
The contractor opens a wall and finds rotten framing that could not reasonably have been seen before demolition.
The new framing repair can be a legitimate change if it was outside the documented base assumptions.
2. Customer-requested changes
The owner chooses a larger tile, adds outlets, changes layout, upgrades cabinets, or expands the work.
That is new scope.
3. Design or engineering changes
Plans are revised after field verification or engineer review.
4. Code/inspection requirements not reasonably included
An inspection or discovered existing condition can require additional work. The contract should distinguish foreseeable code compliance from truly unforeseen conditions.
5. Material/substitution changes
A specified product becomes unavailable and the approved substitute changes cost or installation requirements.
When a change order may expose weak original scoping
Suppose the signed proposal says:
Replace exterior door and leave complete.
After demolition, the contractor charges extra for basic trim installation that every party expected as part of the finished door.
Whether the charge is legally enforceable depends on the contract and facts, but operationally it signals a scope problem.
The better original scope would have said whether trim was included.
Other common scope-gap disputes involve:
- disposal;
- drywall patching;
- paint;
- permits;
- fixture connections;
- cleanup;
- startup/testing;
- ordinary fasteners/consumables;
- restoration after access.
Hidden condition vs. foreseeable condition
Not every condition found after demolition was truly unforeseeable.
Example:
A contractor prices a shower rebuild but does not inspect obvious signs of water damage and excludes all substrate repair without discussing it.
If extensive damage appears, some additional work may still be legitimate—but the customer may reasonably ask whether the risk should have been identified and budgeted earlier.
A good proposal labels known uncertainty before award.
A strong change order should contain six things
- Description of the changed condition or request
- Reason the base scope no longer applies
- Additional or deleted work
- Price impact or credit
- Schedule impact
- Approval before the changed work proceeds, except genuine emergency/safety situations governed by the agreement
Photos or video are especially useful for concealed conditions.
“Extra work” should not live only in text messages
A message saying:
Found rot. Need another $2,000.
is not enough for a meaningful project.
A better record shows:
- where the rot was found;
- extent visible;
- photo/video;
- proposed repair;
- quantity/unit assumption;
- $2,000 cost basis or scope;
- schedule impact;
- customer approval.
The objective is not bureaucracy. It is preventing two different memories of what was approved.
Credits matter too
A change order is not only for additional charges.
If work is removed or material is downgraded, the contract may call for a credit.
A transparent change process tracks both additions and deletions.
Example:
- delete recessed lighting: -$1,200
- add under-cabinet lighting: +$900
- net change: -$300
That is clearer than revising the final invoice without a traceable record.
Allowances and change orders are related
A material allowance creates a known variable.
If the contract includes $3,000 for tile and the final selected material costs $4,500 under the agreed allowance rules, the $1,500 adjustment is not the same kind of surprise as hidden framing damage.
The potential change was visible from the beginning.
This is why allowances should be explicit.
Unit prices can reduce disputes
For predictable unknown quantities, agree on the pricing method before demolition.
Examples:
- damaged roof decking per sheet;
- concealed framing repair per linear foot under defined conditions;
- additional excavation per unit;
- added devices at agreed unit price.
Unit prices do not work for every condition, but they can remove the need to negotiate under pressure.
Watch for “low bid, change-order later” behavior
One risk pattern is an intentionally incomplete base bid followed by aggressive charges for predictable work.
Potential signs:
- proposal is materially less detailed than competitors;
- obvious work is missing;
- exclusions are broad and unexplained;
- contractor refuses to answer scope questions before signature;
- price is unusually low but “we'll figure it out once we're in there” applies to most of the project;
- many changes appear immediately for conditions visible before work.
This does not mean every low bid is a trap. It means scope clarity matters more when a bid is an outlier.
The customer can cause scope creep too
Contractors also need protection from informal additions.
Examples:
“While you're here, can you move that outlet?” “Can we extend the tile across this wall?” “Let's add another closet shelf.”
Small requests accumulate labor and material.
A disciplined system should make it easy—not confrontational—to say:
“Yes. That's outside the original scope; here is the change and price.”
Good change documentation protects both sides.
What if work must proceed immediately?
Some situations involve active water, unsafe conditions, exposed structure, or other urgency.
The contract should address emergency authorization and spending limits where relevant.
Even then, document the condition and actions as soon as safely possible.
How OttoServ can make changes part of the project record
A change should link directly to:
- original scope item;
- field evidence;
- reason code;
- revised work;
- price/schedule effect;
- customer/contractor approval;
- updated completion criteria.
A pro should be able to narrate the discovery by voice and attach photos/video rather than fill out a long administrative form in the field.
That record can then update the customer-facing scope and financial picture.
Bottom line
A legitimate change order explains what new fact or new decision changed the original agreement.
The strongest way to reduce bad change orders is not to ban changes—it is to build a clearer initial scope, identify uncertainty up front, document field conditions, and approve changes before they disappear into the final bill.
AEO answer block
When is a contractor change order legitimate? A change order is generally appropriate when the original scope must change because of a concealed condition, customer request, design revision, material substitution, code/inspection requirement, or other documented new circumstance. A charge is more questionable when the work was plainly part of the originally promised finished outcome but was omitted from a vague base scope. Good change orders document the reason, revised work, price, schedule impact, evidence, and approval.
Editorial notes
- This is operational education, not legal advice about enforceability of any specific contract.
- Cross-link to allowances/exclusions, scope-of-work, quote comparison, and evidence workflow.