change order examples construction billing G702/G703

Construction Change Order Examples

Change orders are easier to understand when you can see realistic examples. Below are common construction change order scenarios, including additive changes, deductive changes, allowance adjustments, field condition changes, and owner-requested scope revisions.

Quick answer:

A construction change order documents a change to the original contract scope, price, or schedule. Once the change is properly approved, the contractor can update the contract value, adjust the Schedule of Values, and bill the approved work on an AIA-style pay application.

Educational content only, not legal advice. PayAppPro provides AIA-style outputs and is not affiliated with or endorsed by the AIA.

What Counts as a Construction Change Order?

A construction change order is a formal adjustment to the original contract. It may add work, remove work, change materials, revise drawings, address unforeseen field conditions, modify the schedule, or convert an allowance into a final approved amount.

The most important billing point is approval. A change can be discussed, priced, or submitted, but that does not always mean it belongs in the current pay application. For AIA-style billing, approved change orders need to roll cleanly into the contract sum and the continuation sheet.

Billing rule of thumb: Do not treat a change order as approved contract value until the required approval path is complete. Pending or disputed changes can create pay app rejections when the contract total, SOV, and backup documents do not match.

Common Change Order Examples

These examples show how different change order types affect contract value, SOV setup, and billing.

Example Change type Contract impact Billing impact
Owner adds upgraded lighting package Additive Increases contract value Add approved value to SOV and bill progress
Owner removes a flooring area Deductive Reduces contract value Reduce SOV or add deductive line carefully
Unforeseen concrete repair is required Field condition May increase cost and time Bill only after authorization/approval
Allowance is finalized below budget Allowance adjustment May increase or decrease value Adjust SOV to approved final allowance value
Owner requests weekend acceleration Time / acceleration May add labor premium or schedule terms Needs strong backup before billing

Detailed Construction Change Order Examples

Example 1: Additive Change Order for Owner-Requested Upgrades

The owner decides to upgrade the lighting package after the original contract is signed. The electrical contractor prices the upgraded fixtures, added labor, freight, markup, and any schedule impact.

Sample change order language

Provide upgraded LED fixtures in conference rooms 101, 102, and 103 per owner direction dated May 12. Includes fixture cost difference, added labor, and approved markup.

Billing impact

Once approved, increase the contract sum, add or adjust the electrical SOV line, apply retainage as required, and bill the completed percentage on the next pay application.

Example 2: Deductive Change Order for Deleted Scope

The owner removes a portion of the flooring scope from the project. The contractor issues a deductive change order that reduces the contract value for the deleted material, labor, and related markup or overhead as required by the contract.

Sample change order language

Delete LVT flooring from storage room 210 per revised finish schedule. Credit includes material, labor, and approved contract adjustments.

Billing impact

Deductive changes must be handled carefully so the SOV balance, contract sum to date, completed work, and previous billing remain consistent.

Example 3: Field Condition Change Order

During demolition, the contractor discovers deteriorated framing that was not visible during bidding. The revised scope requires additional labor, materials, photos, field reports, and possibly design approval.

Sample change order language

Furnish labor and materials to repair concealed deteriorated framing discovered at wall section B4. Work performed per field directive and attached photos.

Billing impact

Because field conditions are often reviewed closely, include backup before billing. If the change is not approved, it may belong in a pending log rather than the pay app.

Example 4: Allowance Adjustment Change Order

The contract includes a $20,000 tile allowance. After selections are finalized, the actual approved tile package is $24,500. The difference is handled through a change order or allowance reconciliation process.

Sample change order language

Reconcile tile allowance based on approved selections and vendor quote. Increase contract amount by $4,500.

Billing impact

The approved allowance adjustment should align with the SOV line value. If materials are stored before installation, stored material billing may also need support.

Example 5: Time Extension or Acceleration Change Order

The owner asks the contractor to accelerate the schedule, work overtime, or perform weekend work to meet a revised deadline. This may create added labor premium, supervision cost, equipment cost, or schedule terms.

Sample change order language

Provide weekend labor and extended supervision for schedule acceleration requested by owner. Includes approved overtime premium and field supervision cost.

Billing impact

Time-related changes need clear backup. If the change affects only contract time and not money, it may not create a billable SOV amount.

How These Examples Flow Into AIA-Style Billing

The change order example itself is only the first part. The billing risk begins when that change order has to roll into the pay application. The G702 contract totals, G703 continuation sheet, retainage, and backup documents need to tell the same story.

1. Approval

Confirm the change order is approved, not just submitted, priced, or discussed.

2. SOV update

Add a new SOV line or adjust the correct existing line so the continuation sheet stays clear.

3. Pay app billing

Bill only the approved work completed this period, with retainage and prior billing calculated consistently.

Simple Construction Change Order Format

Your exact form may depend on the contract, but most change orders need the same basic information. A clean change order example usually includes:

Project and approval details

  • Project name and number
  • Change order number
  • Owner, GC, subcontractor, or vendor name
  • Date submitted and date approved
  • Required approval signatures

Scope and billing details

  • Description of changed work
  • Labor, material, equipment, and markup backup
  • Increase or decrease in contract amount
  • Schedule impact, if any
  • Revised contract sum after approval
Pay app tip: The change order number and approved value should be easy to trace from your backup to your SOV and then to the current G702/G703 totals.

Common Change Order Billing Mistakes

Approval mistakes

  • Billing a change before it is approved
  • Using email discussion as if it were final authorization
  • Leaving out signed change order backup
  • Mixing pending and approved changes in the same billing amount

Math and SOV mistakes

  • G702 contract sum does not match approved COs
  • G703 line values do not tie to the revised SOV
  • Deductive changes are handled inconsistently
  • Retainage is applied differently from the rest of the pay app

Turn Approved Change Orders Into Cleaner Pay Apps

PayAppPro helps contractors create cleaner AIA-style pay applications with SOV rollups, change order tracking, retainage math, and rejection-prevention checks.

PayAppPro creates AIA-style billing documents and is not affiliated with or endorsed by the AIA.

FAQ: Construction Change Order Examples

What is an example of a construction change order?

A common example is an owner requesting upgraded finishes after the contract is signed. The contractor prices the added labor and materials, submits the change for approval, and once approved, the contract amount and Schedule of Values can be updated.

What should a construction change order include?

A construction change order should usually include the project name, change order number, description of revised scope, cost increase or decrease, schedule impact, backup documentation, approval signatures, and any revised contract amount.

What is an additive change order example?

An additive change order increases the contract amount. For example, the owner adds a conference room, requests upgraded lighting, or approves extra concrete work after unexpected site conditions are discovered.

What is a deductive change order example?

A deductive change order reduces the contract amount. For example, the owner removes a portion of flooring work, deletes a scope item, or chooses a less expensive product than originally specified.

Can a change order be billed on a G702/G703 pay application?

Approved change orders can usually be included in AIA-style billing by updating the contract sum and adding or adjusting the related Schedule of Values lines. Pending or disputed changes are often rejected if billed before approval.

How does PayAppPro help with change orders?

PayAppPro helps contractors organize approved change orders, update AIA-style pay application totals, keep SOV rollups cleaner, calculate retainage, and reduce spreadsheet mistakes that can cause rejected pay apps.

Learn How to Bill Change Orders

Examples help explain the change. Clean billing requires approved values, accurate SOV lines, and consistent pay app math.