Expert report review

How do you challenge the engineer's report on a roof leak or hail damage claim?

An engineer's report that says a roof was not damaged by hail, or that a leak came from age and wear, is tested against what the engineer could see and record. A reviewer checks the weather and snow cover on the inspection day, the storm data for the date of loss, the alternative causes the engineer named, the photographs and measurements behind each finding, and whether the engineer is qualified for that roof type.

A gloved hand lifts a weathered asphalt shingle tab on a roof in late sunlight

What does the other side's roof engineer usually conclude, and what can a review test?

Insurers' engineers often conclude that hail did not damage the roof and that any damage is preexisting or has other causes. A review tests each of those findings against the inspection record, the photographs and the storm data.

The Tenth Circuit's order in El Dueno, LLC v. Mid-Century Insurance Co., No. 24-1110, decided May 30, 2025, describes a typical sequence. The owner of a commercial building in Greeley, Colorado, made a claim in April 2019 for roof damage from a hailstorm the previous July. An adjuster found hail damage and estimated about $22,000; the owner's contractor estimated $343,000 to repair the roof and bring it to code. An engineer from Rimkus inspected the roof on December 12, 2019, and concluded that hail did not damage the roof and that any damage was preexisting or had other causes. The insurer denied roof coverage on that report (pp. 2-3).

In other cases the owners' experts reached the opposite result. In Arthur v. Liberty Mutual Personal Insurance Co. (W.D. Tex., October 24, 2022), the plaintiffs' engineer observed frequent strike dents, some breaching the protective roof finish, bent seams and gutter damage, and concluded that widespread storm damage left the roof "in functional failure." In Corrigan v. Liberty Insurance Corp. (D. Colo., April 22, 2020), the owners' roofer found hail-consistent dents in the flashing, including around the chimney, and gave the opinion that hail damage caused a leak on one slope of the tile roof.

A review does not choose between the two engineers by reputation. It lists every finding in the other side's report and asks what observation, photograph, measurement or record supports it. The opinion that remains after that test is the opinion the court has to weigh.

Could the engineer see the roof on the day of the inspection?

The reviewer checks the date, the weather, snow or ice cover, the slopes walked, the time spent and the photographs. In El Dueno the owner's expert questioned what the engineer could see through snow and ice.

In El Dueno the engineer inspected in December, when ice and snow covered parts of the roof. The owner's expert, Kerry Freeman, found hail damage and questioned whether the insurer's engineer could see enough of the roof through the remaining snow and ice. The court noted that the record showed the roof was largely free of snow during the inspection (p. 3 n.1 and p. 4).

The court also addressed what the owner needed to prove that the inspection was inadequate. It said that a standard such as investigating only after snow and ice fully melt would need evidence, which the owner did not provide (p. 8 n.3). Industry standards, the court wrote, "supply the guidepost to assess the reasonableness of the insurer's conduct" (p. 8).

The reviewer turns that lesson into a checklist. What was the weather on the inspection date? Which slopes, ridges, valleys and penetrations appear in the photographs, and which do not? How long was the engineer on the roof? Were test areas marked and counted, and where? A report that does not answer these questions cannot support a finding of no damage for the parts of the roof the engineer did not document.

Was there hail at the property on the date of loss, and what do the storm records show?

The NOAA Storm Events Database holds the records used to create the official NOAA Storm Data publication, entered by the National Weather Service. The reviewer checks whether the engineer consulted them for the claimed date and place.

The National Centers for Environmental Information describe the Storm Events Database as the records "used to create the official NOAA Storm Data publication," with data "entered by NOAA's National Weather Service (NWS)." It covers storms and other weather phenomena intense enough to cause loss of life, injuries, significant property damage or disruption to commerce. The page says the data cover January 1950 through May 2026 and that periods of record differ by event type.

A storm record describes an event reported in the area; it does not measure anything on the roof. The reviewer checks whether the engineer looked at the records for the claimed date, how far the reported hail fell from the building, what size was reported, and whether the report treats the absence of a record as proof that no hail fell.

Dating matters in court. In Corrigan, Judge William J. Martínez excluded the roofer's opinion that the damage came from the May 8, 2017 storm because he gave no basis for judging reliability for that specific date; the inference was a lay one. The owners could still testify that the roof had not leaked before that storm.

How does a review test the alternative causes the engineer named?

By asking what observation separates hail from wear, foot traffic, installation defects or thermal movement on this roof. Rule 702's 2000 committee note asks whether the expert adequately accounted for obvious alternative explanations.

In El Dueno the engineer attributed the damage to preexisting conditions or other causes. Each alternative cause is a causal opinion of its own and needs its own basis. The 2000 committee note to Federal Rule of Evidence 702 asks whether the expert "has adequately accounted for obvious alternative explanations," and the question cuts both ways.

In Corrigan, the court held that alternative causes such as an aging roof did not make the roofer's leak opinion unreliable, because the causation opinion was not "so divorced from facts or data" that it became unreliable. The roofer had acknowledged that the roof was likely at least 20 years old.

