CHANGE ORDER CONTROL

Field request, clarification, substitution, or change order — how to classify what just came in

A field request is a signal, not the final category. A clarification explains the existing contract. A substitution changes what will be supplied. A change order changes scope, cost, time, responsibility, or commercial terms. Most incoming requests arrive labeled as one thing and turn out to be another. The classification determines who pays, who owns the risk, and what gets documented.

Field request

Incoming issue or request that still needs classification. Not a category — an intake label.

Clarification

Scope stays the same. Interpretation of what the contract or drawing already requires.

Substitution

Alternate product, material, or method proposed in place of what was specified.

Change order

Commercial record required. Scope, cost, time, sequencing, responsibility, or contract terms change.

Start your free trial

What each term actually means on a jobsite

These four terms get used interchangeably on jobsites and in project emails. They are not interchangeable. The distinction determines whether you answer a question, submit a submittal, or issue a commercial document that changes the contract. Misclassifying a change order as a clarification means you absorb a cost the project owes you for.

Field request — the intake label, not the decision

A field request is anything that comes in from the field, the GC, the architect, or the owner that requires a response. It arrives unclassified. The electrician flags a conduit conflict. The GC asks about the rough-in schedule. The owner wants to move a receptacle. All of these start as field requests. None of them end as field requests — they route to one of the other three categories once you evaluate what is actually being asked. Treating "field request" as a final category means nothing gets properly documented.

Clarification — the scope stays the same

A clarification answers the question "what does the contract already require?" The work was already in scope. The cost was already in the price. Nothing changes — the contractor needed to understand the intent behind a drawing note, spec section, or contract clause. Clarifications do not carry cost impact and do not require a commercial document. They do require a written response, because an unanswered clarification can become a dispute later if the other party claims you proceeded without direction.

Substitution — the product changes, the function stays close

A substitution proposes an alternate product, material, or method in place of what was specified. The function is equivalent or close. The cost may be higher or lower. Substitutions need written approval from the architect, engineer, or GC — but they do not automatically require a change order unless the installation method, coordination with other trades, or the contract value changes. A straight material swap at equal cost with no installation impact is a substitution, not a change order. A material swap that requires different hangers, different routing, or additional coordination time is a substitution that generates a change order for the delta.

Change order — the commercial record

A change order is required any time scope, cost, time, sequencing, responsibility, or contract terms change from what was agreed. It is not a judgment about whether the change is large or small. If the original contract said 84 water closets and the revision says 96, the 12-unit delta is a change order regardless of whether it helps or hurts the schedule. Change orders create a paper trail that ties the commercial impact to the specific request. Without one, the cost sits in your overhead. For the boundary between revising a quote before acceptance and issuing a change order after, see when to revise a quote vs issue a change order. When quoting lives in spreadsheets, change orders get lost in parallel file versions and email threads — see how spreadsheet revision confusion causes missed change-order recovery.

Decision tree — route the request in 60 seconds

Run every incoming request through these four questions in order. Stop at the first yes.

Step 1: Does the request change scope, cost, time, sequencing, responsibility, or contract terms?

Yes → Change order. Stop here. Document the commercial impact, price the change, and issue the change order. The direction of the change does not matter — additions and deletions both require one. If the pre-award facts already warranted a revision, see what counts as a quote revision trigger for the boundary before acceptance.

No → Go to Step 2.

Step 2: Does the request propose a different product, material, or method than specified?

Yes → Substitution. Submit for approval. If the substitution also changes installation cost or coordination requirements, it generates a change order for the delta — but the classification starts as a substitution.

No → Go to Step 3.

Step 3: Is the request asking what the existing contract, drawing, or spec means?

Yes → Clarification. Answer in writing. Reference the contract section, drawing number, or spec paragraph. File the response as a clarification record. No commercial document needed.

No → Go to Step 4.

Step 4: You have a field request that still needs classification.

The request did not match any of the three categories above. Get more information — what specifically is being asked, what triggered it, and what the requester expects as an outcome. Then rerun from Step 1. Every field request should resolve to one of the other three categories.

Decision matrix

How the four categories differ across the dimensions that matter on a commercial job.

Dimension	Field request	Clarification	Substitution	Change order
Scope impact	Unknown until classified	None — scope stays the same	Same function, different supply	Scope adds, deletes, or shifts
Cost impact	Not yet determined	None — already in the contract price	May differ from original material cost	Contract value changes
Schedule impact	Not yet determined	None	Possible — lead time or install sequence may change	Duration or sequencing changes
Who approves	You — to classify it	Architect or engineer confirms intent	Architect, engineer, or GC approves the swap	Owner or GC authorizes the commercial change
Documentation	Log the request with date, source, and description	Written response referencing contract language	Submittal or substitution request with comparison data	Formal change order with cost breakdown and schedule impact
Margin risk	Unclassified requests sit in your overhead	Low — no commercial exposure if answered promptly	Moderate — cost delta may not be recoverable if not documented	High if not issued — you perform the work and absorb the cost

Real scenarios, real verdicts

