A subcontractor receives a site instruction on Monday morning.
The work needs to start immediately because the next trade is scheduled for Wednesday. The supervisor takes two photographs, writes the additional labor hours in a notebook and tells the project manager by phone.
The work is completed on time. The commercial process is not.
One photograph stays on the supervisor’s phone. The cost calculation is prepared later in a spreadsheet. The project manager searches through emails for the original instruction. The customer asks for more evidence. The subcontractor prepares the change order again, and the payment application moves forward without the additional work.
The construction was completed in two days. The money may remain unresolved for several weeks.
This is not only a documentation problem. It affects cash flow, project margins, forecasting, working relationships and the amount of time experienced people spend on administration.
A better construction change order workflow connects the first field instruction with scope, evidence, pricing, approval, budget and billing. This article explains where the process usually breaks and how contractors can improve it with clear responsibilities and practical technology.
What Is a Construction Change Order?
A construction change order is a formal amendment to the agreed project scope, cost, schedule or another contract term. It may result from a design revision, an unforeseen site condition, an owner request, a material substitution, a quantity difference or corrective work.
Change does not automatically mean that a project has failed. Construction projects involve physical conditions, many participants and decisions made over time. Some changes are unavoidable and some may improve the final result.
The risk appears when work begins before everyone shares the same understanding of:
- What changed
- Who requested it
- Why it was necessary
- Which drawing, instruction or contract item it affects
- What labor, materials and equipment are required
- Whether the schedule will change
- Who must approve the cost
- When the additional work can be billed
Without one reliable record, each party builds its own version of the event. A field supervisor remembers the verbal instruction. The project manager has a photograph. The estimator has a cost sheet. The owner has not seen the complete request. By the time the invoice arrives, the discussion is no longer only about the work. It is about evidence and entitlement.
Why the Problem Deserves Leadership Attention
The 2026 State of Change Orders research, based on a survey of nearly 200 US contractors, shows how widespread the problem remains.
The published findings report that 83% of general contractors still track change-order exposure in spreadsheets even when financial software is available. The same research estimates that change-order administration can consume 36 hours each week on a project. Among specialty contractors, 92% said change orders were not always paid in full.
A separate summary from Dodge Construction Network and Clearstory found that only around one-third of participating contractors believed their process worked very well. It also reported that the journey from completed work to an authorized change order took almost seven weeks for specialty contractors. Read the 2026 findings for the full detail.
These figures come from an industry survey published with a change-order software company, so businesses should treat them as useful market evidence rather than universal benchmarks. The operational pattern is still clear: disconnected records and inconsistent processes make cost control and payment more difficult.
The United States Department of Transportation reaches a similar practical conclusion in its Understanding Construction Change Orders report. It recommends collecting change-order causes, tracking outcomes and using shared data to identify recurring risks and improve decisions.
The issue also connects with rework. Research highlighted by the American Society of Civil Engineers found that field rework costs were often underreported. Better documentation and cause tracking can support more accurate forecasting and quality management.
Where Change Orders Usually Get Stuck
1. The instruction begins in an informal channel
Urgent site decisions often begin through a conversation, phone call, text message or marked-up photograph. That may keep the work moving, but it does not automatically create a complete commercial record.
If the instruction is not transferred into a controlled workflow immediately, the team later spends time rebuilding what happened.
2. Field evidence is incomplete
A useful change record may need photographs, dates, location, drawing references, labor hours, equipment time, material quantities and the person requesting the work.
When these details are collected several days later, accuracy falls. People forget the sequence, photographs become difficult to identify and daily records may not match the submitted cost.
3. Contract notice is handled separately
The operational team may know that the work changed, while the commercial team is still preparing the required notice. If the contract has a specific notice period or submission method, a delay can weaken the claim.
A workflow should flag the notice requirement and its deadline. It should not attempt to replace professional contract review.
4. Pricing waits for several people
The supervisor provides labor hours. Procurement confirms material prices. The estimator adds equipment and subcontractor costs. Commercial management checks rates and markup. Leadership approves requests above a threshold.
When these steps happen through separate emails, nobody has a clear view of what is waiting and who needs to act.
5. The owner sees the request too late
Some changes need immediate action to protect safety, quality or schedule. Even then, the owner or general contractor should receive early notice of the potential cost and schedule effect.
Receiving a complete claim weeks after the work has finished creates surprise. Surprise often becomes challenge, negotiation or delay.
6. Approved work does not reach billing
A signed change can still be missed if the project system, budget and accounting process are not updated. The team may know that approval exists, but the approved value is absent from the next payment application.
The process is complete only when the approved change is ready for billing and visible in the financial forecast.
The Complete Digital Change Order Workflow
Technology should support the commercial process rather than define it. A practical workflow can follow nine connected stages.
| Stage | Required action | Useful system support |
|---|---|---|
| 1. Identify | Record the field event as soon as it occurs | Mobile form with project, location, date and responsible person |
| 2. Capture | Add photographs, notes, drawing references, labor, material and equipment details | Camera upload, structured fields and offline saving |
| 3. Notify | Send early notice to the required internal and external recipients | Templates, deadline reminders and delivery record |
| 4. Assess | Review scope, contract position, schedule and cost effect | Assigned reviewers, comments and status tracking |
| 5. Price | Build the change-order value from approved rates and supporting costs | Rate library, calculations and supporting attachments |
| 6. Approve internally | Apply authority limits before external submission | Approval routing based on value or risk |
| 7. Submit and negotiate | Share one controlled package and record responses | Version control, response log and revision history |
| 8. Authorize | Store the final decision, value, schedule effect and conditions | Electronic acceptance and controlled document storage |
| 9. Bill and report | Update the project budget, forecast and payment application | Accounting integration, dashboard and billing status |
Every stage should use the same change identifier. This prevents the field record, quotation, approval and invoice from becoming separate items that have to be matched manually.
What the Field Team Needs
The field interface must be fast. If recording a change takes too long, supervisors will return to calls and notebooks.
A mobile form should normally allow a supervisor to:
- Select the project and work area
- Describe the requested change
- Identify who gave the instruction
- Link a drawing, RFI or site instruction
- Take before, during and after photographs
- Record labor by worker or crew
- Record material and equipment use
- Note immediate schedule or safety concerns
- Capture acknowledgement when appropriate
- Save information without a stable internet connection
The system can ask the office team for commercial details later. The site team should capture facts at the point of work, not complete a long contract questionnaire. This is the same principle behind our field-first mobile app development work.
What the Project and Commercial Teams Need
The office view should answer five questions without searching through messages:
- 1What is the current potential exposure?
- 2Which changes need notice or pricing today?
- 3Which submissions are waiting for customer action?
- 4Which authorized amounts are ready for billing?
- 5Which causes are appearing repeatedly?
Useful dashboard views include ageing by status, value by project, unapproved exposure, days awaiting approval, disputed value, approved but unbilled value and changes by cause.
The dashboard is not the goal. Its value comes from showing where a decision is waiting and helping the responsible person act.
A Simple Example
Consider an electrical subcontractor asked to move installed containment after a late design revision.
In a disconnected process, the supervisor receives the instruction verbally, completes the work and sends photographs through a message. The estimator prices the work several days later. The general contractor asks when the instruction was given and whether the original installation followed the issued drawing. The project team then searches for the drawing revision and daily report.
In a connected process, the supervisor opens the project record before work starts. The form captures the location, instruction, drawing reference and initial photographs. It creates a unique change number and alerts the project manager. The commercial team issues the required notice, adds approved rates and attaches the design revision. The submission contains one clear timeline. When approval arrives, the value moves into the billing queue.
The system does not decide whether the subcontractor is contractually entitled to payment. It makes the facts easier to review and reduces the time spent reconstructing the event.
Build, Buy or Connect Existing Systems?
Contractors do not always need a completely new platform.
| Situation | Practical approach |
|---|---|
| The company has a suitable project platform but teams use it inconsistently | Simplify forms, configure approvals, train users and improve reporting |
| Field capture is weak but accounting and project controls work well | Add a focused mobile application and connect it to current systems |
| The process depends on email and spreadsheets across many projects | Introduce a managed change-order workflow with clear ownership |
| The business has specialist contract, pricing or customer requirements | Build a tailored module around existing commercial rules and integrations |
| Several systems hold overlapping records | Create an integration layer and agree which system owns each field |
The right answer depends on project volume, contract types, current software, field connectivity, reporting needs and budget. A short process assessment is usually more valuable than choosing a product from a feature list.
What Technology Cannot Fix
A digital form cannot correct an unclear contract. A dashboard cannot force a customer to agree with the price. An electronic approval cannot replace commercial judgement.
Technology will also struggle when:
- Teams do not agree on what counts as a potential change
- Nobody owns early notice
- Rate schedules are outdated
- Approval authority is unclear
- Leaders allow workarounds outside the process
- Field teams see data entry as office administration with no benefit to them
Successful implementation needs clear rules, simple forms, training and visible support from project leadership.
A 90-Day Implementation Plan
Days 1 to 30: Understand the current process
Map one recent change from site instruction to payment. Record every person, document, spreadsheet and system involved. Review delayed, disputed and written-off changes to find repeated causes.
Agree on the required stages, status names, ownership and approval limits. Confirm contract notice requirements with the appropriate commercial advisers.
Days 31 to 60: Configure one pilot
Choose one active project and one cooperative site team. Create the mobile capture form, notice template, pricing structure, approval path and dashboard.
Connect only the systems required for the pilot. Avoid turning the first release into a complete replacement for project management and accounting software.
Days 61 to 90: Test and improve
Use the workflow for real potential changes. Review how long each stage takes and where users leave the system. Speak with supervisors, project managers and commercial staff.
Improve the form, remove unnecessary fields and document the operating process before expanding to more projects.
Metrics Worth Tracking
| Metric | Why it matters |
|---|---|
| Time from field event to first notice | Shows whether the business is protecting its position early |
| Time from notice to priced submission | Measures internal commercial speed |
| Time awaiting external approval | Identifies customer or project bottlenecks |
| Unapproved change value | Shows current financial exposure |
| Approved but unbilled value | Finds revenue that should move into payment applications |
| Percentage paid in full | Measures submission quality and commercial outcome |
| Changes by cause | Supports design, procurement and project improvement |
| User completion rate | Shows whether the workflow works for site teams |
Do not use a single metric to judge a team. A difficult project can produce more changes for reasons outside the contractor’s control. Metrics should support earlier action and better conversations.
How HMB Digital Can Help
HMB Digital helps companies turn manual operational processes into practical web and mobile systems. For construction change orders, that may include process assessment, mobile field capture, project dashboards, approval workflows, document generation, accounting connections and secure customer access.
We can work with an existing project platform or build a focused application where standard tools do not fit the business. The first step is to understand the contract process, current systems and the point where money or information is getting stuck.
See how we built a workplace safety platform for a UK manufacturer, explore our industry software solutions, or contact our consulting team to discuss a change-order workflow assessment.
Final Thought
Construction companies do not lose control of change orders because their teams do not care. They lose control when fast site decisions enter slow and disconnected commercial processes.
The most valuable improvement is a reliable chain from instruction to evidence, price, approval and billing. When every person works from the same record, the business can respond earlier, forecast more accurately and spend less time proving what already happened.
Frequently Asked Questions
What is a construction change order workflow?
It is the controlled process used to identify, document, price, approve, authorize and bill a change to the agreed construction scope, cost or schedule.
Why do change orders take so long to approve?
Common reasons include incomplete field evidence, late notice, unclear scope, missing cost support, several approval levels, disputed responsibility and information spread across different systems.
Can change order software guarantee payment?
No. Payment depends on the contract, entitlement, evidence, pricing and customer decision. Software can make the record clearer, improve timing and show where action is required.
What information should a change order include?
The required content depends on the contract. A useful package often includes the change description, reason, instruction, location, dates, photographs, drawing references, labor, materials, equipment, cost calculation, schedule effect and approvals.
Should site supervisors price change orders?
Site supervisors should capture facts, quantities and resource use promptly. Estimators or commercial staff can apply contract rates, markup and pricing rules unless the company’s process assigns that responsibility differently.
Can a mobile application work without site internet?
Yes. A suitable application can store field records on the device and synchronize them when connectivity returns. Offline behavior should be tested on the actual project site.
Should change orders connect with accounting software?
Usually, yes. Approved values should update project budgets, forecasts and billing without repeated entry. The exact connection depends on the accounting and project systems already used.
What should a contractor improve first?
Start with early field capture and clear ownership. If the initial instruction, photographs, quantities and notice are reliable, the later pricing and approval stages have a much stronger foundation.
Share Article
About the Author

Bipin Verma
LinkedInManaging Director
HireMisterB Digital
Bipin leads HireMisterB's strategic vision and enterprise client relationships. With over a decade of experience helping businesses across the US, UK, and India digitise their operations, he believes technology only matters when it creates measurable business value. His background spans product strategy, digital transformation, and building high-performance distributed teams.


