Engineer Recommendation Disputed by Second Opinion: Response

Purpose

A sealed recommendation is a professional opinion built from what one engineer was shown and personally observed, not an unchallengeable fact about the house. When a customer comes back with a second engineer who disagrees, most of the time neither is wrong; they looked at different scopes of the same house, worked from different data, or were asked a different question, and the disagreement dissolves once someone lines the two reports up side by side.

The failure mode to avoid is a salesperson or technician arguing the second opinion's conclusions on the driveway, point by point, from memory. That personalizes a professional disagreement, commits the shop to a position before anyone has compared what each report was built on, and routinely makes a resolvable gap in scope look like a credibility fight between two engineers who have never spoken to each other.

Scope

Covers the response when a customer presents an independent engineering opinion that contradicts the shop's own sealed recommendation or design, from receiving the second report through comparison, reconciliation, customer communication and the final documented outcome.

Does not cover the shop's own engineer engagement, package assembly or field-change process, which the engineer involvement and sign-off SOP owns and which this procedure references throughout. Does not resolve which engineer is correct where the two remain genuinely irreconcilable; that determination is not this shop's to make. Does not cover a confirmed post-repair recurrence discovered through monitoring, which routes to the settlement recurrence response even where a second opinion is also involved.

Roles and responsibilities

Procedure

Step 1: Request the second opinion in writing before responding to any of it

Ask the customer for the second engineer's actual report, or written authorization to obtain it directly, before discussing any of its specific findings. Acceptance: the full written report in hand, not a customer's paraphrase of a phone conversation with the other engineer. Wrong looks like a supervisor debating a claim the customer describes secondhand, such as "he said the piers are too shallow," without ever seeing what the report actually states, its basis, or its qualifications. Stop rule: no written report, no substantive response beyond acknowledging that the shop takes the concern seriously and needs the document.

Step 2: Compare what each engineer actually observed before comparing what they concluded

Pull the shop's own site walk note from the original engagement and read it against the second report's stated scope: what areas were accessed, what was left unexamined, and whether the second engineer entered the crawl space, exposed the same footing, or worked from a walk-through with no invasive access at all. Acceptance: a written side-by-side of accessed and not-accessed areas for both reports. Wrong looks like jumping straight to the two conclusions; a large share of these disagreements exist because one report examined less of the house than the other, and that gap is invisible until someone lines up the scope statements first. Where the comparison requires re-entering a crawl space or exposing a covered area to confirm what either engineer saw, the crawl entry and atmosphere check SOP governs that access, and the exposed area is patched and restored once the walk is documented.

Step 3: Compare the underlying data each report relied on

Check whether both reports used the same elevation survey benchmark and grid, the same crack measurements, and the same soil information, or whether the second report was built from its own quick measurements taken on a single visit. Acceptance: a written note on whether the two reports share their underlying data or diverge, and where they diverge, which specific figures differ. Wrong looks like accepting that "the numbers are different" without identifying whose benchmark, whose grid, or whose crack readings produced the difference; a report built on a different benchmark is not measuring the same thing, and that is a data problem, not a disagreement about the house.

Step 4: Send both reports to the shop's own engineer for a written reconciliation

Do not let a technician, a salesperson, or the supervisor attempt to reconcile the two opinions personally. Forward both reports, the step 2 scope comparison and the step 3 data comparison to the shop's engineer of record, and request a written response addressing the second report's specific findings one by one. Acceptance: a written reconciliation response in hand before any further customer conversation about the substance of the disagreement. Wrong looks like the shop's engineer giving a verbal "that's not right" over the phone that the supervisor then relays secondhand; a customer holding two written reports deserves a third written document, not a paraphrase of one.

Step 5: Treat a genuine gap the second opinion identifies as a new trigger, not an attack to defend against

Where the reconciliation in step 4 finds that the second engineer observed a real condition the first engineer's site walk note shows was not accessed, such as a section of foundation behind finished space or a crawl area the original walk marked not-accessed, treat that as a new engineer-involvement trigger under the existing SOP rather than defending the original sealed document against information it was never built to cover. Acceptance: a new or amended engagement opened where the gap is real, with the original sealed document's limitations paragraph cited as the reason it did not already address it. Wrong looks like the shop's engineer defending the original conclusion on a condition their own site walk note admits was never observed; that is exactly the situation the original document's limitations paragraph exists to be honest about.

