We pull cores, map the moisture distribution, and give you an honest answer on recover versus replace. A moisture survey before a Fort Worth roof project prevents the expensive discovery of saturated insulation after the work starts.

Saturated roof insulation is the most consequential variable in a commercial roof scope. A recover over wet insulation traps the moisture, prevents the new membrane from bonding properly in adhered systems, and voids the warranty — because every manufacturer's installation requirements specify that the substrate must be dry. A replacement scope that misses the extent of wet insulation gets expensive fast when the crew starts pulling roof and finds more saturation than the scope allowed for.

We run moisture surveys before scoping any recover or replacement project where insulation saturation is a reasonable question — and in Fort Worth, with the freeze-thaw cycling and the hail exposure this market sees, saturation is almost always worth checking. The survey tells us how much of the insulation is wet, where it is wet, and how wet it is. That data drives the scope.

Our moisture survey protocol combines physical core sampling with complementary methods (infrared thermography on qualifying days, nuclear moisture gauge readings in suspect areas) to produce a moisture distribution map that covers the whole roof — not just the zones where we can see ponding water or bubbling membrane.

Core Sampling Protocol

We pull cores at a density that gives us statistically meaningful coverage — typically one core per 2,500-5,000 sq ft on buildings under 50,000 sq ft, denser in zones with visible distress. Each core pulls a plug of membrane and insulation to the deck. We assess the insulation moisture content at the pull, note the depth and distribution of the saturation within the insulation stack, and photograph the core sample with a zone reference before we patch.

Each core site is patched the same day with compatible materials — we do not leave penetrations open overnight. Core locations are plotted on the zone diagram. We note the moisture condition at each location (Dry, Damp, Wet, Saturated) and the depth at which moisture appears in the insulation stack. From that data we interpolate the moisture distribution between core locations using the zone diagram as the base.

The 25% threshold matters because every major manufacturer uses a variant of it in their recover specifications: if more than 25% of the insulation area tests wet, a recover is not warrantable. The threshold applies to the whole roof, not to individual zones — a roof with one heavily saturated zone and several dry zones may still clear the threshold, and we report the distribution so the project team can make an informed decision about whether to replace the saturated zone insulation and recover the rest.

Moisture Distribution Map and Recover-vs-Replace Decision Support

The moisture distribution map overlays the core-sample data on the zone diagram and marks wet, damp, and dry zones by color. For buildings where we also ran infrared or nuclear gauge readings, those data points are added to the map as supplementary evidence. The map is the primary deliverable of the moisture survey — it is what the project team, the owner, and the manufacturer's warranty representative all use to evaluate the scope.

The recover-vs-replace decision is driven by the percentage of wet insulation area and the location of the wet zones. If the wet areas are under 25% and concentrated in areas with drainage problems that the new roof system will correct (drain relocation, tapered insulation addition), a recover with targeted insulation replacement in wet zones is a sound scope. If the wet areas exceed 25%, or if they are distributed broadly across the roof rather than concentrated at drainage problems, replacement is the honest recommendation — and we say so in the report even when replacement is a harder sell than a recover.

Commission a moisture survey before your next Fort Worth roof project.

We will pull cores, map the moisture distribution, and give you a clear recover-vs-replace recommendation based on what we actually find — not what the scope template assumes.