Engineering Investigation: How the Process Actually Works

What an Engineering Investigation Is — and What It Isn't

An engineering investigation is not the same thing as a building inspection. A home inspector or maintenance engineer looks at a structure and tells you its current condition. An engineering investigation asks a different question: why did this happen, when did it start, and who or what caused it. That distinction matters enormously in litigation and insurance work, because the answer to "why" is what determines liability, coverage, and repair scope.

I get calls every month from adjusters who say "we already had someone look at it" — meaning a contractor walked the site and gave a repair estimate. That's not an investigation. A proper engineering investigation follows a documented methodology: it develops a hypothesis about the failure mechanism, tests that hypothesis against physical evidence, and rules out competing explanations before reaching a conclusion. If the methodology isn't defensible, the report won't survive a Daubert challenge, and the conclusions won't hold up when a carrier tries to deny a claim or an opposing expert pushes back.

The output of a real investigation is a chain of evidence: measurements, test results, photographs tied to specific locations, and a stated methodology that another engineer could follow to reach the same conclusion. If you can't reconstruct how the engineer got from observation to conclusion, you don't have an investigation — you have an opinion.

When You Actually Need One

Not every crack or leak justifies a full investigation, and running one when it isn't warranted just burns budget. But there are trigger events where skipping the investigation phase — going straight to repair or straight to settlement — creates real exposure later.

For attorneys, the trigger is usually a claim that's already been filed: a construction defect suit, a personal injury claim tied to a collapse, or a subrogation matter where your client needs to establish causation before discovery closes. For insurance carriers and adjusters, the trigger is a claim where causation is disputed — was this hurricane wind damage or pre-existing wear, was this a sudden pipe failure or long-term deterioration excluded by the policy. For property owners, the trigger is usually a life-safety concern: visible deflection in a floor slab, a wall that's moved measurably since the last time someone looked at it, or a balcony that feels different underfoot than it did a year ago.

• Sudden or progressive structural movement — cracking that's widening, not static
• Disputed causation on an active insurance claim (pre-existing vs. event-caused damage)
• Pending or anticipated litigation involving a building failure or construction defect
• Life-safety concerns flagged by occupants, maintenance staff, or a routine inspection
• Collapse or partial collapse of any structural element, regardless of scale

The Investigation Process, Step by Step

The process is the same whether I'm looking at a cracked foundation slab or a partial parking garage collapse — only the depth and instrumentation change. It starts with document review: as-built drawings, permit history, prior inspection reports, maintenance logs, and any available geotechnical data. I want to know what was supposed to be there before I look at what is there. Skipping this step is the single most common shortcut that weakens an investigation — you can't identify a deviation from design if you never read the design.

Next comes the site investigation itself: a systematic walk-through documenting the failure and its surrounding conditions, with photographs referenced to a floor plan or grid, not just a folder of unlabeled images. Depending on the failure type, this includes crack mapping and width measurement with a comparator gauge, moisture readings, level surveys to quantify differential settlement, and in concrete or masonry structures, in-situ testing — rebound hammer readings, half-cell potential surveys for corrosion activity, or core extraction under ASTM C42 for compressive strength verification. For a structural inspection, I'm typically on site anywhere from four hours to two full days depending on the building size and failure complexity.

After fieldwork comes analysis: comparing field measurements against code-required tolerances and original design capacity, sometimes running structural calculations to check whether an element was ever adequate for its loads, and testing alternative causation theories against the physical evidence. Only then does the report get written. If an engineer hands you a report the same week as the site visit on anything beyond a straightforward crack evaluation, be skeptical — lab results on concrete cores or chloride samples alone take 10 to 14 days to come back.

Evidence Preservation and the Spoliation Problem

This is where I've seen more cases damaged than any other single issue. Structural failures get repaired — sometimes within days, for life-safety or business-interruption reasons — and once the damaged material is gone, so is the primary evidence. If you're an attorney or adjuster and you know litigation or a disputed claim is likely, get an engineer on site before demolition or repair starts, or at minimum before it's completed.

When emergency repair can't wait, the fallback is thorough pre-repair documentation: measured drawings, full photographic coverage, retained material samples (a section of failed rebar, a chunk of spalled concrete, a piece of corroded flashing), and ideally a joint site visit with opposing counsel's expert if the case is already contentious. I've had cases thrown out on spoliation motions because a property owner had a contractor tear out a failed retaining wall before any engineer saw it — the wall's failure mode became a matter of dueling speculation instead of physical evidence.

On active claims, I also recommend a written preservation letter as soon as a dispute is anticipated. It costs nothing and it puts the other side on notice. For litigation-support matters specifically, courts increasingly expect this step, and its absence gets raised in motions more often than most attorneys expect.

Case Example: Parking Garage Deck Failure

A commercial property owner in the Southeast retained our firm after a section of the top deck of a five-level precast parking garage began sagging visibly — about 3/4 inch of deflection over a 24-foot span, noticeable enough that tenants complained. The property manager's initial assumption was overloading from valet stacking, and the insurance carrier's field adjuster leaned toward denying the claim on the theory that the damage was operational, not sudden or accidental.

