See how construction change management software turns verbal field changes into written records before they become disputes.
Mid-walk on the second floor, the super points at a wall and tells the electrical foreman to add four outlets in the conference room. The instruction arrives verbally: "go ahead, we'll square it up later." That verbal instruction can start a change order dispute. Capturing it before the crew picks up a tool is the job construction change management software has to do.
The dispute can start long before pricing gets contested, because once the work is done and the walls are closed, both sides are arguing from memory. That's not a small risk: disputes that reach formal resolution now average $60.1 million in value and take about 12.5 months to resolve according to published reports. The paperwork gap between a verbal directive and a written record is where many of them begin.
Field teams need a repeatable way to turn jobsite deviations into written records before notice deadlines drift away from pricing and authorization.
What this article covers:
- Field changes need written records as soon as cost or schedule impacts appear.
- Verbal approvals, substitutions, and unsigned work become disputes when evidence is thin.
- Plan pins, photos, and same-day notes preserve context before crews cover the work.
- Linked tasks, RFIs, and change orders keep notice deadlines connected to field evidence.
What a field change is, and how it differs from a formal change order
A field change is an informal jobsite deviation from the contract documents, and it's easy to confuse with four related terms that describe different stages of getting it authorized:
- RFI: a question; if the answer modifies scope, the contractor still has to issue a change order request.
- Change order request: a proposal that becomes a change order only after the required signatures.
- Field order: may address minor modifications. Cost or time changes still require a signed change order.
- Signed change order: a written instrument prepared by the architect and signed by the owner, contractor, and architect. It covers the change in the work, the adjustment to the contract sum, and the adjustment to the contract time.
That distinction makes field changes worth documenting immediately: the moment a deviation touches cost or time, it needs to become a formal change order. The rule is plain: no work beyond the scope of the base contract should be performed without prior written authorization from the owner, except in emergencies.
Active jobsites will always have field changes, and each one needs a written record.
Why unmanaged field changes turn into disputes
Several common patterns can move field changes into payment disputes, and they share one root: work happened before anything was written down. Each pattern below fails for a different reason, but the fix is the same one: get the record written the same day, not after the fact.
Verbal instructions with no documentation
Verbal approval doesn't hold up on its own, and field conditions make it the default anyway. Issues arise unexpectedly, schedule pressure pushes crews to proceed, and contractors often skip securing written authorization from the owner first. When that happens, the change order becomes the place where authorization and scope get tested after the fact.
A written record helps show the change was requested, authorized, scoped, and performed. If a contract requires written authorization, verbal approval can leave the contractor arguing waiver or constructive change instead of relying on an approved change order.
In disputes over orally directed work, recovery can turn on whether site representatives' words and conduct showed the written-change-order requirement had been waived. Payment can also turn on whether the person who gave the verbal order had authority to issue it, or whether the order can be verified at all.
Undocumented field substitutions
The second pattern starts when a crew hits a condition that doesn't match the drawings, like a duct bank where the conduit run was supposed to go. The crew makes a field call to substitute material or reroute rather than wait on a formal RFI.
The work is often right. The record is what's missing, and to recover for that kind of constructive change, a contractor must prove both that a true change occurred and that the owner's acts or words ordered it.
That evidence window is also short. Once the substitution is buried under backfill or behind drywall, independent verification of what was installed becomes difficult to reconstruct from memory alone, which is why photographs and videos, time-stamped, are among the project records worth maintaining. When backup is thin, change order pricing becomes harder for trade contractors to defend.
Work performed before a change order is signed
The third pattern is work performed before the change order is signed, extra work that requires careful documentation because most contracts don't obligate a constructor to perform changes affecting contract price or contract time until a change order is executed or a written Construction Change Directive (CCD) is issued. When work truly can't wait, the contractor should document the work as a claim and hit every contractual notice deadline. That deadline matters as much as the final price.
Compare that deadline to how long the paperwork often takes. If a field note sits in a notebook until pricing is finished, the submission can trail the contractual notice window instead of protecting it.
How to capture a field change before it becomes a dispute
Shrink the gap between the deviation and the written record to zero. Start by documenting the deviation while the context is still fresh.
Log the deviation the moment it happens
Documentation created the same day the event occurs is the standard that holds up later. Daily reports, progress records, time records, photographs, videos, RFIs, change orders, and meeting minutes all fall under that same rule: completed and issued while the event is still fresh.
The habit is lighter than it sounds: a 30-second field note is often enough to photograph the condition and capture the conversation. Push the record to the cloud, and the activity history preserves updates with time and date stamps.
A purpose-built tool beats texts and paper for this job. Fieldwire is one example: a mobile-first jobsite management app that turns that 30-second habit into a task, timestamped as it happens. When the super gives the go-ahead on the extra outlets, the foreman creates a task on the spot with the instruction and photo already timestamped, before the work starts, not after.
That task capture works offline on every tier, including the free one, and syncs automatically when the connection comes back.
Tie it to the plan location and photo evidence
A deviation logged in a text thread still has to be matched to a drawing later. A deviation pinned to the plan sheet doesn't. Photograph the condition before work begins and, above all, before it gets covered: rebar before the pour, the reroute before backfill, framing before drywall. Photos carry the most weight when the location and timing are unambiguous, which is exactly what a plan pin and a timestamp provide.
In Fieldwire, tasks anchor to a specific plan location, and photos attach directly to that point on the sheet. On Pro plans and above, photo metadata stamps add the date, time, and GPS coordinates automatically. The record ties the work to its location and timing without anyone typing it up in the trailer that night.
Escalate to an RFI or change order without re-entering data
Each manual handoff where information gets retyped, from field note to email to spreadsheet to formal document, can add delay and drop detail. In Fieldwire, the same record moves forward instead: tasks link directly to change orders, so the field entry that captured the deviation becomes the backup for the formal document without manual re-entry, and RFIs carry the same linked plans and tasks, with an activity log tracking every change by time and date.
RFIs, change orders, and the budget module are available on the Business Plus plan at $89 per user per month billed annually.
Closing the loop: from field change to formal change order
One well-documented change protects one payment. A repeatable loop protects the whole project, and it's the operational habit that prevents disputes systemically rather than one save at a time. The loop your supers and PMs run on every deviation:
- Capture. The moment a deviation is spotted or a verbal instruction is given, it becomes a task. Same day, no exceptions.
- Tag. Pin the task to the plan location and attach timestamped photos, especially of anything that will be covered.
- Escalate. Any task with cost or time impact becomes an RFI or change order built from the same record, inside the notice deadline.
- Approve. Get written sign-off from someone with authority to bind the owner before the work proceeds, or document the claim basis in writing.
- Close. Link the approved change order back to the originating task so the full history, instruction to photo to signature, lives in one place.
That same record, task, photos, RFI, change order, is exactly what disciplined documentation looks like in arbitration, a project history built from the file rather than assembled after the fact.
For a PM, that means change orders priced from evidence instead of reconstructed memory. For a super, it means the go-ahead given at 7 AM is on the record by 7:01.
Frequently asked questions about construction change management software
Create the field record immediately, then move the same record into an RFI or change order request before the notice window closes. If the work truly cannot wait for signature, document the basis for the claim in writing and treat the work as a claim until the formal change order is approved.
The contractor needs proof that the work was directed, authorized, scoped, and performed, plus a record showing who gave the instruction and when. Contemporaneous records are what separate a recoverable oral directive from a denied change order. Good field software should capture the "who" and "when" as a byproduct of the task itself, not as a separate note someone has to remember to write. Fieldwire's activity log ties every task to the person who created or assigned it, with a timestamp, so that detail is on the record automatically.
Track the deadline as soon as the condition is recognized. Waiting until the change order request is fully priced can put the notice period behind the work. The field task, plan pin, photos, RFI, and change order should stay linked so the PM can see whether the notice period is still open.
Include the signed change order form with authorized signatures and written records of related communications including field directives. Add daily logs of labor, materials, and equipment on the changed work, plus site photos before, during, and after the change. Photos of concealed work taken before it's covered carry particular weight. For time-and-materials work specifically, T&M tickets, often built and tracked using Fieldwire's custom forms, add a layer of backup showing exactly what labor, equipment, and materials were logged against the change.
Yes. A field change that touches cost or time is still subject to the same written-authorization requirement as any other change order; the only difference is when the paperwork gets started. Treating a verbal field instruction as informal, or as something to formalize later, is exactly the gap that turns a routine deviation into a dispute.
