Why Subcontractor Change Orders Get Cut: Pricing, Backup and the Markup Fight
Learn why subcontractor change orders get cut—from weak pricing and missing backup to markup disputes—and how better documentation improves approval outcomes.
Subcontractor change orders rarely get rejected on entitlement. They get negotiated down because the pricing package cannot be verified. A GC project manager facing a lump sum number three weeks after the work, with no crew hours, no signed tickets and no quotes attached, has nothing to carry to the owner and cuts it to what is provable. The trade that ties every dollar back to a dated notice gets paid close to what it asked for.
Why GCs cut change order pricing instead of rejecting it
Rejection creates a dispute. A reduction creates a negotiation, and negotiations are won by whoever holds the record.
When a change order lands on a GC's desk, the project manager is not evaluating whether the work happened. They usually know it happened, they may have watched the crew do it. What they are evaluating is whether they can pass the number up to the owner and defend it. Anything they cannot defend becomes their exposure, so they shave it.
That is the mechanism behind nearly every markup dispute. The sub argues about percentage. The GC is actually arguing about the base cost the percentage sits on, because the base cost arrived as a single figure with no derivation. Markup becomes the visible fight because it is the only line that looks negotiable, but the money is lost in the undocumented hours underneath it.
The second pattern is timing. A change priced within days of the event is priced against live field data: the foreman still remembers which three men were pulled off the riser, the rental ticket is on the superintendent's desk, the material quote is current. Priced three weeks later, the same change is reconstructed from memory and a bank of hours that payroll already absorbed into the base contract. Reconstruction reads as estimation, and estimation invites a counter.
How to price a subcontractor change order so it survives review
A change order price is an argument with four parts: what caused the change, what it cost, how that cost was derived, and what the contract says you may add to it. Each part needs its own evidence.
Start with the causing document. Name it. An RFI response, an ASI, a revised drawing with its issue date, a field directive, a signed sketch from the superintendent. "Per field conditions" is not a cause, it is a shrug, and it signals that no one wrote anything down at the time.
Then build cost from the bottom.
- Labor: hours by trade and classification, crew composition, dates worked, and the burdened rate with the burden shown separately. Not "140 manhours" but four journeymen and an apprentice over three and a half days, listed.
- Material: quotes or invoices attached, with quantities tied to the scope described. Take-off quantities should reconcile to what was installed.
- Equipment: rental invoices or the published rate being applied, with hours or days of use. Owned equipment gets the rate schedule your contract references.
- Lower-tier work: the subcontractor's own priced proposal attached, with your markup on it shown at the lower-tier rate your contract specifies.
- Schedule impact: days requested, the activities affected, and whether you are claiming extended general conditions. Silence here is routinely read as a waiver.
Price it as a proposal, not an invoice. A proposal invites a conversation before the work; an invoice invites an audit after it.
T&M tickets versus a lump sum change order
Both mechanisms are legitimate. The failure is using the wrong one for the scope, or using T&M without the daily discipline T&M requires.
| Lump sum change order | Time and materials | |
|---|---|---|
| Use when | Scope, quantities and sequence are defined before work begins | Scope is still moving or work must start immediately |
| Risk carried by | The subcontractor, on productivity and quantity | The general contractor and owner, on duration |
| What must exist | A priced proposal accepted in writing before mobilizing | A signed ticket for every single day worked |
| Typical failure | Quantities grow past the proposal with no second notice | Tickets unsigned, or signed by someone without authority |
| Markup treatment | Calculated once, on the proposal | Applied per ticket or per rolled-up summary, per the contract |
The daily T&M ticket is the single most abused document on a jobsite. A ticket that names the workers, their classifications, start and stop times, equipment on site, materials consumed and the work performed, signed that day by the superintendent, is close to unassailable. A ticket that says "misc. work, 3 men, 8 hrs" and is signed a week later is a memo.
Signature authority matters as much as the signature. If the person signing cannot bind the GC, the ticket proves the hours were observed and nothing more. Confirm at the start of the job who signs field tickets and put the answer in writing. When no one is authorized on site, photograph the work with timestamps and send the ticket by email the same day, which at least establishes contemporaneous notice.
The markup fight, and why it is usually a contract-reading fight
Markup disputes almost always resolve to one of five questions, and all five are answered in the subcontract's changes clause:
- What overhead and profit percentages apply to self-performed work?
- What reduced percentage applies to work performed by lower-tier subcontractors?
- Is markup applied to labor burden, or only to base wage?
- Are bond and insurance costs marked up, added at cost, or excluded?
- Is markup permitted on credits, and is it applied symmetrically?
Quote the clause in the proposal. Show overhead and profit as separate, calculated lines rather than burying them in a unit rate. A markup that is visible and sourced is hard to negotiate down, because the GC is no longer arguing with you, they are arguing with the document they drafted.
The asymmetry on credits is worth watching. Many clauses let the GC take a full credit on deleted scope while capping what you may add on new scope. That is a contract negotiation issue, not a change order issue, but it is why a net-zero scope swap can cost a trade real money if nobody reads the clause until the swap happens.
Building the record before you need it
The pricing package is assembled from documents that either exist or do not by the time you need them. Nothing on this list can be created retroactively with any credibility.
- Written notice, dated, issued inside the contractual window, referencing the causing document. Issue it before the pricing is ready. Notice preserves the right; pricing follows.
- Daily reports that record the extra crew separately from base contract crew, on the day.
- Signed field tickets for every T&M day.
- Photographs with timestamps and location, of the condition before the change and the work after it.
- Correspondence on the change kept in one thread, not scattered across three email chains and a text message to the superintendent.
- A running log of change order status, so that at any point you know which numbers are approved, which are submitted, which are priced and sitting unanswered, and what the open exposure totals.
That log is the difference between negotiating from a position and negotiating from memory. It is also what lets a project manager answer the owner's question about pending costs without a two-day scramble, which is covered in more depth in our guide to managing construction change orders in seven steps.
What delay costs the trade specifically
Every week a priced change order sits unanswered, the cost is carried on your balance sheet. The crew was paid. The material was bought. The GC has no urgency to resolve a number that has not yet hit their owner approval cycle, and the owner's rep will not approve what the GC has not forwarded.
Two things shorten that cycle. The first is submitting a package complete enough that the GC can forward it the same day without building anything themselves. The second is visibility: when a trade, GC and owner all see the same pending change log with the same dates and the same amounts, the item that has sat for eleven days is visible to everyone, and silence stops being free. That is the practical argument for shared change order workflows rather than parallel spreadsheets, and it is why reducing change order delays is as much a documentation problem as an approval problem.
There is also a reputational dimension that specialty trades feel more sharply than anyone else on the project. A trade whose change orders arrive complete, priced against the contract and backed by signed tickets is easy to work with, and GCs remember that at the next bid. A trade whose changes arrive late and get argued about is expensive to administer, and that reputation follows the firm. The discipline that connects field documentation to cost is the same discipline that wins the next invitation.
Platforms like INGENIOUS.BUILD exist to hold that chain together: the notice, the field ticket, the priced proposal, the markup calculation and the approval all sit on one record visible to the trade, the GC and the owner at the same time, so the number being negotiated is the number everyone can see the derivation of. If you are evaluating what that looks like in practice, our overview of change order management software covers what to test before you commit.
The underlying point is simpler than any system. Change orders are not won by argument. They are won by the documents you created on the day the work happened, and by how fast you put them in someone else's hands.
Frequently asked questions
What is a standard contractor markup on change orders?
There is no universal standard. Markup on change orders is set by the subcontract, and most agreements cap overhead and profit on self-performed work somewhere in the low-to-mid teens, with a lower cap on work performed by lower-tier subs. The controlling number is in the contract's changes clause, not in industry convention.
Should a subcontractor price a change as time and materials or lump sum?
Price lump sum when the scope, quantities and sequence are known before work starts, because a priced proposal locks in markup and schedule impact. Use time and materials when scope is still moving or the work must proceed immediately. T&M requires daily signed tickets naming workers, hours, equipment and materials, or the hours become unprovable later.
What backup documentation should a subcontractor submit with a change order?
A defensible package includes the original notice with its date, the document that caused the change, a labor breakdown by trade and classification with crew hours, material quotes or invoices, equipment rates with hours, signed field tickets for any T&M work, the markup calculation referencing the subcontract clause, and the schedule impact.
Why does a general contractor cut a subcontractor's change order price?
Usually because the submission cannot be verified. When a lump sum arrives weeks after the work with no crew hours, no signed tickets and no quotes, the GC's project manager has nothing to carry forward to the owner and reduces the number to what is provable. Entitlement is rarely the issue.
How quickly does a change order have to be submitted?
Written notice is typically due within a short window measured in days from the event, and a priced proposal within a further period, both defined in the subcontract. Missing the notice window can waive the claim entirely regardless of merit, so notice should be issued before the pricing is complete.
How can a subcontractor avoid markup disputes on change orders?
Quote the subcontract's changes clause in the proposal, show overhead and profit as a separate calculated line rather than embedding it in unit rates, apply the correct lower rate to lower-tier work, and state bond and insurance treatment explicitly. A markup that is shown and sourced is difficult to negotiate down.
