Change order tracking for contractors: a log that gets you paid

Where change order money leaks

A change order is a written change to the contract's scope, price or schedule. Every contractor knows changes happen on almost every job. The problem is that the paperwork lives in five places at once: a superintendent's text thread, a daily log, an RFI response, an email from the architect and the PM's memory. When the money goes missing, it usually leaks at one of these points:

• Never captured. The crew moved a wall, added blocking or worked around another trade, and nobody flagged it as a change. This is the biggest leak and the hardest to see, because it never shows up on any list.
• Captured, never priced. Someone noted it, but pricing waited for "when things calm down." Weeks later the backup is gone and the number is a guess.
• Priced, never approved. The request went out and stalled with the owner, architect or GC. Nobody followed up, and the item aged into a closeout argument.
• Approved, never billed. The signed CO sits in a folder but never gets added to the contract value in accounting or onto the next G702/G703 pay application.
• Billed, never passed down or up. A change that affects a subcontractor never becomes a sub change order, or a sub's change never gets carried up to the owner, so someone absorbs the cost.

Each of these is a tracking failure, not a negotiating failure. That's good news: tracking is fixable with a clear process and one reliable list.

PCO vs COR vs CO: the three stages

Separating a change into stages is what lets you see what is stuck and where. Names vary by company and by software (some say "change event," "pending change order" or "change order proposal"), but the stages are the same.

Stage	What it is	Who usually creates it	What closes it
PCO (potential change order)	An internal record that something may have changed cost, scope or schedule	Superintendent, foreman or PM, as soon as it's spotted	Priced into a COR, or voided with a reason
COR (change order request)	A priced proposal with backup, sent to the owner or GC for approval	PM or estimator	Approved, rejected or revised
CO (change order)	The signed document that formally modifies the contract sum or time	Owner, GC or architect issues or signs it	Added to contract value, budget and the next pay app

The key habit is opening a PCO early, even with no price. A PCO with a description, a date and a photo costs two minutes. It costs nothing to void later if the item turns out to be in scope. It is far cheaper than trying to reconstruct a change from memory two months on. Many changes start as an RFI answer, so connect your change log to your RFI and submittal tracking.

What your change order log needs

A change order log is a single list, per project, of every PCO, COR and CO and where each one stands. Whether it lives in a spreadsheet or your project management software, these are the columns that matter.

Column	Why it matters
Number (PCO / COR / CO)	One numbering scheme that links each stage, e.g. PCO-014 becomes COR-009 becomes CO-006
Description	Plain-English summary a stranger could understand
Source	RFI, ASI, field directive, owner request, unforeseen condition, drawing revision
Date identified / date submitted / date approved	Shows aging and helps with contract notice deadlines
Requested amount and schedule days	What you asked for, including time
Approved amount and days	What was actually signed; often different
Status	Open, priced, submitted, approved, rejected, void, in dispute
Ball in court	Who it's waiting on right now, with a name
Cost code	So approved changes land in the right budget line
Sub impact	Which subcontractor changes it creates or depends on
Billed / paid	Which pay app it went on, and whether it was collected
Backup link	Photos, time sheets, material tickets, quotes, the directive itself

If you are building a change order log template from scratch, start with these columns in a shared spreadsheet and add a summary at the top: total pending, total approved, total billed, and the oldest item still waiting on someone. That summary is what the owner of the company should look at every week.

A change order process, step by step

A good change order process for contractors is short enough that the field will actually follow it. Here is a version that works for most commercial and residential general contractors and trade contractors.

1. Spot and flag it the same day. Anyone in the field can open a PCO with a photo and a sentence. Make it as easy as a text message.
2. Check the contract. The PM confirms whether it is really out of scope and notes any notice requirement. Many contracts require written notice of a claim or change within a set number of days.
3. Send notice if required. A short written notice that a change is coming, even before you have a price, protects your right to be paid.
4. Track the cost as it happens. Give the change its own cost code or job phase so labor, materials and equipment are captured separately, not buried in the base contract.
5. Price it and submit the COR. Use your standard rates and markup, attach the backup, include schedule impact, and send it to the person with authority to approve.
6. Follow up on a schedule. Pending CORs get a follow-up every week until they're resolved. Record every response.
7. Execute the CO and update everything. Once signed, update contract value in accounting, the project budget, the schedule of values and any affected subcontracts.
8. Bill it. Add the approved change to the next pay application, and confirm it was paid when the payment arrives.

The steps are simple. What breaks them is that each one is owned by a different person in a different tool. Assign one person per project, usually the PM or a project coordinator, to own the log end to end.

Unapproved change orders and field directives

Unapproved change orders are the hardest part of the job. The owner wants the work done now, the schedule can't wait for paperwork, and the crew goes ahead on a verbal "just do it." Sometimes that's the right call for the project. It is also the most common way contractors end up doing work they never get paid for.

Practical rules that reduce the risk:

• Get something in writing before work starts. A construction change directive, a signed field work order or at minimum an email from someone with authority confirming the instruction. A reply to your own email ("confirmed, please proceed") is better than nothing.
• Confirm who can authorize. A site rep or an architect may not have authority to approve cost under the contract. Know who does before you need them.
• Log it the same day as a PCO marked "proceeding without signed CO," so it shows up on every weekly review until resolved.
• Track time and materials separately with daily signed tickets if you can get them. If the price is disputed later, this is your evidence.
• Watch the aging. A list of work performed without a signed CO, sorted by age and dollar value, is one of the most useful reports a contractor can run.

