Change Order Documentation and Approval

Introduction
In construction projects, change is inevitable. Owners revise requirements, designers issue clarifications, site conditions differ from what was expected, and regulations evolve. The PMI Construction Professional (PMI-CP) credential treats Change Order Documentation and Approval as a core competency within the Scope and Change Order Management domain. This guide covers four things:
• why the topic matters
• what a change order is
• how the documentation and approval process works
• how to answer exam questions on it confidently

1. Why Change Order Documentation and Approval Is Important
• Contractual protection: A construction contract defines a fixed scope, price, and schedule. Any departure from that baseline must be formally recorded. Otherwise, the contractor risks working without payment and the owner risks unauthorized cost growth.
• Claims and dispute avoidance: Poorly documented changes are the leading source of construction claims, disputes, arbitration, and litigation. A clear paper trail turns subjective arguments into objective facts.
• Baseline integrity: Approved change orders update the scope, cost, and schedule baselines. Without them, earned value analysis, forecasting, and performance reporting become meaningless.
• Cash flow and payment: Contractors generally cannot invoice for changed work until a change order is executed. Timely approval keeps money flowing to the general contractor and subcontractors.
• Accountability and governance: Documentation shows who requested, evaluated, approved, and funded each change. This supports audits, public-sector compliance, and lender requirements.
• Lessons learned: Change logs reveal patterns, such as design errors, poor scoping, or recurring site issues. These insights improve future projects.
• Stakeholder trust: A transparent change process builds confidence among owners, designers, contractors, and funders.

2. What Change Order Documentation and Approval Is
A change order (CO) is a written instrument, signed by the authorized parties, that modifies the original contract. It may change:
• scope of work
• contract sum
• contract time

Related documents you must distinguish:
• Request for Information (RFI): A question seeking clarification. It is not a change by itself, but it may trigger one.
• Potential Change Order (PCO) / Change Order Request (COR) / Change Proposal: The contractor's priced proposal for a potential change, submitted for owner review.
• Change Notice / Bulletin / Proposal Request: An owner or architect document describing a proposed change and asking the contractor for pricing.
• Construction Change Directive (CCD) / Field Directive / Work Change Directive: A written order from the owner directing the contractor to proceed with changed work before price and/or time are agreed. It is used to avoid delay. Final adjustment is settled later.
• Architect's Supplemental Instruction (ASI): A minor change or clarification with no cost or time impact.
• Change Order (executed): The final, bilateral agreement signed by owner, contractor, and usually the architect/engineer. It is legally binding.
• Change Log / Change Register: The master tracking document listing every potential and approved change, its status, value, and time impact.

Key characteristics of a valid change order:
• It is written, not verbal.
• It is signed by persons with proper authority.
• It references the original contract.
• It clearly describes the changed work.
• It states the cost adjustment, including the pricing method and markups.
• It states the time adjustment (days added or zero).
• It includes supporting documentation: drawings, specs, quotes, labor and material breakdowns.
• It may include a release or reservation-of-rights language.

3. How the Process Works
The process follows Perform Integrated Change Control principles from PMI, applied within construction contract frameworks such as AIA, ConsensusDocs, FIDIC, and NEC.

Step 1: Identify the change. A change originates from any of these sources:
• owner request
• design error or omission
• differing site conditions
• regulatory change
• value engineering
• constructability issue
It is often surfaced through an RFI, a site observation, or a stakeholder request.

Step 2: Give timely notice. Most contracts require written notice within a defined period, for example 7, 14, or 21 days. Failure to notify can waive the contractor's right to compensation. This is a frequent exam point.

Step 3: Document the change. Record what, why, where, and when, along with supporting evidence:
• photos
• daily reports
• correspondence
• marked-up drawings
Log it in the change register with a unique number.

Step 4: Evaluate the impact. Assess the effects on:
• scope
• cost (direct, indirect, overhead, profit)
• schedule (critical path analysis, time impact analysis)
• quality
• risk
• safety
• other contract packages
Consult designers, estimators, schedulers, and subcontractors.

Step 5: Price the change. Common pricing methods:
• lump sum
• unit prices from the contract
• time and materials / cost-plus with agreed markup
Supporting backup must be provided.

Step 6: Submit the proposal (PCO/COR). Submit to the owner's representative or architect for review.

Step 7: Review and negotiate. The owner, designer, or Change Control Board (CCB) reviews whether the change is justified, in scope or out of scope, fairly priced, and properly scheduled. Negotiation may follow.

