Why Change Orders Go Undocumented and Unbilled: Automating the Change Order Paper Trail

Why do change orders go undocumented, disputed or unbilled?

A change order is a written agreement that changes the scope, price or schedule of a construction contract. Scope creep is the informal version: extra work that grows without a matching written change. The money is lost in the gap between the two. This article is written for mid-size and large contractors, where many projects run at once and the paper trail passes through field, project management, accounting and the owner or general contractor (GC).

Procore's 2022 report with Dodge Construction Network, a Procore-sponsored survey of over 500 specialty contractors in the United States, Canada, the United Kingdom and Australia/New Zealand, states that "Approximately 30 percent of project revenue is lost because of change orders that go unbilled and unpaid"^[1]. Treat that as a vendor-sponsored estimate from specialty contractors, not a measured industry average.

A 2026 Clearstory and Dodge Construction Network report, produced by a change order software vendor, found that 66% of subcontractor respondents had written off change order revenue in the last 12 months, and that half say their change order logs are misaligned with their GCs'^[2]. The report page does not state the number of respondents.

Disputes have a documentation side too. Arcadis, a consultancy, lists among the most frequent causes of construction disputes in its 2023 disputes report for North America "Errors and/or omissions in the contract documents" and "Poorly drafted or incomplete and unsubstantiated claims"^[3]. The second item is the kind of problem a change order faces when its backup is thin.

What causes construction cost overruns tied to change orders? From the contractor's side, the cost of changed work is incurred whether or not it is recovered, so unrecovered change work shows up as margin loss. None of these sources ranks the causes. These are the failure points to check:

• An unrecorded field change, where extra work starts without a written direction.
• A price built without the backup the owner or GC will ask for.
• An unsigned approval that nobody chases.
• A signed change that never reaches the pay application.

The change order paper-trail table

The table follows one change order through four stages. Use it as a review checklist for your own process. The third column describes what an AI agent can prepare from your documents; the fourth is the decision that stays with a named person at your company.

Can AI draft a change order proposal from project data?

Yes, as a draft, and that is how to automate change order processing without removing review. An AI agent can assemble the pieces of a proposal from records you already hold, then lay them out in the format your contract and your owner or GC expect. The pieces include:

• The daily report that shows the work.
• Labor tickets and material receipts.
• The subcontractor quote.
• The contract clause the change refers to.

The draft is the start of a review, not the end of one. The agent does not decide the price, whether the work was in scope, or whether to proceed before approval. We describe this pattern of extraction, checks and approval on our page about document review with human approval, and the implementation work behind it on AI agent implementation.

Project management suites can include change order tools. Procore's documentation, for example, says "Use a potential change order to manage any additional costs affecting the prime contract."^[4] Where a tool like that is in use, an agent can cover whatever document work your configuration doesn't already handle, such as collecting backup, checking the package or reconciling the log to billing. Confirm with your own vendor documentation what your configuration covers.

How do you get a change order approved and signed faster?

Send a complete package to the named approver, then track and follow up on every open change. Each step below removes a reason for the owner or GC to send a package back. We have no sourced benchmark for approval time, so treat this as a working checklist, not a promise.

1. 01
   Send a complete package

   Include the description, the cause, the price with backup, the schedule effect and the contract clause, in the format the contract requires.

2. 02
   Send it to the right person

   Check the approver named in the contract and copy the people who will be asked about it, so it doesn't stall in the wrong inbox.

3. 03
   Track the age of every open change

   Keep one log of open, signed and rejected changes with the date each was sent, and review it on a fixed rhythm.

4. 04
   Follow up from the log

   Draft follow-ups from the log's open items, and have the project manager send them.

5. 05
   Match your log to theirs

   Compare your change log with the owner's or GC's log before billing, since a mismatch is easier to fix before the pay application than after.

What stays human, and when this doesn't apply

Pricing judgment and scope decisions stay with your project managers and estimators. So does deciding whether to do extra work before a signature, and how to negotiate with an owner or GC. The agent prepares, checks and tracks. A person approves.

The two layers answer different questions. A project management suite is where a team runs a project, including change events and approvals. An AI agent layer reads the documents that live across email, PDFs and spreadsheets, and checks them against the contract and the accounting record. A controller weighing the two should ask which stage is actually breaking.

• Your volume is low enough that a project accountant already reconciles every change by hand without a backlog.
• The failure is upstream: unclear contract language or a scope that was never defined. A document workflow does not fix that.
• Your existing suite already routes, tracks and reconciles changes, and the team uses it. Fix adoption before adding anything.
• Contracts, change logs or accounting codes are not consistent enough to compare. Clean them up first.

For a wider view of back-office work in construction, see our AI for construction companies page. To scope a first workflow, our 360 AI Blueprint is the planning step.

Frequently asked questions

Related reading

• Document review with human approval covers the extraction, checking and approval pattern behind the paper-trail table.
• AI agent implementation covers how we build and run an agent inside your existing systems.
• 360 AI Blueprint covers the planning step for choosing a first workflow.
• AI for construction companies sets this workflow in the wider picture of contractor back-office work.

Sources

1. [1] — Procore blog post, October 14, 2022 (accessed 2026-10-29)
2. [2] — The State of Change Orders in 2026: Subcontractor Report, landing page (accessed 2026-10-29)
3. [3] — Arcadis blog post, July 11, 2023 (accessed 2026-10-29)
4. [4] — Procore support, Change Management Tools, Potential Change Order (accessed 2026-10-29)