Change order documentation is the signed contract amendment that authorizes and records scope, cost, or schedule changes. Never start work without one. A construction change order becomes a legal modification only after both parties sign it, and until that signature exists, you’re working at your own financial risk.

That’s the whole game in one sentence, but the paperwork around it decides whether you get paid. Standard forms like ConsensusDocs 202 Change Order and AIA G701 exist precisely because handshake agreements and email chains don’t hold up when a dispute lands in front of an owner’s attorney. Every serious documentation system needs three things working together:

  • A signed, standardized change order form for every approved modification
  • A running change order log that tracks status, cost, and schedule impact in one place
  • Field records (photos, daily logs, RFIs) that prove entitlement before the ink dries

Key Takeaways

Change order documentation only protects you if it’s signed before work starts, standardized across every project, and backed by a daily record connecting photos, logs, and cost data to each entry in your change order log.

Point Details
Never start on a verbal order alone Document verbal authorization in writing the same day and follow with a formal COR.
Use a standardized form ConsensusDocs 202 or AIA G701 capture the required fields consistently across every job.
Keep one running log Update your change order log daily or weekly with cost, schedule, and status fields.
Match pricing to scope certainty Use lump sum for defined scope, unit price for known work with uncertain quantities, T&M for undefined scope.
Connect field capture to the record Platforms like Debecorp’s CHERP and SiteComm tie photos and daily logs directly to change order tracking.

Table of Contents

What Is a Change Order, and How Does It Differ From a COR?

A change order is a formal amendment to the original contract that adjusts scope, price, or time, and it only carries legal weight once both the owner and contractor sign it. A construction change order is a mutual agreement, not a unilateral demand, which is exactly why the paperwork matters so much. Confuse it with a change order request or a directive, and you’ll misjudge your own risk exposure on the job.

Three terms get thrown around interchangeably on jobsites, and the differences aren’t cosmetic:

  1. Change order request (COR): A proposal, typically from the contractor, describing a potential change and its estimated cost and time impact. It has no binding force. It’s an opening bid.
  2. Construction change directive: An owner or architect’s instruction to proceed with work before price and time are finalized. Many contracts allow these, but they usually require the contractor to track costs meticulously since the value gets negotiated later.
  3. Signed change order: The executed amendment. Once both parties sign, the original contract is legally modified, and the new scope, price, and schedule become enforceable.

Contract clauses typically spell out exactly what triggers a binding change: written notice within a set number of days, a specific signature authority (project executive versus site super), and sometimes a cap on directive value before it needs owner sign-off. Read those clauses during preconstruction, not after a dispute starts.

Six Elements Every Change Order Should Include

A change order document that’s missing even one of these fields creates an opening for a dispute later. Whether you’re using ConsensusDocs 202, AIA G701, or a homegrown template, the content has to cover the same ground.

  • Project and contact information: Project name, contract number, CO sequence number, and the names of the parties signing.
  • Precise description of the change: Reference specific drawings, spec sections, or RFI numbers. “Additional electrical work” invites arguments. “Add three 20A circuits per RFI #14 and revised drawing E102, Rev 3” doesn’t.
  • Dates: Date of notice, date of submission, and the proposed effective date. Timing disputes are common, so nail these down.
  • Schedule impact: State the number of added or removed calendar days, and whether the critical path is affected.
  • Cost impact and updated contract value: Break out the change amount and show the new total contract sum, not just the delta.
  • Signatures and reservation language: Signature lines with printed names, titles, and dates, plus a clause reserving rights to claim additional costs discovered later if the scope grows.

Attach supporting exhibits: the sub’s quote, a marked-up drawing, or photos of the existing condition. A change order without exhibits is an assertion. A change order with exhibits is evidence.

Pro Tip: Number your change orders sequentially by contract to keep records unambiguous and clear.

What Is the Change Order Process From Start to Finish?