How this classification plays out on actual commercial jobs. Each scenario includes the context, what came in, and what it actually is.

Scenario 1 — Electrical contractor, hospital renovation

Conduit routing conflict flagged by field crew

A $387,000 electrical contract on a hospital 4th-floor patient wing. The GC sends an RFI: does drawing E-201 show conduit routing as actual or schematic? The drawing shows conduit running through a mechanical chase that the plumbing contractor has already claimed for waste lines. Your field team needs to know where to route before rough-in starts.

Verdict: Clarification

The scope has not changed. The contract requires conduit to be routed — the question is where the drawing intends it to go. The conflict with plumbing is a coordination issue, not a scope addition. Answer the RFI in writing, reference the drawing number, and log it as a clarification. If the answer requires a route that adds 200 feet of conduit and six additional boxes beyond what was estimated, that additional scope becomes a change order — but the RFI itself is a clarification.

Scenario 2 — Mechanical contractor, school project

Engineer-specified RTUs swapped for faster availability

The engineer's schedule calls for Trane 20-ton RTUs on a $624,000 HVAC contract for a middle school renovation — 6 units total. Your supplier quotes Carrier equivalents that are available 4 weeks sooner at $3,200 less per unit. The total savings: $19,200. You propose the swap to the GC and engineer to improve the schedule.

Verdict: Substitution

Same function, different manufacturer. Submit as a substitution request with side-by-side performance data, lead times, and unit costs. Get written approval from the engineer. If the Carrier units require different curb adapters or a revised electrical connection, the installation delta becomes a change order for the additional material and labor — but the product swap itself is a substitution. If the substitution changes nothing about the install, it stays a substitution with no commercial document needed beyond the approval.

Scenario 3 — Plumbing contractor, multi-family build

Floor plan revision adds fixtures and relocates main stack

A 7-story multi-family project with a $1.12M plumbing contract. The architect issues a revision that adds 12 water closets, 2 mop sink basin assemblies, and relocates the main sanitary stack 14 feet to accommodate a lobby layout change. The original scope had 84 water closets, 4 mop sinks, and the stack in its original location.

Verdict: Change order

Scope increased by 12 water closets and 2 mop sinks (fixtures, trim, supply risers, waste and vent connections for each). The main stack relocation means 14 feet of additional 4-inch cast iron at approximately $78 per installed foot plus fittings, hangers, and penetration fire-stopping. The rough-in sequencing shifts because the stack move affects floors 1 through 7. This is not a clarification — the scope changed. It is not a substitution — nothing is being swapped for an equivalent. Issue a change order with a full cost breakdown: materials, labor, fittings, hangers, fire-stopping, and schedule impact per floor.

Scenario 4 — Electrical sub, commercial office buildout

Existing panel lacks space for specified breakers

You are running the electrical on a $163,500 tenant buildout. Your crew opens the existing 200-amp panel to tie in the new circuits shown on the one-line, and there are no available breaker positions. The original scope assumed the panel had capacity for 12 additional circuits. The field foreman sends a request to the PM: need a new panel or a subpanel.

Verdict: Field request that escalates to change order

This arrived as a field request — an unclassified signal from the field. The condition (no panel space) was not foreseeable from the drawings alone. The resolution requires additional scope: either a new panel ($1,800–$2,400 for a 200A subpanel with breakers, conduit home run, and labor) or a subpanel fed from the existing gear. The original contract did not include this work. Classify it correctly: the request is a field request, but the resolution is a change order. Document the existing condition with photos, price the change, and issue it. The cost of a 200A subpanel installation is not something you absorb as a coordination item — the contract assumed capacity that does not exist. For guidance on documenting the assumptions that make situations like this billable rather than arguable, see how to document assumptions so changes become billable, not arguable.

Scenario 5 — HVAC contractor, warehouse distribution center

Spec lists two different insulation R-values

On a $298,000 warehouse HVAC contract, the project manual specifies R-6 duct insulation in Section 23 07 13 but the energy compliance worksheet in the appendix references R-8 for the same duct runs. The owner asks which value governs.

Verdict: Clarification

No change to scope or cost until the engineer answers. Both values appear in contract documents — the contractor needs the design professional to confirm which one governs. Submit an RFI, reference both spec sections, and file the response as a clarification. If the answer is R-8 and you priced R-6, the cost difference becomes a change order — but the question itself is a clarification.

What should trigger a change order immediately

These situations are change orders regardless of how the request was labeled when it came in. Waiting to classify them costs margin.

Any scope addition or deletion not in the original contract

If the work was not in the bid package and it is now being asked for, it is a change order. This applies to additions and deletions. A scope deletion that removes $14,000 of work from a $186,000 contract reduces your revenue and may increase your unit costs on remaining items. Document it with a change order so the contract value reflects reality.

Cost impact above a meaningful threshold

Set a threshold — $2,500, or 2 to 3 percent of contract value — and treat any cost impact above that threshold as a change order automatically. Below the threshold, track it. Above the threshold, document it commercially. Small untracked costs across 20 change events on a $500,000 contract can consume an entire markup buffer.

