Field change order and takeoff field guide for data centers

The field change order, and where the money is won or lost

A field change order captures added or changed scope that shows up after the contract is signed, and it converts that field work into a priced, defensible amount the owner has agreed to pay. The base contract covers the base scope. Everything past it is a change, and a change you do not document and price before you build it is work you did for free.

On a data center the changes come fast and they come big. The slab gets cored where the drawing showed clear floor. The busway run grows three sections because the gear landed where it landed, not where the plan said. Integrated systems testing during commissioning kicks back a control sequence that adds devices nobody priced. Each one is a chance to get paid or a chance to eat the cost, and the difference is almost never the work itself. It is the paper.

Here is the part crews learn the hard way. The field is good at building and bad at billing. A foreman will install the change, do it well, and move on, and three weeks later the office tries to bill it with no notice on file, no signed ticket, and a quantity nobody measured. That change is dead. The work happened, the cost is real, and there is nothing to defend it with. The change order is where the field quantity becomes a number on a pay application, and that handoff is the weakest link on most jobs.

What are the types of field change order?

There are five common origins for a change, and they are handled differently because the entitlement is different for each. Knowing which one you are looking at tells you what you have to prove to get paid.

An owner-directed change is the cleanest. The owner or the design team tells you to add or alter scope, in writing, and your job is to price it and proceed. The entitlement is rarely in dispute. The fight, if there is one, is over the number. An RFI-driven change starts as a question. You ask how to build something the documents do not resolve, the answer comes back changing the work, and that answer is the trigger. The RFI and its response are your entitlement, so keep them.

A differing or unforeseen condition is what you hit when the field does not match the documents: rebar where the drawing showed clear concrete, a utility that is not on the plan, soil that will not hold. The standard contracts treat concealed and unknown conditions as a basis for an adjustment, but only if you stop and give notice before you disturb the condition. A design error or omission is scope that should have been in the documents and was not. That one gets political, because pricing it as extra invites the argument that it was always your responsibility. Document what the drawings actually showed at bid time, because that snapshot is the whole case.

When does a change require notice, and what is the deadline?

The trigger is the moment you recognize that work has been added or changed beyond the contract. The clock starts there, not when you finish the work and not when the office gets around to it. Almost every contract sets a deadline to give written notice of a change or a claim, and missing it can waive the right to be paid no matter how real the cost is.

Under the AIA A201 general conditions, the common framework on commercial and data center work, notice of a claim is generally required in writing within 21 days of the event or of recognizing the condition that gives rise to it, and concealed or unknown conditions carry their own short window, shortened to 14 days in the 2017 edition. ConsensusDocs uses its own timing. Do not carry these numbers in your head as gospel. The edition, the supplementary conditions, and any owner amendments rewrite them constantly, so the deadline you actually live under is the one in your contract, every time.

Late notice is the single most avoidable way to lose a legitimate change. The argument the owner makes is that they were deprived of the chance to mitigate, to redirect, to decide not to do it. A contemporaneous notice kills that argument before it starts. Blunt version: if you recognize a change and sit on it, you are gambling a real cost against a calendar, and the calendar usually wins.

Time and materials vs lump-sum change pricing

There are two ways to price a change, and the choice usually comes down to whether the scope is known before you build it. A lump-sum proposal, sometimes called a fixed-price change, is what you submit when you can take the work off and price it cleanly up front. You count it, you price it, you add markup, and you hand over one number the owner accepts or negotiates. The risk is yours, so the takeoff has to be right.

Time and materials, T&M, is for work you cannot define in advance. You bill the actual labor hours, the actual material, and the equipment, against agreed rates, and you track it as you go. T&M is the default for emergency work, for changes where the extent is unknown until you open it up, and for differing conditions where nobody can price the unknown. The owner carries the risk on quantity, which is why owners resist it and why the documentation has to be tight enough to survive that resistance.

The honest read is that owners want lump sum because it caps their exposure, and contractors reach for T&M when the scope is murky because fixed-pricing an unknown is how you lose money. Pick lump sum when you can take it off with confidence. Pick T&M when you cannot, and then prove every hour.

Force account: the signed daily ticket is the claim

Force account is T&M work tracked on a daily ticket and signed by the owner's representative the day the work happens. The ticket lists the labor by classification and hours, the equipment by unit and hours, and the material used, and it gets a signature before the crew leaves. That signed daily ticket is not paperwork around the claim. It is the claim.

