Straight into the service manual page
WrenchQuarry
More

Caltrans differing site conditions: the 5-day draft step

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

On a Caltrans job, document the condition, compare it with the project documents, and check the manual's definition before calling it a differing site condition.

Key takeaways

  • Make the site safe, stop anything that could make the condition worse, and document it with photos, notes, and measurements.
  • Pull the project documents and compare them with what you found, without drawing conclusions yet.
  • Read the scope-of-work section, the control-of-work section, and the relevant contract language. Check whether the situation is one the manual excludes.
  • Tell the client what you know, what you do not know, and what you are checking.
  • Route any potential claim record right away, and track the five-day draft clock for a supplemental potential claim record on a differing site condition dispute from the day it is received.

Why this lands on the team lead

When a crew hits something nobody expected, the first phone call usually goes to the team lead. The client wants to know what it is, what it will cost, and how long it will take. Those questions sound simple. On a state highway job, they run into a formal process, and the words you use in the first few days can shape how the issue is handled later.

This post is for team leads who have to explain an unexpected site condition to a client on a Caltrans-type job. It draws on the manual's section on scope of work, which covers differing site conditions. It is general information, not legal advice. Your contract, your specifications, and the current version of the manual decide what applies on your project, so check those before you commit to a position.

Start with the defined term

"Differing site condition" is a defined term in the manual, and it does not mean every surprise on site. The manual describes Type 2 differing site conditions this way:

> "unknown physical conditions of an unusual nature that are materially different from those ordinarily encountered and generally recognized as not inherent in the work provided for in the contract."

That sentence sets several tests at once. The condition has to be unknown. It has to be physical. It has to be unusual in nature and materially different from what is ordinarily encountered. And it has to be something not generally recognized as inherent in the work the contract requires. A condition that fails any one of these is a problem to explain, not automatically a claim.

In practice, the harder questions tend to be the middle ones. Anyone can see that a buried obstruction is physical. The harder questions are whether it was reasonably unknown, whether it was materially different from what the project information suggested, and whether it is the kind of thing the work already accounts for. Treat each test as a separate question with its own evidence.

The manual's scope-of-work section is at Chapter 3, Section 4: Scope of Work.

Surprise is not the same as differing

Team leads often reach for the word "differing" in the first hour, because it feels like the answer the client wants. Slow down. A surprise you did not plan for is only the starting point. The useful question is whether the condition is materially different from what is ordinarily encountered on this kind of work, and whether it would generally be recognized as part of the work.

Those are judgment calls, and they depend on the facts. Soft ground, old fill, groundwater, and buried debris can each be ordinary on one job and unusual on another. Write down what you observed, where you observed it, and what the project documents said about that location. Then let the comparison do the work, instead of starting from the conclusion you hoped for.

Some conditions are excluded by name

Not every buried or hidden thing qualifies. The manual gives examples of situations that are not differing site conditions. It names Section 5-1.36C, "Nonhighway Facilities," and Section 19-1.03D, "Buried Man-Made Objects," as cases that fall outside the category.

For a team lead, the practical step is simple. Before you tell a client that a buried object is a differing condition, check whether the manual or your contract places that situation in the excluded group. Read the referenced sections yourself rather than relying on a summary passed along from the field, because a summary can drop the detail that decides the question.

Type 2 claims are harder to prove

The manual is direct about the proof problem:

> "Type 2 differing site conditions are more difficult to prove and are most frequently asserted by the contractor when there is no soils report data available for comparative analysis."

What this means for you: a differing site condition claim is a comparison. You are showing that what you found is materially different from what the project information led everyone to expect. If there is a soils report or other subsurface data, you have a baseline to compare against. If there is not, you have less to measure against, and the claim is harder to prove.

So the first internal task is an inventory. Pull together every document in the bid package and the project file that says anything about the ground, the structure, or the area you are working in. Note what each one says and how precise it is. Do not overstate what the documents show. A general note about the site is not the same as a specific finding about the spot where your crew is digging.

Keep the inventory separate from your opinions. List each document, the date it was issued, the location it covers, and the exact language it uses. Then write a separate list of what your crew observed. Two short lists side by side make the comparison much easier to explain to a client, a supervisor, or a reviewer than one long narrative.

Read the control-of-work section too

The scope-of-work section points you elsewhere for more detail: "Refer to Section 3-5, 'Control of Work,' of this manual for additional information." Read that section before you write the client explanation. Do not treat section 3-4 as the whole answer. A team lead who quotes one section while the other governs a related point will have a harder conversation later.

What the five-day step covers

The title of this post refers to a five-day deadline. The manual's wording is specific, so here is the rule in plain terms: within 5 days after a supplemental potential claim record pertaining to a differing site condition dispute arrives, the resident engineer prepares a draft response to that record and submits the response to the deputy district director of Construction.

Break that down:

  • The trigger is the arrival of a supplemental potential claim record that pertains to a differing site condition dispute.
  • The five days run from that arrival.
  • The resident engineer is the one who prepares the draft response.
  • The draft responds to the potential claim record and is submitted to the deputy district director of Construction.

Two things follow. First, the five days belong to the agency's draft, not to you. Your job is to have your side of the record organized so the resident engineer has something solid to respond to. Second, the sentence does not tell you how quickly you must raise the issue yourself. That question sits in your contract and in the related sections of the manual, and you should answer it before the client call, not after.

Illustrative example: documenting buried material

Suppose a crew excavating for a drainage structure hits buried material that is not on the plans. The soils report does not match what they found. The lead's first instinct is to call it a differing site condition and tell the client it is a change order.

