Field Change Request: What Subcontractors Need to Know
What a field change request (FCR) is, what to put in it, who approves it, and how subcontractors protect cost and schedule when the field changes first.

A field change request (FCR) is a written request to change the work because what is in the field does not match the drawings or specifications. It records the discrepancy, the proposed fix, and the effect on cost and schedule, so the change can be reviewed and approved before it turns into an unpaid argument. For a subcontractor, the FCR is the first piece of paper in the change order trail, and we built CO Hub so that paper starts in the field, on a phone, the moment the problem shows up.
TL;DR
- An FCR documents a gap between the contract documents and field conditions, and proposes a change. It is not yet a change to the contract.
- Include what changed, why, the affected drawings or spec sections, the cost breakdown, the time impact and the other work it touches.
- Send written notice early. Many contracts and federal clauses bar an adjustment if notice comes late.
- If approval is slow, proceed under written protest rather than stopping work, unless safety is at risk.
- A signed FCR should flow into a priced change order with the same records, so nothing is typed twice.
Table of Contents
- What a field change request is
- FCR, field order, change directive and change order
- What to put in a field change request
- How to submit an FCR and who approves it
- Why notice timing decides who pays
- What to do when the field can’t wait for approval
- Common FCR mistakes
- Our perspective
- Put your FCRs on one system
- FAQ
- Sources
What a field change request is
The term comes from owner and agency procedures. NASA’s field change request release describes the FCR as a document used to document, track and implement changes, and says anyone associated with the project can start one. It covers discrepancies between drawings or specifications and field conditions, inconsistencies within the drawings or specs, certain recommended changes that do not affect form, fit or function, and changes needed to correct design deficiencies.
Utilities use the same idea. Con Edison’s quality procedures require that changes to an approved-for-construction drawing, or field conditions that differ from the contract documents, be documented on a field change report. The name varies (request, report, notice), but the job is the same: put the field reality in writing and route it to someone who can decide.
Typical examples a commercial subcontractor runs into:
- A duct run that collides with a beam the mechanical drawings did not show.
- A conduit path that has to move because an existing wall is not where the plans say it is.
- A spec section that calls for a product that is no longer available, with a proposed equal.
- Two sheets that disagree on a dimension, rating or quantity.
- Existing conditions behind a wall that change the scope of demolition or patching.
FCR, field order, change directive and change order
These terms get mixed up on job sites, and the difference matters for who pays.
| Document | What it does | Who starts it | Does it change price or time? |
|---|---|---|---|
| Field change request | Asks for a change and records the field condition | Usually the subcontractor or field staff | Only once approved and priced |
| Field order | Directs work to proceed when scope or cost cannot yet be set | The owner or its representative | Adjusted later from backup documentation |
| Change directive | Directs a change before price is agreed | The owner or architect | Price settled afterward |
| Change order | Formally modifies the contract | Agreed by the parties | Yes, price and time are stated |
The University of California’s facilities manual shows how a field order works. A field order may be issued in emergencies, when the extent of work cannot be determined because of unknown conditions, or when proceeding would affect the critical path, and the contractor must promptly proceed with it. If the contractor does not sign, the owner’s representative adjusts the contract sum and time from the backup documentation the contractor provides. Read that last part twice: your cost records decide the number.
The FHWA describes a change as any alteration to the original construction contract, and change orders as negotiated agreements that affect cost, schedule, design details or specifications. An FCR is the request. The change order is the agreement. If you want the contract-side detail, our guides on the construction change directive and the change order approval process cover what happens after the request.
What to put in a field change request
A request that is vague gets sent back, and every day in the inbox is a day the crew either waits or works at risk. Public agency procedures are consistent on what a reviewer needs.
The change itself. NASA’s release requires the contractor to provide everything asked for at the top of the form, describe the recommended change with a detailed rationale, and list the affected documentation including revision. Name the sheet numbers and spec sections. Cite the revision.
Location and limits. Caltrans says a change order should be clear, concise and explicit, and when appropriate state what is to be done, the location or limits, the specification references, the effect on completion time, and the method and amount of compensation. Grid lines, floor and room numbers beat “near the loading dock.”
Cost breakdown. A utility’s change order procedures ask for a scope description, the reason for the change and its relationship to other work, a price with breakdown of added labor, material and equipment plus overhead and profit percentages, and the effect on contract time and milestones. The same document asks for a deadline for the owner’s response so a delay does not stop the work. Include that deadline in your own requests.
Consequences and affected work. Con Edison’s FCR asks for the reason the change is necessary, including what happens if it is not made, and identification of other work the change will affect. Saying what the other trades will run into is often what moves an approval.
Photos and redlines. NASA requires redlined documentation to accompany the FCR within two working days. Even where your contract sets no such clock, a marked-up sheet and dated photos make the request easy to approve.

