Watch: Construction Subcontract Change Orders: Full End-to-End Walkthrough
Recorded May 2026 by Zach Koerber, Co-founder. Want to see this on your own subcontracts? Book a demo.
Construction change order management is one of those problems that sounds simple until you’re in it. Issue a change, get it signed, track the money. Simple enough. But for most GCs managing multiple subcontractors across multiple projects, the reality looks nothing like that, and the breakdown is expensive.
This is a full walkthrough of how Contracts Connected handles construction change order management end to end. From issuing the change order, to vendor e-signature, to automatic document filing and cumulative cost tracking, all without downloading a file, opening DocuSign, or touching a spreadsheet.
Why Subcontract Change Orders Break Down
Change orders fail quietly. Nobody intends to lose track of the paperwork, it just happens when the process depends on email threads, manual tracking, and judgment calls about which version is current.
Here’s what the broken version looks like: a PM issues a change order by emailing a Word document to the sub. The sub prints it, signs it, scans it back. Or they redline it first, and now there are two versions. The signed copy lands in someone’s Downloads folder. The finance team has a separate spreadsheet tracking COs by project. Nobody is sure whether the running total on that spreadsheet reflects the two COs from March or just one of them.
Multiply that across ten subcontractors on one project and you have a version drift problem, a cumulative total problem, and a document retrieval problem all running simultaneously.
The specific failure modes are worth naming:
Email-thread version drift. When change orders travel via email, there is no enforced single version. Attachments get forwarded, renamed, re-sent. It is genuinely common to discover that a subcontractor has a different version of a signed change order than the GC does.
Untracked cumulative totals. Each change order changes the commitment amount. The original contract plus every change order equals the revised commitment. That number drives forecasting, lien exposure, and pay app processing. If it lives in a manually updated spreadsheet, it’s wrong as often as it’s right.
No automatic filing. Executed change orders need to live somewhere findable. “Somewhere” usually means a shared drive with inconsistent naming conventions, or a folder that gets cleaned up during project close-out when everyone is too busy to do it properly.
Scope disputes downstream. Without a paper trail showing what was approved, when, and by whom, scope disputes become he-said-she-said. Change orders that got informally approved via text but never executed formally are a standard source of payment disputes at project close.
None of these are catastrophic in isolation. Together, they’re a serious operational and financial exposure, and they’re entirely avoidable.
Reading about it is step one.
Watching Contracts Connected fill out a real change order, route it for signature, and file it automatically is another. The full walkthrough is earlier on this page. Or book a demo and we’ll run it against one of your own subcontracts.
How Contracts Connected Handles It
The walkthrough covers a live example: issuing change order 002 against a fully executed subcontract for a Windows scope on the Repair Well project. The original contract on that scope was $90,000. One change order had already been issued and fully executed for $10,000. Here’s what the system does with the second one.
Step 1: Select the project and commitment. From anywhere in the platform, click New Change Order. Select the project. The system shows every fully executed commitment under that project, contracts where both parties have already signed. If there are multiple commitments, you can select multiple and issue the same change order against all of them simultaneously. That matters for things like zero-dollar administrative change orders you need to push to every vendor on a project at once.
Step 2: Choose your template. Contracts Connected does not force you to use a system-default change order form. You upload your own template, the same document your subcontractors already recognize and expect from you. If you have multiple change order templates for different project types or contract structures, they’re all available here. The system auto-fills whichever one you select.
Step 3: Fill in the details. Enter the dollar amount for this change order (in this case, $40,000). The system shows you the original contract amount, the total value of any prior change orders, and the new revised commitment total, updated in real time as you type. Fill in scope description, contract number (or work order number, or purchase order number, whatever your organization uses), inclusions, exclusions, and designate who at the vendor’s organization will receive this for signature.
Step 4: Preview before you send. Before issuing, you can preview the fully populated change order in your template. The system has pulled in all the project data, the dollar amounts, the signer information, everything placed into your document exactly as it would appear when the vendor opens it. No copy-paste, no manual data entry.
Step 5: Issue and route. Click Issue Change Order. The system fills out the document, routes it for e-signature, and sends an email to the designated signer at the vendor’s organization. That email contains a direct signing link, no DocuSign account required, no separate platform to log into.
Step 6: The vendor signs. The vendor clicks the link in their email and lands on a signing page that shows them the change order in the context of the full commitment: original contract amount, this change order amount, total change orders to date, and revised commitment total. They review the document, which looks exactly like your preview, and sign with identity verification built directly into the signing flow. That verification step exists so the executed document can stand on its own if a scope dispute ever comes up later, there’s a record of who actually signed, not just an email address that clicked a link.
Step 7: The prime signs. After vendor execution, the change order surfaces in the prime contractor’s to-do list as pending their signature. The system automatically names it CO-002 (or whatever the next sequential number is). Click, sign, verify. Done.
Step 8: Everything updates automatically. Once fully executed, the platform does several things at once. The change order status updates to Fully Executed. The running commitment total, original contract plus all change orders, updates on the project, on the scope, and in the commitment record. The change order document is filed automatically with a standardized naming convention: subcontractor name, EIN, project name, change order number. No manual filing, no renaming.
What This Looks Like Across Your Project
The tracking doesn’t stop at the individual change order record. In this walkthrough, after both parties sign, the project Scopes view updates to show new columns: total change orders issued ($50,000 across CO-001 and CO-002 in this example), and the revised commitment amount ($140,000 against the original $90,000 contract). Drill into the scope and you can see each individual change order, its status, whether it’s pending vendor signature, pending your internal signature, or fully executed, and open the actual document directly from there.
This is the source of truth for your commitment. Not a spreadsheet that someone updates manually. Not an email thread you have to excavate. The number on the screen is the correct number because the system built it from the executed documents.
Document filing follows the same logic. Every executed change order lands in the project document section, automatically named according to your account settings. The default convention in this walkthrough is subcontractor name plus EIN plus project name plus “Change Order” plus number. You configure this once, it applies automatically to every document filed thereafter.
For the full feature breakdown outside of this walkthrough, including how change orders connect to your broader subcontract and compliance workflow, see the Change Order Management product page.
What This Replaces
This workflow eliminates the four failure modes listed above. Version drift disappears because there is one version, living in one system, signed by both parties in that same system. Cumulative totals are always current because every signed change order feeds the number automatically. Document filing is automatic and consistent because the naming convention is enforced by the system, not by whoever is in the office that afternoon.
Most GCs who switch to this describe the bigger shift as confidence: they know what the commitment total is, they know which change orders are executed versus pending, and they can pull any signed document in seconds. That confidence has real value, in negotiations, in pay app reviews, and in dispute resolution when the project is done and someone is contesting what was agreed to.
Construction change order management doesn’t have to be a manual process. This is what automated looks like.
Reading about it is step one.
Watching Contracts Connected fill out a real change order, route it for signature, and file it automatically is another. The full walkthrough is earlier on this page. Or book a demo and we’ll run it against one of your own subcontracts.
Join the AI Blueprint live
The AI Blueprint, the free weekly webinar, is back on Tuesday, January 12, 2027, at 10 AM Pacific (1 PM Eastern). Register once and join any Tuesday. Until then, every past session is on the AI Blueprint page.
Ready to stop chasing paperwork?
Contracts Connected issues, routes, signs, and files your subcontract change orders automatically, with cumulative totals that are always correct and documents that file themselves. See it running against your own subcontracts.
See the product: Change Order Management software→
Related Articles
- AI for Construction: The Complete Guide. The full landscape of AI tools, workflows, and automation opportunities for construction teams.
- AI Document Analysis for Construction. How AI reads, extracts, and validates construction documents, the same underlying pattern that powers change order auto-fill.
- Custom GPT for Contract Risk Review. Using purpose-built AI to review contract language and flag risk before signature.
Frequently Asked Questions
How do you manage change orders for multiple subcontractors on one project?
In Contracts Connected, you select the project, then see all fully executed commitments under it. You can issue a change order against one subcontract or select multiple, useful for zero-dollar change orders you need to push to every vendor on a project simultaneously. The system routes each one for e-signature automatically.
Can I use my own change order template instead of a system default?
Yes. Contracts Connected never forces a default template on you. You upload your own change order template, the same document your vendors already recognize, and the system auto-fills it with the correct project data, dollar amounts, scope details, and signer information. No copy-pasting required.
How does the system track cumulative change order totals?
Every change order is logged against the original commitment. The platform automatically calculates the total value of all change orders issued to date, the revised commitment amount, and shows both pending and fully executed status at the project and scope level. This updates in real time as each change order is signed.
What happens after both parties sign a change order?
Once fully executed, the status updates to “Fully Executed,” projected amounts are replaced with final figures, and the document is automatically filed with a standardized naming convention (subcontractor name, EIN, project name, change order number), all without any manual downloading, renaming, or filing.
Does Contracts Connected require DocuSign for change order e-signatures?
No. E-signature is built directly into the platform. The vendor receives an email with a signing link, reviews the filled-out change order, and signs with identity verification, all without a separate DocuSign account or any drag-and-drop field setup. The prime contractor signs from their own account the same way.