The reason the signature has to happen daily is memory and turnover. Try to reconstruct three weeks of T&M from time cards and nobody remembers what was extra and what was base, the owner's rep who watched the work has rotated off, and the new one has no reason to sign for hours he did not witness. Get it signed at the end of the shift, while the person who watched the work is still standing there. A signature that says the hours and quantities are correct is worth more than a binder of unsigned backup.

Two field habits separate the crews that get paid from the crews that argue. First, the signer acknowledges the hours and quantities, even if the contract says the signature is not an admission of entitlement, because the number is now agreed and only the right to it is left to settle. Second, you keep the ticket organized as you go, not in a shoebox for the office to sort later. A running daily record, tracked the same way every day, is what turns a force-account log into an invoice instead of a fight. This is the kind of running record FieldOS keeps without anyone retyping it at the trailer.

How do you take off a field change?

A field takeoff is the count and measure of the added scope, done where the work is, and it is the input to the price. You quantify the change in the units the work is built in: count for devices, terminations, supports, and fittings; length for conduit, cable, busway, and tray; area for housekeeping pads, fireproofing, and floor. Get the field quantity right and the price has a foundation. Get it wrong and every markup you add is multiplying an error.

The discipline is to measure the routed and installed reality, not the plan. The conduit goes up, over, and around the structure, so the field length beats the straight-line drawing distance, often by a lot. The cable pull includes the slack, the training radius at the gear, and the terminations at both ends. On a copper or tray scope, the fill and the drop counts come off the field, not the riser diagram, which is exactly the discipline the cable tray fill and copper drop takeoff guide gets into for that trade.

This is where the field quantity becomes a priced line instead of a number on a scrap of cardboard. You count and measure once, in the field, and the quantity flows straight into material and labor without being retyped, rounded, or lost between the deck and the office. That is the whole point of taking off in the field with takeofffielddc: the count you make standing in the work is the count that gets priced, so nothing leaks out of the change between the measure and the money.

Pricing the change from the field quantity

Pricing turns the field quantity into a number with five parts: material, labor, equipment, markup, and the bond and insurance adder. Get each part from a defensible source and the price holds up under review. Pull any of them out of the air and the first sharp owner's rep finds the soft spot.

Material is the quantity plus waste, priced at real cost with documentation. Waste is a real percentage that varies by material and how it installs, not a round-up you invent. Labor is the hours the work takes, found by applying a labor unit, a per-unit install time, to the quantity, then adjusting it with a labor factor for the conditions. Hours times the labor rate gives the labor cost, and the labor rate is the burdened rate, wages plus the burden, not the bare wage. Equipment is the lifts, the cores, the welders, and the trenchers, at their rates for the time used.

Then the markup, the overhead and profit. The standard contracts entitle the contractor to OH&P on a change but, in the case of the AIA A201, do not actually state the percentage, which leaves it to the agreement or the supplementary conditions. When a change has both adds and credits, the OH&P is commonly figured on the net increase, not on the gross add, which is the detail that gets negotiated. Confirm your allowed markup against the contract before you submit, because a number the contract does not support gets stripped out and you have taught the reviewer to distrust the rest of your sheet. Last, the bond and insurance adder, where the contract allows it, sits on top. RSMeans-style cost data is a fine sanity check on a unit price, but the project's own agreed rates govern when they exist.

Labor productivity and the impact nobody prices

The direct cost of a change is the easy part. The hard part, and the part most crews never recover, is the productivity loss the change causes everywhere else. Work done out of sequence costs more per unit than the same work done in its planned order, and a change that forces you out of sequence is charging you twice: once for the new scope and once for the inefficiency it injects into the base.

The mechanisms are specific. Stacking of trades, where the change crowds more crews into the same space than the area can hold, drops everyone's output. Out-of-sequence work means you build it, leave it, and come back, losing the rhythm and the setup each time. Acceleration, where the owner adds scope but holds the date, forces overtime and added crews, and crews working long hours and unfamiliar partners produce fewer units per hour. None of this shows up on a takeoff. All of it shows up in the actual hours.

The cumulative impact claim, the one for the death-by-a-thousand-changes erosion of productivity across the whole job, is the hardest thing to get paid for and the easiest to wave away, because the owner says prove it. You prove it with measured-mile comparisons, with the labor curves before and after the changes started, with the daily records that show the crowding and the resequencing as they happened. If you did not record it contemporaneously, you will not reconstruct it later. Price the direct work in every change, and reserve your rights on impact in writing, so the cumulative claim is not the first time the owner hears about it.

The documentation that wins the change

The change is won or lost on the contemporaneous record, the paper made while the work was happening, not after. A reviewer trusts a dated photo and a signed daily ticket. A reviewer discounts a narrative typed up three weeks later to support a number. The whole game is making the record at the moment, so the change defends itself.

