Home › Construction Administration › Proposed Changes (CCNs)

CA FIELD GUIDE · 06

Proposed Changes & CCNs: Price It Before Anyone Builds It

A proposed change asks the contractor one question: if we made this change, what would it cost and how much time would it add? Here's how to ask it properly, and how to review the answer.

Construction pricing reviews: a guide for architects.

THE SHORT ANSWER

A proposed change is a request for the contractor's price and schedule impact for a potential change, before anyone builds it. In Canada it's often called a CCN (Contemplated Change Notice); in the US, a Proposal Request or PCO (Potential Change Order). Pricing is not authorization. The work only proceeds once a change order or change directive is issued.

KEY TAKEAWAYS

  • Define the scope clearly. A vague CCN gets a vague (and expensive) price.
  • Ask for a breakdown: labour, materials, equipment, sub quotes, markup and time.
  • Review the price with every consultant whose discipline it touches.
  • Check the quantities first. That's where extras go out to lunch.

What is a proposed change (CCN)?

A proposed change asks the contractor: "If we made this change, what would it cost and how much time would it add?" That's it. It's a request for pricing, not permission to do the work.

NameWhere you'll see it
CCN – Contemplated Change NoticeCommon on Canadian jobs, especially in BC
PC / PCN – Proposed Change (Notice)Many firms and specs
Proposal Request / PCOUS, AIA-based projects

Whatever your contract calls it, the rule is the same: the contractor doesn't build it until a change order or change directive says so.

Where proposed changes come from

  • An owner request: "Can we add receptacles in the library?"
  • An RFI answer that turns out to add scope
  • An SI the contractor flagged as an extra
  • Unforeseen conditions: bad soils, something behind the wall
  • Code or authority requirements that came up after tender

The CCN workflow

  1. Define the scope. Revise the drawings, cloud them and write a clear description.
  2. Issue for pricing. Ask for a breakdown: labour, materials, equipment, sub quotes, markup and schedule impact. Not a lump sum on a napkin.
  3. Coordinate the review. Route the price to every consultant whose discipline it touches.
  4. Recommend. Fair and reasonable? Recommend it to the owner. Not? Push back with specifics.
  5. Owner decides. Approve, revise or drop it.
  6. Authorize. If approved, it becomes a change order. If the work can't wait for agreement on price, use a change directive.

Reviewing the price is a team sport

As the architect, and often the coordinating registered professional, you're making sure the whole price makes sense, but you're not reviewing it alone. Say the owner wants a new rooftop unit to add cooling to a zone. Mechanical reviews the unit and the ductwork. Electrical reviews the power. Structural reviews the added load and seismic. You make sure the miscellaneous labour and general items are sensible.

Then check the details:

  • Are the quantities right? This is the big one.
  • Does the scope match what you asked for? Not more, not less.
  • Are unit rates and markups per the contract?
  • Is the time extension real, and is it on the critical path?

WATCH

Site instructions vs. proposed changes

Choosing the right document before you price anything.

Tracking pending changes

Pending CCNs are where owners get blindsided. The approved change orders look fine, and then there's $200k of "pending" nobody added up. Keep pending and approved changes visible side by side, every month.

That's built into Project Arc: change notices go out from the project record, the contractor's pricing comes back into the same record, and approved and pending changes sit on one line-by-line ledger.

BUILT BY THE HOST OF WHAT THE RFI?

The price comes back with its paperwork.

In Project Arc, you issue change notices from the project record and the contractor's pricing comes back into the same record. Once it's approved, it becomes a change order without anyone retyping a number, and it flows into the line-by-line construction finances.

  • Change notices with GC pricing in the same record
  • Approve into a change order without retyping
  • Approved and pending changes on one ledger
  • The owner's "where are we?" has a one-screen answer

Full disclosure: I built Project Arc. One project. Every phase. projectarc.io

FAQ

Frequently asked questions

What does CCN stand for in construction?

CCN stands for Contemplated Change Notice: a request for the contractor's price and time impact for a potential change.

Does a proposed change authorize the work?

No. A proposed change or CCN is a request for pricing. Work proceeds only once a change order or change directive is issued.

Who reviews proposed change pricing?

The architect, together with every consultant whose discipline is affected (mechanical, electrical, structural, civil and others).

Why does schedule impact matter on a proposed change?

Time costs money: site overhead, general conditions and potentially the owner's move-in date. Ask for the time impact every time.

What is the difference between a proposed change and a change directive?

A proposed change asks for a price before work proceeds. A change directive instructs the contractor to proceed before price and time are agreed.

How many RFIs did you get this week?

Got a CA question you want answered on the show? Send it in. Architects keep designing, contractors keep making those blueprints a reality.

How many RFIs did you get this week?

Have a Construction Administration question, a podcast topic you’d like us to cover, or are you interested in being a guest, speaking opportunity, or sponsorship? We’d love to hear from you.