Step 6: Communicate factually, without disparaging the other engineer

Give the customer the reconciliation response and the scope and data comparisons that support it, in writing, without characterizing the second engineer's competence or motives. Acceptance: a written communication that addresses the report's substance and cites the comparison, with no commentary on the other professional beyond what the technical comparison itself shows. Wrong looks like a supervisor telling the customer the other engineer "doesn't know what they're doing," which reads as defensive regardless of whether the shop's position is correct and gives the customer no way to evaluate the actual disagreement.

Step 7: Where the two opinions remain genuinely irreconcilable, name it as the customer's decision

Where step 4's reconciliation stands by the original conclusion, the second engineer stands by theirs, and no scope or data gap explains the difference, tell the customer plainly that this is now a decision between two professional opinions and route it to the shop's own attorney before altering the contract, offering a refund, or agreeing to a redesign on the strength of the disagreement alone. Acceptance: a written statement naming the disagreement as unresolved at the technical level, with any contract or scope change routed through the attorney rather than decided by sales. Wrong looks like a supervisor unilaterally splitting the difference by offering a partial redesign to make the disagreement go away; that decision carries the same liability weight as the original design and should not be made to smooth over an argument.

Step 8: Document every outcome, whichever way the customer decides

Whether the customer proceeds under the original design, proceeds under a revised design produced from step 5, or cancels, record the decision in writing with both reports, the reconciliation, and the comparisons attached. Acceptance: a closed file naming the customer's decision and the date. Wrong looks like a verbal agreement to proceed that leaves no record of which design version the customer actually chose, which is the exact ambiguity a callback two years later would need resolved.

The record this produces

One second-opinion file: the second engineer's full report, the scope comparison, the data comparison, the shop engineer's written reconciliation, any new engagement opened under step 5, the customer communication, the attorney referral where the disagreement remained unresolved, and the final documented decision.

It attaches to the original engineer-involvement file rather than replacing it, since the warranty administrator and any future inspector need both the original design and the record of how a later challenge to it was resolved.

One worked pass

A customer preparing to sell hires an independent structural engineer for a pre-listing inspection, and that report states the shop's four helical piers, installed under a sealed design eighteen months earlier, are inadequate and recommends six additional piers. Step 1 requests the full report rather than responding to the customer's summary that "the new engineer says we need more piers," and it arrives within a week.

Step 2's scope comparison finds the original site walk note lists the crawl space as accessed, with the engineer present for atmosphere testing, while the second report's stated scope reads "visual inspection from grade, crawl space not entered." Step 3's data comparison finds the second report cites no elevation survey at all, working from a level held at four points during a walk-through, against the original's gridded eight-foot survey with a photographed benchmark.

Step 4 sends both reports and the comparisons to the shop's engineer of record. The written reconciliation states that the second report's added-pier recommendation appears to be a margin-of-safety judgment made without entering the crawl space to verify installed depth and without a comparable survey to establish whether measurable movement has occurred since the original work. It does not claim the second engineer is wrong to be cautious from a grade-level walk; it states the two reports are not evaluating the same evidence.

Step 5 is where this pass has its failure and correction. The shop's engineer, drafting the reconciliation, initially proposes closing the matter on the scope gap alone, treating the second report as insufficiently informed rather than checking whether it raises anything new. Under step 5's rule, that is not enough: the second report notes visible efflorescence at one pier location from grade that the original site walk note does not mention. That observation is a genuine new data point regardless of the survey gap, and it triggers a new engagement rather than being dismissed inside the reconciliation that closes out the depth question.

Step 6 delivers the reconciliation and the new engagement to the customer, without characterizing the second engineer's methods. Step 7 does not activate, since the technical gap fully explains the difference once the efflorescence finding is separated out. The new engagement finds a minor grade issue at that pier location, unrelated to pier adequacy, resolved with a grading correction rather than additional piers. Step 8 closes the file with both reports, the reconciliation, the finding, and the customer's decision to proceed with the grading fix, all attached.

References

• Your state's professional engineering practice act, on what a sealed opinion represents and its limits, which the shop's engineer cites in framing the reconciliation.
• Your own attorney, for any case where the two opinions remain genuinely irreconcilable and a contract, refund or scope decision is being considered on that basis.
• See related: engineer involvement and sign-off, whose package-and-site-walk pattern this procedure compares against; crawl space entry and atmosphere check, for any access required to verify what either engineer's report describes.