The record that wins has a few pieces working together. Photos of the condition before you touch it, time-stamped, showing what the documents did not. The daily report that ties the crew, the hours, and the location to the change. The signed T&M or force-account ticket. The RFI and its response, or the written direction, that establishes the entitlement. And the schedule fragment that shows the impact, if there is one. Each piece alone is an assertion. Together they are a case.

Photograph the differing condition before you disturb it, every time, no exceptions. Once you have cored the slab or pulled the cable, the condition you are claiming for no longer exists, and a photo taken after is worth nothing. Keep the photos, the tickets, and the daily reports attached to the change as they are made, so the package assembles itself instead of being reconstructed under deadline. A single change file that travels with the work, which is how teams run it in FieldOS, beats a search through three apps and a truck cab when the owner asks for backup.

Can a change order add time to the schedule?

Yes, and the time is a separate ask from the money. A change can add cost, add time, or add both, and the two are recovered on different proof. The direct-cost change pays for the work. The time extension protects you from liquidated damages and pays the extended general conditions for the days the change pushed the job out. Ask for the money and forget the time, and you can win the change and still owe delay damages on the schedule the change blew.

Not every change moves the date. A change that adds work off the critical path consumes float, not time, and asking for a time extension on non-critical work invites a fight you do not need. A change on the critical path, or one that consumes the last of the float, moves the completion date and is worth a time-extension request. Knowing which one you have means knowing where the change lands in the schedule, which means a real schedule analysis, not a feeling.

Reserve the time even when you cannot quantify it yet. The change that looks like five days of impact in the moment can turn into twenty once it ripples through the sequence. Note in the change that you are reserving the right to a time extension and the associated costs, price the direct work now, and quantify the time when the impact is known. Cost and time are two asks. Make both.

The change order and the construction change directive

The contract gives you two instruments for a change, and they are not interchangeable. A change order, in the AIA A201 framework, is a written agreement signed by the owner, the contractor, and the architect, fixing the change in scope, the adjustment to the contract sum, and the adjustment to the contract time. All three sign because all three agree. The change order is the finished, settled change, with the price and the time nailed down.

A construction change directive, the CCD, exists for when you cannot wait for all three to agree. It is signed by the owner and the architect, not the contractor, and it directs you to proceed with a change before the price and the time are settled. The contractor is bound to perform the directed work, and the adjustment gets resolved afterward and eventually rolled into a change order once everyone agrees. The CCD is the mechanism that keeps the job moving when the change is urgent or the number is still in dispute.

ConsensusDocs and other contract families have their own versions of the same two-step idea: a settled, signed change and a directive to proceed ahead of settlement. The names and the signatures differ, so read your contract for which form applies and who has to sign it. The concept is constant. There is a fully agreed change, and there is an order to build now and settle later.

Disputed changes: building under protest while the price is open

Sometimes the owner directs you to build a change you do not agree is a change, or at a price you have not accepted, and the schedule will not wait for the argument to finish. The contract's answer is the directive, a CCD or its equivalent, which lets the owner order the work and you to do it while the entitlement and the number stay open. You build it. You do not concede it.

Proceeding under protest is how you keep your rights while keeping the job moving. You perform the directed work, you state in writing that you are proceeding under protest and reserving your right to the cost and time, and you track the work on force account so the actual cost is captured as it happens. The protest is not a refusal. It is a flag that says you are building this because you were directed to, not because the dispute is settled.

The trap is going quiet. A contractor who builds the disputed change without protest and without tracking the cost has, in practice, accepted it, because there is no record that says otherwise and no backup to price it. If you are directed to build something you intend to claim, say so in writing before you start, and run it on force account from the first hour. Silence reads as agreement, every time.

Getting the approved change into the pay application

An approved change order is not money until it lands on a pay application and gets certified. The change has to be added to the schedule of values as its own line, billed as it is completed like any other line, and carried through the application with its own percentage complete and retention. A change that is approved but never added to the schedule of values quietly never gets billed, and that happens more than anyone admits.

The timing matters. Get the executed change onto the next application after it is signed, not the one after that, because every cycle it sits unbilled is cash you financed for the owner for free. Reconcile the approved changes against the schedule of values each period so an executed change does not fall through the gap between the change log and the billing.

Directed-but-unsettled work is the harder case. A CCD without an agreed price cannot be billed as a fixed line, but the force-account cost is real and the contract usually allows billing the documented cost of directed work pending final adjustment. Confirm how your contract handles billing for unsettled directives, because leaving directed work entirely off the application until it settles can starve the job of the cash it has already spent.

