The Change Order Approval Process, Step by Step

A change order approval process is the sequence a scope change follows from first request to final signature: create, review, approve, execute, and closeout. Skip a stage, and you either stall payment or build something the owner never agreed to pay for. Before anything else, document the basis for the change in writing, and never mobilize crews on a verbal go-ahead without logging it.

The five stages break down like this:

• Create: capture the trigger, draft the change order request (COR), attach backup
• Review: internal pricing check, then owner or architect review
• Approve: routing through the designated approval matrix
• Execute: signatures captured, work authorized
• Closeout: invoiced, archived, and reflected in the schedule of values (SOV)

Pro Tip: If you started work before paper was signed, write a same-day memo naming who gave verbal authorization and when. That memo is often the only thing standing between you and an unpaid change order.

Key Takeaways

The change order approval process succeeds when every request carries complete documentation, a clear approver, and an SOV reference before it’s ever submitted.

Table of Contents

• Change Order Workflow: From Identification To Closeout
• Who Approves Change Orders And How To Set Thresholds
• What Belongs In A Complete Change Order
• Reading Change Order Statuses And Tracking Approvals
• Why Change Orders Stall Or Get Rejected
• Tools That Shorten The Approval Cycle
• The 90-Second Pre-Submit Checklist
• Getting Your Team To Actually Follow The Process
• Legal And Compliance Considerations For Change Order Approvals
• Connecting Change Orders To Your Accounting And Project Management Systems
• Metrics That Tell You If Your Approval Process Is Working
• What I’ve Learned Running Change Order Approvals
• How CO Hub Fits Into Your Approval Workflow
• Sources

Change Order Workflow: From Identification To Closeout

Most disputes trace back to a step that got skipped, not a step that got done wrong. Here’s the sequence that actually holds up.

1. Identify and flag the change early. Owner requests, RFI responses, and field discoveries (a buried utility, an out-of-tolerance slab) all count. Flag it the day it surfaces, not the day the crew needs an answer.
2. Document the basis. Photos, RFI references, spec citations, and a rough cost range go into the file before you price anything. This is your evidence if the change gets challenged later.
3. Price the change. Break out labor, materials, subcontractor quotes, overhead, and markup separately, then note any schedule impact in days.
4. Submit the COR or PCO. Attach your backup and state an expected response window, typically a few business days depending on contract terms.
5. Route for review. Internal estimator review first, then the owner or architect, then negotiation if the number gets pushback.
6. Execute the approval. Signatures get captured, and the change order becomes binding.
7. Close it out. Invoice against the approved amount, track payment, and archive the historical change order report for your records.

Automation at the notification and signature steps is what actually shortens the cycle, not adding more reviewers.

Pro Tip: Price the change before you flag it as urgent to the owner. A number that arrives fast but wrong invites a second round of negotiation, which costs you more time than waiting one extra day to get it right.

Who Approves Change Orders And How To Set Thresholds

Every change order needs a named approver, and vague ownership is how requests sit untouched for weeks. The typical lineup:

• Project manager: verifies scope accuracy and initial pricing
• Project engineer: checks technical detail against drawings and specs
• Architect or engineer of record: confirms design intent is preserved
• Owner or owner’s representative: approves cost and schedule impact
• Contracting authority: signs for public or bonded work where formal authority is required
• Financial approver: confirms budget availability, especially past a dollar threshold

Approval routing can require all members of a group to sign or just one acting on the group’s behalf, a setting Oracle’s change management documentation calls “Response Required From.” Set dollar thresholds so small changes route to a single approver and large ones require the full chain. When an approver goes silent, escalate through a delegated backup rather than letting the request sit in limbo.

What Belongs In A Complete Change Order

A change order missing even one field invites a rejection or a delay. At minimum, include:

• Header data: CO number, project ID, author, date issued, date needed
• Scope description: specific enough to reference the exact drawing sheet or spec section it modifies
• Itemized cost breakdown: labor, materials, subcontractor quotes, overhead, and markup shown separately
• Schedule impact: revised completion date, stated in calendar days
• SOV line references: which line item the cost adds to or deducts from
• Supporting attachments: subcontractor quotes, photos, RFI numbers
• Signature block: physical signature or e-signature audit trail

Procore’s guidance on change orders notes that a complete request with clear description, reason, and impact analysis is one of the biggest levers against disputes. Deduct lines carry their own risk: if the deduct doesn’t cite the specific SOV line it’s reducing, some systems will lock the SOV entirely until the reference gets corrected.

Reading Change Order Statuses And Tracking Approvals

Every change order moves through a defined lifecycle, and knowing what each status actually means saves you from chasing the wrong person.

