Roof Warranty Coordination.

In a Gulf Coast storm market, manufacturer warranty claims are most likely to be filed in the weeks after a named storm — when the manufacturer's warranty department is at peak volume and scrutinizing maintenance documentation most carefully. We complete the annual maintenance documentation before hurricane season opens, not after a claim is already running.

We hold active manufacturer credentials with GAF, Carlisle SynTec, Johns Manville, Sika Sarnafil, and Versico. Those credentials are the prerequisite for performing warranty-qualifying maintenance work and for submitting maintenance documentation to each manufacturer's warranty tracking system. An uncredentialed contractor walking a GAF EverGuard-warranted roof in April does not produce documentation that GAF accepts as warranty-compliant maintenance — regardless of what was found or repaired.

The New Orleans market concentrates warranty risk in a way that flat-market cities do not. Storm events generate claims across the Gulf Coast region simultaneously, and manufacturers' warranty departments process them in the order they are received, with complete documentation reviewed before incomplete documentation. Building owners who file claims without a complete annual maintenance record behind them — or who discover in August that the maintenance documentation for the current year was not filed — face delays, coverage reductions, and denials at the worst possible time.

Our warranty coordination program is specifically timed around this risk. Pre-hurricane inspections in May and June complete the annual maintenance documentation for every warranted building in our program before the Atlantic hurricane season opens on June 1. If a storm event generates a claim in August, September, or October, the maintenance record for that calendar year is already filed with the manufacturer — not pending, not in progress, filed.

What Each Manufacturer Actually Requires

GAF EverGuard Extreme warranties require annual maintenance by a GAF-credentialed contractor with a maintenance report submitted to GAF's warranty management system within 90 days of the service date. The report format is GAF-specified — a generic inspection form does not satisfy the requirement. We submit directly to GAF's system and retain the submission confirmation for every building in our program.

Carlisle SynTec SureCast and Sure-Weld warranties require annual maintenance with a Carlisle-approved contractor. Carlisle's maintenance standard requires a documented inspection of every accessible seam — not just visual assessment of the field membrane — plus drain clearing and flashing condition documentation. We follow Carlisle's published protocol for each warranty tier and submit documentation to Carlisle's warranty tracking system.

Johns Manville JM PremiumPlus warranties specify maintenance frequency by warranty tier — some are annual, some biannual — with documentation submitted to JM's warranty system. JM also requires that any repairs during the warranty period be performed by a JM-credentialed contractor and documented against the warranty number. We flag JM-warranted buildings that need repair work and perform the repairs under the JM repair protocol before filing the maintenance record.

Sika Sarnafil and Versico, now both part of the Sika group, maintain separate warranty programs with their own documentation requirements. Many New Orleans commercial buildings have Sarnafil or Versico systems installed in the post-Katrina reconstruction wave of 2006-2015 — buildings now in the middle or late portion of their original warranty term. we install both legacy programs and file maintenance documentation under whichever warranty number the building's roof was registered under.

Any repair performed on a warranted roof during the warranty period needs to follow the manufacturer's detail standard and be documented against the building's warranty number. This is the failure mode that post-storm repairs generate most often in the New Orleans market: a building takes storm damage, an emergency repair is made quickly under post-storm pressure by whoever is available, and the repair is physically sound but does not use the correct membrane material or flashing detail for that manufacturer's system. The building performs fine for years. Then the roof fails elsewhere, the owner files a warranty claim, and the manufacturer's field inspector finds the non-compliant prior repair and excludes the area around it from coverage.

We perform repairs on warranted systems under the applicable manufacturer's repair standard and document every repair against the building's warranty number. For emergency post-storm situations where a temporary dry-in repair needs to be made immediately, we document the temporary repair separately from the permanent repair, perform the permanent repair under the manufacturer's protocol as soon as conditions allow, and ensure the warranty record reflects both phases clearly. If a building already has non-compliant prior repairs when we take over the account, we assess them, note them in the condition record, and advise the owner of the specific warranty exposure.

Coordinating Storm-Related Warranty Claims

When a named storm event generates a warranty claim situation — a membrane failure at a field seam or a flashing failure at a manufacturer-detailed transition that the storm exposed or accelerated — we coordinate the claim process with the manufacturer's warranty department. That means documenting the failure with zone-keyed photography, identifying whether it is within the warranty coverage scope, notifying the manufacturer's warranty department with the maintenance record attached, and scheduling the manufacturer's field inspection.

New Orleans's geographic situation means post-storm warranty claims are filed in clusters — every manufacturer's Gulf Coast warranty portfolio gets hit simultaneously after a significant storm. The claims with complete maintenance records behind them move through the process fastest. We attend the manufacturer's field inspection and present the pre-storm condition documentation alongside the post-storm damage documentation, so the field rep can see the chronology clearly.