Why do change orders get rejected?

Change orders get rejected for a short list of reasons, and almost all of them are paperwork failures, not pricing disputes. The cost is usually real. The defense is what is missing. Fix the defense and the rejection rate drops faster than any sharpening of the number ever will.

No notice is the first killer. The work happened, but the contract deadline to notify passed, and the owner uses the late notice to waive the claim. No signed ticket is the second. On T&M and force-account work, an unsigned ticket is an assertion the owner is free to dispute hour by hour. Scope was in the base is the third, and it is the most embarrassing, because it means you billed as extra what you already agreed to do. No backup is the fourth: a lump-sum number with no takeoff, no quotes, and no labor basis behind it gives the reviewer nothing to certify, so they do not. Math errors are the fifth and the most avoidable, and they do more damage than the dollars they cost, because a sheet that does not add up teaches the reviewer to distrust everything on it.

The pattern across all five is that the field built the work and the paper did not keep up. The change that gets paid is the one where the notice, the takeoff, the signature, and the math were handled while the work was live, so that by the time it reaches the reviewer there is nothing left to reject.

What to document for every change

Run a single change log and track the same fields on every change from the day it is recognized. The log is how you reconcile what was noticed against what was priced, what was approved against what was billed, and what is still open. A change that is not on the log is a change that gets forgotten until it is too late to claim.

Field checklist

Common mistakes

• Building the change before documenting and pricing it, which is working for free.
• Running T&M on unsigned tickets the owner can dispute hour by hour later.
• Skipping the before photo on a differing condition that no longer exists once disturbed.
• Missing the contract notice deadline and handing the owner a waiver argument.
• Pricing the direct cost with no markup, or a markup the contract does not support.
• Claiming base scope as extra and losing credibility on the whole change.
• Asking for the money but forgetting the time extension, then owing delay damages.
• Letting an approved change never reach the schedule of values, so it never gets billed.
• Reconstructing the productivity-impact case after the fact instead of recording it as it happened.

Standards and references

The governing document is the contract, and on most commercial and data center work that means a general-conditions document and its supplementary conditions. The AIA A201 General Conditions of the Contract for Construction is the common framework. It defines the change order as the agreement signed by owner, contractor, and architect, the construction change directive as the owner-and-architect instrument to proceed without full agreement, and it carries the notice-of-claim and concealed-condition timing that controls your deadlines. ConsensusDocs is the other widely used family and handles the same ideas with its own articles and timing.

The numbers and article references move between editions and get rewritten by supplementary conditions and owner amendments, so treat any section number as a pointer, not an authority. The OH&P entitlement on changes is recognized in these documents, but the percentage is commonly left to the agreement rather than fixed in the general conditions, which is why your allowed markup lives in the contract, not in a rule of thumb. Read the contract you signed for the deadlines, the markup, and the forms, every time, because that document, not this guide and not industry custom, decides what gets paid.

For pricing the underlying work, company estimating standards and published cost data such as RSMeans-type unit-cost references are reasonable starting points and sanity checks, but the project's agreed rates and unit prices govern wherever they exist. Commissioning and integrated systems testing generate a steady stream of late changes on data center jobs, so coordinate the change process with the commissioning and turnover plan covered in the data center commissioning and operations overview.

Units, terms, and definitions

Change work carries its own vocabulary, and the same idea goes by different names across contract families and trades. Quantities are taken off in the units the work installs in: each or count for devices, terminations, and supports; linear feet for conduit, cable, busway, and tray; square feet for pads, fireproofing, and floor.

The terms below are the ones that decide how a change is documented, priced, and paid. Learn the difference between a change order and a directive, and between T&M tracked loosely and force account signed daily, because those distinctions are exactly where changes get lost.

Change order (CO)

A written, signed agreement fixing the change in scope, contract sum, and contract time; the settled change

Construction change directive (CCD)

An owner-and-architect instrument directing the work to proceed before the price and time are agreed, settled later by change order

Time and materials (T&M)

Pricing by actual labor, material, and equipment against agreed rates, used when scope cannot be taken off in advance

Force account

T&M work tracked on a daily ticket signed by the owner's representative the day it happens; the signed ticket is the claim

OH&P

Overhead and profit, the markup on a change; entitlement is recognized but the percentage is commonly set by the contract

Labor factor

An adjustment to base install hours for conditions like out-of-sequence work, stacking, congestion, or overtime fatigue

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is commissioning in construction?
• What is the maximum cable tray fill?
• What is an as-built drawing?
• Why do battery rooms need ventilation?
• What is the difference between an F-rating and a T-rating?