SubAscentVisit Website →
← Back to blog

Cut Rejections: 6 Item GC Change Order Checklist for Trade Subs

October 9, 2026
Cut Rejections: 6 Item GC Change Order Checklist for Trade Subs

A GC change order approval is a signed amendment that changes the contract sum, the schedule, or both, and until that signature exists, you have no contractual right to extra payment. The general contractor signs it, the owner usually has to sign off too, and the architect typically only advises. The one thing to do the moment a change surfaces: issue a PCO or Notice of Change, or get a written directive, before you touch the extra work.

TL;DR:

  • Issue a PCO or Notice of Change within your contract’s notice window, before starting extra work; a missed deadline can erase payment rights.
  • Do not rely on an architect’s verbal approval: the GC and usually the owner must sign, or provide a written directive before work begins.
  • Tie every cost line to the triggering RFI or directive, dated evidence, takeoffs, labor rates, and supplier quotes instead of submitting a lump sum.
  • Request a Time Impact Analysis only when the change affects the finish date; if critical path work is delayed, request a formal schedule update too.
  • After execution, add the signed amendment to the next pay application, and record its labor separately from base contract hours.
Subascent
Keep Change Orders Moving
Subascent supports trade businesses managing change order workflows with GCs, so you can keep job changes and billing in view.
Visit Subascent

Table of Contents

The approval workflow from PCO to executed change order

Every change order moves through the same basic sequence, whether it starts with a dropped ceiling tile or a redesigned electrical panel.

  1. Notice. You spot the change (a conflict, a missing detail, an owner request) and issue a Potential Change Order or Notice of Change right away, inside your contract's notice window.
  2. Proposal. You price the work and submit a Change Order Request (COR) with scope, cost, and schedule impact.
  3. Review. The GC checks the submission, the architect or engineer may weigh in on design intent, and the owner approves the cost and time impact.
  4. Execution. Everyone signs, and the change order becomes part of the contract. It now adjusts your contract sum and, if a time extension was granted, your completion date.

If the owner or GC wants work started before agreement on price, they may issue a change directive, a unilateral order to proceed while cost stays unresolved. A negotiated change order is cleaner: price and time are locked before you start. Either way, once it's executed, that change order goes on your very next pay application. Architects generally act only in an advisory capacity on design and safety matters; a verbal nod from an architect carries no contractual weight on its own, according to AIA guidance on change management.

Approval-ready submission: the six elements reviewers expect

A GC reviewer looks for a complete package on the first pass. Missing any of these gives them a reason to send it back instead of signing it.

  • Project and contact information: job name, CO number, date, and who submitted it.
  • Bounded scope: a clear description tied to specific drawing sheets or spec sections, not a vague summary.
  • Broken-out cost: labor, material, equipment, subcontractor quotes, and markup listed separately, never as one lump figure.
  • Schedule impact: a stated number of days, with a short Time Impact Analysis when the change touches the critical path.
  • Supporting backup: photos, RFI references, vendor quotes, and meeting minutes that back every line item.
  • Standard forms where applicable: many GCs still route changes through AIA G701 or G701S, so matching that format avoids unnecessary reformatting.

Our eight-item documentation checklist walks through exactly what belongs in each attachment. A submission lacking broken-out costs is one of the most common reasons GCs stall approval, since it gives a reviewer nothing to verify against a vendor quote or labor rate, according to guidance on demonstrating entitlement for change orders.

The three pillars: entitlement, causation, quantum

A defensible change order request proves three things, and a reviewer is checking for all three before signing anything, per the entitlement framework from Long International.

  • Entitlement: the contractual right to be paid. Point to the triggering document, an RFI answer, a Construction Change Directive, or written owner direction.
  • Causation: proof the GC's event, not your error, caused the cost. Dated photos, annotated drawings, and a direct RFI cross-reference carry this.
  • Quantum: the dollar amount, built from unit takeoffs, labor rates, and supplier quotes rather than a round number.

A lump sum of "$8,400 for extra framing" is weak evidence. A line-item breakout showing 40 labor hours at a stated rate, 320 board feet of lumber at a quoted price, and a dated RFI answer authorizing the change is defensible.

Pro Tip: Attach the triggering RFI number directly in your cost breakdown line, not just in a cover memo. It gives the reviewer one less document to hunt for.

Schedule impact and when a Time Impact Analysis is worth submitting

Not every change deserves a time extension. If the added work can absorb into existing float without pushing the project's finish date, a reviewer has no reason to grant one. A Time Impact Analysis tests this directly by comparing the delayed finish date against your currently accepted baseline schedule, according to Long International's explanation of time impact analyses.

  • Identify the activities the change actually touches and their durations.
  • Show the logic ties: what the delayed activity feeds into downstream.
  • State your conclusion plainly: how many days, and whether the delay hits the critical path or just eats float.

If the change clearly affects a critical-path activity, ask for a formal schedule update alongside the TIA rather than relying on a verbal estimate of lost days.

What GCs check before they sign (and why they reject submissions)

GC reviewers run through the same four checks on every submission, generally in this order.

  1. Entitlement: is there a triggering document that justifies the change at all?
  2. Scope bounding: is the work clearly defined, with no room to sneak in unrelated items?
  3. Pricing support: does every cost line tie to a quote, rate, or takeoff?
  4. Schedule impact: is the time claim backed by logic, not just a number?

