Engineering Litigation Support: What Attorneys Need to Know
What Engineering Litigation Support Actually Means
Attorneys often call us after they've already retained an expert witness, assuming that's the whole job. It isn't. Engineering litigation support is the broader technical partnership that happens before, during, and often long after a deposition — case merit screening, document review, site investigation, causation analysis, and report drafting that either supports or kills a claim before it ever reaches trial.
The distinction matters because the two roles carry different obligations. An expert witness signs a Rule 26 report (or state equivalent) and testifies under oath about opinions formed to a reasonable degree of engineering certainty. A litigation support engineer can do all the same technical work — but consult, advise on strategy, flag weaknesses in opposing reports, and stay off the stand entirely if the attorney wants to preserve work-product protection. Many of our engagements start as pure consulting and only convert to testifying expert status once liability looks defensible.
If you've read our piece on the role of expert witnesses in construction defect litigation, think of this article as what happens in the months before that witness ever gets deposed.
The Four Phases of a Litigation Support Engagement
Every case we take on — foundation failure, roof collapse, facade cladding dispute, parking garage deterioration — moves through the same four phases, even if the timeline compresses to weeks in an emergency insurance dispute or stretches to two years in complex multi-party construction defect litigation.
Phase one is intake and merit screening: a few hours of document review to tell you honestly whether the claim has engineering legs. Phase two is discovery support: helping draft interrogatories, reviewing opposing expert reports, and identifying what testing or inspection access you need before spoliation becomes an issue. Phase three is field investigation and analysis — the part most people picture when they hear 'forensic engineer.' Phase four is report production and trial preparation, including deposition prep sessions where we walk you through the technical vulnerabilities in your own case before opposing counsel finds them.
- Phase 1 — Merit screening (typically 5-15 hours, flat fee or capped hourly)
- Phase 2 — Discovery support and opposing report critique
- Phase 3 — Site investigation, testing, and causation analysis
- Phase 4 — Report drafting, Daubert/Frye prep, deposition and trial support
Case Evaluation: Where Most Cases Are Won or Lost Before Discovery Even Starts
I've turned down more cases at intake than I've accepted. A property owner suing a contractor for a leaking below-grade wall isn't automatically a construction defect case — it might be a maintenance failure, a drainage design issue outside the contractor's scope, or simple hydrostatic pressure that no waterproofing system on earth would have stopped without a functioning perimeter drain. Sorting that out early saves everyone six figures in discovery costs on a case that was never going to survive summary judgment.
At intake, we're looking for three things: is there physical evidence of a defect (not just a symptom like a stain or crack), is there a plausible causal chain connecting that defect to a specific party's scope of work, and does the damage timeline align with the alleged cause. Weak cases usually fail on the second point — plenty of visible damage, no clean line back to a specific breach of the applicable code section or industry standard (ACI 318 for concrete, TMS 402 for masonry, ASCE 7 for wind and snow loads, or the manufacturer's installation instructions incorporated by reference into most building codes).
Document and Discovery Review: What We're Actually Looking For
Construction litigation generates enormous paper trails, and most of it is noise. When we get pulled into discovery support, we're triaging for a handful of document types that actually move the causation needle: the approved construction drawings versus as-built conditions, RFIs and change orders that show design intent shifted mid-project, daily field reports and inspection logs, material submittals and test reports, and any prior repair or complaint history.
A recurring pattern: the stamped structural drawings call for a detail that field photos or as-built conditions don't match. That gap — designed condition versus built condition — is often the single most powerful piece of evidence in a case, and it's routinely buried in a 40,000-page document production that nobody on the legal team has the technical background to parse quickly. We've found governing discrepancies in under two hours of review that took prior counsel's paralegals three weeks to not find at all, simply because you need an engineer's eye to know what drawing detail actually controls.
Field Investigation and Evidence Preservation
Once litigation support moves to the field, evidence preservation rules take over from pure engineering judgment. Destructive testing — cutting into a wall assembly, coring concrete, exposing a foundation — requires coordination with opposing counsel, spoliation protocols, and often a joint inspection protocol signed by all parties before a single tool touches the structure. Skipping that step is how otherwise solid engineering findings get excluded at a Daubert hearing.
Our field protocol on litigation matters is more rigorous than a standard structural inspection because every measurement has to survive cross-examination. That means calibrated equipment with documented calibration certificates, photographs with a fixed reference scale in every frame, GPS-tagged locations for every test point, and a written chain of custody for any samples removed. On a recent facade dispute, we logged 34 individual moisture readings across a stucco-clad elevation using a calibrated Delmhorst BD-2100 pin meter, each one photographed against a numbered grid overlay taped to the wall — because six months later, in deposition, opposing counsel asked exactly where reading #22 was taken, and we had the answer on a single page.
A Case Example: Stucco Cladding Failure, Multi-Family Property
A defense firm retained us on a construction defect claim involving a 96-unit stucco-clad apartment building, four years post-construction, with the HOA alleging systemic water intrusion causing wood rot in the framing behind the cladding. Plaintiff's expert had documented moisture staining at roughly 40% of window openings and concluded the entire building envelope needed replacement — a repair estimate north of $4.1 million.
Our litigation support engagement started with document review: the approved drawings called for a two-layer weather-resistant barrier with flashing details compliant with ASTM E2112, and a minimum 7/8-inch three-coat stucco assembly per ASTM C926. Field investigation at 22 destructive test locations found the actual installed stucco averaged 5/8 inch — a real deficiency — but moisture content readings in the underlying sheathing, taken per ASTM D4444 protocol, exceeded 19% (the threshold for active decay risk) at only 6 of the 22 locations, all of them clustered around a single roof-to-wall transition detail that had been field-modified from the approved drawings during construction.
The finding reframed the entire case: this wasn't a systemic envelope failure requiring full re-cladding, it was a localized flashing defect at one recurring detail, repairable for roughly $310,000. The case settled within that repair scope rather than the original $4.1 million demand. That's the value litigation support brings before trial — not winning an argument, but right-sizing the actual engineering problem so both sides are negotiating against real numbers instead of a worst-case narrative.
Report Writing and Deposition Preparation
A litigation-ready engineering report is a different document from a standard damage assessment. It has to state the methodology explicitly enough to survive a Daubert or Frye challenge, cite the specific code sections and standards relied upon, address alternative causes and explain why they were ruled out, and separate observed fact from engineering opinion with visible clarity — judges and opposing counsel will pull that seam apart if it isn't clean.
Deposition prep is where a lot of otherwise strong reports get damaged, usually because the retaining attorney and the engineer never rehearsed the weak points together. We walk through every assumption in the report, every measurement that could be second-guessed, and every place opposing counsel is likely to probe for scope creep or bias. An engineer who can't calmly explain, in plain language, why they chose one moisture threshold over another is a liability on the stand regardless of how sound the underlying analysis is.
Choosing the Right Litigation Support Partner
Not every P.E. who inspects buildings is suited to litigation work. Ask about prior deposition and trial experience, request a sample redacted report, and confirm the firm has a documented conflict-check process — multi-state practices that also do insurance carrier work need clean walls between claim-side and litigation-side engagements. We maintain those separations explicitly and disclose prior involvement with any party before accepting an engagement.
For attorneys building a bench of experts, our litigation and expert witness services page outlines credentials and coverage areas, and our attorney resources section has templates for the kind of preservation letters and inspection protocols referenced above. If the dispute centers on a specific failure mode, our failure library and case studies pages show how we've approached similar fact patterns in reported matters.
Frequently Asked Questions
What's the difference between an engineering consultant and a testifying expert witness?
A consultant's work product is generally protected and doesn't have to be disclosed unless the attorney later designates them as a testifying expert. A testifying expert's report, data, and opinions are fully discoverable and subject to deposition. Many litigation support engagements start as consulting and only convert to a testifying role once the technical findings are strong enough to support disclosure.
How early should an attorney bring in an engineer on a construction defect or property damage case?
Before the demand letter goes out, ideally. Early merit screening — often just a few hours of document and photo review — tells you whether the causal theory holds up before you invest in full discovery. We've seen cases where a single site visit at intake reshaped the entire damages claim, and cases where it revealed there was no viable engineering theory at all.
Can the same engineer serve both insurance claim support and litigation support on the same case?
It depends on timing and who retained them first. If an engineer did a claim-side damage assessment for a carrier, they generally shouldn't later serve as an independent litigation expert against that same carrier without disclosure, since it raises bias questions at deposition. Firms handling both insurance claim support and litigation work need documented conflict screening before accepting any new engagement.
What does destructive testing during litigation typically involve, and who pays for it?
Destructive testing — concrete coring, wall assembly cuts, foundation excavation — usually requires a joint inspection protocol agreed to by all parties, often memorialized in a stipulated order. Costs are typically allocated by agreement or court order, and the protocol specifies who may be present, how samples are documented, and how the opening is repaired afterward.