Schedule impact on the critical path

If a request adds or removes days from the critical path — whether through additional work, rework, or a sequencing change — it is a change order. The schedule impact carries real cost: extended general conditions, trade stacking, compression on downstream activities. Do not absorb schedule changes as field coordination. Document them.

Responsibility shifts between parties

If work that was in your scope moves to another contractor, or work that was in another contractor's scope lands on you, that is a change order. Scope transfers change your cost basis, your labor hours, and your material commitments. Track every transfer with a commercial document.

Changed site conditions that make the original scope infeasible

If field conditions differ materially from what the contract documents show — buried utilities not on the survey, structural conditions that do not match the drawings, asbestos in a demolition area that was assumed clear — the work required to address those conditions is a change order. The original scope assumed conditions that do not exist. Document the actual condition, quantify the delta, and issue the change order.

Documentation checklist — what to capture for each classification

Every incoming request should produce a paper trail. The trail looks different depending on the classification. Capture the right items and you can defend every cost position on the job. Skip them and you absorb costs you could have recovered.

Classification	What to document	Why it matters
Field request	Date received, source (GC, owner, architect, field crew), description of what was requested, who flagged it	Establishes when you became aware of the issue. Protects against claims that you delayed response.
Clarification	RFI or question number, contract reference (spec section, drawing number, clause), written response from the design professional, date answered	Proves you did not proceed without direction. Prevents the response from being recharacterized as a scope change later.
Substitution	Original specified product vs proposed product, performance comparison, unit cost comparison, lead time comparison, written approval from architect or engineer	Confirms the swap was authorized. Captures the cost delta. Required for submittal logs and closeout documentation.
Change order	Description of the change, cause (who initiated and why), scope delta with quantities, cost breakdown (material, labor, equipment, overhead, markup), schedule impact in days, before and after contract values, authorization signatures	The commercial record. Without this, the cost sits in your overhead. With it, the contract value reflects actual scope. Use the exclusions and assumptions builder to capture the contract language that supports the change order position.

Published April 2026 · Last reviewed April 2026 · Written by the Quoteloc team — construction quote governance and change order management specialists.

Common misclassification mistakes

These are the classification errors that cost margin on active jobs. Most happen because the request was categorized by who sent it or how it arrived, not by what it actually asks for.

Calling a change order a clarification because it came through an RFI

An RFI is a delivery method, not a category. A request for information can carry a clarification, a substitution proposal, or a scope change. If the RFI asks for work that was not in the contract, the answer to the RFI may be a clarification — but the work it triggers is a change order. Classify the content, not the envelope.

Treating a substitution as minor when the installation method changes

Swapping a 4-inch cast iron pipe for 4-inch PVC at similar material cost looks like a straight substitution. But if the PVC requires different hangers, different supports, and a revised seismic bracing layout, the installation delta is a change order. The material swap is a substitution. The rework and additional hangers are not.

Absorbing a scope addition as field coordination

The GC asks your crew to add six outlets while they are on site. Your foreman agrees because it is faster than stopping to ask. Those six outlets were not in the contract. The labor, the material, and the circuit breaker positions they consume are all additional scope. The request started as a field request and should have been classified as a change order before any work proceeded. For the full breakdown of where this pattern creates unrecoverable cost, see the hidden cost of approving extra work without written change control.

Classifying based on who sent the request instead of what it asks for

A request from the architect is not automatically a clarification. A request from the GC is not automatically a change order. The origin does not determine the category. What the request asks for does. A design professional asking for additional work is a scope change regardless of the source. An owner asking what color the fixtures should be is a clarification regardless of their authority.

What not to do

The patterns that create margin loss and record confusion. Avoid all of them.

Do not proceed on verbal direction alone

Verbal approvals do not hold up at billing. If the GC says go ahead, document it in writing before the crew starts. An email confirming the verbal direction is the minimum. A formal change order is better.

Do not skip documentation because the amount is small

Small undocumented changes accumulate. A $640 material swap here, a $1,200 labor addition there — across 15 events on a $500,000 contract, that is $27,600 in undocumented scope changes. That is margin you will not recover.

Do not edit the original contract to reflect changes

The original contract is the baseline. If you edit it, the baseline disappears. Every downstream team — billing, operations, closeout — loses the reference point. Changes go on separate documents that supplement the original, never replace it. For the full argument, see the change order control hub.

Do not wait until billing to classify

Classification happens when the request arrives, not when the invoice goes out. By billing time, the facts are stale, memories are unreliable, and the other party has no incentive to agree with your interpretation. Classify immediately, document in real time, and file by category. Use the change order log builder to keep every request tracked from intake to resolution.

Classify every request before it costs you margin

Quoteloc gives contractor teams a structured way to log, classify, and track incoming field requests, clarifications, substitutions, and change orders — so nothing sits unclassified and no cost goes undocumented. For the broader framework on how pricing risk and contract changes interact, see the pricing uncertainty decision guide for contractor quotes.