The reviewer's task is therefore concrete. For each alternative cause, the reviewer asks what the engineer saw that separates it from hail on this roof, and in which photograph it appears. A cause named without an observation that distinguishes it from hail is an assumption, and the report should say so.

Did the engineer check soft metals and other collateral areas?

The reviewer checks whether gutters, vents, flashing and other soft metals were inspected and photographed. In Corrigan the roofer described the agreed approach: look for hail-consistent dents on collateral areas and soft metals first.

The roofer in Corrigan described the method the parties accepted: check collateral areas and soft metals for damage consistent with hail. In his words, "If there's no dents in any of that, then there's probably not any hail [damage] up [on the roof]." He relied on his own observations, photographs, the owner's report of a leak and his knowledge that the underlayment keeps water out.

In Arthur, the plaintiffs' engineer relied on strike dents, bent seams and gutter damage. In both cases the experts relied on marks on metal components. A report that finds no hail damage on the roofing but does not mention the condition of the gutters, vents and flashing leaves out evidence the other side will use.

The reviewer lists the collateral components visible in the photographs and compares the report's text with them. A dented vent cap in a photograph and a sentence saying no hail indicators were found is a contradiction for the deposition.

Does the opinion turn on a definition of functional damage?

Often. Engineers distinguish functional from cosmetic damage, and policies may exclude cosmetic damage. The reviewer checks which definition the engineer used, where it comes from and whether it matches the policy wording the court will apply.

In Arthur, Liberty Mutual relied on a cosmetic damage exclusion. The court held that the plaintiffs' engineer's testimony was relevant to whether the insurer could prove the exclusion applied, because his concession about water penetration did not address the policy's second test, failure to perform the intended function. The engineer's opinion that the roof was "in functional failure" went to that test.

What counts as functional damage is a technical threshold inside a legal question. The engineer can testify that a dent breached the finish, that a tile cracked, or that a seam no longer sheds water. Whether that is damage under the policy depends on the policy wording, which the court construes. The reviewer separates the two in the rebuttal: the observations and their technical meaning in one part, and the definition the engineer applied, with its source, in another.

A threshold that comes from a laboratory test, such as a minimum hailstone size said to cause functional damage to a roof type, is a fact or datum the engineer considered. Rule 26(a)(2)(B)(ii) requires the report to state "the facts or data considered by the witness in forming them," so the source of the threshold should be in the report.

Which photographs and data must the engineer disclose?

All facts or data considered and the exhibits that support the opinions. The 2010 committee note reads facts or data broadly, so every photograph, note, measurement and weather printout the engineer considered belongs in the disclosure.

Rule 26(a)(2)(B) requires a complete statement of all opinions with "the basis and reasons for them," "the facts or data considered by the witness in forming them" and "any exhibits that will be used to summarize or support them." The 2010 committee note says "facts or data" is to be "interpreted broadly to require disclosure of any material considered by the expert, from whatever source, that contains factual ingredients."

In Corrigan, most of the roofer's photographs were lost after his computer crashed, and the court still rejected most of the insurer's challenges to his opinions. In Arthur, the insurer argued that the engineer could not say at his deposition which area of the roof his magnified photographs showed, and the court held: "This is an issue for cross examination, not wholesale exclusion of McIntyre's testimony."

Rule 34(a)(1)(A) reaches "any designated documents or electronically stored information," and Rule 34(b)(1)(C) lets the requesting party specify the form of production. The reviewer asks for the photographs as native files, not copies pasted into the report, and asks for every photograph taken on the roof, including those left out of the report, and for the field notes and test-area counts.

Is the engineer qualified for this roof and this question?

Rule 702 asks about qualification for each opinion. Courts have weighed engineers against adjusters and experienced roofers against short careers; the reviewer compares the expert's record with the roof type and the causal question.

In El Dueno, the district court found that the insurer's engineer was a qualified engineer, while the adjuster who first found hail damage was not an engineer and had less experience inspecting roofs and assessing hail damage; the owner did not show that relying on the more experienced inspector was unreasonable (p. 9 n.4). In Corrigan, the roofer had about four years of industry experience as of July 2017; on the tile breakage factor he applied, the court held that the insurer had not shown his experience was so minimal that he lacked reliable knowledge of industry standards.

Disclosure rules differ by role. The roofer in Corrigan was designated as a non-retained expert under Rule 26(a)(2)(C), so the owners disclosed a summary of his opinions instead of a full report. A retained engineer owes a full report with qualifications, publications from the previous 10 years and testimony from the previous 4 years under Rule 26(a)(2)(B)(iv) and (v).

The reviewer checks whether the engineer's casework covers the roof covering at issue: asphalt shingles, concrete or clay tile, metal, modified bitumen. A causal opinion on tile breakage from an engineer whose experience is with steep-slope shingles is a qualification question for each opinion, under Rule 702(a).

Does a conflicting expert report prove that the insurer acted in bad faith?

Not by itself. In El Dueno the Tenth Circuit held that mere disagreement between experts is not enough under Colorado law and that the insurer's conduct is judged on the information it had when it decided.

