- 07961839260
A fragile roof risk register is a practical record that helps facilities managers identify roof areas, rooflights, materials, access points, known hazards and information gaps before roof maintenance, cleaning, inspection or repair work is planned. It is not a replacement for a competent roof survey, contractor method statement, access plan, rescue plan or risk assessment. It is a management tool that helps the person responsible for the building brief the right people before anyone works on or near the roof.
This guide is for facilities managers, building owners, landlords, property managers, estates teams and commercial site managers responsible for industrial or commercial buildings. It explains what a fragile roof risk register is, what it should contain, how it supports maintenance planning and when roof access should be paused until competent advice is obtained.
The main risk is simple. A roof can look serviceable from below, from the edge or in old photographs, but still be unsafe to stand on. Rooflights, ageing sheets, asbestos cement materials, corroded metal sheets, patched areas and unsupported roof sections can all create serious fall-through hazards. The register should therefore be treated as a safety planning record, not as permission for access.
This guide does not prove whether a roof is safe to walk on. It does not replace a roof survey, structural assessment, asbestos management process, work-at-height plan, method statement, rescue plan or contractor risk assessment. It also does not authorise maintenance staff, cleaners, surveyors or contractors to access a roof without proper planning.
A fragile roof risk register is most useful when it brings together information that might otherwise sit across old survey PDFs, maintenance emails, site drawings, contractor notes and building files. It helps the facilities manager understand what is known, what is uncertain and what must be checked before work begins.
If the roof is old, altered, patched, storm-damaged or poorly documented, the register should make that uncertainty visible. In many cases, the right next step is a professional inspection rather than an internal maintenance task. Where a site-specific condition review is needed, Industrial Roofing Services (NE) Ltd provides roof condition survey support for commercial buildings.
Pause before arranging roof maintenance if anyone is unsure whether the roof, rooflights or access route can safely support work. Escalate the issue if the job involves work near unprotected edges, rooflights, asbestos cement sheeting, damaged sheets, corroded fixings, gutter lines, valley gutters, service penetrations or areas previously affected by leaks.
Stop the task if internal staff are expected to walk on an unverified roof area, if a contractor asks for roof access without a clear access plan, or if the only available information is a verbal assumption such as “it has always been fine”. A roof that has been accessed before is not automatically safe now. Weathering, age, corrosion, repairs and previous loading can change the risk profile.
Escalation is also sensible where the building remains operational during the work. Warehouses, factories, schools, healthcare buildings, retail units and food production sites may need extra planning because roof work can affect staff, visitors, production, stock, hygiene controls, access routes and business continuity.
A fragile roof risk register is a controlled record of known and suspected roof fragility issues. It should identify the parts of a roof where access may be hazardous, the evidence behind that view and the actions needed before work proceeds. It is not just a list of defects. It is a planning record that helps facilities teams make safer decisions before surveys, maintenance, cleaning, repairs or contractor visits.
The register is especially useful for industrial and commercial buildings because roof areas are often large, split across extensions or phases, and built from different materials. A single building may include metal sheets, rooflights, valley gutters, older fibre-cement sheets, flat roof sections, coated areas, patched details and newer replacement panels. Each area may have a different risk profile.
The register should help answer five practical questions. Which roof areas exist? Which areas are known or suspected to be fragile? What evidence supports that view? What controls or restrictions are already in place? What must be checked before the next person accesses the roof or works near it?
For a facilities manager, the value is not only safety. A good register can also reduce delay when urgent roof maintenance is needed. If the building already has clear roof zone references, access notes, survey dates and risk status, it is easier to brief a contractor and avoid wasting time while basic information is gathered.
The register should be specific enough to support real decisions. A vague note saying “roof may be fragile” is better than no warning, but it is not enough for good planning. Use clear roof zones, dates, evidence, confidence levels and actions.
Start with the building name, site address, roof zone, roof level and any internal reference used by the business. For a large site, split the roof into logical areas such as warehouse roof, office flat roof, loading bay canopy, production hall roof, plant deck, extension roof and valley gutter runs. Where drawings exist, the register should refer to those drawings clearly.
Each roof zone should have a short description of the roof type. For example, the register may record profiled metal sheet roofing, built-up felt, single-ply membrane, fibre-cement sheets, rooflights, insulated panels or mixed materials. Do not guess the construction where it is unknown. Mark it as unknown and set an action to verify it.
Record rooflights, older sheets, asbestos cement materials, corroded or weathered panels, patched areas, damaged areas, unsupported sections and any location where a previous report raised concern. Rooflights should be treated carefully because they can weather, discolour or blend into surrounding sheets. Some may not be obvious in poor light or from an access point.
If asbestos roof materials are known or suspected, record the location of the asbestos information and do not treat the register as an asbestos survey. The register should point users to the correct asbestos record and flag that specialist controls may be needed. Where asbestos roof issues affect repair planning, refer the task to a competent contractor with commercial asbestos roof repair experience.
Record how each roof area is normally accessed, if at all. Include fixed ladders, roof hatches, plant room access, scaffold routes, mobile elevated work platforms, mansafe systems, walkways and any prohibited access points. If there is no approved access route, say so clearly.
The register should also record whether access equipment, edge protection, crawling boards, fall prevention systems or specialist contractor arrangements may be required. Avoid writing instructions that encourage untrained staff to use equipment. The aim is to identify planning requirements, not to create a step-by-step access method.
Every entry should show where the information came from. Evidence may include a roof survey, drone inspection, maintenance report, contractor photographs, asbestos documentation, repair records, incident notes, warranty files, building drawings or a site inspection. Add the date of the evidence because roof condition can change.
Use a confidence level. For example, “confirmed fragile by survey”, “suspected fragile due to age and material”, “unknown condition” or “restricted access until assessed”. This helps avoid false certainty. Unknown is a valid status when the building records are incomplete.
Each risk entry should have a next action. That action may be to request a roof survey, update drawings, restrict access, brief contractors, obtain asbestos information, arrange safe access planning, review a maintenance method or update the register after repairs. Add an owner and review date so actions are not left open indefinitely.
A fragile roof register is most useful when it supports a decision. The decision should not be “can someone get up there quickly?” The better question is “what must be confirmed before anyone is exposed to roof risk?”
This route may be suitable where the roof has recent survey information, the fragile areas are clearly marked, access routes are understood and the planned work can be briefed to a competent contractor. Even then, the register should be shared as background information only. The contractor still needs to assess the job, plan the work and apply suitable controls.
This situation often applies to planned maintenance, routine inspections, known gutter runs and roof areas with recent condition information. It may also apply where a previous survey has identified safe inspection routes and areas that must not be stepped on.
This route is appropriate where the roof condition is uncertain, the building has older materials, previous repairs are poorly documented, leaks are recurring or the maintenance request requires access near rooflights, gutters or fragile sheets. A survey can help turn uncertainty into a clearer maintenance plan.
Where direct access is difficult or would create unnecessary risk, remote visual roof inspection options may help gather information before a closer inspection is planned. Drone inspection does not solve every technical question, but it can be useful for identifying visible condition issues and deciding what should happen next.
Stop and escalate if the job requires someone to step onto a roof area that is unverified, damaged or suspected to contain fragile materials. Also stop if rooflights are present and their condition is unknown, if asbestos cement sheets may be present, if the access route is unclear or if work is proposed during adverse weather.
Escalate if the roof issue affects business continuity, public safety, critical equipment, production, stock protection or vulnerable building users. In these cases, speed matters, but uncontrolled access can make the problem worse.
The register should be used before work is ordered, not after a contractor arrives on site. A simple process helps keep the record useful.
Collect roof surveys, planned maintenance notes, photographs, drawings, asbestos records, previous repair reports, leak logs, gutter clearance records and warranty information. Look for contradictions. One report may describe an area as metal sheet roofing, while an older drawing shows a different material. Do not resolve uncertainty by guessing. Record the conflict and set an action to verify it.
A register should not treat a complex roof as one surface. Split it into areas that reflect how people access, inspect and maintain it. Zone-based records are easier for contractors to understand and easier for site teams to keep updated.
For example, a building may have a main warehouse roof, office flat roof, rear extension, loading canopy, valley gutter section and plant platform. Each area may need a separate risk status.
Use cautious wording where certainty is limited. “Suspected fragile rooflights to be verified before access” is better than a blank entry. “Do not access until surveyed” is better than informal memory. The register should make uncertainty visible enough that nobody treats missing information as permission.
Different maintenance tasks create different access needs. Gutter clearance, leak tracing, plant servicing, roof repairs, roof cleaning and visual inspections may all require different approaches. A register should show which roof zone is affected, what access may be needed and whether the task should proceed to survey, contractor briefing or escalation.
For roof drainage work, check the register before arranging commercial gutter clearance for industrial roof areas, especially where valley gutters sit next to older sheets, rooflights or restricted access zones.
A job request that says “clear gutters” or “inspect leak above unit 4” may not give enough risk context. A better brief includes the roof zone, access restrictions, known fragile features, asbestos information, previous survey dates, photographs and any site rules. The register helps the facilities manager assemble that information quickly.
The contractor should still carry out their own assessment and plan the work. The register is background information and a dutyholder management record. It does not transfer responsibility for safe work planning away from the competent contractor.
One common mistake is treating roof access as routine because a site has had maintenance work before. Previous access does not prove current safety. Roof condition can deteriorate, especially around fixings, laps, gutters, coatings, rooflights and older sheets.
Another mistake is recording only obvious defects. A fragile roof register should include suspected risk and uncertainty. Missing information is itself a management issue because it can lead to poor decisions under time pressure.
A third mistake is allowing small jobs to bypass the register. Short maintenance tasks, leak checks and cleaning jobs can still create serious risk. A small task can involve stepping near a rooflight, leaning over a gutter or crossing an unverified sheeted area.
Facilities teams can also rely too heavily on photographs without context. Photographs are useful, but they need dates, locations and interpretation. A close-up image of a damaged sheet is much more useful when the register states which roof zone it relates to and what action followed.
Another issue is failing to update the register after work. If a roof section is repaired, overclad, surveyed or restricted, the register should reflect the new position. Old warnings should not be deleted without reason. Keep a record of the change so future teams understand the history.
A fragile roof risk register works best when it is part of planned roof management. It should not be created once and forgotten. Review it after surveys, repairs, leaks, storm events, gutter clearance, plant installation, refurbishment and any incident or near miss.
For planned roof care, the register can sit alongside ongoing industrial roof maintenance planning. This helps align safety records with practical maintenance needs, such as drainage checks, coating condition, sheet defects, fixings, flashings and previous repair areas.
For multi-site estates, keep the format consistent. Use the same roof zone naming logic, risk categories and review fields across all buildings. This makes it easier to compare risks, prioritise surveys and brief contractors. It also helps when staff move roles or external property managers take over a site.
The register should be accessible to the people who need it, but controlled enough to avoid outdated versions being used. Store it with other live building safety, maintenance and contractor briefing information. If the business uses a property management system, make sure the register links to the correct roof drawings, survey files and action logs.
Do not let the register become a paperwork exercise. Its value comes from practical use. If a roof zone is marked as unknown, someone should decide whether that uncertainty is acceptable or whether it must be resolved before work is planned.
To create a useful fragile roof risk register, start by gathering existing roof records and splitting the roof into clear zones. Record known fragile features, suspected fragile features, access restrictions, evidence sources, confidence levels and actions. Use cautious wording where information is incomplete.
If the building has older roof materials, rooflights, asbestos cement sheets, poorly documented repairs, recurring leaks or unclear access routes, arrange a professional review before work is scoped. A site-specific survey can help confirm roof condition, identify priority risks and support a safer maintenance plan.
When briefing a contractor, provide the register along with photographs, drawings, access information, asbestos records where relevant and any known restrictions. Ask for a method that reflects the roof condition, not just the task. A good response should explain how access will be controlled, what areas are excluded, what assumptions have been made and what additional checks are needed.
For industrial and commercial buildings in the North East, Industrial Roofing Services (NE) Ltd can help with roof condition surveys, planned maintenance advice and risk-led roof inspections. If the register identifies uncertainty that needs a site visit, contact Industrial Roofing Services (NE) Ltd with your building details, including the roof type, known issues, photographs and any previous survey information.
A fragile roof risk register helps facilities managers record what is known, what is suspected and what must be checked before roof maintenance work begins. It should cover roof zones, access points, rooflights, fragile materials, asbestos information, previous surveys, repairs, restrictions and actions.
The safest approach is to treat uncertain roof areas as potentially fragile until competent evidence says otherwise. The register should support better planning, clearer contractor briefing and safer decision-making. It should never be used as permission for unplanned roof access.
A fragile roof risk register is a record of known and suspected fragile roof areas, access restrictions, evidence, actions and review dates. It helps facilities managers plan roof work more safely before maintenance, cleaning, inspection or repair tasks are arranged.
No. The register does not prove roof safety. It records available information and highlights uncertainty. If the roof condition is unknown, rooflights are present or fragile materials are suspected, a professional survey may be needed before work proceeds.
Record rooflights, older sheet materials, asbestos cement information, corroded panels, patched areas, gutters, access points, plant areas, previous repairs, survey findings and any roof zone where the condition is unknown or restricted.
The register is usually owned by the dutyholder, facilities manager, property manager or site management team. Contractors can provide useful evidence, but the building owner or responsible management team should keep the record current.
Review the register after roof surveys, maintenance work, repairs, storm damage, leak investigations, gutter clearance, refurbishment, plant installation or any change that may affect roof access or fragility risk.
No. The register should not be used as permission for roof access. If access is needed, the work must be planned by competent people with suitable controls. Unknown or suspected fragile areas should be escalated before anyone accesses the roof.
