Change Orders That Never Get Paid: Turn Field Directives into Defensible CORs

Answer first: To get paid for field extras, capture the directive the same day in your daily log, quantify labor and materials with photos, record schedule impact, submit the COR before multi-week lag eats your margin, and approve the change into your SOV so the next pay app stays honest. Software can keep that chain searchable, but the discipline still starts with the superintendent and PM.

Owners and architects often give verbal direction on active jobs. Crews execute. Weeks later someone tries to reconstruct a COR from memory, texts, and a sticky note in a truck cab. That is how change orders that should have been paid become write-offs, strained relationships, or liquidated damages arguments you cannot answer.

Industry research in 2026 underscores how common the failure is. Dodge Construction Network and Clearstory found that only about one-third of general and specialty contractors say their change order process works well. Roughly 96% of GCs say lack of change order visibility hurts cost control, and about 91% sometimes do not pay full change order amounts, often because documentation, pricing, or scope alignment is incomplete. Specialty trades report multi-week gaps from field ticket to priced COR and again to signed authorization. When that lag tax hits, cash sits idle and negotiated-down settlements become normal.

Legal and industry write-ups show the same pattern at dispute time. Bradley's BuildSmart coverage of a federal case where missing contemporaneous project documents undercut a contractor's narrative is a blunt reminder: if the schedule story and supporting records were not created and stored during the job, end-of-project testimony rarely saves you. Fullerton & Knowles similarly note that many contracts enforce written change-order clauses so thoroughly that unsigned extras can mean no payment regardless of how much work was performed. This post is operational guidance, not legal advice. Follow your contract notice rules.

For weather-driven entitlement, use the companion guide on documenting construction weather delays. For searching the field timeline after the fact, see Project Historian for searchable daily logs.

Step 1: Capture the directive the same day in the daily log

1. Name who directed the change (owner, architect, CM) and how (verbal, email, text).
2. Describe the added or altered scope in plain language tied to location and trade.
3. Note whether crews started, stood by, or demobilized while waiting on written confirmation.
4. Seal the entry before leaving the site. Same-day beats Friday reconstruction.

A log that only says "work continued" is not a COR seed. A log that names the directive, the people, and the immediate impact is.

Step 2: Quantify labor, materials, equipment, and photos

1. Record crew counts, hours, and trade for the extra work.
2. List materials and equipment, including idle or standby time caused by the change.
3. Attach timestamped photos that show conditions or completed extras.
4. If a T&M ticket is used, keep it tied to the same day's log narrative.

Quantities turn a story into a priced COR. Vague narratives invite cuts.

Step 3: Record schedule impact, not cost alone

1. State how many days or shifts were affected.
2. Name the activities delayed and whether the critical path moved.
3. Reserve time entitlement in writing when full impact is not yet known.

Cost without time is a common trap. You may recover labor and still eat liquidated damages or denied extensions because the schedule story was never documented. Treat every meaningful change as both a cost issue and a time issue.

Step 4: Meet notice and COR timing before the lag tax

1. Check your contract for notice windows and written change requirements.
2. Send dated notice with facts that match the daily log.
3. Price and submit the COR while backup is fresh, not weeks later from memory.

Multi-week lag from field ticket to priced COR is where margin disappears. Incomplete backup leads to revision cycles, negotiated-down settlements, and write-offs. Speed is a commercial control, not bureaucracy.

Step 5: Approve into the SOV and keep the pay app honest

1. Track Draft, Submitted, and Approved status on every COR.
2. When approved, update contract sum and SOV lines so billing matches entitlement.
3. Keep percent complete and pay app narrative consistent with the field record.

An approved change that never reaches the SOV is still invisible money. Alignment between field truth, change log, and CSI pay applications is how you stop funding someone else's scope.

Where BalanceBuild Pro fits without replacing judgment

BalanceBuild Pro is commercial construction management software for general contractors. It supports AI daily logs with jobsite-ready voice capture, Project Historian search across the field timeline, and a change order workflow from Draft to Submitted to Approved with schedule impact days that can update SOV and contract totals. CSI pay applications stay connected to that financial picture.

It does not replace contract notice discipline, attorney review, or superintendent judgment. It reduces the chance that the proof chain is missing when a COR is challenged or a pay app is questioned. Bookkeeping support from Balance & Build can help monthly close match jobsite reality for product customers, but the operating record for change entitlement still starts in the field.

Quick checklist before you leave the site

• Same-day log: who directed, what changed, verbal or written
• Quantified labor, materials, equipment, and photos
• Schedule impact noted (duration and affected activities)
• Notice / COR path started while evidence is fresh
• Financial status tracked so approved changes reach SOV and the next pay app

FAQ

When should a GC document a verbal change order?

The same day the directive is given. Record who directed the work, what changed, and the immediate impact before crews leave the site.

What belongs in a defensible construction COR package?

Contemporaneous daily log notes, quantified labor and materials, photos, schedule impact, and timely notice that matches your contract.

Why do change orders go unpaid at the end of a project?

Usually because work started on a verbal yes, the COR lagged, backup was incomplete, or the approved change never reached the SOV and pay app.

How does BalanceBuild Pro help?

It helps capture AI daily logs, search the field timeline in Project Historian, run Draft to Approved change orders with schedule impact, update SOV totals, and keep CSI pay apps aligned with approved contract value.

Is a signed AIA G701 required before starting extra work?

Many contracts require written change orders before payment entitlement. When work must start immediately, document same day, give written notice, and price quickly. Follow your contract; this is not legal advice.

Ready to tighten the field-to-COR habit on your next active job? See BalanceBuild Pro or book a discovery call.