- 07961839260
A commercial roof warranty can be valuable, but the facilities team still needs a reliable record of what has happened to the roof after handover. If inspections, maintenance, repairs, alterations and access events are poorly documented, it becomes much harder to understand the roof’s condition, prove what work has been completed or respond clearly when a defect or warranty question arises.
This guide is not a universal warranty rulebook. Warranty terms vary by manufacturer, roofing system, installer, contract and project. The correct maintenance obligations are the ones stated in the actual warranty, operation and maintenance information and other project documents that apply to that roof.
The practical objective is therefore evidence control. FM teams should be able to show what the roof was at handover, when it was inspected, what defects were identified, what maintenance or repair followed, what changes were made and which warranty or manufacturer requirements were checked before work was authorised.
This guide does not tell you whether a specific warranty claim will be accepted. That depends on the warranty wording, cause of failure, evidence, exclusions and any contractual or technical issues relevant to the claim.
It also does not state how often every commercial roof must be inspected. Inspection frequency should follow the applicable warranty, manufacturer information, O&M documents, survey recommendations, roof condition, building use and risk profile.
A generic internet rule should never replace the maintenance obligations written into the actual documents for the roof.
Pause before authorising a repair or alteration if nobody has checked whether the roof is still under warranty, whether the proposed material is compatible or whether the work must be completed by an approved contractor or under a specific process.
Escalate where there is active water ingress, structural concern, unsafe roof access, suspected widespread moisture, damaged safety equipment or another defect that should not wait for routine record administration.
The evidence file supports decisions, but it does not replace urgent technical action.
RICS planned preventative maintenance guidance treats condition data, inspection records and maintenance planning as part of structured asset management. This matters because a roof’s history should be visible rather than reconstructed after a problem develops.
An FM team should be able to answer:
The value of this record extends beyond warranty claims. It also supports planned maintenance, CAPEX decisions, due diligence, contractor briefing and future refurbishment.
The evidence trail should begin with the project handover. Retain the final roof specification, as-built drawings, roof-zone information, warranties, manufacturer data, maintenance instructions, relevant certificates and access information.
The existing commercial roof handover file checklist explains the broader close-out package. For warranty evidence, the key is to identify which handover documents create ongoing FM actions.
For example, if the maintenance section requires periodic inspections or sets conditions for approved repairs, transfer those items into the planned maintenance system rather than leaving them buried in a PDF.
A simple register makes it easier to see the current warranty position across a site or estate. Use one row per roof system or warranted area.
The register is an index, not a substitute for the warranty. Where the summary and original document differ, the original project-specific document controls.
RICS guidance supports methodical inspection and structured recording. For FM teams, consistency is more useful than elaborate reporting.
Every inspection record should identify:
A commercial roof condition survey can provide a stronger baseline where the roof condition is uncertain or the FM team needs an independent assessment.
Photographs are useful only if they can be understood later. A folder containing hundreds of unlabeled roof images is weak evidence.
Use a consistent naming method and capture both context and detail. For a defect, one image should show where it is on the roof and another can show the close-up condition.
Useful photo categories include:
Repeat photographs from similar viewpoints where practical. That makes change easier to see.
An inspection proves that somebody looked at the roof. It does not prove that the resulting maintenance was completed.
For each maintenance action, record the instruction date, contractor, scope, roof zone, completion date and evidence. If an outlet was cleared, a seal repaired or debris removed, the maintenance record should show that the action followed the inspection finding.
The existing industrial roof maintenance schedule guide can support the recurring-task structure, while the site’s commercial roof maintenance service provides the service route for planned work.
Repairs deserve more detail than routine cleaning because they can alter the waterproofing system and may affect future warranty discussions.
Record:
If the repair method is unclear, pause before allowing an improvised patch. The short-term need to stop a leak should be balanced with system compatibility and the consequences of introducing unapproved materials.
Commercial roofs rarely remain exactly as handed over. New HVAC equipment, ducts, solar PV, cable routes, aerials, extraction systems and access equipment can all change the roof.
Create a roof-change log that records:
This prevents a later FM team from finding an unfamiliar penetration and having no record of who installed it or how it was weathered.
The warranty may contain minimum conditions, but a good maintenance strategy should also reflect the roof’s actual condition, exposure, occupancy and business-critical risks.
A roof over sensitive production equipment may justify more frequent observation than a lower-risk area, even if the warranty wording is the same. Likewise, a recurring drainage problem may justify targeted inspection beyond the minimum maintenance schedule.
Use the warranty as one control input, not the only asset-management input.
A practical evidence register can use one row per event or action:
This mirrors the wider RICS principle of using structured schedules with location, defect, condition, action and photo references rather than relying on disconnected narrative reports.
The roof evidence file should change when the roof changes. Add new defects, repairs, maintenance obligations and alterations as they occur.
RICS PPM guidance recognises that new defects or maintenance obligations can emerge over time and should be introduced into the record. This prevents the evidence file becoming a historical handover archive that no longer describes the asset.
Review the record after major leaks, repairs, inspections and alterations, and during the normal annual maintenance or budgeting cycle.
If a defect could develop into a warranty claim, preserve the evidence before repair work changes the condition.
Do not destroy or overwrite earlier evidence simply because a new report has been produced. A timeline is often more useful than the latest document alone.
When a roof defect appears, the evidence file should avoid jumping directly from “there is a leak” to “the roof system has failed”. A useful record separates the observed condition, the suspected cause, the investigation undertaken and the party responsible for the next action.
For example, internal water staining may relate to a roof-covering defect, blocked drainage, a service penetration, condensation, plant leakage or another building issue. The first inspection should record what was actually observed rather than presenting an unverified diagnosis as fact.
Use four fields:
This distinction improves warranty administration because it preserves the original evidence before later repairs or assumptions change the record.
Contractor reports should be stored in the same evidence structure rather than as isolated attachments. When a maintenance or repair contractor attends the roof, ask for enough information to connect the visit to the existing roof history.
A useful contractor completion record should identify the roof zone, reported issue, work completed, materials used where relevant, photographs and any recommendation for follow-up. If the contractor identifies an issue outside the instructed scope, record it as a new open item rather than relying on a note hidden in the invoice.
Where the roof remains under warranty, the FM team should also record whether the contractor was selected or approved in line with any applicable warranty condition. Do not assume that appointing a competent contractor automatically satisfies every warranty requirement, because individual schemes may impose specific conditions.
Evidence becomes much more valuable when every document refers to the same roof areas in the same way. Establish a simple roof-zone naming convention at handover and reuse it for inspections, photographs, repairs and maintenance.
For example, a large industrial building might use Roof A, Roof B and Roof C, with further references such as A-North Gutter, B-Rooflight Run 2 or C-Plant Zone. The exact naming method matters less than consistency.
A controlled roof plan with zone labels can then act as the common reference point for contractors, FM teams and future surveyors. This reduces ambiguity when a historic record says “repair completed near rear outlet” several years later.
Warranty and maintenance records can also improve CAPEX decisions. Before approving a major refurbishment or replacement, review the evidence trail to understand the frequency of defects, repair history, recurring locations and whether deterioration is isolated or becoming systemic.
A roof that has required repeated work in the same zones may justify deeper investigation before another local repair is approved. Conversely, a roof with a stable inspection history and isolated defects may support a more targeted intervention.
The evidence trail should therefore feed both warranty administration and wider asset planning. It is not merely a defensive record for disputes.
Keeping only the warranty certificate. The conditions, exclusions and maintenance information are often more important operationally than the headline certificate.
Using generic inspection rules. Check the actual warranty and manufacturer information for the roof.
Taking photographs without locations. Evidence is stronger when the roof zone and observation are clear.
Recording defects but not repairs. An open defect list without completion evidence does not show what happened next.
Allowing penetrations without updating records. Later alterations can materially affect the roof and should be documented.
Mixing versions of reports. Keep a controlled current record and retain superseded records as history rather than allowing several conflicting “latest” versions.
Start with the handover file and identify the actual warranty documents, roof build-up, maintenance instructions and as-built information. Create a warranty register and one evidence log for inspections, defects, maintenance, repairs and changes.
For every inspection, use the same roof-zone naming and photo-reference system. Transfer recommended actions into the maintenance programme and record completion evidence when the work is finished.
Before any later repair or penetration, check the warranty and system information. If compatibility or approval requirements are unclear, obtain the appropriate technical advice before altering the roof.
If you need a current condition baseline or ongoing inspection support, send the roof and warranty details to Industrial Roofing Services to discuss the appropriate survey or maintenance route.
Commercial roof warranty evidence is not one certificate. It is the timeline that shows what was installed, what warranty applied, how the roof was inspected, what defects were found, what maintenance and repairs were completed and what later changes were made.
The strongest FM record combines the original handover documents with a controlled inspection, maintenance, repair and alteration log. It uses location-based photographs and keeps project-specific warranty conditions visible rather than replacing them with generic rules.
This evidence supports more than warranty discussions. It also improves roof maintenance, CAPEX planning, contractor briefing and future refurbishment decisions.
There is no universal interval that applies to every commercial roof warranty. Follow the actual warranty, manufacturer information, O&M documents and project-specific maintenance requirements.
Keep the warranty, as-built information, inspections, defect records, maintenance, repairs, roof alterations, photographs and relevant correspondence in one controlled evidence trail.
Yes, particularly where the repair changes the waterproofing system. Record the original defect, approved repair method, contractor, completion date and evidence.
They can. The effect depends on the roof system and warranty terms. Check the actual documents before approving alterations and record the completed detail.
No. A condition survey is a point-in-time assessment. The FM evidence trail should continue with later inspections, maintenance, repairs and changes.
No. Keep historic records so the roof’s condition and actions can be followed over time, while clearly identifying the current controlled version.
Try to recover them from the project records, contractor, system provider or building owner. Until the terms are known, avoid assuming generic maintenance or repair rules apply.
