Building Failure Analysis Report: What Attorneys & Insurers Need

Why the Report Matters More Than the Site Visit

Clients hire us for the site visit — the walkthrough, the measurements, the photographs. But the deliverable that actually gets used in a deposition, a claim denial appeal, or a settlement negotiation is the report. I've seen technically sound investigations get gutted on cross-examination because the report was sloppy about methodology, or because it stated conclusions the data didn't support. I've also seen a 14-page report with three clear photographs and a load calculation settle a six-figure claim without a lawsuit ever being filed.

If you're an attorney retaining an engineer, or an adjuster reviewing one, the question isn't just "did they find the cause of the failure." It's "will this document hold up when someone with an incentive to discredit it tears into every paragraph." That's a different standard than most people assume going in.

What a Defensible Building Failure Analysis Report Actually Contains

A report that will survive scrutiny in litigation or an appraisal process has a predictable skeleton. It states the scope of assignment and who requested it. It lists every document reviewed — permits, as-built drawings, maintenance logs, prior inspection reports — with dates. It describes field methodology in enough detail that another engineer could replicate the inspection: instrumentation used, number of test locations, environmental conditions during the visit.

Then it separates observation from opinion. This is where weak reports fall apart. An observation is "measured concrete cover over top reinforcing steel at 11 locations, ranging from 0.4 inch to 0.9 inch, against a specified 1.5 inch per the structural drawings." An opinion is "inadequate cover contributed to accelerated corrosion and loss of section." Both belong in the report, but they need to be clearly distinguishable, and the opinion needs to trace back to a stated engineering basis — a code section, a published failure mode, a calculation — not just the engineer's say-so.

Finally, the report needs a stated degree of engineering certainty, consistent with how your jurisdiction defines it (usually "more likely than not" or "reasonable degree of engineering certainty"), and it needs to address — not ignore — the alternative causes a defense expert will raise. If I don't address the obvious counter-argument in my own report, opposing counsel will raise it for me, and it looks a lot worse coming from them.

Case Example: A Parking Structure Report That Held Up

A four-level post-tensioned parking structure in south Texas had a 38-foot span of the third-level slab develop a sudden sag of roughly 2.25 inches, visible as ponding during rain and a crack pattern radiating from a tendon anchorage. The property owner's insurer initially attributed it to vehicle overload — a plausible theory given it was a parking deck.

Our investigation found something different. Ground-penetrating radar located the post-tensioning tendon profile; at the failure location the tendon had draped nearly 3 inches lower than its design profile, consistent with chair displacement during the original concrete pour decades earlier. A grout intrusion survey at the anchorage showed voids consistent with incomplete grouting, and chloride testing near the anchor returned 3.8 lbs/cy — well above the 1.0 lb/cy corrosion threshold commonly referenced for post-tensioned systems. The tendon had corroded through at a wire-break location, and lost roughly 40% of its load-carrying capacity at that cross-section before the remaining wires yielded under normal live load.

The report laid out each finding with GPR scan images, core photos, and lab chloride data side by side with the design drawings, then walked through why vehicle overload — static passenger vehicle loads of roughly 4,000 to 6,000 lbs — could not explain a tendon failure of that magnitude. The case settled before a deposition was ever scheduled, largely because the defense expert's rebuttal report never addressed the chloride data at all. That's the difference a well-built report makes — it doesn't just state a conclusion, it forecloses the easy counter-arguments.

Timeline and Cost: What to Realistically Expect

Clients frequently ask for a number before they've described the failure, and I understand why — budgets and litigation deadlines are real constraints. But building failure analysis cost scales with complexity, not square footage. A single foundation crack with an obvious cause might run a few thousand dollars and two to three weeks from site visit to final report. A multi-building roof collapse with competing theories, destructive testing, and lab analysis can run well into five figures and take two to four months, largely because lab turnaround on concrete cores, steel metallurgy, or moisture content testing is outside our control.