General information, not legal advice. Change order, notice and claim requirements depend on your contract and your state. Some contracts waive your right to payment if notice isn't given on time, and lien rights have their own deadlines. Review your contracts and talk to a construction attorney about specific disputes.

Pricing and markup

Change order markup is where contractors often leave money on the table, usually by pricing changes inconsistently. Start with your contract: many contracts specify the overhead and profit percentages allowed on changes, sometimes different for self-performed and subcontracted work, and those terms control.

Within what the contract allows, a complete change order price usually covers:

• Direct labor at burdened rates (wages plus taxes, insurance and benefits)
• Materials, equipment and any rental or delivery cost
• Subcontractor and supplier quotes, with their own markup if allowed
• Supervision and project management time
• Overhead and profit
• Bond and insurance costs, if they scale with contract value
• Schedule impact, including extended general conditions, if the change adds time

Illustrative example: a change needs $4,000 of labor at burdened rates, $2,500 of materials and a $3,000 electrical sub quote. If your contract allowed, say, 15% overhead and profit on self-performed work and 10% on sub work, the request would be $6,500 × 1.15 + $3,000 × 1.10, or about $10,775 before bond and any time impact. The percentages here are hypothetical; use your contract's numbers. The bigger point is to write your standard rates down once, so every PM prices changes the same way and nobody forgets the sub markup or the supervision time.

Time matters as much as money. If a change pushes the schedule, ask for the days in the COR. Accepting the money without the time can leave you exposed if the job finishes late.

Getting paid: from approved CO to collected cash

Getting paid for change orders depends on what happens after the signature. An approved CO that never reaches the pay app is the most frustrating leak of all, because the hard part is already done.

• Update the schedule of values. Add approved changes as their own lines (or as the contract requires) so the owner and lender can see them on the G703.
• Reconcile monthly. Before each pay app goes out, compare the log's "approved, not yet billed" list with the draft. Any approved CO missing from the draft is money you're about to delay a month. Our guide to automating draw requests covers how this fits into the monthly package.
• Bill pending items only if the contract allows. Many owners and lenders won't pay for unapproved changes. Keep them in the log, not on the pay app, unless your contract says otherwise.
• Match the lien waivers. Payments that include change order work often need waivers covering those amounts. See lien waiver management for how to keep waivers from holding up a draw.
• Pass changes down. When the owner approves a change that involves a sub, issue the sub change order promptly so their billing matches yours.
• Chase what's overdue. Once billed, change order amounts should be followed up like any other receivable. For the collections side, see how to chase unpaid invoices.

Finally, close out cleanly. Before final payment, every PCO should be resolved: approved, rejected or void, with a reason. Unresolved items at closeout are exactly where final payment gets held up.

Tracking in Procore, Buildertrend, QuickBooks and spreadsheets

The right tool depends on your size and what you already use. Most of the common options can work; the gaps between them are the usual problem.

Tool	Typical fit	Watch out for
Spreadsheet	Smaller contractors, a handful of active jobs	Version copies, no link to accounting, depends on one person's discipline
Procore	Commercial GCs and larger subs managing many changes and stakeholders	Change workflow setup varies by company; budget and accounting sync depend on your integration
Buildertrend	Residential builders and remodelers, including owner-facing change approvals	Whether approved changes flow cleanly into your accounting depends on your setup
QuickBooks, Sage 100 Contractor, Sage Intacct, Foundation	Contract value, job cost and billing	Usually the system of record for billing, but rarely where changes are first spotted

Construction project management tools generally include change order features, and construction accounting systems can track contract changes, depending on your plan and configuration. Whatever mix you use, decide which system is the source of truth for status, and make sure an approved change updates both project management and accounting. If your team re-keys change orders from Procore or Buildertrend into QuickBooks or Sage by hand, that handoff is where numbers drift and items get skipped.

What to automate, and what to keep human

Change order tracking is a good candidate for workflow automation and AI agents because most of the effort is noticing, collecting, reminding and reconciling. The judgment, which is pricing, negotiating and deciding what is really out of scope, is a smaller share of the hours but all of the risk.

Good to automate	Keep with a person
Scanning daily logs, RFIs and emails for likely changes and opening draft PCOs	Deciding whether an item is truly out of scope
Gathering photos, time tickets, material receipts and sub quotes as backup	Final pricing and markup decisions
Drafting the COR from your standard rates and template	Negotiating with the owner, GC or architect
Weekly follow-up on pending CORs and updating "ball in court"	Handling disputes and claims
Flagging approved COs missing from the next pay app or from accounting	Signing the pay application
Alerting on notice deadlines and work proceeding without a signed CO	Legal positions on notice and entitlement

The design that works is human-in-the-loop: the agent does the gathering and chasing, and routes anything unusual to the PM through clear exception handling rules. A PM who starts the week with a list of five drafted CORs to review, instead of five changes to reconstruct, spends their time where it counts.

This is the kind of work Tarvora does on construction engagements. We build agents inside the tools you already use, such as Procore, Buildertrend, QuickBooks or Sage, start with a free working prototype on your own jobs, and are paid a share of the measured savings. If you're weighing where to start with AI more generally, our AI implementation guide for small businesses walks through picking the first process, and shared-savings pricing explains how the fee model works.

Frequently asked questions