Choosing a structural engineer for retrofit work is a decision most property owners make only a handful of times, if that, which means most owners are making an important, expensive decision with very little accumulated experience to draw on. This article is a practical checklist for that decision — not a replacement for a proper scoping conversation with each candidate, but a starting framework for what to actually ask and verify.
Credentials and Experience to Verify
A current, active Professional Engineer license in the relevant jurisdiction is the baseline, not a differentiator — verify it directly through the state or national licensing board rather than taking a firm's word for it, which takes only a few minutes and is worth doing every time.
Retrofit-specific experience, not just general structural design experience. Diagnosing and strengthening an existing, often undocumented building draws on a genuinely different skill set than designing a new structure from a clean set of assumptions — ask specifically about retrofit projects, not structural engineering experience in general.
Experience with the specific building type and era involved. A firm experienced with steel-frame commercial retrofit isn't automatically well suited to unreinforced masonry, and vice versa — the failure modes and applicable techniques genuinely differ, as covered elsewhere on this site.
Familiarity with the local jurisdiction's specific requirements, including any applicable mandatory retrofit ordinances, which — as our soft-story article notes — vary significantly by location and aren't something a firm based in a different region can be assumed to know well.
Questions About Their Process
What does their evaluation process actually include? A desktop review of drawings, a site visit, exploratory probing, testing — ask specifically what's included at each stage, since firms vary meaningfully here even for similar-sounding scopes.
How do they handle a discrepancy between drawings and field conditions? A firm with a clear, ready answer to this question — because they've encountered it often — is a good sign; a firm that seems not to have considered it is worth asking more about.
What does their report actually look like? Ask to see a redacted or sample report. A report structured to help an owner make a decision, per our reports-writing article on this site, looks different from one written primarily to document technical work for another engineer.
How do they handle construction-phase involvement? Some engineers design and hand off; others stay involved through construction administration and special inspection. Neither is automatically wrong, but the difference matters and should be an explicit part of the scope discussion, not an assumption.
Red Flags Worth Taking Seriously
Reluctance to explain reasoning in plain language. An engineer who can't or won't translate a finding into terms a client can understand — rather than choosing not to, for a specific good reason — may also struggle to write a report that actually serves its purpose.
A quote significantly lower than comparable proposals with no clear explanation of the scope difference. As covered in our client-mistakes article, this is worth investigating rather than simply accepting as good fortune.
Reluctance to provide references from comparable past projects. A firm confident in its retrofit track record should be willing to connect a prospective client with a past client for a similar project type.
Pressure to commit quickly without a proper scoping conversation. A retrofit decision, and the firm chosen to guide it, deserves the deliberate process outlined in our scoping article — legitimate urgency, an ordinance deadline, for instance, is real and common, but it shouldn't be used to rush past questions that matter.
Fit Beyond Technical Competence
Technical competence is necessary but not sufficient — a retrofit project, especially an occupied one, is a months-long working relationship, and responsiveness, clarity, and communication style matter for how smoothly that relationship actually goes. An engineer who's technically excellent but slow to respond or difficult to reach can meaningfully degrade a project's experience even if the eventual design is sound.
Asking a candidate directly how they handle client communication during a project — frequency of updates, who the actual point of contact will be, how questions get answered between formal deliverables — surfaces this before it becomes a source of frustration mid-project rather than after.
Practical Application: Comparing Two Proposals
A composite, illustrative comparison: an owner receives two proposals for the same evaluation scope. One is noticeably less expensive and includes a one-paragraph description of the process; the other costs more and includes a detailed breakdown of site-visit scope, exploratory probing assumptions, and a sample report excerpt.
A direct comparison call with each firm reveals that the lower-priced proposal's process is genuinely leaner — the firm specializes in straightforward evaluations for a specific building type the owner's property matches closely, and their leaner process reflects real efficiency rather than a cut corner. The higher-priced proposal's additional cost, on inspection, reflects a broader scope the owner's building doesn't actually need at this stage.
The owner selects the lower-priced firm, but only after the comparison call turned an unexplained price gap into an understood one — the same due-diligence step that, run the other direction on a different pair of proposals, might just as easily have justified paying more for the firm with the deeper process.
Frequently Asked Questions
A few questions owners ask repeatedly during this decision:
Do I need a structural engineer, or would a general contractor be enough?
A general contractor can execute a retrofit design but shouldn't be relied on to diagnose the deficiency or design the fix — that requires a licensed structural engineer's evaluation and stamped design, which the contractor then builds to.
How many proposals should I get before deciding?
Three is a reasonable typical range for a meaningful comparison without an excessive time investment, though a highly specialized building type may narrow the realistic candidate pool below that.
Should I choose a local firm over one from a larger region?
Local familiarity with the specific jurisdiction's requirements and any applicable retrofit ordinances is a genuine advantage; it's worth weighing against a non-local firm's deeper experience with your specific building type, rather than treating either factor as automatically decisive.
Common Mistakes
Verifying only the firm's license, not the specific engineer who will actually be on the project. Larger firms can assign engineers with meaningfully different experience levels to a given project; ask who specifically will be responsible.
Skipping reference checks because the proposal looked strong on paper. A past client's actual experience, especially around communication and how surprises were handled, tells you things a proposal document can't.
Deciding based on the proposal alone without a direct conversation. As the practical-application example above shows, a conversation can change the entire picture a written proposal presents on its own.
- ✓A PE license is a baseline to verify directly, not a differentiator — retrofit-specific experience with the specific building type involved matters more for this decision.
- ✓Asking directly how a firm handles as-built discrepancies, construction-phase involvement, and client communication surfaces meaningful differences that a proposal document alone won't show.
- ✓An unexplained price gap between proposals is worth investigating through direct conversation, not simply accepting as either a red flag or good fortune.
- ✓Fit and communication style matter alongside technical competence — a months-long retrofit relationship goes more smoothly with a responsive, clear communicator.
Discussion
Loading comments...