Step 8: Approve or reject. Approval follows the authority matrix defined in the contract and the project management plan. For example:
• the PM may approve up to a threshold
• the owner's executive or board approves above it
If the work is urgent and pricing is unresolved, a Construction Change Directive may be issued.

Step 9: Execute the change order. All authorized parties sign. Only then is the contract formally amended.

Step 10: Update the baselines and documents. Update all of the following:
• scope baseline
• cost baseline/budget
• schedule baseline
• change log
• drawings (conformed sets, as-builts)
• risk register
• procurement documents and subcontracts (flow-down)

Step 11: Communicate and implement. Notify the affected stakeholders, crews, and subcontractors. Then perform the work.

Step 12: Verify and close. Confirm the work was completed as approved, invoice through the payment application, and archive the records for closeout and lessons learned.

Key roles:
• Owner/Client: funds and ultimately approves changes.
• Architect/Engineer: evaluates technical merit, certifies, and often signs.
• General Contractor/Construction Manager: identifies, prices, and documents changes, and manages subcontractor changes.
• Change Control Board: a formal body reviewing significant changes.
• Project Manager: ensures the process is followed and baselines are maintained.

Common pitfalls:
• proceeding on verbal instructions
• missing notice deadlines
• vague scope descriptions
• not including time impact (leading to later delay claims)
• failing to flow changes down to subcontractors
• scope creep through undocumented minor changes
• gold plating

4. How to Answer Exam Questions on This Topic
PMI-CP questions are typically situational: a scenario is described and you choose the BEST, FIRST, or NEXT action. Use this approach:
• Identify the stage of the change process the scenario describes: identification, notice, evaluation, approval, implementation, or closeout.
• Apply the process before action. PMI favors following the formal change control process over jumping to implementation or rejection.
• Look for documentation. The correct answer usually involves documenting, logging, analyzing impact, or referring to the contract.
• Check authority. Ask who is allowed to approve. The answer is rarely the site supervisor or the PM alone if the change exceeds their limit.
• Consider the contract. Contract terms govern notice periods, pricing methods, markups, and approval routes.

Sample question 1: The owner's representative verbally asks the superintendent to relocate a wall. What should the project manager do FIRST?
Best answer: request written direction and document the request as a potential change, then evaluate its impact. Do not simply proceed, and do not refuse outright.

Sample question 2: Urgent changed work is needed to avoid delay, but the owner and contractor cannot agree on price. What document is appropriate?
Answer: a Construction Change Directive (or the equivalent field directive).

Sample question 3: A change order has been approved. What is the NEXT step?
Answer: update the baselines, the change log, and the project documents, then communicate the change to stakeholders and subcontractors.

Exam Tips: Answering Questions on Change Order Documentation and Approval
• Never implement before approval unless a directive (CCD) authorizes it. Unapproved work is a red-flag answer.
• Writing beats words. Any answer that accepts verbal changes without written confirmation is almost always wrong.
• Assess impact first. Before approving or rejecting, analyze the impact on scope, cost, schedule, quality, and risk.
• Respect notice clauses. Timely written notice preserves entitlement. Late notice may forfeit rights.
• Know the document types. Distinguish RFI, ASI, PCO/COR, CCD, and executed CO. Questions often hinge on these differences.
• Approved means bilateral. A change order is final when signed by authorized parties. A CCD is unilateral and pending final pricing.
• Update everything. After approval, think baselines, logs, drawings, subcontracts, and communications.
• Include time, not just money. A good change order states the schedule impact, even if zero days. This prevents later delay claims.
• Use the authority matrix. Escalate changes beyond your approval threshold to the CCB or owner.
• Prevent scope creep. Even small, no-cost changes should be documented, for example via an ASI or log entry.
• Flow down changes to affected subcontractors and suppliers.
• Prefer collaboration over confrontation. PMI favors negotiation and documented resolution before claims or disputes.
• Watch keywords such as FIRST, NEXT, BEST, and MOST appropriate. Eliminate answers that skip process steps.
• Remember lessons learned. Change history feeds organizational process assets at closeout.

Summary
Change Order Documentation and Approval keeps construction projects contractually sound, financially controlled, and dispute-resistant. The process runs from identification and notice, through impact evaluation and pricing, to authorized approval, execution, and baseline updates. On the exam, choose answers that follow the formal written process, respect contractual authority and deadlines, analyze impact before deciding, and fully update and communicate approved changes.