Roof Replacement vs Recover Analysis in Orlando, FL

Capability

Moisture Core Testing Protocol

Moisture core pulls are the only reliable way to determine insulation saturation condition. Visual inspection of the membrane surface does not reveal whether insulation below is wet. Infrared thermography can indicate moisture distribution on the roof surface but is not definitive for insulation condition and requires the right atmospheric conditions — temperature differential, low humidity, and a clear sky — to produce reliable data. Cores are definitive.

My protocol for a replacement-vs-recover analysis on an Orlando commercial building starts with a core pull program based on the building's drainage pattern and repair history. I pull five to ten cores in representative locations: at each drain and in the ponding zone upslope of each drain, at areas where spot repairs have been made (spot repairs are a reliable indicator of prior water intrusion), and at any area where the membrane surface shows bubbling, wrinkles, or discoloration that suggests moisture below. Each core is cut through the full membrane and insulation stack to the deck, inspected for moisture content visually and by hand, and photographed.

If more than 25% of cores read wet, full replacement is the recommendation. This threshold comes from the fact that wet insulation migrates — moisture in one core location is often connected to a larger wet zone that the cores sample at points but do not fully define. An owner who recovers over 25% wet cores is recovering over a wet field that will continue to degrade. If fewer than 25% of cores read wet and the wet locations are isolated and addressable by cutting out and replacing those sections before recover, the recover path can be viable with that remediation.

Deck Condition Assessment

Deck condition is the second determinant. Metal deck on Central Florida commercial buildings — particularly buildings from the 1980s through the mid-1990s that make up a large part of the commercial inventory in South Orange, SODO, and along the Sand Lake Road corridor — often shows corrosion at drain points and at perimeter edges where water has ponded and evaporated repeatedly over the decades. A corroded metal deck cannot accept the fasteners that a mechanically attached recover system requires — the fastener pullout strength is compromised, and the FBC wind-uplift requirements cannot be met without deck replacement.

I open deck inspection ports at wet core locations and at any area where the membrane shows significant deflection — deflection under foot traffic is a reliable indicator of compromised deck capacity below. The inspection ports are cut small enough to be easily patched but large enough to visually assess the deck condition over a meaningful area. If more than 10% of the deck area shows corrosion beyond cosmetic surface rust, deck replacement is added to the scope — and deck replacement moves the project firmly into full replacement territory, both in cost and in code compliance obligation.

Florida Building Code also requires that a recover be evaluated for roof-to-wall connection compliance at the perimeter. Buildings constructed before the 2001 FBC updates may have perimeter connections that do not A recover that adds a second layer of insulation and membrane increases the wind load on the roof-to-wall connection. If the existing connection does not meet FBC requirements for the total assembly, the recover triggers a connection upgrade — which may require structural involvement and changes the cost calculus significantly.

Florida Building Code Weight and Layer Limits

Florida Building Code limits commercial roofs to two membrane layers. A building that already has two layers of roofing cannot legally receive a recover — tear-off of at least one layer is required before a new installation. This is a frequent situation on Central Florida commercial buildings from the 1980s and 1990s that received their first recover in the early 2000s. Layer count verification is part of every replacement-vs-recover analysis I conduct.

The FBC two-layer limit exists for structural load reasons and for fire rating integrity — the cumulative weight of multiple membrane and insulation layers changes the dead load on the deck and can affect the fire rating of the assembly. For buildings with existing two-layer systems, the decision is not replacement-vs-recover; the decision is which layer to tear off and what to specify for the replacement. Often the answer is tearing both layers and starting fresh, because the deck condition under a 30-year-old two-layer system is usually worth inspecting before committing to any scope.

Weight load is also relevant for buildings where the owner wants to add a ballasted system, a green roof element, or a rooftop solar array in connection with the recover project. I calculate the combined dead load of the proposed assembly against the structural engineer's documented roof live and dead load capacity before recommending any ballasted or vegetated system option.

Written Recommendation and Supporting Documentation

The output of the replacement-vs-recover analysis is a written report that an owner can act on — and that a contractor, a lender, or an insurance carrier can review and evaluate. The report covers: the inspection date and building location, the core pull locations and findings, the deck condition findings at inspection ports, the layer count verification, the FBC compliance status of the existing system, the recommendation (replace or recover with rationale), and an estimated cost band for each option based on current Central Florida market pricing.

The written recommendation is the asset the owner uses to solicit competitive bids. A contractor who disagrees with the recommendation has to explain why the core pull data does not support their alternative recommendation — which is a very different conversation than an informal dispute over whether the roof really needs to be replaced. The documented analysis shifts the burden of argument from the owner to the contractor who wants to deviate from it.

Frequently asked questions