What a Milestone Inspection Report Does Not Cover

The report arrived. The board read it at a meeting, the engineer answered questions, and everyone left with a clearer picture of the structural condition of the building. What a lot of boards do not realize in that same meeting is that the report they are holding is not a project plan. It is a structural assessment, and a structural assessment is scoped narrower than most boards assume.

The gap between what the report covers and what the community actually needs to plan, budget, and fix is where projects stall. Not because the board did not act. Because the board thought the report had already told them everything, and it had not.

A note before anything else: this article does not characterize legal requirements. Whether your community is subject to a milestone inspection, on what timeline, and what a structural inspection report must legally contain are questions for your association attorney and the engineer you have retained, not a blog post. What follows is about scope, not law: what a structural report is built to look at, and what it typically is not.

What a Milestone Inspection Is Built to Look At

A milestone inspection is a structural engineering review. The engineer conducting it is scoped, by their own contract and professional judgment, to evaluate the structural systems and life-safety-related building elements of the property: load-bearing walls and columns, structural slabs, the structural condition of balconies and decks, waterproofing where it is tied directly to structural integrity, and the general condition of the building envelope as it relates to structural performance.

That is deliberately a narrow lens, and it should be. An engineer is not going to certify the structural adequacy of a building and simultaneously wander the property commenting on whether the mulch beds drain well. Their report is only as reliable as the boundary they held around it. The findings that come back are real, often serious, and worth taking seriously exactly as written. The mistake happens after the meeting, when a board treats the structural report as a complete inventory of everything the property needs.

The Scope Gap, Mapped

The clearest way to see the gap is side by side: what the report typically speaks to, and what it typically does not, even though a board still has to plan and fund it.

None of the items in the right-hand column are less real to a board's budget or a resident's daily experience than the items on the left. They are simply outside what the engineer was retained to evaluate. A cracked pool deck or a chronically wet planting bed will not appear in a structural report, no matter how visible it is standing next to the building, unless it happens to intersect with a structural finding.

Why the Gap Exists, and Why That Is Not a Flaw

It is worth being direct about why this gap exists, because it is not a shortcoming in the engineer's work. A structural engineer's report is a professional opinion with liability attached to it. The engineer scopes their evaluation to what they are qualified and retained to assess, and they do not extend their signature to conditions outside that scope. Asking a structural engineer to also evaluate landscape drainage or fence condition is asking them to certify something outside their expertise, which does neither the board nor the engineer any favors.

The report doing exactly what it says it does is the report working correctly. The problem is entirely on the receiving end: a board that reads a scoped structural document and mentally files it as "the full picture of what this property needs."

Reserve Study Findings Are a Related, Separate Document

Many communities also maintain a reserve study, which looks at anticipated replacement of major components over time. A reserve study can flag items a structural report does not, because it is built around a different question: what components will need replacement, and roughly when, rather than what is structurally sound today. Like the milestone inspection, the exact scope and requirements around a reserve study are a legal and financial planning question for your attorney and reserve specialist, not something this article characterizes. The practical point for a board is simpler: a reserve study and a structural report answer different questions, and neither one, on its own, adds up to a complete list of the physical work a property needs.

A Practical Walk-Through

Picture a mid-rise condo community off a collector road in Central Florida. The structural report comes back with findings on a handful of balcony railings, some spalling on an exterior stair landing, and a waterproofing recommendation at one roof-to-wall transition. The board reads it, is relieved the list is not longer, and starts getting proposals for exactly those items.

What the report never touched: a low spot near the mail kiosk that holds water after every afternoon storm, hairline cracking across several stucco panels on the pool-facing elevation that has nothing to do with the structural findings, a section of perimeter fencing with failing posts, an irrigation zone that has been overwatering a planting bed against the foundation wall for at least a year, and a pool deck with several trip-level height differences at the expansion joints. None of that shows up anywhere in the engineer's report, and none of it is the engineer's fault. It was never inside the frame they were asked to look through.

