The Change Order File: How Environmental Vendors Build Mid-Project Adjustments That Hold Up

Environmental fieldwork is priced against assumptions. The proposal says the borings will reach twenty feet; the driller finds refusal at six. The plan assumes one mobilization; the agency asks for a second round of sampling at a property across the county. The site plan shows a gate wide enough for a rig; the gate is chained and the adjoining owner will not grant an easement.

None of this is unusual. What separates a routine adjustment from a disputed invoice is rarely the substance of the change. It is the paper trail behind it. Vendors who treat change orders as a billing form rather than a contemporaneous record tend to win the work and lose the argument six months later, when the client's project controls group asks why the approved budget moved by nineteen percent.

Distinguishing Variability From Change

Every subsurface project carries a band of expected variability — modest depth differences, an extra hour of decontamination, a sample that must be re-run. Sound proposals name that band and price it, usually through a modest contingency or a stated allowance. Trouble begins when a change exceeds the band and no one says so out loud.

A written trigger schedule, negotiated during contracting rather than invented after mobilization, resolves most of this. Common triggers include:

• Encountering contaminated media, utilities, or structures not identified in the client's records
• Access constraints requiring a different rig class, a longer mobilization, or traffic control
• Agency-requested additions — additional boring locations, expanded analyte lists, extended monitoring
• Schedule compression that forces overtime, second shifts, or expedited laboratory turnaround
• Third-party permitting or utility clearance delays that generate standby time

Each trigger should be paired with a defined response: a notification requirement, a cost estimate, and an approval threshold. Vendors and clients who settle this list before mobilization, when no one is under schedule pressure, generally find that mid-project conversations become administrative rather than adversarial.

The Standard Entry: Four Fields, Every Time

The strongest change orders read like a factual record, not a sales document. They share a consistent structure.

Observation. What was encountered, where, when, and by whom — recorded the same day, cross-referenced to photograph numbers, the daily field report, and the boring or sampling log.

Delta. The explicit comparison between the proposal assumption and field reality. For example: "Proposal assumed eight borings to twenty feet via direct-push; two borings encountered refusal at six and nine feet and required hollow-stem auger completion."

Quantification. Labor hours by classification, equipment, disposal quantities with manifest references, analytical costs, and third-party charges — itemized rather than aggregated.

Notification. Who was informed at the client, through what channel, at what time, and what response was received. This field is the one most often left thin and the one most often probed during a dispute.

A change-order log that captures these four elements for every event hands the client's project manager a defensible record for their own internal approval — usually the real bottleneck in getting work authorized. Helping the client clear that internal hurdle is a service, not a favor.

Pricing Language Built for Review

Change-order disputes frequently turn on rates rather than quantities. The remedy is to price the adjustment mechanisms at the same time the base scope is priced.

Pre-negotiated unit rates for labor classifications and equipment should carry through the master services agreement and be explicitly reaffirmed in proposal exhibits, with an effective date and an escalation provision. Subcontractor pass-through costs should state the markup basis — whether applied to invoiced cost, whether a cap applies, and what the markup covers in terms of management, scheduling, and insurance. Disposal pricing should specify whether it is weight-based or volume-based and address the cost of recharacterization if a waste stream is reclassified.

Two clauses merit particular attention. First, standby and delay rates: crews that sit on a site because a gate is locked or a utility is unmarked still cost money, and an hourly standby rate agreed in advance is far easier to defend than a first-time argument in month four. Second, a written authorization threshold — for instance, that any single event exceeding a stated dollar value or labor-hour count requires written approval before work proceeds, with a narrow carve-out where health and safety demands immediate action. That carve-out should be documented afterward, not relied on as a general practice.

The Verbal Go-Ahead

The most expensive words in environmental fieldwork are "go ahead, we'll paper it later." Verbal approvals are common, understandable, and hazardous in equal measure.

The practical mitigation is a same-day confirmation email to the client representative who gave the instruction, restating the additional scope, the estimated cost, and the time and date of the verbal authorization, with a request to confirm by reply. This is not a confrontational act. It protects the client representative who made a reasonable call under field conditions, and it produces the record their organization needs to approve the work without argument.

Where a vendor proceeds and bills without confirmation, the burden shifts entirely to the vendor, and the honest answer to "who authorized this?" becomes difficult to support. Firms that maintain a standing template, used by every field lead without exception, report fewer of these gaps than firms that rely on individual judgment.

Reconciliation Before Closeout

A change-order log should be cumulative and shared. A monthly summary to the client — original contract value, approved changes, pending changes, remaining contingency, projected final value — costs an hour and prevents the end-of-project surprise that damages otherwise strong relationships.

At closeout, a short reconciliation session walking the log line by line resolves ambiguous entries while memories are fresh and identifies where the proposal's assumptions proved unreliable. That last output is the most valuable. Assumptions that fail repeatedly across a client's portfolio should be repriced, not absorbed.

Change orders are not evidence that a proposal was wrong. They are evidence that the field is not the office. Handled with a consistent record, agreed triggers, and pricing language set before mobilization, they become what they ought to be: a routine administrative act that lets both parties keep working.