A client who commissions a structural evaluation is, by definition, someone who can't independently verify the answer they're being given. That's an unusual position for most people to be in as a paying customer, and it creates a trust dynamic that has less to do with the engineering itself than with how it's communicated — which means trust, in this line of work, is a practice skill worth developing deliberately, not a byproduct of being right.
Why the Trust Gap Exists
Structural engineering findings often carry real financial and emotional weight — a finding can mean a large unplanned expense, a delayed sale, or genuine anxiety about a place someone lives or works. A client facing that weight, with no way to independently check the technical claim behind it, is naturally inclined toward some suspicion, whether or not the engineer has done anything to earn it.
This isn't a flaw in the client; it's a rational response to information asymmetry. The engineer knows things the client can't verify, and the client knows this. Acknowledging that dynamic directly, rather than assuming trust is automatic once credentials are established, is the starting point for actually closing the gap.
Communication Habits That Build Trust
Explain the reasoning, not just the conclusion. A client who understands why a column is a concern — not just that it is one — is in a fundamentally different position than one who's simply told to trust the finding. This takes longer in the moment and pays off in every subsequent conversation about the same project.
Show your work visually wherever possible. A photo with an annotation, a simple diagram of a load path, or a side-by-side comparison of what's deficient versus what code requires does more to build genuine understanding — and therefore trust — than the equivalent explained verbally.
Answer the question actually being asked, even when it's not phrased in engineering terms. "Is my building going to fall down" is rarely meant literally, but dismissing it as an unsophisticated question rather than translating the real underlying concern into an honest answer erodes trust fast.
Be consistent between what's said in person and what's written in the report. Clients notice, and rightly distrust, a gap between an in-person explanation that sounds urgent and a written report that hedges everything into vagueness — the two need to say the same thing.
Being Honest About Uncertainty Without Undermining Confidence
Structural engineering involves genuine uncertainty — ranges, not single numbers, and recommendations that depend on assumptions that can't always be fully verified without more invasive, and expensive, investigation. Hiding that uncertainty to sound more authoritative backfires eventually, usually at the worst possible time, when an assumption turns out to have been wrong.
The more durable approach is being specific about what is and isn't known, and why. "Based on the original drawings, we expect X, but we recommend a small number of exploratory probes to confirm before finalizing the design" is a more trustworthy statement than either false certainty or vague hedging, because it gives the client an actual, concrete picture of what's confirmed versus what's still being verified — and a clear next step rather than an open-ended shrug.
Practical Application: Walking a Client Through an Uncomfortable Finding
A composite, illustrative scenario: a homeowner commissions an evaluation after noticing a crack, expecting — based on a contractor's informal opinion — that the fix will be minor and inexpensive. The evaluation instead finds a more significant deficiency requiring a retrofit well beyond what the homeowner was mentally and financially prepared for.
Delivering that finding well starts before the number is mentioned at all: walking the homeowner through what was actually found, using the same photos and simple diagrams that would go into the report, so the finding makes sense on its own terms before it's attached to a cost. The conversation explicitly separates what's certain (the deficiency itself, confirmed by direct observation and calculation) from what still has some range (the exact retrofit cost, which depends on a design phase not yet started).
The homeowner leaves the conversation still unhappy about the cost — that part doesn't change — but with a clear understanding of why the finding is what it is, and enough confidence in the process to move forward rather than shop for a second opinion hoping for a more comfortable answer. That outcome, not the homeowner's initial mood, is what actually indicates the trust-building worked.
Common Mistakes
Over-explaining with jargon in an attempt to sound thorough. More technical detail doesn't automatically build more trust — it can just as easily read as evasive if the client can't follow it, especially if it arrives instead of a clear answer rather than alongside one.
Softening a serious finding to avoid an uncomfortable conversation. This trades a hard conversation now for a much harder one later, once the softened version turns out not to have matched reality.
Treating trust as established once, rather than maintained continuously. A single good first meeting doesn't carry a multi-month project — consistency across every subsequent interaction is what actually sustains it.
- ✓Trust between an engineer and a client who can't verify the engineering is built through communication practice, not established automatically by credentials.
- ✓Explaining reasoning, not just conclusions, and showing findings visually build genuine understanding faster than a verbal explanation alone.
- ✓Stating uncertainty specifically — what's confirmed versus what still needs verification — is more trustworthy than either false certainty or vague hedging.
- ✓Consistency between what's said in person and what's written in the report matters; clients notice and distrust a gap between the two.
Discussion
Loading comments...