Our investigation found something different. Chloride ion testing on concrete samples from the affected span came back at 8.1 lbs per cubic yard near the top mat of reinforcing steel — well above the 1.5 to 2.0 lbs/yd³ threshold generally accepted as the corrosion initiation point for embedded steel (per ACI 222R guidance). Half-cell potential readings across the span averaged -380 mV, indicating active, ongoing corrosion, not incidental surface staining. When we exposed the top reinforcing mat at three locations, actual concrete cover measured 0.7 to 0.9 inches against a specified 1.5 inches on the original 1998 structural drawings — a construction-era placement deficiency, not overloading and not a maintenance failure by the current owner.

The corrosion had been progressing for years, accelerated by de-icing salt exposure from a nearby roadway and inadequate waterproofing membrane detailing at the deck's expansion joints — a building envelope deficiency compounding a structural one. That combination shifted the causation analysis away from the owner's operations and toward original construction defects, which had coverage implications for the carrier and liability implications for the original contractor, who was later brought into the case. The matter settled before trial, with repair costs — full-depth deck replacement across two bays — estimated at $1.2 million.

Standards That Govern a Defensible Investigation

A big part of what makes an investigation defensible under cross-examination is that it follows recognized standards rather than the engineer's personal judgment alone. ASTM E2018 governs property condition assessments; ASTM C42 governs concrete core testing; ASTM C876 governs half-cell corrosion potential surveys; ACI 318 and ACI 562 set the framework for evaluating existing concrete structures against original design intent. Building code compliance gets checked against whichever edition of the IBC (or state-adopted equivalent) was in force at the time of original construction — not the current code, which is a mistake I still see from less experienced experts.

Citing the applicable standard for every test performed isn't a formality — it's what lets another engineer, or opposing counsel's expert, verify the work independently. When a report just says "testing revealed corrosion" with no standard referenced, no equipment specified, and no raw data attached, that's a report built to be attacked.

Common Mistakes That Undermine an Investigation

Most of the weak investigations I get asked to review as a rebuttal expert share the same handful of problems: destructive testing performed before adequate non-destructive documentation, conclusions stated with more certainty than the data supports, single-cause narratives when a failure clearly involves multiple contributing factors, and reports that skip the

• Testing or demolition performed before adequate photographic and measured documentation
• Conclusions stated as certainties when the physical evidence only supports a probable cause
• Ignoring competing causation theories instead of ruling them out with evidence
• Missing chain-of-custody documentation for retained samples
• No reference to applicable codes, standards, or original design documents

Choosing the Right Investigator and What to Expect in the Deliverable

For attorneys and adjusters, the engineer's credentials matter less than their investigation discipline and courtroom track record. Ask how many depositions and trials they've testified in, whether their reports have survived Daubert or Frye challenges, and whether they've handled the specific failure type at issue — corrosion-driven concrete failure, foundation settlement, and wind-driven envelope failure each require different testing protocols and different code knowledge.

A complete deliverable should include a narrative methodology section, raw field and lab data (not just summarized conclusions), photographs referenced to a site plan, applicable code and standard citations, a stated degree of engineering certainty for each conclusion, and — where relevant — a repair scope with a cost basis. If you're evaluating a report and any of those pieces are missing, that's worth flagging before you rely on it for a settlement decision or a filing deadline. For a deeper look at what happens once fieldwork is complete, see our guide on what to expect during a forensic structural inspection, and browse documented failure types if you're trying to understand a specific mechanism before you call an expert.

Frequently Asked Questions

How long does an engineering investigation typically take?

Straightforward cases — a single foundation crack, an isolated roof leak — can be documented in a single site visit with a report in two to three weeks, largely dependent on lab turnaround for material testing. Complex cases involving collapse, multiple failure mechanisms, or extensive lab testing on concrete, steel, or masonry samples often run six to ten weeks from initial site visit to final signed report.

Who typically requests an engineering investigation?

The three most common requesting parties are plaintiff and defense attorneys building or defending a construction defect or injury claim, insurance adjusters or carriers evaluating disputed causation on a property claim, and commercial or industrial property owners responding to a life-safety concern or preparing for a due-diligence transaction.

What's the difference between an engineering investigation and a routine structural inspection?

A routine inspection documents current condition — is the structure safe to occupy today. An investigation goes further: it determines root cause, timeline of onset, and often assigns a defensible causation opinion suitable for litigation or claims decisions. Investigations require more testing, more documentation rigor, and a report built to withstand cross-examination.

Can an engineering investigation be conducted after repairs are already underway?

Sometimes, but it's far weaker. If demolition or repair has already destroyed the primary physical evidence, the investigation relies heavily on photographs, retained samples, and secondary documentation instead of direct field testing. Whenever litigation or a disputed claim is anticipated, get an engineer on site before repair work proceeds, even if that means a short delay.

Does a forensic engineering investigation replace the need for an expert witness at trial?

No — the investigation produces the factual and technical foundation; the expert witness role is a separate function of presenting and defending that work in deposition and at trial. Most attorneys retain the same engineer for both, since continuity between the investigation and the testimony strengthens credibility, but they are distinct deliverables with distinct standards.