Change management works best as a repeatable sequence, and AACEI’s RP 100R-19 frames it as a staged process built around three things owners want proven before they’ll approve a claim: entitlement, causation, and quantum. In plain terms, you have to show you’re owed something, why, and how much.

  1. Identify the change. Something doesn’t match the drawings, a site condition surprises you, or the owner asks for something new. Log it the same day, with a photo and a note in the daily report.
  2. Issue internal notice. Superintendent flags it to the PM. Most contracts require formal written notice to the owner within a set number of days of discovering the condition. Miss that window and you may forfeit the claim entirely, regardless of merit.
  3. Prepare the preliminary submittal. Package the COR: description, rough cost range, schedule impact, and supporting documents.
  4. Price the change. Choose lump sum, unit price, or time and materials based on how well-defined the scope is.
  5. Submit, negotiate, approve. The owner’s rep reviews, negotiates line items, and either approves, rejects, or counters.
  6. Execute the signed change order. Once signed, update the master contract value, revise the schedule, and issue formal instruction to affected subcontractors.
  7. Handle directives separately. If you’re told to proceed before pricing is settled, document that instruction in writing immediately, even if it’s just a confirming email after a verbal order, and keep cost records as if it were already a signed CO.

Skipping steps to save time is how contractors end up doing $40,000 of extra work on a verbal promise that nobody can later confirm was ever made.

How Should You Price a Change Order?

Pricing methods for change orders generally fall into three categories, and picking the wrong one for the situation is a common way contractors lose money on legitimate work.

  • Lump sum: Use this when the scope is fully defined by drawings or specs. It’s the cleanest method for the owner to approve and the fastest to negotiate, but it requires a tight scope description up front. Vague scope plus lump sum pricing equals arguments over what was included.
  • Unit price: Best when quantities are uncertain but the work type is known, like excavation priced per cubic yard. Track actual quantities daily against the unit rate.
  • Time and materials (T&M): Use when scope truly can’t be defined in advance, such as emergency repairs or investigative work. T&M demands the tightest daily records of anyone on the pricing spectrum, because your entire claim rests on hours, rates, and receipts.

Whichever method you pick, build the estimate the same way every time: labor hours and rates, material costs with quotes attached, equipment time, subcontractor quotes, then indirect costs and markup applied per your contract’s formula.

Write down your assumptions and exclusions on every submittal. If you’re pricing based on daytime access and the owner later restricts you to nights, that assumption protects you. Include a contingency line item where justified, and document it separately from base cost so it’s clear what’s estimate and what’s buffer.

Schedule-related costs, sometimes called prolongation costs, need their own paper trail entirely: extended equipment rental, extended supervision, and any general conditions costs tied directly to the added duration. The pricing method you choose has to match how well you can measure and document the actual work performed.

How Do You Keep a Change Order Log?

A change order log is the single source of truth for every modification on a project, and it should exist from contract award straight through closeout. Without one, you’re reconstructing the financial history of your project from memory during a dispute, which never goes well.

Hand photographing damaged steel beam onsite

The recommended fields for a working log include CO number, initiation date, description, requester, current status, cost impact, schedule impact, and a running total of the revised contract value. Update it daily on active projects with frequent changes, weekly at minimum on everything else. Letting the log lapse for a month is how contract value discrepancies sneak into a billing application unnoticed.

Log Field Why It Matters
CO number and status Prevents duplicate submissions and shows what’s pending vs. approved
Cost and schedule impact Feeds directly into revised contract sum and updated milestones
Requester and date initiated Establishes the notice timeline if a dispute arises later
Running contract value Keeps billing applications aligned with actual approved changes

The log alone isn’t proof of anything; it needs supporting records behind it. Every entry should connect back to:

  • Time-stamped photos with location metadata showing the condition before and after
  • Daily logs referencing the same date and work area
  • The RFI thread that triggered the discovery, if applicable
  • Subcontractor quotes or signed T&M tickets backing the cost figure
  • Delivery tickets or material invoices for anything billed at cost plus markup

Link every change order to the RFI that started it, the schedule update it caused, and the payment application where it eventually shows up. A change order that can’t be traced through all three is a red flag during an audit.

What Mistakes Cause Change Order Disputes?