Six months later, once the structural items are funded and underway, the board starts fielding resident complaints about the standing water and the pool deck. Nothing about those conditions is new. They were there the whole time, sitting just outside the one document the board had been treating as complete.

The Flatwork and Amenity Inventory Belongs on Its Own List

Concrete alone covers more ground on a typical property than most boards track in one place: sidewalks, curbs, ADA ramps, dumpster pads, pool decks, mail kiosk pads, equipment pads, and entry aprons all fail differently and on different timelines, a full breakdown covered in the concrete inventory guide. None of that is a structural report's job to catalog. If a trip hazard at a sidewalk joint is severe enough, it may eventually intersect with liability concerns the board's attorney should weigh in on, but the condition assessment itself, and the decision between grinding and replacement, is a separate scope from anything in the milestone report, as covered in sidewalk grinding versus replacement.

The practical move is to build this inventory the same way the structural findings get tracked: a defined list, walked and photographed, with a status column, not a mental note that gets revisited only when a resident trips or a board member happens to notice.

Funding Work the Report Never Priced

A structural report, by design, does not price anything outside its own findings, which means a board budgeting off the report alone is budgeting for only part of what the property needs. The categories in the right-hand column above still have to be funded, whether through reserves, a special assessment, or a phased operating allocation, and that funding conversation goes better when the board can show a defined, sequenced inventory rather than an open-ended list of concerns.

This is also where timing matters more than boards expect. A proposal priced today for a phase scheduled a year out may not hold by the time funding is approved and the board is ready to award, for reasons that have nothing to do with the contractor changing their mind, covered in budgeting when construction prices move. Building the translation work described below early, well before the funding vote, gives the board a defined scope to re-price close to the actual award date instead of trying to defend a stale number in a meeting.

The Translation Work Nobody Assigns

Between "the report says X" and "the community has a funded, scheduled project" sits a body of work that nobody automatically owns unless the board assigns it. That work has four parts.

Scoping

Turning a finding, or a condition the board already knew about but that fell outside the report, into a defined scope of work: what exactly gets fixed, to what extent, and with what boundary. "The stucco has some cracking near the entry" is an observation. "Repair and refinish the stucco on the north and east elevations of the entry structure, from grade to the roofline, including crack routing and sealant at movement joints" is a scope. Only the second one can be priced or bid.

Sequencing

Deciding what happens first, and why. Sequencing is not just about severity. A drainage problem that is actively undermining a slab may need to happen before cosmetic work in the same area, or paint work may need to wait until stucco repairs in the same zone are complete, so the finish is not applied twice. A board sequencing purely off which finding sounds most alarming in the report, without regard for how the physical work actually has to happen in order, ends up paying for rework.

Phasing

Breaking a large body of work into stages the association can actually fund and tolerate operationally, without every trade and every crew on the property at the same time indefinitely. Phasing decisions should account for resident disruption, access, and the reality that some items are urgent and others can reasonably wait a phase or two.

Competitive Pricing

Getting more than one qualified bid on the defined scope, not just accepting whichever number arrives first because the board is anxious to show movement. A scope that has been properly defined in the scoping step is also the scope that produces comparable, apples-to-apples proposals, which is covered in more depth in how to read a contractor proposal.

None of these four steps are things an engineer's report performs. They are contracting and project-management work, and if no one on the board explicitly assigns them to a person or a firm, they simply do not happen, and the report sits exactly where it landed.

Sequencing Checklist: From Report to Funded Work