• Draft: still being priced or written, not yet submitted
• Pending Approval: submitted and sitting with the current approver
• Interim Approval: partial signoff, often used when a group requires multiple signatures in sequence
• Approved: fully executed and binding
• Rejected: sent back, usually with comments attached
• Void or Completed: closed out, either canceled or fully invoiced

Wisconsin DOT’s change order documentation lays out this lifecycle clearly, and most construction platforms mirror it with an approval-tracking view showing the current approver, the approval round, and any override history. Configure reminders so an untouched request escalates automatically after a set number of days rather than relying on someone remembering to follow up. Once every signature lands, the historical change order report becomes your proof of finalization, and in most systems it locks the record from further edits.

Why Change Orders Stall Or Get Rejected

Most rejections trace back to the same handful of mistakes.

1. Starting work without written approval. If field conditions force a same-day start, document the verbal authorization in writing within 24 hours, including who gave it.
2. Missing SOV references. Deduct lines without a clear reference to the original line item get bounced back almost automatically.
3. Vague scope language. “Additional electrical work” invites questions; “relocate three 20-amp circuits from Room 214 to Room 218 per RFI #47” does not.
4. Misconfigured approver groups. If nobody’s designated as the required signer, requests sit indefinitely. Audit your approval matrix quarterly.
5. Resubmitting without changes. After a rejection, version the document, attach a short cover memo explaining what changed, and highlight the corrected fields.

Pro Tip: When a change order bounces twice, stop editing the same document. Start a fresh version with a change log at the top listing exactly what was revised. Reviewers approve faster when they can see what’s different without re-reading the whole thing.

Tools That Shorten The Approval Cycle

Paper-based routing is where most delays actually live, not in the pricing itself. Electronic signature platforms like DocuSign create a timestamped, unalterable audit trail. That trail becomes your record if a change order is ever questioned months later during a dispute or audit.

Software that links change orders directly to SOV lines prevents the deduct-line failures covered above, since the system flags a missing reference before submission instead of after rejection. Standard templates, PCO/COR forms and AIA G701, keep formatting consistent across a portfolio of projects.

Won2Build’s CO Hub builds capture, SOV linking, approval routing, and e-signature capture into one workflow, so the historical report generates automatically once the last signature lands.

• Templates: PCO, COR, AIA G701 for formal change order execution
• Attachments: photos, subcontractor quotes, RFI references, cost backup
• Audit trail: signature timestamps tied to the SOV line they affect

The 90-Second Pre-Submit Checklist

Run this before you route anything:

1. CO number and project ID entered correctly
2. SOV line reference attached for any add or deduct
3. Itemized pricing broken out (labor, materials, subs, markup)
4. Schedule impact stated in days
5. Backup attachments included (photos, quotes, RFI numbers)
6. Correct approver group assigned
7. Signature method confirmed and ready (wet ink or e-signature)

Once approved, notify affected subs immediately, update the schedule and budget forecast, and file the historical report where it’s accessible for both audits and post-project profitability analysis.

Getting Your Team To Actually Follow The Process

The workflow only works if everyone touching a change order follows it the same way, and that takes more than handing out a flowchart. Field superintendents need a five-minute walkthrough on what counts as a documentable trigger, an owner ask, an RFI answer, a field discovery, versus something that’s just normal scope. Estimators need a standard pricing template so two people don’t format cost breakdowns differently on the same project.

Run a short onboarding session anytime someone new joins the CO chain, whether that’s a new PE, a subcontractor’s foreman, or an owner’s rep unfamiliar with your system. Fifteen minutes covering the five stages, who owns each one, and where the SOV references live prevents the most common failure mode: someone submitting a request that looks nothing like the standard format, which then bounces for reformatting instead of real revision.

Change management matters most when you’re moving from paper or email chains to a digital system. Field crews resist new software when it feels like extra steps on top of what they already do; using BRCKS construction project communication software can simplify presenting change orders and streamline communication workflows. Frame it the other way: the SOP and template approach documented by Glyde shows that a defined standard operating procedure with target SLAs, say, five business days from PCO to approved CO, gives everyone a shared benchmark to measure against, rather than a vague sense that things are “taking too long.” Post that SLA somewhere visible. Review it monthly with whoever owns the approval matrix, and adjust thresholds when one role consistently becomes the bottleneck.

Legal And Compliance Considerations For Change Order Approvals

A change order that lacks proper written authorization isn’t just an administrative gap, it can be a payment risk. Most construction contracts specify that only a change order signed by an authorized representative constitutes a binding modification to the contract sum or schedule. Proceeding on a verbal instruction, even from a project owner who clearly wants the work done, leaves you exposed if that same owner later disputes the cost.