Most change order disputes trace back to the same handful of avoidable mistakes, and nearly all of them get fixed cheaper before the project starts than after.

  • Contradictory contract clauses. One section requires written approval for any change; another allows the super to issue verbal field directives. Resolve these conflicts during contract review, not mid-project, because ambiguous language almost always gets read in the owner’s favor.
  • Missed notice windows. Many contracts require written notice within a specified timeframe of discovering a change condition. Track these deadlines carefully, because a valid claim submitted late can be rejected on procedural grounds.
  • Starting work on a handshake. If you’re forced to proceed on a verbal instruction, document it in writing that same day and follow with a formal COR. A confirming email sent an hour later is worth more than a strong memory six months from now.
  • Template drift. Different PMs on the same company using different change order forms creates inconsistency that owners notice and exploit during negotiation.

Pro Tip: Keep one master change order template locked behind version control, and date every revision, as recommended in the practical templates and advice on the Wells Manager blog. If a sub or PM downloads an old version from an email thread, you’ll end up with two “current” templates floating around the same project.

What Should a Change Order Template Include?

A usable template needs a pre-submit checklist and a pre-execution checklist, because the risks at each stage are different.

Before you submit a change order for approval, confirm you have:

  1. A scope description tied to specific drawings, specs, or RFI numbers
  2. A pricing method selected and cost backup attached
  3. Schedule impact calculated against the current critical path
  4. Supporting photos and daily log references pulled together

Before execution, confirm:

  1. All signature blocks filled with printed names, titles, and dates
  2. The updated contract sum stated correctly, not just the delta
  3. Reservation-of-rights language included if scope could still grow

A sample structure runs top to bottom: project header, CO number, description of change, cost breakdown, schedule impact, exhibits list, and signature blocks. Name your files consistently, something like “ProjectName_CO014_v2_2026-03-12,” and store every version in one shared folder rather than scattered across email attachments. Whoever inherits the project file in five years should be able to reconstruct the entire cost history from the folder alone.

How Do Field Teams Actually Capture This Evidence in Real Time?

The theory of good documentation is simple. The practice usually breaks down because someone on the crew has to remember to take the photo, write the log entry, and update the log, all while running a jobsite. Superintendents typically own the photo and daily log capture, while the PM owns the change order log and submittal packaging, but the handoff between those two roles is where records get lost.

Field platforms built specifically for the trades close that gap by tying photo capture, daily logs, and change tracking to the same record instead of three disconnected systems. When a super snaps a photo of an unforeseen condition directly into a jobsite platform with a timestamp and location attached, and that photo links automatically to the day’s log entry, there’s no separate step where someone has to remember to save it somewhere findable.

On a project where photo evidence, daily logs, and the change order log all live in one connected system, tracing a disputed change back to its origin takes minutes instead of a week of digging through email and phone camera rolls.

  • Superintendent: photos, daily log entries, verbal directive notes
  • PM: COR packaging, pricing, log updates, submittal tracking
  • Both: cross-checking that every entry ties back to a dated, retrievable record

Tools like DeBe’s CHERP platform are built around exactly this kind of connected daily record.

Documentation Habits Are a Culture Problem Before They’re a Paperwork Problem

Most superintendents didn’t come up through the trades learning to write detailed daily logs. They learned to build. Asking them to also become meticulous record keepers overnight rarely works, no matter how good the template is.

What actually moves the needle is treating documentation as a daily habit rather than a crisis response. A photo taken the day a condition is discovered is worth more than a detailed narrative written from memory three weeks later. Pick one template, one log, and one capture method across every project you run, and give it 90 days before judging whether it’s working.

How Debecorp Supports Change Order Documentation on the Jobsite

Every workflow described above depends on the same thing: getting field evidence captured the moment it happens and connected to a single record instead of scattered across texts, emails, and paper logs. That’s the exact gap Debecorp’s platforms were built to close.

Debecorp

CHERP handles the field side of this equation: daily logs, photo capture with timestamps, and time and attendance tracking, all built by tradespeople who’ve actually filled out a change order form on a tailgate at 6 p.m. SiteComm connects that field data to jobsite communication, so a discovered condition, the photo proving it, and the resulting change order request live in a traceable chain instead of three separate systems nobody cross-checks. The result is fewer arguments over what happened and when, because the record was built in real time instead of reconstructed from memory. See how the CHERP and SiteComm platforms handle photo evidence and change tracking, or check out per-trade features to see how the tools adapt to your specific work.

Where to Find the Official Forms and Guidance

For readers building or refining their own change order process, these sources cover the standardized forms and procedural frameworks referenced throughout this article.

Sources