• Read the report with the engineer present or reachable, and separate findings into structural items and anything the engineer noted as outside their scope.
• Walk the property separately from the report, specifically looking for the categories a structural report typically does not cover: drainage, flatwork, cosmetic stucco and paint, fencing, irrigation, landscape grading, amenity surfaces.
• Combine both lists into one master scope inventory, tagged by category, not just by which document mentioned it first.
• For each item, write an enforceable scope description, not a one-line observation.
• Group items by physical zone and logical sequence, not only by severity, so trades are not repeating work in the same area.
• Identify any item where a delay creates a bigger problem later, such as active water intrusion or drainage undermining a structural element, and prioritize those regardless of phase.
• Break the full inventory into phases the community can fund and tolerate, with a rough timeline for each phase.
• Solicit competitive proposals against the defined scope for each phase, not a single early number.
• Document the board's sequencing and phasing decisions in meeting minutes, including why any item was deferred, so a future board can see the reasoning, not just the outcome.
• Revisit the master inventory at least annually, since conditions outside the structural report can change faster than a full re-inspection cycle.

Who Does the Translation Work

This is where a board's choice of partner matters. An engineer delivers findings and, in many cases, tracking support for those specific structural findings, a discipline covered in what boards do after an engineer's report arrives. A general contractor experienced in community association work is who typically performs the scoping, sequencing, phasing, and pricing translation across the categories the report never touched, because that is a construction management skill, not a structural engineering one.

Whoever the board assigns this to should be someone whose crews the board can actually verify are the ones showing up, not a subcontracted patchwork assembled project by project, a distinction covered in what changes when the crew works directly for the contractor. A translation plan that gets handed off between three or four different vendors for the drainage, the flatwork, the stucco, and the landscaping tends to produce exactly the coordination gaps described in the hidden cost of managing multiple vendors: schedule conflicts, disputes over which trade caused which condition, and no single party accountable for the finished result.

Common Mistakes Boards Make With the Report

A Note on Timing and Compliance Questions

Boards understandably want to know whether a given requirement applies to their community, on what schedule, and what the consequences of delay are. Those are legal and regulatory questions, and they deserve a direct answer from the association's attorney, not an inference drawn from a general article. What this article can offer instead is scope clarity: once your board has a structural report in hand, for whatever reason it was commissioned, the scope gap described here exists regardless of the legal driver behind the inspection. The translation work is the same whether the report was voluntary, board-initiated, or tied to a requirement your attorney has confirmed applies to your property.

Frequently asked questions

If the structural report does not mention drainage or landscaping, does that mean those items are fine?

No. It means the engineer was not scoped to evaluate them, not that they were checked and passed. A separate walk of the property, specifically looking at the categories outside a structural report's scope, is the only way to know their actual condition.

Should the board wait until every structural finding is resolved before addressing non-structural items?

Not necessarily, and waiting can backfire if a non-structural condition, like poor drainage near a foundation, is actually contributing to a structural finding. Sequencing should be based on how the physical work relates, not a strict rule that structural always goes first regardless of connection.

Who should the board ask to walk the property for the non-structural categories?

A general contractor with experience across the categories involved, drainage, flatwork, stucco and paint, fencing, irrigation, and landscaping, so the same walk produces a usable scope inventory rather than a list of vague observations that still need translating later.

Does a reserve study cover what the structural report misses?

Partially, and only for items it happens to track as major components. A reserve study is built around anticipated replacement timing for tracked components, not a full condition assessment of every surface and system on the property, so gaps can still exist between the two documents.

How often should the non-structural scope inventory be revisited?

At least annually, and after any major weather event. Conditions like drainage, flatwork, and irrigation can change meaningfully in a year, faster than most structural re-inspection cycles, so relying on the last full inventory for multiple years risks missing something that has since become urgent.

Can the same contractor handle both the translation work and the actual repairs?

Yes, and there is an advantage to it: the party that scoped and sequenced the work is also accountable for pricing and executing it, rather than handing a scope document to a separate bidder who did not do the original walk and may interpret it differently.

Get a Property Walk That Covers What the Report Did Not

If your board has a structural report in hand and is not sure what it still does not know about the rest of the property, start with a complimentary on-site inspection. We will walk the categories a structural report is not scoped to cover, drainage, flatwork, stucco and paint, fencing, irrigation, and landscape grading, and help translate what you already have into a sequenced, priced plan the board can act on. Request a visit to see where your property stands outside the report.