An engineer's report only protects a community if every finding gets a written status. Here is the discipline that turns a document in a drawer into work that actually gets done.
In 2018, a structural engineer delivered a report to the board of Champlain Towers South in Surfside, Florida. It identified significant structural repairs the building needed. The full scope of that work was never completed. In June 2021, the building collapsed. Ninety-eight people died.
That sequence deserves to be stated plainly, without drama added to it. The report existed. The findings were on paper. The gap was not knowledge. The gap was what happened between the report landing and the work being done.
This article is not about why that gap happened at one building. It is about the simple discipline that keeps a gap like it from opening quietly at yours.
An engineer's report is a snapshot. It tells a board what a trained set of eyes found on the day of the inspection. It carries no power of its own. It fixes nothing, funds nothing, and schedules nothing.
Boards sometimes treat receiving the report as the accomplishment. The binder gets passed around at a meeting, everyone nods at the photos, and it goes on a shelf. Eighteen months later, nobody in the room can say which findings were addressed and which were not. Board seats turn over. Managers change. The report stays exactly as useful as the tracking wrapped around it.
What happens in the first weeks after a report lands sets the tone for everything that follows. Here is a practical sequence, with realistic time framing, that keeps a report from drifting.
Schedule time, either a dedicated session or a substantial block of a regular meeting, for the board to go through the report with the engineer present or reachable by phone. A report full of technical language read silently by five different people produces five different impressions of how serious it is. Reading it together, with someone able to answer questions in the room, produces one shared understanding.
Before the meeting ends, convert every finding in the report into a row on the tracking table described later in this guide. A report with fifteen findings becomes a table with fifteen rows, no exceptions. A finding that has not yet been assigned a status is not forgotten. It simply starts with a status of "not yet assigned," which is its own kind of honesty.
The table is not a one-time exercise. It gets read aloud, or at minimum reviewed by the board, at every regular meeting until every finding reaches completed. This takes minutes per meeting once the habit is established, and it is the single practice that keeps a report from becoming a document nobody remembers.
Owners deserve to know, in language that does not require an engineering background, what the report found and what the board is doing about it. The owner-briefing section below covers how to do that without either alarming people unnecessarily or minimizing real findings.
Here is the whole discipline in one sentence. Every finding in the report carries a written status at all times, and there are only four acceptable statuses:
Notice what is not on the list. "We discussed it" is not a status. "Getting quotes eventually" is not a status. If a finding cannot honestly be placed in one of the four categories, its real status is "nobody owns this," and that is the status that grows teeth over time.
Deferring work can be a legitimate call. Budgets are finite, and not every finding is urgent. The difference between responsible deferral and quiet neglect is documentation.
A responsible deferral names the finding, states the reason, and sets a date when the board will look at it again. It survives board turnover because it is written down. A default deferral is just silence. Nothing was decided, so nothing was recorded, so the finding slid off the agenda without anyone choosing that outcome. Every finding at Surfside that went unaddressed went unaddressed one quiet meeting at a time.
A report with many findings needs an order of attention, but that order should come from the engineer's own risk framing, not from a board's guess about what matters most. Ask the engineer directly, in plain language, which findings they would want addressed first if the board could only tackle a few this year, and why.
This is a conversation, not a formula a board should invent on its own. Boards are not positioned to judge structural severity independently, and this guide does not attempt to hand you a substitute for that judgment. What a board can do is make sure the engineer's stated priorities, once given, actually show up in the tracking table as funded or under-contract statuses first, rather than getting reordered by whichever finding happens to be easiest or cheapest to schedule.
You do not need software for this. One table, reviewed at every board meeting, does the job:
| Finding | Location | Status | Reason if deferred | Next review date |
|---|---|---|---|---|
| Example: spalling concrete at garage column | Building B garage | Under contract | n/a | At completion |
| Example: stucco cracking at building corners | Buildings A and C | Deferred | Bundling with repaint next year | January meeting |
| Example: drainage pooling near building entry | Building A entry | Funded | n/a | Bid comparison at next meeting |
| Example: railing corrosion at walkway | Building C, third floor | Not yet assigned | Awaiting board discussion | Next meeting |
Ten minutes per meeting. Read the table aloud, update any status that changed, and record it in the minutes. That is the entire system. It costs nothing and it is the difference between a report that worked and a report that sat.
The tracking table only has staying power if it lives inside the board's official record, not a spreadsheet one volunteer keeps on a personal laptop. Two habits make this durable.
First, attach the current version of the table to the minutes of every meeting where it is reviewed, even when nothing changed. A minutes entry that says "tracking table reviewed, no status changes" is still a record that the board looked at it that month.
Second, note who reported each status update in the minutes, not just what changed. A status of "completed" carries more weight when the minutes show a board member or manager confirmed it with photos on file, rather than simply repeating what a contractor said in an email.
Owners are going to hear about the report one way or another. A board that communicates it proactively, in plain language, keeps the conversation grounded. A board that says nothing leaves owners to fill the silence with rumor.
A report works best when the two roles that follow it stay separate and independent of each other. The engineer diagnoses. The repair contractor executes the fix. Keeping those roles distinct protects the board from a conflict of interest and protects the quality of the diagnosis itself.
An engineer who also stands to profit from the repair work has an incentive, even an unintentional one, to describe findings in a way that favors more work. A board is better served asking the engineer to define the finding and, where they are willing, describe what a proper fix generally needs to accomplish, then taking that scope out to repair contractors to bid and execute independently.
Once a finding is funded, it needs to become a real scope, and this is where boards should demand specificity. An engineer's finding describes a condition. A contractor's estimate should describe the fix, broken out clearly, not folded into one lump number. The same vetting habits that apply to any contractor hire apply here: verify the license, verify the insurance, and check references, all covered in our guide to how Florida boards vet contractors. The trade-show version of that same scrutiny is in our guide to questions to ask a contractor at a trade show.
Many report findings correspond to symptoms a board can learn to read on its own property. Cracked or delaminating patches are covered in our guide to why concrete patches fail. Diagonal cracking at building corners is covered in stucco corner cracks and what they say about movement. Rust streaks bleeding through a wall are covered in rust stains on community walls. Reading those guides will not replace your engineer. It will make your board a sharper buyer of the repairs the engineer recommends.
Engineer's reports arrive years apart. Conditions do not wait between them. Water is the most common driver of the deterioration that ends up in the next report, which is why routine attention to drainage around your buildings and common areas is structural maintenance in slow motion.
A quarterly property walk with a camera, plus a standing general maintenance relationship for the small repairs, keeps small findings from graduating into report findings. The cheapest structural repair is the one a future report never has to mention. Knowing how to vet the contractors who do that work is part of the same discipline.
Engineer's reports carry their own vocabulary. Here is what the terms that matter most tend to mean, in plain English, so a board is not guessing at severity from unfamiliar words alone.
| Term | Plain-English Meaning |
|---|---|
| Spalling | Concrete that has cracked and broken away from the surface, often exposing the reinforcing steel underneath. A common finding on garages, balconies, and exposed structural columns. |
| Delamination | A layer of concrete or coating separating from the layer beneath it, frequently invisible from the surface until it is tested or until it fails outright. |
| Reinforcing steel (rebar) corrosion | Rusting of the steel embedded inside concrete, which expands and cracks the surrounding concrete from the inside out. Often the underlying cause behind a stain or a crack a board can see. |
| Load-bearing element | A structural component, such as a column or beam, that carries weight from the building above it. Findings involving load-bearing elements are why an engineer's judgment on sequencing matters. |
| Scope of repair | The engineer's description of what a fix needs to accomplish, distinct from a contractor's priced plan for how to execute it. |
| Follow-up inspection | A return visit by the engineer to confirm a completed repair actually resolved the finding as intended, rather than relying on the contractor's own sign-off alone. |
Beyond the tracking table, keep a simple file specifically for the report and its history, filed alongside the vetting documentation described in our contractor vetting guide.
This file, kept together and handed to each new board as it turns over, is what actually protects a community. A report sitting alone in a drawer, without this surrounding record, is the exact condition this guide is written to prevent.
Board seats change hands regularly, often faster than a multi-year repair program takes to complete. A tracking table and a documentation file are what let a report survive that turnover intact. Build the habit of a five-minute handoff briefing for any new board member: walk them through the current tracking table, show them where the documentation file lives, and point out which findings are furthest from completed. A new board member who inherits a clear table inherits the discipline along with it. A new board member who inherits a binder and a vague memory of "we handled most of it" inherits the exact gap this guide is written to close.
Read it together with the engineer available to answer questions, then immediately convert every finding into a row on a tracking table, even if some rows start as "not yet assigned."
At every regular board meeting, until every finding reaches completed. It takes minutes once the habit is established.
Yes, when the deferral is a documented decision with a stated reason and a date to revisit it. The problem is silent neglect, not deferral itself.
Keeping the diagnosing role and the repair role independent of each other protects both the quality of the diagnosis and the board from a conflict of interest.
Enough plain-language detail to see that findings have owners, dates, and a written status, without speculation beyond what the engineer actually reported.
That conversation belongs with the engineer directly. A board is not positioned to reorder structural priorities on its own judgment.
No. Conditions change between reports, which is why a regular property walk and ongoing maintenance matter in the years a report is not scheduled.
If your association has a report with findings that still need scoping, or visible conditions you want assessed before the next report, we offer a complimentary on-site inspection and a clear, specific proposal across Central Florida, including Orlando, Longwood, Sanford, Maitland, Casselberry, Winter Park, and Lake Mary. Call the office at (407) 744-9122 or message us to schedule a walk-through of your property.