Direct answer
A good change order explains what changed, why it changed, what evidence supports it, what it adds or removes from the scope, how price changes, how schedule changes, and who approved it.
For an investor, the goal is not “zero change orders.” Some changes are legitimate because concealed conditions, owner decisions, code/permit findings, or field realities cannot always be known in advance. The goal is to prevent undocumented scope drift and to distinguish a real changed condition from work that should already have been included in the base scope.
The three kinds of change an investor should distinguish
1. Owner-requested change
The investor changes the desired outcome after award.
Examples:
- upgrade flooring;
- add a second bathroom vanity;
- change cabinet scope from refinish to replacement;
- add exterior work that was not in the original contract.
This is not a contractor estimating error. The owner changed the scope.
2. Unforeseen or concealed condition
The project reveals a condition that could not reasonably be confirmed earlier.
Examples:
- concealed rot after finish removal;
- hidden plumbing damage behind cabinetry;
- damaged subfloor beyond the visible area;
- concealed framing condition requiring additional repair.
This is where a clear base assumption and evidence process matter.
3. Scope gap or interpretation dispute
The parties disagree about whether work was already included.
Examples:
- proposal says “paint interior” and contractor excludes ceilings;
- scope calls for “replace flooring” but transitions were never addressed;
- contractor assumed permit fees were owner-paid while investor assumed included;
- demolition was priced but disposal was not mentioned.
These are the changes a stronger pre-award scope and bid-leveling process can reduce.
A change order should answer seven questions
Every material change should state:
- What condition or decision triggered the change?
- What evidence supports it?
- What original scope language or assumption is affected?
- What work is being added, deleted, or revised?
- What is the price impact?
- What is the schedule impact?
- Who authorized the change and when?
If several of those are missing, the investor may know that the price changed without understanding why.
Start with the original scope version
A change order only makes sense relative to a baseline.
Record:
- original scope version/date;
- contractor proposal version/date;
- accepted alternates;
- accepted allowances;
- known assumptions;
- original contract amount;
- previous approved changes.
Without version control, change-order disputes often become memory contests.
Require evidence before pricing where practical
For a hidden condition, useful evidence may include:
- photos;
- video;
- measurements;
- marked-up plans or room diagrams;
- specialist findings;
- inspection result;
- quantity calculation;
- damaged material after removal.
The evidence should show the condition clearly enough that the investor can understand what changed.
This does not mean delaying urgent protective work when immediate action is necessary. The process should have an emergency exception with prompt documentation afterward.
Distinguish discovery from authorization
A contractor discovering additional work does not automatically mean the contractor has authority to perform it.
The workflow should be:
discover → document → define → price → approve → perform
unless immediate action is required for safety, property protection, or another agreed emergency condition.
This single distinction can prevent large amounts of unplanned scope from accumulating before the owner understands it.
Change-order pricing should be understandable
Depending on the contract and scope, pricing may be:
- lump sum;
- unit price;
- time and materials;
- allowance reconciliation;
- credit for deleted work;
- net change combining additions and deletions.
The investor should understand which method applies.
For time-and-material work, define what documentation is expected. For unit pricing, define the measurable unit. For lump-sum changes, define the changed scope clearly enough that the amount has meaning.
Do not approve duplicate work
Before approving a change, compare it with:
- base scope;
- proposal;
- clarifications;
- accepted alternates;
- allowance coverage;
- previous change orders.
Questions to ask:
- Was this work already included?
- Is this a different quantity from the one originally assumed?
- Is this an upgraded selection rather than a new scope item?
- Did a previous change already cover part of it?
- Is a credit due for work that will no longer be performed?
A change order should show the net change, not just new additions.
Credits matter as much as additions
Investors often focus on extra charges and forget deleted work.
Example:
Original scope includes repairing existing cabinets. Investor later chooses full cabinet replacement.
The change should address:
- cost of new cabinet scope;
- credit for repair/refinish work removed from base scope, if that work was priced in the base contract;
- related countertop/plumbing/finish changes;
- schedule impact.
Otherwise the owner may pay for both the original path and the replacement path.
Allowance changes are not always scope changes
If a $1,000 fixture allowance is already in the contract and the investor selects a $1,250 fixture, the change may primarily be an allowance overage, not an entirely new scope.
But if the new fixture requires:
- different rough-in;
- extra electrical work;
- structural support;
- additional finish repair;
- different installation labor;
then the change can include both allowance reconciliation and scope impact.
See: Allowances vs. Selections in a Rehab Budget.
Contingency does not remove approval discipline
A project may have money reserved for unknown conditions, but that reserve should not authorize automatic spending.
Contingency answers:
“Do we have financial capacity for uncertainty?”
The change order answers:
“What specifically happened and are we approving this response?”
See: How to Build a Rehab Contingency Without Hiding Scope Gaps.
Track cumulative change, not isolated tickets
Every approved change affects the current project position.
Maintain a log with:
| CO | Description | Add | Credit | Net | Schedule impact | Status |
|---|---|---|---|---|---|---|
| 001 | ||||||
| 002 |
Then show:
- original contract amount;
- approved additions;
- approved credits;
- current contract amount;
- pending changes;
- remaining owner contingency, if tracked separately.
The investor should be able to answer “Where are we now?” without reconstructing every text thread.
Track schedule impact explicitly
A change may affect schedule even if the dollar amount is small.
Examples:
- a selected fixture has a long lead time;
- additional inspection is required;
- hidden repair must occur before finishes continue;
- owner decision delays procurement;
- newly discovered work changes subcontractor sequence.
Require the change to state whether schedule impact is:
- none expected;
- known number of added days;
- dependent on material/inspection/decision; or
- not yet determinable.
“Price only” change orders can hide schedule consequences.
Define emergency authority in advance
Some conditions require immediate action.
Examples may include:
- active water intrusion;
- exposed unsafe condition;
- temporary stabilization;
- protection of completed work from ongoing damage.
The contract or operating agreement should define:
- who may authorize emergency work;
- any dollar limit;
- required documentation;
- notification deadline;
- how permanent repair is scoped afterward.
The emergency exception should be narrow enough that it does not become a general bypass of owner approval.
Common change-order failure modes
Verbal approval only
Weeks later, no one agrees on what was authorized.
Price approved, scope unclear
The investor pays an amount without a precise changed deliverable.
Work completed before approval
The owner loses decision leverage and may not know whether another response was possible.
No credits
Added work is charged, but deleted base work remains in the contract amount.
No schedule impact
The project drifts and the owner cannot tell which decisions caused delay.
Duplicate changes
Several change orders overlap the same condition.
Contingency treated as spendable contractor money
The reserve disappears without condition-level accountability.
A practical change-order template
Change order number: Project/property: Date: Baseline scope/proposal version: Trigger: Observed condition or owner request: Evidence links/photos: Original assumption or scope affected: Added work: Deleted work / credit: Material/selection changes: Price add: Price credit: Net change: Schedule impact: Permit/inspection impact if applicable: Approval: Approval date: Completion evidence required:
That is enough structure to preserve the story of the change.
How OttoServ fits
OttoServ can keep a change tied to the condition, original scope, evidence, approval, contractor communication, cost, schedule, and final closeout.
The intended workflow is:
baseline scope → field condition → evidence → proposed change → owner decision → approved scope/cost/schedule → execution → completion evidence → property history
This matters for investors because the value of documentation continues after the rehab. Future maintenance, resale diligence, turnover work, warranty conversations, and portfolio decisions can all benefit from knowing what changed and why.
FAQ
Are change orders always a sign the original contractor bid was bad?
No. Some changes arise from legitimate concealed conditions or owner decisions. The key is distinguishing those from scope gaps that should have been resolved earlier.
Should a contractor start changed work before approval?
Normally the change should be documented and authorized first. A narrow emergency exception may be appropriate for immediate safety or property-protection needs.
Should deleted work generate a credit?
If the deleted work was included in the original contract price, the change should address the corresponding credit or explain why none applies.
Can contingency pay for change orders?
An owner may use contingency funds for approved changes, but the existence of contingency should not eliminate condition-level documentation and approval.
Should every tiny field adjustment require a formal change order?
The project can define a materiality threshold or field-directive process, but changes that affect scope, price, schedule, compliance, or the intended finished result should remain traceable.