Where scope creep comes from
Most unpaid extra work is not the result of a customer trying to get something for free. It comes from a gap between what the contract said and what happened on site, and nobody stopping to write it down. The crew fixes the problem because that is what good crews do, and by the time anyone thinks about billing it, the evidence is gone and the conversation is awkward.
Knowing the common sources helps the crew recognize a change when they see one.
- Hidden conditions: rot, outdated wiring, undersized framing, or anything behind a wall or under a floor
- Customer requests made directly to the crew on site: "while you are here, could you also..."
- Selections that cost more than the allowance in the contract
- Plan changes or inspector requirements that differ from what was priced
- Quantities that run past what was contracted, such as more square footage of repair than estimated
- Delays or rework caused by others, such as late customer-supplied materials
Capture the evidence the day it happens
A change order is easy to agree to when the customer can see why it exists. Build that case in the field, at the time, with records the crew is already making. The goal is that anyone reading the job file later — the customer, your office, or a third party in a dispute — can see what was found, when, and what was said about it.
- 1
Photograph it before touching it
Take wide and close-up photos of the condition as found, with a caption saying where it is and what it shows. Add a tape measure or reference object for scale.
- 2
Write it in the daily log
Note the date, what was found or requested, who was told, and whether work on that item stopped or continued.
- 3
Record the customer’s request in their words
If the customer asked for extra work, get the request in writing — a message, an email, or a note they confirm. A verbal request on site is the easiest thing to dispute later.
- 4
Track the time and material separately
Clock time and log material against the change, not the original scope, so the cost is known even before it is priced.
- 5
Tell the office the same day
The person who prices changes should know about it before the crew goes home, not at the end of the job.
What to put in a change order
A change order is a short contract amendment. It should be clear enough to stand on its own if someone reads it a year from now without the rest of the file. Keep the language plain and specific, the same way you wrote the original scope.
- Job name, address, and the original contract or estimate it amends
- A change order number and date
- The reason for the change: customer request, hidden condition, plan or code change
- The contract line, assumption, or exclusion it relates to
- A clear description of the added, removed, or changed work, with quantities
- The price, and whether it is fixed, time and material, or time and material with a not-to-exceed amount
- The effect on the schedule, in working days
- Payment terms for the change: billed now, with the next progress invoice, or on completion
- Reference to the supporting photos or log entries
- Signature and date lines for the customer and the contractor
Timing: price and sign before the work
The best time to agree the price of a change is before the changed work begins. Before, it is a decision the customer makes with full information. After, it is a bill they did not expect. Make pausing on the changed item — not the whole job — the default, and give the customer a quick way to review and sign.
Some situations cannot wait: an active leak, a structural issue, or a condition that stops other trades. For those, many contractors agree a time-and-material approach with a not-to-exceed amount, get written authorization to proceed, and document the actual hours and material as they go. Whatever approach you use, make sure it is consistent with the change clause in your contract.
Some states have specific rules for home improvement contracts, including requirements that changes be in writing and signed. Requirements vary, so check your state’s rules and your contract, and consider having your change order form reviewed by an attorney.
Worked example: a hypothetical bathroom remodel
Example only — the job and the numbers are invented. A contractor is remodeling a bathroom under a fixed-price contract that assumes the subfloor is sound and excludes repair of concealed damage. During demolition, the crew finds soft, discolored subfloor around the toilet flange.
The lead photographs the area before removing anything, with a tape measure showing the damaged section is roughly 3 ft by 4 ft. The daily log records the finding, that the customer was shown the area at 11:30, and that work on the floor near the toilet paused while other demolition continued. The same afternoon, the customer asks in a message whether a recessed shampoo niche could be added to the shower.
The office prices the subfloor repair from cost: 10 labor hours at a hypothetical loaded rate of $45 is $450, material is $280, and disposal is $50, for $780 of cost. With the company’s 25% markup, the change is $975 and adds one working day. The niche is priced from the company’s standard assembly at $650 with no schedule effect. Both go to the customer as change orders 1 and 2, each citing the subfloor assumption or the customer’s message, with the photos attached.
The customer signs both that evening. The crew replaces the subfloor the next morning. Because the contract bills changes with the next progress payment, the next invoice shows the original progress amount plus two separate lines, CO 1 subfloor repair $975 and CO 2 shower niche $650, each tied to its signed change order. Nobody is surprised at the final walkthrough.
From signed change order to collected invoice
An approved change order is only money when it is collected. Bill it as its own line or its own invoice, referencing the change order number, so the customer can match what they approved to what they are paying. Folding changes into a single revised total makes them harder to recognize and easier to question.
Bill promptly. A change billed with the next scheduled payment, or on completion of that item, is fresh in everyone’s mind. A stack of changes that first appears on the final invoice invites a dispute at exactly the moment you have the least leverage — the work is done and the customer is holding the final payment.
Update the job budget at the same time. The approved change adds revenue and cost to the job, and your job-cost report should show it on its own code so you can see whether the change itself made money.
Keep a change order log on every job
A change order log is a running list of every change on a job, whatever its status. It is the single place the office, the crew lead, and the customer can look to see what has been asked for, what has been priced, what has been approved, and what has been billed. Without one, changes live in text threads, notebooks, and memory, and the ones that fall through the cracks are almost always the ones you did the work for and never billed.
Review the log in the same weekly routine as your job costs. Anything that has been priced but not signed for more than a few days needs a follow-up. Anything signed but not yet billed needs to go on the next invoice. Anything rejected should be marked rejected, with a note confirming the crew knows not to do that work.
- Change order number and date raised
- Short description and reason: customer request, hidden condition, plan or code change
- Status: identified, priced, sent, approved, rejected, billed, paid
- Price and schedule effect
- Links to the supporting photos, log entries, and customer messages
- The invoice it was billed on
Avoiding change order disputes
Most disputes come from surprise, not price. The practices below reduce surprise at each step.
- Walk the customer through assumptions and exclusions before they sign the original contract
- Tell crews what is in scope and who is allowed to approve extras — usually not the crew
- Show the customer the condition in person or in photos before presenting a price
- Give a price and schedule effect in writing, not a verbal ballpark
- Keep a running change order log on the job, visible to the customer
- Never bill a change the customer has not approved in the way your contract requires
Where JobLoad360 fits
In JobLoad360, photos tagged as before, progress, or issue, and daily logs written from a voice note (AI daily logs are on Basic and Pro) are filed to the job from the field. On Basic and Pro, a customer can raise a change request from their portal; priced change orders go to the portal for approval, and an approved change order bills as its own invoice and adjusts the job budget.
On Pro, Scope Protection compares field evidence — daily logs, photos, time, purchases, and customer messages — against the signed estimate’s lines, assumptions, and exclusions, and raises change-order candidates with the evidence attached. A person reviews each one; nothing is billed or approved on its own.