# Common Mistakes Clients Make Before Hiring a Structural Engineer > The decisions owners make before the first site visit often matter more than anything that happens during it. *Retrofitting & Rehabilitation — August 22, 2026 — 6 min read* By the time a structural problem is visible enough for a property owner to call an engineer, several decisions have often already been made that will shape the whole project — usually without the owner realizing they were decisions at all. The mistakes covered here aren't exotic; they're the same handful that show up across most projects that end up costing more, taking longer, or delivering less than the owner expected, and every one of them is avoidable with a small amount of upfront diligence. None of what follows requires specialized construction knowledge to catch — it mostly requires knowing which questions matter before signing a contract, not after. ## Treating the Evaluation as Optional Some owners, especially once a specific fix has already been suggested by a contractor or a well-meaning building manager, try to skip straight to pricing that fix — bracing, a jacket, a wall — without a proper evaluation confirming it's the right one, or the only one needed. This can save money upfront and cost considerably more later, either because the fix doesn't actually address the real deficiency or because a second, undiscovered problem surfaces mid-construction. This pattern shows up especially often when a contractor, rather than an engineer, is the first person to look at a visible problem — a contractor's read on a crack or a lean is informed by experience, but it isn't a substitute for the kind of quantified analysis a Tier 1 or Tier 2 evaluation actually provides, and contractors are rarely positioned to tell an owner that. An evaluation isn't a formality that delays getting to the real work; for a retrofit project, it typically is the real work that determines everything downstream of it. ## Choosing Solely on Price Structural engineering fees for a comparable-sounding scope can vary meaningfully between firms, and the lowest quote isn't automatically the wrong choice — but choosing without understanding why the numbers differ usually is. A lower fee sometimes reflects a genuinely leaner, more efficient process; other times it reflects a narrower scope, less field verification, or less experience with the specific building type or retrofit method involved. Asking each firm to explain what's actually included in their number — site visits, exploratory probing, report depth, construction administration — turns an apples-to-oranges comparison into one that actually informs the decision. It's also worth remembering that the cheapest quote for an inadequate scope isn't actually cheap once the missing scope surfaces later, as the comparison below illustrates directly. ## Skipping Credential and Scope Verification A professional engineering license is a baseline, not a differentiator — but it's still worth confirming directly, along with whether the specific engineer proposed on the project (not just the firm's name) has actual retrofit experience, not only new-construction design experience. The two require overlapping but genuinely different skill sets, and general structural design experience doesn't automatically transfer to diagnosing and strengthening an existing, often undocumented building. This matters more for retrofit than for most other engineering work, since diagnosing an existing, often undocumented building draws on pattern recognition built specifically from doing that kind of diagnostic work repeatedly. Asking for examples of comparable retrofit projects, and ideally speaking with a past client, surfaces this distinction faster than reading a firm's marketing materials. ## Not Aligning on a Performance Objective Early Life Safety and Immediate Occupancy are both legitimate, code-recognized performance objectives, and they can carry meaningfully different costs for the same building. Owners who don't discuss which objective they actually need — and can afford — before design work starts sometimes discover partway through that the design in progress targets a level of performance, and cost, they never explicitly agreed to. This is a conversation worth having directly and early, even though it can feel premature before a technical evaluation has happened — the evaluation informs what's achievable, but the target objective should still be discussed as a starting point, not left implicit. It's a short conversation, but one that's easy to skip when everyone in the room is eager to get past scoping and into the technical work. ![Group of professionals in discussion around a meeting table](https://images.unsplash.com/photo-1758518732175-5d608ba3abdf?q=80&w=1200&auto=format&fit=crop) *The conversations owners have — or skip — before signing a contract shape a retrofit project as much as anything that happens on site. — Photo: [Vitaly Gariev](https://unsplash.com/@silverkblack)* ## Practical Application: Two Owners, Two Outcomes A composite, illustrative comparison shows how these mistakes compound. One owner, facing a similar deficiency to a neighboring property, selects an engineer based purely on the lowest of three quotes, without asking what each quote actually included. The selected proposal, it turns out, priced only a desktop review of existing drawings with a single site visit — not the exploratory probing the other two firms had built into their higher quotes. Midway through design, undocumented modifications are discovered that the desktop review couldn't have caught, and the project pauses for a supplemental investigation that, combined with the original fee, ends up costing more than the higher initial quotes would have. A second, otherwise comparable owner asks each firm to walk through their proposed scope in detail, selects a mid-priced option specifically because its scope included field verification the lowest bid didn't, and also has an explicit conversation with the selected engineer about targeting Life Safety rather than Immediate Occupancy given budget constraints. That project proceeds without a major scope surprise — not because the building happened to be simpler, but because the decisions made before hiring left less room for one. ## Getting It Right None of these mistakes require unusual foresight to avoid — they mostly require treating the hiring decision itself as part of the project, not a formality that precedes it. A short conversation about scope, credentials, and performance objective before signing a contract is a small time investment relative to the cost of discovering the gap mid-project instead. The owners who get this right aren't necessarily more sophisticated about engineering; they're just more deliberate about the handful of questions that matter before the contract is signed, not after. **Key Takeaways** - Skipping a proper evaluation to jump straight to a suggested fix is a common, costly mistake — the evaluation usually is the real work, not a delay before it. - Comparing quotes on price alone, without understanding what scope each number actually includes, invites an apples-to-oranges decision that surfaces as a problem mid-project. - A PE license is a baseline; retrofit-specific experience with the proposed engineer, not just the firm, is worth verifying separately. - Discussing the target performance objective (Life Safety vs. Immediate Occupancy) before design work starts prevents an expensive, unwelcome surprise partway through. --- **Author:** Retrofit Engineering Editorial Team — Practice & Client Advisory Division Source: https://retrofit-engineering.com/blog/common-mistakes-clients-make-before-hiring-a-structural-engineer