Construction projects change. Customers request additional work, hidden conditions emerge, materials become unavailable, and plans require revisions.
The challenge is not always the change itself. It is keeping a reliable record of what happened, what additional work was proposed, how much it might cost, and who authorized it.
Poor change-order documentation can create confusion about project scope, pricing, schedules, and approvals.
Here are eight common mistakes contractors should watch for.
1. Using Vague Descriptions of Additional Work
A note that says “extra plumbing” or “additional electrical work” may make sense to the person writing it, but it provides little context for someone reviewing the record later.
Better approach: Identify the location, existing condition, proposed work, and reason the work is needed.
For example, instead of “repair pipe,” write:
“Replace the damaged supply-line section discovered behind the kitchen wall during demolition, including associated fittings and pressure testing.”
Specific descriptions help distinguish additional work from the original contract scope.
2. Failing to Document Existing Conditions
A change may be necessary because of a condition that was not visible during the original estimate.
If that condition is not recorded, explaining the reason for additional work may become difficult.
Better approach: Capture dated photographs, measurements, field notes, and other relevant evidence before the condition is altered, when practical and safe.
Include enough context to identify the location and the issue.
Preserve original records where possible.
3. Discussing Changes Without Creating a Written Record
Contractors and customers often discuss project changes by telephone or in person.
Those conversations may be useful, but relying entirely on memory can lead to different understandings of what was requested.
Better approach: Document the discussion promptly and send a written summary through an appropriate communication channel.
Distinguish a discussion or request from formal authorization. Whether a particular communication constitutes approval depends on the contract and applicable law.
4. Providing an Unclear Cost Breakdown
A single lump-sum price may not provide enough information for a customer or project administrator to understand the proposed adjustment.
Better approach: Organize pricing into categories such as labor, materials, equipment, subcontractor costs, and applicable contractual charges.
For example:
| Cost category | Illustrative amount |
|---|---|
| Labor | $600 |
| Materials | $320 |
| Equipment | $80 |
| Subtotal | $1,000 |
These figures are illustrative, not actual project prices.
Any applicable taxes, markups, overhead, or other charges should be handled according to the contract.
5. Ignoring the Schedule Impact
Additional work can affect inspections, deliveries, crew availability, or the sequence of other trades.
Even a relatively small change may influence project timing.
Better approach: State whether the proposed work is expected to affect the schedule. If the effect is unknown, identify what must be evaluated.
Do not confuse a preliminary delay estimate with an approved extension of contract time.
6. Treating a Proposal as an Approved Change Order
A proposed change and an authorized change are not necessarily the same thing.
For example, the American Institute of Architects’ G701 process is designed to document agreed changes to the work, including applicable adjustments to contract sum and contract time.
Different contracts may establish other procedures for notices, approvals, or directed changes.
Better approach: Track the status of each change clearly:
- Identified
- Documented
- Submitted for review
- Revised, if necessary
- Approved, rejected, or otherwise resolved
Follow the governing contract before proceeding with work that requires authorization.
7. Losing Track of Revisions
A proposed change may be revised several times as the parties discuss materials, scope, pricing, or timing.
Without version control, someone may approve or rely on an outdated proposal.
Better approach: Assign a reference number and maintain dated revisions.
For example:
CO-012 — Additional ductwork
- Revision 1: Initial proposed scope and estimate
- Revision 2: Updated material requirements
- Revision 3: Final submitted proposal
Retain important prior versions and correspondence so the history remains understandable.
8. Scattering Records Across Multiple Places
Photographs may be stored on a phone, pricing in a spreadsheet, approvals in email, and field notes on paper.
When those records are disconnected, reconstructing a change becomes unnecessarily difficult.
Better approach: Establish a consistent system for organizing each change with its supporting evidence, communications, pricing, schedule information, and final disposition.
The system can be digital or paper-based. What matters is that the information is complete, accessible, and retained appropriately.
A Practical Change-Order Documentation Checklist
Before submitting a change, confirm that you can answer these questions:
- What changed from the original scope?
- Why is the change necessary?
- What evidence supports the proposed work?
- What labor, materials, and other costs are involved?
- Does the change affect the schedule?
- Who must review or authorize it?
- Which version is current?
- Where will the final record be stored?
A repeatable process makes it easier to maintain consistent records across projects.
How ChangeProof Fits Into the Workflow
ChangeProof: Job Change Orders is a Caivra Tech LLC Android application focused on job change-order documentation.
For contractors looking to organize their field documentation, a dedicated application may offer a more structured alternative to disconnected notes and messages.
Before adopting any tool, verify that its current capabilities meet your business needs and contractual recordkeeping requirements.
Explore ChangeProof: Job Change Orders on Google Play.
For a step-by-step introduction, read our related guide: How to Document Construction Change Orders: A Step-by-Step Guide for Contractors.
Final Thoughts
Good documentation cannot eliminate every disagreement, guarantee payment, or replace contractual approval requirements.
It can, however, provide a clearer record of what was proposed, why it was needed, and how the parties responded.
Avoiding these eight mistakes is a practical starting point for contractors who want more consistent change-order records.
Educational notice: This article provides general construction project-documentation information and is not legal advice. Contract terms and applicable laws govern individual projects.