Contractor guidance on change order management draws a firm line between a COR, which is a proposal, and an executed change order, which is a contract modification. That distinction matters most on public or bonded work, where a contracting authority may have statutory limits on what can be approved without additional board or agency signoff. If a change pushes past a certain dollar threshold, some public contracts require a separate approval process entirely, sometimes involving a public meeting or formal bid amendment.

Retention rules and lien rights can also hinge on how a change order is documented. In many states, unapproved extra work isn’t lien-eligible the same way contracted work is, which means the paperwork isn’t just about getting paid faster, it’s about whether you can legally compel payment at all. Keep every verbal authorization memo, every rejected version, and every signature timestamp. That record is what protects you if a dispute ends up in front of an arbitrator or a court years after the work is done.

Connecting Change Orders To Your Accounting And Project Management Systems

A change order that lives only in a shared drive or an email thread creates a second problem beyond approval delay: your budget and your accounting system don’t know it exists until someone remembers to update them. That gap is where profit margins quietly erode.

The fix is integration, not more spreadsheets. When an approved change order automatically updates your job cost budget and flows into your accounting system’s billing schedule, the SOV stays accurate in real time instead of getting reconciled weeks later during a monthly close. This matters most on projects with a high change order volume, where a dozen small approved changes can add up to a meaningful shift in projected profit that nobody notices until the final job cost report.

Project management platforms that sync field data with office accounting also cut down on the double entry that causes most reporting errors: a PM logging a change order in one system while the accounting team re-keys the same numbers into QuickBooks or Sage. Every re-key is a chance for a typo, a wrong line item, or a missed deduct reference. Tools built for subcontractors, rather than adapted from general contractor software, tend to handle this better because the SOV structure and billing cycles match how subs actually invoice.

Metrics That Tell You If Your Approval Process Is Working

You can’t fix a slow approval process you’re not measuring. A handful of KPIs give you a real read on where the bottleneck sits.

Average days from submission to approval is the baseline metric. Track it by project and by approver, not just as a portfolio average, since one slow-moving owner’s rep can drag the whole number down without the rest of your process being broken.

Rejection rate tells you whether your team is submitting clean requests or generating rework. A rejection rate climbing month over month usually points to a documentation gap, not a pricing problem, since most owners reject on missing backup before they reject on cost.

Change order volume as a percentage of contract value flags scope creep early. If change orders are running well above your historical average on a project type you’ve built before, something in the original scope or estimate was off, and that’s worth a post-project review regardless of how smoothly the approvals went.

Time from approval to invoice measures whether your closeout step is actually happening promptly or getting deprioritized once the excitement of getting signoff wears off. A gap here is pure cash flow leakage.

Track these quarterly at minimum, and review them with whoever owns your approval matrix. A number moving in the wrong direction is usually your earliest signal that a role, a threshold, or a template needs adjusting before it becomes a pattern across every project you run.

What I’ve Learned Running Change Order Approvals

I once watched a $40,000 change order sit for three weeks because nobody had updated the approval matrix after a project engineer left the company. The fix was embarrassingly simple: a monthly five-minute audit of who’s actually assigned to approve. My rule of thumb now: if a CO hasn’t moved in five business days, someone isn’t the problem, your routing is.

— Jen Reese

How CO Hub Fits Into Your Approval Workflow

You’ve seen every stage of this process now, and the pattern is clear: the delays almost never come from pricing disagreements, they come from missing references, unclear routing, and paperwork sitting in someone’s inbox. Won2Build’s CO Hub is built around that exact gap.

CO Hub captures the change request, links it directly to the affected SOV line so deduct errors get caught before submission, routes it through your configured approval matrix, and captures e-signatures with a full audit trail. Once the last signature lands, the historical report generates on its own, no manual PDF assembly required. Because CO Hub runs on the same login as Won2Build’s Takeoff module, the quantities behind your change order pricing come from the same source as your original estimate, which cuts down on the re-keying that causes so many pricing disputes in the first place.

If you’re still routing change orders through email and shared spreadsheets, start with a free trial of CO Hub and run your next change order through it end to end. You’ll see exactly where your current process loses time.

Sources

• Change order approval process
• Change Order Workflow processes (OFCC)
• Change order approval process (Oracle docs)

Recommended

• Best Change Order Tracking Solutions for Subcontractors — Won2Build Blog
• Commercial Construction Addendum: What Contractors Need to Know — Won2Build Blog
• Construction Bid Submission Checklist for Subcontractors — Won2Build Blog