Cano Solutions insight
Construction Change-Order Workflow Tool & Free Tracker
Calculate approval-delay and unauthorized-work exposure, download a free change-order tracker, and build a workflow connecting scope, approval, job cost, and billing.
Published July 12, 2026 · Cano Solutions
Key takeaways
- A reliable change-order process connects identification, pricing, approval, field authorization, job cost, schedule, billing, and closeout.
- Pre-approval work should be a visible, controlled exception with documented authority, scope, limits, evidence, and follow-up ownership.
- Measure approval aging, value pending, administrative effort, exposure, approval yield, and approval-to-billing time—not only the number of open changes.
Free, no-signup tool
Construction Change-Order Workflow Tool
Estimate approval-delay and unauthorized-work exposure, then download a practical tracker for ownership, approval, job cost, and billing status.
End-to-end workflow
A change order is a process—not only a form
A polished form does not prevent margin leakage if the request is not priced, routed, authorized, reflected in the field plan, added to job cost, and billed. The workflow must preserve the contract requirements for each project while giving operations one current view of ownership, aging, value, schedule impact, and authorization.
1. Identify
Capture the potential change, source, date, project context, evidence, and person requesting it.
2. Clarify
Confirm scope, cause, responsibility, contract notice requirements, and whether work is time-sensitive.
3. Price
Estimate labor, material, equipment, subcontractor, overhead, markup, schedule, and downstream effects.
4. Review
Validate scope, pricing, contract support, risk, and internal authority before external submission.
5. Submit
Send the required package through the contractually permitted channel and record receipt and due date.
6. Decide
Capture approval, rejection, revision, partial approval, or documented field authorization with conditions.
7. Execute
Communicate authorized scope, budget, cost code, schedule, procurement, and field instructions.
8. Close
Update job cost, contract value, forecast, billing, invoice reference, documents, and final status.
Information quality
Make each record decision-ready
Required fields should support a decision and the next operating action. The exact requirements depend on the contract, delivery method, company role, and jurisdiction, so align the workflow with project-specific notice, documentation, and authorization requirements.
| Area | Information to capture | Why it matters |
|---|---|---|
| Identity | Project, contract, change ID, originator, date identified, reason category, and related RFI, drawing, directive, or correspondence | Prevents duplicate records and establishes traceability |
| Scope | Clear description, exclusions, assumptions, affected location, trade, quantities, and supporting documents | Defines what is and is not being priced or authorized |
| Cost | Labor, material, equipment, subcontractor, tax, overhead, markup, credits, and total requested value | Supports review, negotiation, forecast, and billing |
| Schedule | Days requested, activities affected, procurement lead time, sequencing, and mitigation assumptions | Makes time impact visible before authorization |
| Approval | Internal reviewer, customer or owner approver, submission channel, submitted date, due date, decision, conditions, and evidence | Clarifies authority, aging, and permitted action |
| Execution | Field authorization, responsible manager, cost code, budget update, schedule update, procurement, and communication date | Connects the commercial decision to the work |
| Billing | Approved value, contract update, billing status, invoice number, billed date, payment status, and close date | Prevents approved work from disappearing before cash collection |
Authorization and risk
Make pre-approval work an explicit exception
Field urgency can pressure teams to proceed while scope and price remain unresolved. The workflow should not silently treat that condition as normal. If project requirements permit an interim directive or field authorization, capture who authorized it, the scope and limit, pricing basis, supporting evidence, notice, and the deadline for formal resolution.
Release work when
- The authorized person and permitted authorization method are verified.
- The scope, financial limit, schedule effect, and conditions are recorded.
- Required notice and supporting documentation have been preserved.
- The field team receives one current instruction tied to the change ID.
- Job cost, forecast, and follow-up responsibility are updated.
Escalate when
- Authority, scope, price basis, or contract notice is unclear.
- Work would conceal a material safety, quality, schedule, or commercial risk.
- Requested work exceeds a documented limit or creates downstream impacts.
- The approval deadline passes while field or procurement commitments approach.
- Decision evidence conflicts across email, meeting notes, portal, and project system.
This operational guidance is not legal advice. Have qualified counsel and contract professionals review notice, authorization, waiver, documentation, and payment requirements for the applicable contracts and jurisdictions.
Workflow state
Define status by the next required action
Status labels should tell the team what is true and who acts next. “Open” is too vague to distinguish a pricing queue from an overdue owner decision or approved work waiting for billing.
Potential change
Scope and supporting evidence are being clarified. Owner: project team.
Pricing
Cost and schedule impact are being prepared. Owner: estimator or project manager.
Internal review
Commercial, contractual, and management review is required before submission.
Submitted
The decision package was delivered and receipt, approver, and due date are recorded.
Revision requested
Specific scope, price, or evidence changes are required before resubmission.
Authorized with conditions
Work may proceed only within documented scope, value, time, or other limits.
Approved
Formal approval is complete and operational and financial systems must be updated.
Rejected or withdrawn
The decision and reason are recorded; commitments, forecast, and field direction are reconciled.
Ready to bill
Approved work and required billing support are complete.
Closed
Work, job cost, contract, billing, documents, and final decision are reconciled.
Connected execution
Connect approval to job cost, schedule, and billing
Change-order data often crosses project management, estimating, document storage, scheduling, ERP or accounting, and customer portals. Define the authoritative source for the commercial record and the business events that update other systems. Avoid copying every field everywhere.
When submitted
Record the submission package, recipient, channel, receipt, due date, requested value, and schedule impact; begin aging and reminders.
When authorized
Notify the project and field owners, create or release budget and cost codes, update forecast and schedule, and preserve conditions.
When revised
Retain version history and superseded values so teams do not act from an outdated attachment or email.
When rejected
Stop or reconcile commitments, update exposure and forecast, communicate field direction, and preserve the reason and evidence.
When complete
Confirm actual cost and schedule impact, required documentation, approved value, and readiness for billing.
When billed
Link the invoice, billed amount, date, payment state, and remaining approved value before closing the record.
Performance visibility
Measure flow, exposure, and collection
| Measure | Definition | Operating question |
|---|---|---|
| Approval cycle time | Calendar days from complete submission to decision | Where are decisions waiting and which approvers or package defects drive delay? |
| Aging by status | Count and value in each status and age band | Which action, owner, or customer decision is overdue? |
| Pre-approval exposure | Value committed or performed without final authorization | How much work is moving under exception and why? |
| Approval yield | Approved value divided by submitted value, with rejected and reduced amounts | Are scope, pricing, evidence, or contract support consistently weak? |
| Administrative touch time | Employee hours spent preparing, following up, updating, and billing each change | Which repetitive steps can be simplified or automated? |
| Approval-to-billing time | Days from approval or completion to billing readiness and invoice | Is approved value becoming cash promptly? |
| Forecast variance | Difference between expected, approved, actual-cost, and billed values | Are margin and cash forecasts reflecting current change exposure? |
Frequently asked questions
Construction change-order workflow FAQs
What is a construction change-order workflow?
It is the controlled process for identifying, clarifying, pricing, reviewing, submitting, authorizing, executing, updating, billing, and closing a change to project scope, cost, or time.
What should a change-order tracker include?
At minimum, track the project and change ID, scope, reason, value, schedule impact, status, current owner, submission and due dates, approval evidence, field authorization, job-cost update, and billing status.
How do you calculate change-order approval exposure?
Useful views include value pending approval, administrative cost, work committed before authorization, disputed or unrecovered value, approval cycle time, and the carrying cost of delayed approval and billing.
Can work begin before a change order is approved?
Contract and legal requirements vary. If an authorized interim path exists, document the authority, scope, limit, conditions, notice, evidence, and formal-resolution deadline. Seek qualified legal and contract guidance.
Can the workflow connect to project and accounting software?
Often, yes. Approved events can update project controls, budgets, cost codes, forecasts, schedules, documents, ERP or accounting, and billing, subject to system capabilities and data ownership.
Where should workflow automation begin?
Start with complete intake, status ownership, approval aging, reminders, and approved-value handoffs. Automate only after contract rules, authorization, exceptions, and systems of record are clear.