A retrofit quote built on an incomplete picture of the building isn't really a quote — it's a placeholder that both sides will end up renegotiating once the real scope surfaces mid-project. The fix isn't a longer proposal template; it's a short, specific set of questions asked before the number ever gets written down.
Most of these questions take less than thirty minutes to work through on an initial call or site walk, and most engineers who've been doing this long enough have their own version of this list, refined by whichever question they wish they'd asked on a project that went sideways. What follows is a practical version, organized by the categories that most often hide the scope that wasn't in the original ask.
Questions About the Building's History
When was it built, and has it been renovated since? The construction date sets expectations for detailing standards and likely deficiencies; renovation history matters just as much, since a change made years ago — a removed wall, an added floor, a converted use — can shift the structural picture in ways that aren't visible without asking.
Has any part of the structure ever been damaged or repaired? Prior settlement, fire damage, or flood exposure changes what an evaluation needs to check, and owners don't always volunteer this information unless asked directly — it's not always top of mind, or they assume a repair years ago is no longer relevant.
Is there a history of code violations or open permits related to structural work? This can surface unresolved issues that will need to be addressed as part of, or alongside, the retrofit scope, and it's far better to know before pricing than to discover it once work starts.
Questions About Access and Occupancy
Will the building need to remain occupied during construction? This single answer can eliminate entire categories of retrofit technique before design even starts, and it has a direct, often large effect on cost and schedule — as covered in more depth in our occupied-retrofit article elsewhere on this site.
What physical access constraints exist? Basement headroom, narrow site access for equipment, adjacent structures limiting excavation, or protected landscaping can all rule out techniques that would otherwise be the obvious, lowest-cost choice.
Are there tenant lease terms or use restrictions that affect scheduling? A retail tenant's lease might restrict construction hours or require advance notice periods that materially affect how a project can be phased.
Questions About Existing Documentation
Do original structural drawings exist, and how confident is the owner in their accuracy? Drawings that exist but haven't been field-verified are a starting point, not a guarantee — as our case-study article on this site illustrates, field conditions deviate from original drawings more often than most owners expect.
Has a prior structural evaluation been done, and can it be shared? A previous report, even an outdated one, can save real time and should shape the scope of a new evaluation rather than being ignored in favor of starting from zero.
Are there geotechnical reports, either original or from any nearby recent construction? Soil conditions relevant to a foundation-touching retrofit are sometimes already documented from unrelated nearby work and worth asking about specifically.
Questions About Performance Goals and Budget
What is the actual driver for this project? A code-mandated ordinance deadline, an insurance requirement, a refinancing condition, and a purely voluntary safety upgrade all imply different urgency, different acceptable performance objectives, and different budget flexibility — and clients don't always state the real driver unless asked directly.
Is there a target budget range, even a rough one? Owners are sometimes reluctant to share this, worried it will anchor the quote artificially high. In practice, knowing the range early lets the engineer flag immediately whether the likely scope fits it, or whether a phased approach needs to be part of the conversation from day one.
Who else needs to be satisfied by the outcome — a lender, an insurer, a heritage authority? Third-party requirements can add scope, review timelines, or documentation obligations that aren't visible from the building alone.
Practical Application: A Scoping Call That Changed the Quote
A composite, illustrative example: an initial inquiry describes a straightforward request — an evaluation of a single retail building's roof-to-wall connections, prompted by a routine insurance inspection that flagged the item generically. A quote based only on that description would price a narrow, single-issue assessment.
A short scoping call surfaces three details that weren't in the original ask: the building had a rear addition built without permits roughly fifteen years earlier, the owner mentioned in passing that a neighboring lot was slated for excavation later that year, and the insurance deadline was six weeks out, tighter than the described scope suggested. None of these would have been discovered from the building alone, and each changes the actual project: the addition needs to be checked for how it ties into the original structure, the adjacent excavation raises an underpinning question worth flagging even if it's not this project's scope, and the compressed timeline affects how the evaluation itself needs to be resourced and scheduled.
The resulting quote looks meaningfully different from what the initial description would have produced — not because the engineer padded the scope, but because the real scope only became visible once the right questions were asked.
Common Mistakes
Pricing from the client's initial description without a scoping conversation. Clients describe the problem as they understand it, which is rarely the same as the actual structural scope.
Treating the scoping call as a formality before writing the number the client expects. The questions only add value if the answers are actually allowed to change the quote.
Not documenting scoping answers in the proposal itself. Recording what was asked and answered protects both sides if the scope later needs to expand — it shows the original quote was based on the information available at the time, not an underestimate.
- ✓Most retrofit scope surprises trace back to a question that wasn't asked during initial scoping, not to an unforeseeable condition.
- ✓Occupancy and access constraints can eliminate entire categories of retrofit technique before design work even starts, and should be established before pricing.
- ✓Existing drawings and prior reports are a starting point, not a guarantee of field accuracy — ask about them, but don't quote as if they're confirmed.
- ✓The actual driver behind a project (ordinance deadline, insurance requirement, voluntary upgrade) shapes acceptable performance objectives and budget flexibility, and clients often don't volunteer it unless asked directly.
Discussion
Loading comments...