The court wrote that a bad-faith plaintiff "must establish that the insurer acted unreasonably and with knowledge of or reckless disregard" of the lack of a reasonable basis, and that the decision "must be evaluated based on the information before the insurer at the time of that decision" (p. 6). The owner's and the insurer's later expert reports were not available when coverage was denied (p. 6 n.2).

Even if the engineer's report was wrong, the owner had to show that the reliance itself was unreasonable (p. 9). "Mere disagreement is not enough for a claim under Colorado law" (pp. 9-10). The order is unpublished and is not binding precedent, but it states the line a review has to cross in a bad-faith claim: a coverage dispute asks whether hail damaged the roof, a bad-faith claim asks whether relying on the report was unreasonable.

For a bad-faith claim the review therefore names the specific industry standard or the specific fact the engineer missed, and shows when the insurer knew of it. The court in El Dueno observed that the owner "never articulates any industry standard" (p. 7); a review that does articulate one, with its source, answers that gap.

How do courts handle a Rule 702 challenge to a roof engineer?

In Arthur and Corrigan the courts admitted most opinions, excluded specific ones and left the rest to cross-examination. Since December 2023, Rule 702 requires the proponent to establish each requirement more likely than not.

In Arthur the magistrate judge denied the motion to exclude the plaintiffs' engineer because the insurer "has not identified a specific reliability challenge based on flawed methodology," and observed that "the rejection of expert testimony is the exception rather than the rule." In Corrigan the court admitted most of the roofer's opinions and excluded the storm-date causation opinion and one opinion that was irrelevant under Rule 402.

Rule 702 as amended on December 1, 2023 admits expert testimony only if the proponent establishes that "it is more likely than not" that the testimony "is based on sufficient facts or data" and "is the product of reliable principles and methods." The 2023 committee note rejects the view that arguments about the sufficiency of an expert's basis "always go to weight and not admissibility."

A challenge that names a specific gap in method has a better footing than a general attack. The review supplies that gap: the slopes not inspected, the storm record not consulted, the collateral damage not mentioned, the threshold not sourced. General Electric Co. v. Joiner, 522 U.S. 136 (1997), held that a court may conclude that "there is simply too great an analytical gap between the data and the opinion proffered."

What should counsel request for the reviewer?

The full report, all roof photographs in native form, field notes and sketches, test-area counts, hail size measurements, the storm data the engineer used, the policy wording given to the engineer and any assumptions counsel provided.

Rule 26(b)(4)(C) protects most communications between counsel and a reporting expert, but not those that identify "facts or data that the party's attorney provided and that the expert considered" or "assumptions that the party's attorney provided and that the expert relied on." A date of loss, a policy definition of damage or a statement about prior repairs supplied by counsel falls in those exceptions.

Rule 26(b)(4)(A) permits the deposition of an expert who must give a report only after the report is provided, and Rule 30(d)(1) limits a deposition to "1 day of 7 hours" unless stipulated or ordered. The reviewer prepares the document list and the question outline together, so the deposition time goes to the gaps the review found.

Rule 26(a)(2)(D)(ii) gives 30 days after the other side's disclosure for evidence "intended solely to contradict or rebut evidence on the same subject matter," absent a stipulation or court order. A roof reinspection, if one is needed, is planned against that date.

What does IAE do when the other side's roof engineer report is disputed?

An IAE engineer reviews the opposing construction expert's report for a US case, tests each opinion against the data behind it and writes a rebuttal report. Delivery in up to 5 business days after format and cost are confirmed.

The IAE review of the opposing construction expert's report is for attorneys facing the other side's expert on a leak, defective work or a repair estimate. The reviewer tests each opinion against the data behind it and writes a rebuttal report, due within 30 days after the opposing disclosure unless the court sets other dates. The documents offered are a review of the opposing expert report, a rebuttal expert report and deposition questions. In IAE's own leak investigations the expert first checks whether the water came from the roof, plumbing or condensation before testing the wall, under ASTM E2128-26.

The client sends the opposing report and the case materials and describes what to check. The secretariat confirms receipt the same day, and within one business day IAE confirms the format, the cost, the deadline and the specialist from its registry. The client approves the candidate and the CV before work starts. The signed PDF is issued in up to 5 business days after the format and cost are confirmed, and a 48-hour rush is available for tight deadlines.

Specialists are members of the public IAE registry and passed the council's attestation under the published Criteria Matrix; the Member ID or QR code in the document opens the specialist's record. The specialist confirms in the document that he or she has no interest in the outcome, and materials are not passed to third parties without the client's consent. A review is evidence the court weighs with the other materials; neither IAE nor the reviewer guarantees the outcome or a coverage decision, and IAE is not a law firm.

Sources

Read also

All articles

Expert report review

Ready to discuss your case?

Send the materials: the secretariat will confirm the format, cost, deadline and the specialist within one business day.

Expertise request

Received

Cost and timeline estimate

WorkReview of an opinion
TimelineUp to 5 business days
ExpertIAE registry member