The lead stops work on the affected item, makes the area safe, and photographs the material with a scale reference in frame. The lead records the location and depth, notes who was present, and pulls the soils report and the plans. Then the lead checks whether the manual names the material as not a differing site condition. Only after that comparison does the lead tell the client what has been found and that the team is evaluating whether it qualifies.

This is not a ruling. The point is the order of operations: observe, document, compare, then characterize.

Questions to answer before the client call

Before you pick up the phone, be able to answer these questions:

  • Where exactly is the condition, and how large is it?
  • What did the project documents say about that location, and how specific were they?
  • What did the crew do when they found it, and did they stop work on the affected item?
  • Is anything about the condition a safety issue right now?
  • What is the current status of the work around it?
  • Who else has seen it, such as an inspector or an agency representative?
  • What are you still unsure about?

If you cannot answer the first three, you are not ready to characterize the condition. You can still call the client. You just should not call it a differing site condition yet.

Explaining it to the client

Clients do not need the whole manual. They need to know what happened, what you are doing about it, what you do not know yet, and what you need from them. A short structure works well:

  1. What we found, where, and when.
  2. How it differs from what the project documents showed, in plain terms.
  3. What we have done to protect the work and the site.
  4. Whether we think this may be a differing site condition, and that we are checking against the contract and the manual.
  5. What we do not know yet, including cost and schedule.
  6. What we need from you, and by when.

A first message might read something like this: "We encountered material at the north footing that is not shown on the plans. We have stopped work on that footing, photographed the material, and recorded its location and depth. We are comparing what we found with the project documents and will confirm whether it qualifies as a differing site condition under the contract. We will send you our findings as soon as that comparison is complete."

Notice what the message avoids. It does not call the condition a differing site condition before the check is done. It does not promise reimbursement. It does not give a dollar figure or a completion date you cannot yet support. Honest uncertainty, stated clearly, usually goes over better than a confident answer that later has to be walked back.

Keep the tone steady, too. Clients often hear a surprise condition as a sign of poor planning, and they may push for a quick answer. Acknowledge the concern, give them the next step and when to expect it, and resist the urge to speculate about who is at fault. Speculation in an early email is hard to take back. For related client messages, see customer arrival updates.

Coordinating inside your company

The team lead should not be the only person deciding how to describe the condition. Bring in whoever handles contracts, estimating, and project controls before the first client message goes out, and agree on the facts together. Keep one person responsible for the written record so that field notes, emails, and daily reports tell the same story. Inconsistent descriptions are one of the easiest ways for a reasonable claim to look weak.

Brief the field crews as well. Foremen and operators are often the first to see a condition, and they need to know what to photograph, what to write down, and whom to call before they decide anything on their own. A short huddle on this topic costs little and can save the team from a weak record later. For related handoff habits, see Field Service Work Order Checklist for Dispatch Handoffs.

Keep the record clean

Whatever you tell the client, the written record is what gets reviewed later. Practical habits make a difference:

  • Take dated photos with a scale reference, from the same spots you will describe in writing.
  • Write daily notes that say what was found, where, when, who saw it, and what was done about it.
  • Track the time and resources spent on the affected item separately from normal work.
  • Keep physical samples or other evidence if safety and the project allow it.
  • Save every communication about the condition, and write a short summary after each phone call.
  • Keep the bid documents, soil data, and drawings you relied on, in the form you had them.
  • Never edit a note after the fact. If something needs correcting, add a dated correction instead.

For related record habits, see job file closeout.

Mistakes that weaken the position

  • Calling every surprise a differing site condition.
  • Implying that the crew should have known, or that someone ignored a document that said otherwise.
  • Waiting to write things down until someone asks for them.
  • Quoting a dollar figure before the cost has been tracked.
  • Continuing work on the affected item without recording what was found and where.
  • Receiving a potential claim record and deciding it is not urgent.

Each of these is easy to do under schedule pressure, and each one makes the later review harder. The fix is usually a checklist the team agrees on before the first condition is found, not a rule invented in the middle of the dispute.

When a claim record arrives

When a supplemental potential claim record on a differing site condition dispute reaches you, treat it as a deadline item the same day. Log the date you received it, confirm who is on the distribution, and calendar the date the agency's five-day period for its draft response ends. Read the record against your own notes and photos, and mark every statement you disagree with or cannot verify. Respond in writing and keep copies of everything you send.

When you respond, stay with facts. Say what your records show, cite the document or note, and identify where you agree and where you disagree. Avoid characterizing the other side's motives. A short, factual response is easier to review than a long argument, and it gives the agency's draft process clear material to work from.

If the record includes facts you can check, check them. Do not argue from memory. Memory tends to smooth over the details that matter most, such as the exact location or the time a crew stopped work. Your written record is the thing that holds up under review, so the goal is to make sure it is complete, accurate, and easy to follow.

Final word

An unexpected site condition is a problem to solve first and a claim to evaluate second. The Caltrans language gives you a precise vocabulary and a specific clock, and both are worth using carefully. Name the condition accurately, compare it honestly against the documents, and keep the client informed without promising an outcome you cannot yet support.

Your next step today

Today, pull together the bid package and project file for the affected area and list what each document says about the ground, the structure, or the work area, with its date and exact wording.

Frequently asked questions

Is every unexpected condition a differing site condition?

No. A surprise becomes a differing site condition only after the manual's definition and its tests are checked against your evidence.

Should the client hear that it is a differing site condition on the first call?

Not yet. Tell the client the condition is being checked against the contract and the manual, and say when you will report back.

Sources

More field guides