The phases are generally consistent: initial document review and site visit (1-2 weeks out from engagement), field testing and any lab submittals (2-6 weeks depending on lab backlog), analysis and calculation (1-3 weeks), and draft report review (1-2 weeks). If litigation is already filed, build in time for a Rule 26 or state-equivalent disclosure deadline — that date should drive when you engage the engineer, not the other way around. Engaging an engineer six weeks before a disclosure deadline on a complex failure is a common and avoidable mistake.

How Insurers and Attorneys Use the Report Differently

An insurance carrier reviewing a report for claim support is usually asking a narrower question: is this damage attributable to a covered peril, and what is the cost to repair it to pre-loss condition. The report needs to map cleanly to policy language — distinguishing wear-and-tear or pre-existing conditions from sudden, covered events, and itemizing repair scope in a way the carrier's estimators can price.

An attorney retaining the same type of expert for litigation needs the report to do more: survive a Daubert or Frye challenge, support deposition testimony without contradiction, and anticipate the opposing expert's likely theory. I've had carriers ask me to soften language that was accurate but unfavorable to their position — that's a line I won't cross, and it's worth confirming up front with any engineer you retain that the report reflects findings, not the client's preferred outcome. A report that reads as advocacy rather than analysis gets excluded or discredited, and it damages the retaining party's credibility along with the engineer's.

Red Flags That Signal a Weak Report

Most problems I see in reports from other firms — ones I review as a rebuttal expert — fall into a short list of patterns. Watch for these when you're reviewing a report from any engineer, including one you've retained yourself.

• Conclusions stated before the methodology that supports them, or methodology that's vague ("visual inspection was performed" with no detail on what was measured or observed)
• No discussion of alternative causes, especially in cases — like foundation movement or differential settlement — where multiple plausible mechanisms exist
• Photographs without scale references, location keys, or timestamps tying them to specific findings
• Code or standard citations that are outdated for the building's construction date, or cited without edition year
• No statement of the degree of certainty behind the opinions offered

Choosing the Right Engineer for the Analysis

Licensure in the state where the failure occurred is non-negotiable — it's a credibility issue the moment it's raised in deposition. Beyond that, ask about relevant project experience with the specific failure type, not just general structural engineering background. An engineer who has spent a career on new design but has investigated only a handful of structural collapses is a different resource than one who has testified on a dozen similar failures.

Ask to see a redacted sample report before engagement. It tells you more about how the engagement will go than any conversation will. Our structural inspection and construction defect analysis teams produce sample-format reports on request for exactly this reason — attorneys and adjusters should know what they're buying before the invoice arrives.

Frequently Asked Questions

How long does a building failure analysis report take to complete?

For a straightforward failure with a clear cause, expect 2-4 weeks from site visit to final report. Complex failures requiring lab testing, destructive investigation, or multiple competing theories typically take 2-4 months because of lab turnaround times outside the engineer's control.

What's the difference between a building failure analysis and a construction defect analysis?

Building failure analysis focuses on why a structure or component failed — collapse, cracking, excessive deflection — regardless of cause. Construction defect analysis specifically examines whether the failure resulted from deficient design, materials, or workmanship during original construction, which matters for statute of repose and contractor liability questions.

Can a building failure analysis report be used in both an insurance claim and later litigation?

Yes, but the report needs to be built to litigation standards from the start if there's any chance of a lawsuit. Reports written loosely for claims purposes often lack the methodology detail and alternative-cause analysis a court will require, which forces a second, more rigorous report later.

What credentials should I verify before relying on a building failure analysis report?

Confirm the engineer holds an active P.E. license in the state where the failure occurred, ask for their litigation and testimony history, and request a sample report to evaluate how clearly they separate observations from engineering opinions.

Who typically pays for a building failure analysis — the property owner, attorney, or insurer?

It depends on who retains the engineer. Property owners sometimes commission an independent report before filing a claim; insurers retain engineers to evaluate coverage and damages; and attorneys retain experts once litigation is anticipated or filed. The retaining party owns the report, though it can become discoverable depending on jurisdiction and privilege rules.