CHANGE ORDER CONTROL
Published April 2026 · Written by the Quoteloc team — construction pricing and scope control specialists
What to do when the buyer says “just include it” without approving a price change
When a buyer says “just include it” without approving a price change, the contractor must classify the request into one of four documented paths before any work changes: confirm it is already included in the quoted scope, revise the quote with adjusted pricing before acceptance, use an allowance with a reconciliation mechanism for uncertain scope, or issue a change order with written approval after acceptance. None of these paths allow silent absorption.
“Just include it” is not commercial approval. It is informal language that creates scope expansion without a price, a markup record, or a recovery path. Every time a contractor absorbs that language as an instruction to proceed, margin erodes silently. The correct response is to classify the request into one of four paths — and force written confirmation before any work changes.
- —If the work is already in the quote, show where — do not re-price it
- —If it is new scope before acceptance, revise the quote with adjusted pricing
- —If the scope is uncertain, use an allowance with a reconciliation mechanism
- —If the quote is accepted, issue a change order with written approval before work starts
What “just include it” usually means
Buyers say “just include it” for different reasons. Understanding which one you are dealing with determines what happens next — because the same words can mean three completely different things.
Convenience language — not commercial intent
Most of the time, the buyer is not trying to add scope for free. They are using shorthand. They assume the work is minor, that it is probably covered already, or that the contractor will price it fairly and add it to the next invoice. The buyer is not thinking about your scope boundaries, your markup structure, or your margin. They are thinking about getting the job done. The problem is that convenience language still creates commercial exposure — because “just include it” contains no scope definition, no price, no markup, and no approval mechanism.
Scope expansion under pressure
Sometimes the buyer knows the work is not included and is using informal language to avoid triggering a price conversation. On fast-tracked jobs, design-incomplete projects, and negotiated work, the buyer is under pressure to deliver and the easiest path is to push scope downstream without acknowledging the cost. This is contractor scope creep before award — the scope grows but the price does not. The contractor who absorbs this silently is the one who pays for it.
Ambiguity benefits the buyer — not the contractor
When the scope is unclear, the default interpretation favours the party with more leverage at invoicing time — and that is almost always the buyer. If the work was done but never priced, the buyer can challenge the amount, reject the markup, or dispute that the scope was ever formally requested. This is the classic included-in-scope dispute: the buyer claims it was part of the original price, the contractor cannot prove it was not. The contractor carries the cost of ambiguity. The buyer does not. For the broader pattern of how informal scope handling erodes commercial control, see how contractors lose margin on commercial jobs. For the full discipline of keeping the contract baseline clean, see the change order control hub.
Why this destroys margin
The margin damage from “just include it” does not happen in a single moment. It compounds through a chain of operational failures that start with an informal request and end with unrecoverable cost.
The failure chain
Informal request arrives. The buyer says “just include it” during a call, a site walk, or an email thread. No scope is defined. No price is discussed. No documentation is created.
Estimator absorbs the scope. The estimator or project manager adds the work to the job file without a pricing entry. The scope grows. The cost structure does not.
No pricing approval. There is no change order, no quote revision, no allowance, and no budget line for the addition. The extra work has no price approval and no commercial home.
Field executes. The crew does the work because it was requested. Materials are purchased. Labour is spent. The cost is real.
Dispute later. At invoicing, the buyer challenges the additional cost because there is no record of a priced, approved change. The added scope was never approved, and the contractor has no documentation to defend the claim.
Unrecoverable margin loss. The cost was incurred. The revenue was not. The difference comes out of the job margin — and the contractor carries it.
Worked example: the cost of absorbing one “just include it”
An electrical contractor quotes a $94,200 tenant fitout with a 14% markup buffer ($13,188). During a site walk, the buyer asks to “just include” twelve additional data outlets and a dedicated circuit for a server room. The estimator adds the scope. No price revision. No change order.
The additional work requires 360m of Cat6 cable, 12 data outlets, 1 dedicated circuit with 20mm conduit, a new MCB in the distribution board, and 18 hours of labour. Actual cost: $3,420 in materials and $2,340 in labour — $5,760 total. With 14% markup, the billable value should have been $6,566.
That $5,760 of unapproved scope consumes 44% of the markup buffer on the entire job. Two more additions of similar size and the job margin is gone. Use the floor price calculator to see what your real minimum price should be before absorbing informal additions.
What to do instead: the four-path decision framework
Every “just include it” request must be forced into one of four paths. None of the paths allow silent absorption. Each path produces a documented, priced, and approved outcome.
Path 1: Already included scope
The requested work is already covered by an existing line item in the quote. The quantity, specification, and pricing match. No action is needed other than confirming coverage to the buyer.
How to verify: Check the accepted quote line items, scope notes, and inclusions. If the work falls within a described inclusion at the quoted quantity and specification, it is covered. Point the buyer to the specific line item or scope note. If the work extends the quantity, changes the spec, or falls outside the described inclusion, it is not included — move to Path 2, 3, or 4.
Path 2: Quote revision with price adjustment
The work is new scope and the quote has not been accepted yet. Revise the quote to include the addition, adjust the price, and reissue. The buyer receives an updated price that reflects the full scope — and decides whether to accept it.
When to use this path: The buyer has not accepted the quote. The additional scope changes the total value. The revision replaces the previous version. For the complete decision framework around revisions, see when to revise a quote vs issue a change order.
Path 3: Allowance / assumption treatment
The scope is uncertain or the final cost cannot be determined at quoting stage. Include the work as a conditional allowance — a stated dollar amount for a defined scope, with a reconciliation mechanism that specifies what happens when actual cost differs from the allowance.
What the allowance must state: The scope it covers. The dollar amount included. The basis for the amount (estimate, supplier quote, historical cost). What happens if actual cost exceeds the allowance — who pays the difference and under what terms. An allowance without these elements is not protection. It is exposure dressed as inclusion. For the discipline of documenting assumptions that make scope changes billable rather than arguable, see how to document assumptions so changes become billable.
Path 4: Post-award change order
The quote has been accepted and the work is new scope. The accepted quote is the contract baseline. Issue a change order that describes the addition, prices it at current rates with standard markup, states the schedule impact, and requires written approval from the buyer before work proceeds.
Critical rule: Do not start the additional work before the change order is approved. Once the work is done, your leverage drops to near zero. The buyer has received the value and negotiating price after delivery is always harder than before. For the full discipline of written change control, see the hidden cost of approving extra work without written change control.
Decision matrix: safest action by project stage
The correct response to “just include it” depends on where the job sits in the commercial timeline. Use this matrix to determine the safest action at each stage.
| Project stage | Safest action | Why |
|---|---|---|
| Before quote sent | Include in quote | The quote has not been issued yet. Add the scope with proper pricing, materials, and labour. The buyer sees the full cost upfront and accepts or rejects the total. No separate document needed — the inclusion becomes part of the base quote. |
| Quote under review | Revise quote | The buyer has the quote but has not accepted it. Revise the quote to include the addition with adjusted pricing and reissue. The previous version is replaced. No change order needed — the contract baseline has not been established yet. If the scope is uncertain, use an allowance with a reconciliation mechanism. |
| Quote accepted | Change order | The quote is now the contract baseline. It stays locked. Any scope addition goes through a change order — priced, approved, and recorded separately. Do not edit the accepted quote. The change order supplements the baseline; it does not replace it. |
| During execution / field request | Change order before work starts | The field team is on site and the buyer or their representative asks for additional work. Stop. Write the scope, price it, present it for approval. If schedule pressure demands immediate action, get at minimum a written email acknowledgment of the cost before work is substantially complete. Do not let the crew proceed on a verbal instruction — use a work order to document the instruction and tie it to the change order. |
Common contractor mistakes
These are the behaviours that turn a manageable scope request into an unrecoverable cost.
Treating vague buyer language as approval
“Just include it,” “that should be fine,” “work it out,” and “I am sure it is minor” are not approvals. None of these phrases define scope, set a price, assign markup, or create a recoverable cost record. They are verbal gestures that the contractor interprets as permission and the buyer forgets they said. If you cannot point to a document that describes the scope, the price, and the approval, you do not have approval.
Confusing clarification with expanded scope
A buyer asks a question about what is included. The contractor answers the question and then adds work that was not in the original scope, thinking the question implied a request. Clarification is informational — it confirms what was already quoted. Expanded scope is commercial — it changes what was quoted. If answering the question requires a scope change, that change needs to follow one of the four paths.
Adding work to preserve the relationship
The contractor absorbs the cost because they want to keep the buyer happy for the next job. The math does not work. A $5,760 absorbed cost on a $94,200 job consumes nearly half the markup buffer. If the relationship is worth protecting, protect it with clear communication and documented agreements — not silent cost absorption that builds resentment on the contractor side and expectation on the buyer side. Use the change order log builder to keep every addition visible and tracked.
Hoping to recover cost later
The contractor proceeds with the additional work, planning to “sort it out” at final account or in the next progress claim. By that point, the buyer has received the value and has no incentive to agree to the price. Late cost recovery is negotiation from a weak position. Price it, present it, and get approval before the work starts — every time.
Letting site teams proceed before paperwork is aligned
The buyer tells the site foreman to add some extra work. The foreman instructs the crew. The work is done before the office knows it happened. By the time the estimator or project manager finds out, the cost is incurred and the leverage is gone. Site teams should never proceed on informal buyer instructions. If the buyer asks for extra work on site, the foreman should acknowledge the request and confirm that scope and pricing will follow from the office before work begins.
What to send back: three response templates
These templates are starting points. Adapt the language to your project and your relationship with the buyer. The goal in each is to acknowledge the request, classify it, and force a documented commercial outcome.
Template 1
Pre-award clarification response
Use when: the quote has not been accepted yet. The response forces the buyer to acknowledge that the addition is new scope, not already included.
Template 2
Quote revision response
Use when: the quote is still under review. The response clearly separates original scope from the addition and asks for explicit acceptance of the revised total.
Template 3
Post-award change-order response
Use when: the quote has been accepted and any scope addition requires a formal change order. The response ties the change to the accepted baseline, presents a full cost breakdown, and requests written approval before work starts.
How to document it: scope-addition checklist
Every “just include it” request that results in scope change must generate a record that includes these items. Use this checklist before filing the revision, allowance, or change order.
Request source — Who asked for the addition, when, and in what medium (email, call, site walk, meeting minutes)
Exact scope description — What was requested, where, and in what quantities. Specific enough that someone not involved in the conversation could understand it
Inclusions / exclusions impact — Does this addition change any existing inclusion or exclusion in the quote? If so, which ones and how?
Labour / material / equipment effect — What additional hours, materials, and equipment are required? Itemise by trade if applicable
Schedule effect — Does the addition extend the timeline, displace planned work, or affect other trades? Quantify in days
Revised price or change order value — The dollar amount with markup applied. State the markup rate and the calculation
Approval state — Pending, approved, or rejected. Who approved it, when, and in what medium. If not yet approved, state that clearly
Reference documents — Emails, drawings, sketches, photographs, site instructions, or meeting minutes that support the request and the pricing
Related resources
These pages address the adjacent problems that “just include it” creates — revision control, assumption documentation, change order pricing, and margin protection.
Change order control hub
The full guide to keeping the contract baseline clean, issuing change orders correctly, and preventing margin leakage from uncontrolled scope changes.
When to revise a quote vs issue a change order
The boundary is acceptance. Before acceptance, revise. After acceptance, issue a change order. Includes a decision matrix and trade examples.
Document assumptions so changes become billable, not arguable
A defensible assumption states what was assumed, what it was based on, what happens if wrong, and who carries the cost. Includes weak vs strong wording examples.
How contractors lose margin on commercial jobs
The patterns that create margin erosion — from informal scope handling and uncontrolled extras to weak markup discipline and missing documentation.
Change order log builder
Build a structured, shareable change order log that keeps every addition visible to the team — with scope, cost, approval state, and contract total tracking.
Floor price calculator
Calculate the minimum price a job must carry before absorbing any scope additions. Know your floor before the buyer asks you to “just include” more work.
Bottom line
“Just include it” is not commercial approval. Every informal scope request must be classified into one of four paths — included scope, quote revision, allowance, or change order — and documented with scope, price, and written approval before work changes. The contractor who absorbs informal requests silently is the contractor who carries the cost.
One absorbed addition of $5,760 on a $94,200 job consumed 44% of the markup buffer. Two more additions of similar size and the job margin is gone. Price the addition, present it for approval, and get it in writing — every time.
Frequently asked questions
Does “just include it” count as approval to add scope?
No. “Just include it” is informal language that does not define scope, set a price, assign markup, or create a recoverable cost record. Treat it as an unresolved request until it is classified into one of four paths: already included scope, quote revision with price adjustment, allowance or assumption treatment, or post-award change order.
What if the buyer says it during a site walk?
Acknowledge the request, note it, and classify it before taking action. Do not instruct the field team to proceed. A verbal request during a site walk has no scope definition, no price, and no documentation. Write it up, price it, and send it back through the proper channel — whether that is a quote revision or a change order depends on whether the quote has been accepted.
Should I just add the work and recover the cost later?
No. Once the work is done, your leverage drops to near zero. The buyer has received the value. Negotiating price after delivery is always harder than negotiating before. Price the addition, present it for approval, and get written confirmation before the work proceeds.
How do I classify whether something is already included or is new scope?
Check the accepted quote line items and the scope notes. If the requested work matches a line item description and quantity, it is included. If it extends the quantity, adds a new item, or changes the specification, it is new scope. When in doubt, check the exclusions list — if it was excluded, it was never included.
What is the difference between an allowance and a change order?
An allowance is a conditional inclusion placed in the quote before acceptance — it states the amount, the scope it covers, and what happens if actual cost differs. A change order is a post-acceptance document that modifies the contract baseline. Allowances are set during quoting. Change orders are issued after the quote is accepted.
Can I use an allowance to cover work that might be added later?
Yes, if the allowance is stated in the quote before acceptance, includes a defined scope, a dollar amount, and a reconciliation mechanism. The allowance must state what happens if the actual cost exceeds the allowance — who pays the difference and under what terms. An undocumented “we will figure it out later” is not an allowance. It is scope exposure.
Stop scope expansion from slipping into the quote unnoticed
Quoteloc helps contractor teams classify every scope request into a documented, priced, and approved channel — before the work starts. Quote revisions before acceptance. Change orders after. Allowances for uncertain scope. Locked baselines that cannot be silently edited. For the full discipline of scope control and margin protection, see the change order control hub.
7-day free trial. No credit card required.
Back to all resourcesBack to change order control hub