The FHWA gives a short test for any change request. The contractor should assess why the change is necessary, its impact on the original scope, who is responsible for costs or delays, and who should pay. If your request answers those four questions, it is ready to send.
A short template
Use these fields in this order:
- Project, request number, date and your name
- Location (level, area, grid lines)
- Drawing and spec references with revisions
- Field condition found, with photos
- Proposed change and reason
- Cost: labor hours, material, equipment, markup
- Schedule effect and the date you need an answer
- Other work affected
Our change order template guide goes through the six fields a change order itself needs, so the FCR and the priced change line up.
How to submit an FCR and who approves it
The routing is set by your subcontract, but the pattern is steady. In Con Edison’s process the FCR is prepared by the field supervisor, routed to a project engineer who assigns the FCR number, keeps a copy for the log and contract files, and forwards copies to the others involved. NASA requires the project manager’s signature, sends the FCR to an engineer for evaluation, and says changes affecting cost or schedule go to the Contracting Officer for approval.
Owners also set dollar thresholds. Spokane Public Schools’ procedure says all change orders go through an approval process that weighs criticality, responsibility and who pays, cost and the consequences of disapproval. For major projects, board approval is needed once a change exceeds the board-approved contingency, set there at 5% of original contract cost for new buildings and 8% for remodels. Your request may be right and still wait on a meeting, which is why you flag the date you need an answer.
For your own routing, a written scope and a clear site implementation workflow make review faster: one site implementation workflow example shows how a defined sequence keeps site work consistent. Applied to an FCR, that means one numbered request, one named reviewer, one log.
A practical routine:
- Number and log it the day it is raised, before anyone argues about it.
- Send it to the person the contract names, not whoever is on site. Check the subcontract for the notice address and method.
- Keep proof of delivery. Smith Currie advises contractors to give prompt written notice by methods that show proof of the owner’s receipt, and never assume oral notice is enough.
- Chase on a schedule. A request with a response deadline gets a follow-up the day after that deadline.
- Convert the approval into a priced change order and attach the FCR as backup.
CO Hub is the tool we built for steps 1 to 5. It manages change orders and T&M tickets in one place, syncs in real time between field and office, works on mobile and produces per-project reporting. On the field side, your foreman raises the request from the job; in the office, your project manager sees it without a phone call. Our guide to the six stage change order workflow shows how the stages fit together.
Why notice timing decides who pays
The most expensive FCR mistake is not a bad form. It is a late one.
Federal contracts show the rule in its plainest form. Under the FAR differing site conditions clause, the contractor must give written notice promptly and before the conditions are disturbed, and no equitable adjustment is allowed without that notice. Federal-aid highway contracts say much the same: the party discovering the condition notifies the other in writing before the site is disturbed and before the affected work is performed, and no adjustment benefiting the contractor is allowed without the written notice.
Private contracts are different documents, but many carry similar notice clauses. Smith Currie notes that most contracts require the contractor to stop and notify the owner before disturbing a differing condition, and that failing to give the required notice may jeopardize recovery of added cost, time or both. It also notes that courts sometimes excuse strict compliance, but a contractor should not count on that.
The FCR is often how you meet that notice duty, so treat it as a notice document too. Our guide to what a notice of change must contain and when to send it lays out the timing question in detail, and the one on same-hour notices explains why speed matters on the job.
What to do when the field can’t wait for approval
Real jobs do not pause for paperwork. The crew is on the wall, the inspector is coming, and the answer is two days out.
The NECA subcontractor handbook calls proceeding under written protest the most prudent course when a signed change order is not possible, and describes stopping work as a drastic and risky option that may expose the contractor to delay costs if the stoppage is deemed wrongful. ConsensusDocs reports that courts and boards have consistently enforced duty-to-proceed clauses, making it almost always prudent to proceed under protest and file a claim for the changed work.
In practice:
- Send the FCR first, then say in writing that you are proceeding under protest and expect compensation and time.
- Track the changed work separately from base-contract work: its own cost code, its own timecards, its own photos.
- Get the daily sign-off on time and materials where the contract allows it.
- Never stop on your own unless there is a safety issue or your contract expressly gives you that right. Where a dispute is already forming, a construction attorney who knows your state’s law is the right call.
The records are what win these. The UC field order procedure above sets the adjustment from your backup documentation if you do not sign, so cost records kept day by day are your case. Our same-day field checklist for change order documentation lists what to capture before you leave the site, and the article on preventing and winning change order disputes covers what to do when the dispute comes anyway.
This is where labor tracking matters. The hours spent on a changed condition need to be separated from base scope when they are worked, not rebuilt from memory a month later. Time Budge, our labor tracking app, is priced at $199 per month per company, and it sits on the same login as CO Hub, so the field hours behind a change are in the same suite as the request. Foreman approvals matter here too; our piece on mobile timecard approvals explains how locking approved time keeps the numbers clean.
Common FCR mistakes
- Writing the request without a price. A reviewer cannot approve what he cannot size. Give at least a labor and material estimate, flagged as an estimate if needed.
- Skipping the time impact. Even a zero-day impact should say “no impact” so the record is complete.
- Using the wrong channel. A text to the superintendent is not the notice the contract names.
- Burying several issues in one request. One condition, one request. Separate numbers let the approved ones move while the contested ones wait.
- Losing the thread. An FCR that never becomes a change order leaves approved work unpaid. Track every request to a final status.
- Retyping. When the field request, the T&M ticket and the change order live in different files, numbers drift. Single sign-on across one suite removes the double entry.
Our perspective
Most subcontractors we talk about at Won2Build do not lose change order money because the owner said no. They lose it because the request was late, thin or sitting in someone’s truck.
The field sees the problem first, and the office prices it. Between those two sits a gap where photos, hours and the original note get lost. We designed CO Hub, and the whole Won2Build Hub around it, to close that gap: one login, field and office looking at the same record, and change orders and T&M tickets tracked together.
Our position is simple. The FCR should not be a separate chore. It should be the first entry in a change order that already has its photos, its labor and its history attached, so by the time you price the work you are copying nothing.
Jen Reese
Put your FCRs on one system
CO Hub is $59 per month per company, and The Hub and Takeoff are listed at $0 per month. The active field worker fee is $2 per month per active field worker. Plans are billed monthly per company after a free trial, and you can take the all-in-one bundle or a single app. Prices are on the pricing page, and you can read more about CO Hub change order management before you start.

