Contracts

What is a change order request in construction?

A change order request (COR) is the contractor's written proposal asking the owner to change the contract's scope, price, or schedule. It becomes a binding change only when it is approved as a change order.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

A change order request is the paperwork that starts most changes. The contractor sees something that is outside the contract, describes it, prices it, and sends it to the owner or architect. Some contracts call it a change proposal, a potential change order (PCO), or a request for change. AIA's G709 Work Changes Proposal Request runs the other direction: it is the architect asking the contractor to price a possible change.

A COR is not approval. Until the owner signs a change order, the money is unearned and the scope is still in question. That gap is where contractors lose money.

What a good change order request includes

  • A reference to what triggered it: an RFI answer, an architect's supplemental instruction, a revised drawing, or a field condition.
  • A clear scope description with drawing and spec references.
  • A cost breakdown: labor hours and rates, material, equipment, subcontractor quotes, and markup per the contract.
  • The schedule impact in days, or a statement that time is reserved.
  • A response deadline and a note on what happens to the schedule if the answer comes late.

How a COR works on a real job

Say a drywall sub on a $6 million office building gets RFI 42 answered: the architect adds a rated shaft wall at the elevator lobby that was not on the bid drawings. The sub writes COR 7 for 1,200 square feet of shaft wall at $14,600 including markup and two additional days. The GC reviews it, adds its own markup, and sends it to the owner as GC COR 19 for $16,060. The owner's rep asks for backup on the labor hours, gets it, and signs change order 11 two weeks later.

Two weeks of waiting is normal. Two months is a problem, especially if the sub has already built the wall. Track the age of every open request, and raise the oldest ones at every owner meeting until they close.

Why change order requests stall

  1. Missing backup. Owners will not approve a lump sum with no breakdown.
  2. No reference to the trigger, so the owner argues the work was in the base scope.
  3. Requests submitted weeks after the work, past the notice window in the contract.
  4. Too many small CORs sent one at a time. Some owners respond faster to a weekly batch.
  5. The owner's approver changes and nobody re-sends the open list.

Related terms

See change directive, scope gap, and notice of claim. For the process side, read how to track change orders across projects and how subcontractors should track change orders.

Frequently asked questions

Is a change order request binding?

No. It is a proposal. It becomes binding when both parties sign a change order or the owner issues a change directive for the work.

What is the difference between a COR and a PCO?

Terms vary by company. A potential change order is often an internal placeholder for a possible change; a COR is the priced request sent to the owner. Some firms use the terms interchangeably.

Should I start work before a COR is approved?

Only if you have a written directive to proceed. Starting on an unapproved request is the most common way contractors end up doing free work.

How long should an owner take to respond?

The contract may set a response time. If it does not, put a requested response date on the COR and follow up weekly.

Sources

  1. AIA Contract Documents: G-Series contract administration and project management forms
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment