construction.live Article
Unexpected Site Conditions in Construction: What to Document Before Work Continues
Unexpected site conditions can delay construction and put payment at risk if they aren't documented correctly. This guide explains what contractors should record before work continues to support change orders and protect project revenue.
The excavation crew starts trenching exactly where the drawings show. Two feet down, they hit an abandoned concrete foundation that isn't shown anywhere in the plans.
Now everything stops.
The superintendent has three questions. Can the crew keep working? Who pays for this? What needs to be documented before anyone moves forward?
The first few hours after discovering an unexpected condition often decide whether the contractor gets paid for the extra work or ends up absorbing the cost. This guide walks through exactly what to document before work continues, step by step.
What Are Differing Site Conditions?
A differing site condition is a physical condition at the jobsite that doesn't match what the contract documents described, or that no one could reasonably have expected based on normal industry experience. Most contracts call this a Differing Site Conditions clause, sometimes shortened to DSC.
Common examples include:
Buried utilities not shown on the drawings
Rock where the soil report indicated sand or clay
Groundwater at a depth that wasn't disclosed
Unsuitable soil that can't support the planned foundation
Hidden concrete or abandoned foundations from prior structures
Undocumented pipes or conduit
Contaminated material
This article isn't a legal breakdown of DSC clauses or claim requirements. It's a field guide: what to document, in what order, so the condition is provable and the change order that follows has a real chance of getting approved.
What Is a Differing Site Conditions Clause?
Most construction contracts include a Differing Site Conditions (DSC) clause that outlines what contractors must do when unexpected physical conditions are encountered. While the wording varies between contracts, these clauses typically require prompt notice, documentation of the condition, and owner review before additional work proceeds.
Common Examples of Unexpected Site Conditions
Not every differing site condition looks the same, but most fall into a few common categories that affect cost, schedule, or both. Buried utilities that were not shown on the drawings can stop excavation and require coordination before work continues. Unexpected rock often means bringing in different excavation equipment, increasing both labor and equipment costs. High groundwater may require dewatering, which can delay the schedule and add unplanned expenses.
Contractors also encounter existing concrete or abandoned foundations that were not identified during preconstruction. These conditions usually require additional demolition before the planned work can continue. In other cases, unstable or unsuitable soil may require the engineer to revise the foundation design or specify additional ground improvement measures. Hazardous materials, such as contaminated soil or asbestos-containing debris, introduce safety and regulatory requirements that must be addressed before work resumes.
Although each condition presents different challenges, the response should remain consistent. Stop work in the affected area, document what was found, notify the appropriate project stakeholders, and maintain clear records before any additional work begins. Those early records often become the foundation of a change order and help explain both the cost and schedule impact of the unexpected condition.
Unexpected site conditions are just one category of jobsite events that should be documented. Learn about the other jobsite events contractors should document to reduce disputes, support change orders, and protect payment.
What to Do Before Work Continues
Step 1: Stop Work in the Affected Area
Don't keep digging, cutting, or moving material once the condition is discovered. Continuing to disturb the area destroys the evidence that supports a change order later. Isolate the area, keep workers clear, and hold that section of the site exactly as it was found.
Field Tip
Never remove or disturb the unexpected condition before documenting it. Once the evidence is gone, it's much harder to justify additional costs, schedule impacts, or the need for a change order. Take photos, measurements, and notes while the condition remains undisturbed whenever it is safe to do so.
Step 2: Record the Condition Immediately
Capture the location, dimensions, date, time, and which crew discovered it. Do this at the moment of discovery, not at the end of the day. A voice note recorded while standing at the discovery holds details a memory from six hours earlier won't.
Step 3: Take Clear Photos and Videos
A single photo from one angle isn't enough to prove anything. Capture:
Wide shots showing the full extent of the condition
Close-ups of the specific material or obstruction
Measurements, using a tape measure or known object for scale
A reference object in frame (a hard hat, a tool, anything with a known size)
GPS location or a clear description of exactly where on the site this is
Weather conditions at the time
Equipment on site
Crew present
These photos become the primary evidence behind the change order request. Vague or single-angle photos give a reviewer room to question what actually happened.
Step 4: Notify the Superintendent, PM, and Owner
Most contracts require prompt written notice of a differing site condition, and missing that window can weaken or waive the claim entirely. Notify everyone who needs to know before work resumes:
General contractor
Owner
Architect
Engineer
Subcontractor, if the condition affects their scope
Step 5: Document Labor, Equipment, and Materials
This is the section that directly supports future billing. Track:
Labor hours already spent, including any idle time while waiting for direction
Equipment idle time
Extra equipment brought in to address the condition
Rental costs
Materials used or wasted
Subcontractor time affected
Without this, the change order has a description of what happened but no defensible cost behind it.
Step 6: Build the Change Order Documentation
Everything gathered in the steps above feeds into one package:
Photos and video
Daily reports
Voice notes
RFI, if one was submitted
Field sketches
Labor records
Equipment logs
Material receipts
A clear timeline of when the condition was found, when it was reported, and when direction was received
A complete package like this moves through review faster because the reviewer isn't asking follow-up questions. Everything they need is already attached.
Step 7: Wait for Direction Before Proceeding
Work resumes only after the owner or engineer reviews the condition, a change is approved, and instructions are documented in writing. Proceeding before that happens removes the leverage the documentation was built to protect.
What Should You Document?
Date
Time
Exact location
Description of the condition
Weather
Photos
Video
Labor hours
Equipment
Materials
Witnesses present
Notifications sent, and to whom
Related drawings
RFIs
Daily report entry
Voice note
Common Documentation Mistakes
Continuing work before documenting the condition
Taking a single photo instead of a full set
Skipping measurements, so scale can't be verified later
No timestamps on photos or notes
No daily report entry for the day the condition was found
Skipping owner notification, or notifying late
Waiting until evening to write anything down, once details have faded
Forgetting to log equipment hours during the delay
How Proper Documentation Protects Payment
The path from discovery to payment runs through a clear chain: unexpected conditions, documentation, notification, change order, pay application, payment. A break at any link, especially the documentation step, weakens everything that follows. A change order without photos and labor records is a request. A change order with a complete, timestamped package is a claim a reviewer can approve without a second round of questions.
How Construction.live Helps
Most of the documentation gap doesn't happen because crews don't understand the process. It happens because the moment a condition is discovered is chaotic, and details that matter get written down hours later, if at all.
Construction.live helps field teams capture voice notes, geotagged photos, labor records, equipment usage, and site events the moment they're discovered. Every record is automatically organized into a timestamped documentation package that supports change orders, protects payment, and reduces disputes.
Unexpected site conditions don't have to become costly payment issues.
Frequently Asked Questions
What is a differing site condition in construction?
A differing site condition is a physical condition found during construction that differs from the contract documents or from what a contractor could reasonably expect before work began. Common examples include buried utilities, unexpected rock, groundwater, hidden foundations, or unsuitable soil.
What should you do when an unexpected site condition is discovered?
Stop work in the affected area and document the condition before it changes. Record the location, take photos and videos, note the labor and equipment involved, notify the project team, and follow the contract's notice requirements before work resumes.
What documents should be collected for a differing site condition?
Keep records that explain what was found and how it affected the project. This typically includes photos, videos, daily reports, field notes, RFIs, labor records, equipment logs, material receipts, and any supporting drawings or sketches. These documents help support change orders and payment requests.
What are common examples of differing site conditions?
Common examples include buried utilities that are not shown on the drawings, unexpected rock, high groundwater, hidden concrete or abandoned foundations, unsuitable soil, and hazardous or contaminated materials. Each of these conditions can affect project cost, schedule, or both.
Can work continue after discovering a differing site condition?
The affected work area should generally be documented and reported before work continues. The next steps depend on the contract requirements and the direction provided by the owner, engineer, or project manager. Continuing work without documenting the condition can make it more difficult to support a change order later.
Conclusion
Unexpected site conditions don't automatically become expensive disputes. They become disputes when they're poorly documented. The sooner the condition is captured, with photos, labor records, equipment logs, and field notes, the easier it is to justify the change order, keep the project moving, and protect payment for the additional work.
Related reading:
Written by
Rahul Vaishnav
.