If you also want the labor side connected, Time Budge tracks field hours on the same login.
FAQ
What does FCR mean in construction?
FCR usually means field change request, and some owners, such as utilities, use field change report. It is a written document that records a difference between the contract documents and field conditions, or a recommended change, and routes it for review. It is a request, not an authorization to be paid.
Is a field change request the same as a change order?
No. The FCR asks for or documents a change. A change order is the signed agreement that modifies the contract price, time or scope. Many FCRs turn into change orders once reviewed and priced, so keep the FCR as backup.
Who can submit an FCR?
This depends on your contract, but NASA’s procedure says an FCR can be initiated by anyone associated with the project. On most commercial jobs, a foreman or project manager raises it, and the subcontract names who must receive it and by what method.
Should we keep working while the FCR is pending?
Usually yes, under written protest, unless there is a safety issue. Duty-to-proceed clauses are enforced by courts, and stopping on your own can expose you to delay costs. Send the written notice first, track the changed work separately, and check your subcontract’s notice and claim terms.
What records should we keep?
Keep the numbered request, dated photos, marked-up drawings, the proof of delivery, daily labor and material records for the changed work, and the approval or protest correspondence. These are what support the price and time in the change order.
Sources
- NASA, Field Change Request (FCR) release
- Con Edison, quality assurance and control plan with FCR process
- University of California, Contract Modifications, Volume 5, Chapter 13
- FHWA, Companion Resource for Change Orders
- Caltrans, Construction Manual, Section 5-3 Change Orders
- Change Order Procedures, Applications for Payment
- Spokane Public Schools, Procedure 6950P
- Smith Currie, Differing Site Conditions Produce Differing Challenges
- eCFR, 48 CFR 52.236-2 Differing Site Conditions
- Cornell LII, 23 CFR 635.109 Standardized changed condition clauses
- NECA Subcontractor Contract and Collections Handbook
- ConsensusDocs, The Duty to Proceed and Right to Stop Work
Recommended
One login for estimating, bid tracking, change orders, and labor.
The Hub is free. Pay only for the apps you turn on.
Create your free Hub account- Timecard Rounding Rules for Subcontractors: What's LegalFederal timecard rounding rules in plain English for US subcontractors: the 7-minute rule, the neutrality test, California limits, and a worked payroll example.
- Construction Software Implementation: A Plan for SubcontractorsA step-by-step plan for rolling out construction software at a commercial subcontractor: goals, data cleanup, phasing, field buy-in, training and go-live.
- Estimate Review Checklist for Commercial SubcontractorsA practical estimate review checklist for commercial subcontractors: scope, takeoff, pricing, markups, risks and sign-off, so errors are caught before you submit.