A submission that fails any one of these gets delayed or rejected outright. The most common failure points are a missed notice deadline, lump-sum pricing with no backup, a missing vendor quote, scope that overlaps a previous change order, or wording vague enough that the GC can't tell what's actually being billed. Missing the contractual notice window is especially damaging because it can extinguish your right to payment entirely, regardless of how well the rest of the package is built, according to ConsensusDocs' analysis of notice and timing provisions. GCs often cross-check your request against the RFI log and prior pay applications to catch duplicate billing before it reaches the owner.

Pro Tip: Lead your submission with a one-paragraph cover memo that states the triggering event, the dollar amount, and the day impact in plain language. Reviewers approve faster when they don't have to dig for the summary.

A step-by-step submission workflow for trade subs

Follows this sequence from the moment you spot a change through getting paid for it.

  1. Document immediately. Take dated photos, mark up the affected drawing sheet, and note who directed the change.
  2. Issue notice fast. File a PCO or Notice of Change inside your contract's notice window, even before pricing is final.
  3. Build defensible pricing. Break out labor, material, and equipment with line-item takeoffs and real vendor quotes, never a round estimate. Our HVAC estimating workflow covers this for mechanical scopes, and the same discipline applies across trades.
  4. Separate time sheets. Keep base contract hours and change order hours on different lines so reviewers can verify added labor without a dispute over double billing.
  5. Submit the full package. Include a short cover memo, cross-reference the triggering RFI or directive, label every attachment, and add a TIA when the schedule is affected.
  6. Bill it once executed. Add the signed change order to your schedule of values and the next pay application, and log it in a running CO tracker so nothing falls through the cracks.

Field examples and a checklist worth keeping on your desk

A defensible COR for a plumbing sub might look like this: 18 labor hours at a stated crew rate, two 4-inch cast iron fittings at an actual supplier quote, equipment rental for a jackhammer at a daily rate, and a reference to the RFI that directed the rerouting. No round numbers, no "miscellaneous."

Cast-iron fittings and jackhammer at plumbing reroute

Keep an eight-item checklist on every submission: project info, CO number, bounded scope, labor breakout, material breakout, equipment breakout, schedule impact statement, and supporting backup (photos, RFI, quotes). Our construction document control guide covers how to keep that evidence organized from day one instead of scrambling for it at submission time, and this field guide for trade contractors walks through similar templates from an operations consulting lens.

Three habits that cut down disputes: confirm every verbal directive in writing within 24 hours, never let base work and CO work blur on the same time sheet, and send your pricing backup before the GC asks for it rather than after.

Why most change order advice misses the real problem

Most guidance on change orders focuses on paperwork, get a signature, fill out the form, attach a photo. That's not wrong, but it treats the symptom. The real failure point is timing. A sub who documents perfectly but issues notice three weeks late has already lost the argument, notice provisions are enforced strictly, and a missed window can erase entitlement no matter how clean the cost breakdown is.

Why most change order advice misses the real problem — overview diagram

The second overrated piece of advice is "get everything in writing." True, but vague. What actually protects you is tying every dollar to a specific triggering document, logged the same day the change happens. Reviewers aren't rejecting submissions because subs are dishonest. They're rejecting them because the paper trail doesn't connect cause to cost in a way they can verify in five minutes.

If you take one thing from this guide, make it this: build your notice and documentation habit around the moment of discovery, not the moment of submission. Everything else, the forms, the markup percentages, the TIA format, is secondary to that one discipline.

— Dave

How Subascent helps you track and bill change orders faster

We built this platform for specialty trade subcontractors who want to avoid losing money to slow change order approvals and missed notice windows. Our platform keeps a running CO log tied to each job, so every PCO, attachment, and approval status lives in one place instead of scattered emails and sticky notes.

Subascent

That means fewer missed notice deadlines, faster GC sign-off because your backup is already organized, and a change order that flows straight onto your next invoice without manual re-entry. For current pricing details, visit the company's website. If pricing markup is where you're leaving money on the table, our piece on change order pricing is worth a look too. Visit Subascent to see how the workflow fits your trade and start a trial.

FAQ

Do change orders need to be approved?

Yes. A change order has no contractual effect until it's signed by the GC and, in most contracts, the owner. Performing extra work without a signed change order or a written directive puts your payment rights at risk, according to The Porter Firm's analysis of change order disputes.

When can a contractor refuse to accept a change order?

A GC can decline a change order request when it lacks entitlement, such as no triggering document, when the scope isn't clearly bounded, or when the pricing has no supporting backup. Missing the contract's notice deadline can also forfeit the right to that change order entirely.

Who approves a change order?

The general contractor and typically the owner sign off on cost and schedule impact. The architect or engineer usually plays an advisory role on design intent and does not have contractual authority to approve changes on their own, per AIA best practices.

What is the process of a change order?

It starts with a notice or Potential Change Order, moves to a priced proposal with scope and cost backup, goes through GC and owner review, and ends with execution once everyone signs. Once executed, it adjusts the contract sum and gets added to the next pay application.

Sources