- 07961839260
A usable roof maintenance schedule is a service plan: it defines what to check, how often to check it, how to record findings, and when to escalate to competent professionals. This updated guide is written for UK industrial and public-sector estates teams who need an auditable, risk-based approach that protects the roof system, manages working-at-height risk, and supports warranties and procurement.
Your schedule should do three things: spot defects early, prevent avoidable deterioration (especially drainage-related), and create clear records that support safe decisions and contractor accountability. Everything else-tables, checklists and frequencies-exists to make those outcomes repeatable.
Roof maintenance involves work at height and must be planned and managed as a high-risk activity. Your schedule should prioritise avoiding roof access where possible and using competent contractors with safe systems of work when access is necessary.
HSE guidance and the Work at Height Regulations place duties on employers and those who control work at height to ensure work is planned, supervised and carried out by competent people, and to avoid work at height where it is reasonably practicable to do the job another way. Use HSE guidance as your baseline reference: Working at height: a brief guide (HSE), Assessing all work at height (HSE), and Roof work (HSE).
HSE advises that roofs should be treated as fragile until a competent person confirms they are non-fragile. Effective precautions are required for any work on or near fragile surfaces, even for short-duration tasks. For practical guidance, see Fragile surfaces (HSE) and Roof work (HSE).
You cannot schedule effectively until you know what you are maintaining. Start by confirming roof type, waterproofing system, drainage arrangement, and high-risk interfaces (plant, rooflights, parapets, penetrations).
Use a risk-based cadence: routine monitoring to catch early warning signs, plus periodic competent roof inspections to assess the waterproofing system and interfaces. Add event-driven inspections after anything that changes risk.
| Activity level | Who | Typical frequency (starting point) | What it covers | Notes |
| Routine monitoring (no roof access where possible) | Facilities/site team | Monthly and after heavy rainfall (adjust to site risk) | Internal leak indicators, ceiling voids, plant alarms, visible gutter/outlet issues from safe vantage points | Do not create an unsafe access routine. Record issues and escalate. |
| Competent roof inspection | Competent roofing contractor or surveyor | At least twice yearly is a common baseline; increase for high-risk roofs | System condition, seams/joints, flashings, penetrations, drainage, rooflights, edge protection interfaces | Use a method statement and safe system of work aligned to HSE guidance. |
| Post-event inspection | Competent person (contractor/surveyor) | After severe wind, hail, snow loading, flooding, or any rooftop works | Damage, displaced components, blocked outlets, punctures, loosened flashings, compromised rooflights | Define what counts as a “trigger” for your location and site exposure. |
| Diagnostic investigation | Surveyor/roofing specialist | As indicated by defects or recurring leaks | Moisture/condensation diagnosis, drainage performance issues, intrusive checks where justified | Specify deliverables and reinstatement requirements up front. |
A standard checklist improves quality and comparability between visits. Split your checklist into “internal early warning” and “external system condition” so you do not default to unsafe roof access for routine monitoring.
Most avoidable roof deterioration starts with poor drainage: blocked outlets, inadequate falls, or localised ponding. Your schedule should treat drainage as a first-order maintenance item, not an afterthought.
Falls and drainage design are technical design matters and should be checked by competent designers/surveyors when problems recur. Industry guidance notes reference BS EN 12056-3 for roof drainage design and discuss falls/ponding in relation to flat roof standards. Useful signposts include HR Wallingford’s roof drainage manual (SR 620) and LRWA Guidance Note No. 7 (Flat Roof Falls).
Note on standards governance: editions change. For example, BSI lists BS 6229:2018 as withdrawn. Use BSI’s BS 6229 status page to confirm current status and always reference the current edition in specifications.
Some technical manuals and warranty standards include specific requirements for secondary outlets/overflows on roofs boxed in by upstands/parapets. Treat these as specification checks rather than universal rules. As an example reference, see LABC Warranty Technical Manual – Drainage (Section 5).
Leaks most often start at interfaces-upstands, parapets, rooflights, plant bases, and service penetrations – so your schedule must focus attention there.
Not all “damp” is rainwater ingress. If you see recurring moisture without clear external defects, treat it as a moisture-management problem and investigate before repeating patch repairs.
Escalate to a competent surveyor/roofing specialist to review build-up, ventilation and vapour control assumptions. As a standards signpost for moisture management, see the reference to BS 5250 on LRWA’s British standards list. Your schedule should include a rule: “Recurring moisture without clear external defects triggers diagnostic investigation.”
Define escalation rules in writing so that defects are handled consistently and safely. If you rely on judgment alone, urgent issues can be normalised, and low-risk issues can trigger unnecessary disruption.
| Rating | Definition | Action | Evidence to record |
| Good | No defect observed; normal ageing only | Continue scheduled inspections | Photos of representative areas; note any watch items |
| Fair | Defect present but stable; no active ingress | Plan repair and monitor | Defect location, dimensions (approx.), photos, recommended repair type |
| Poor | Active ingress or high likelihood of rapid deterioration | Urgent competent attendance; restrict access if required | Immediate risk notes, affected areas, temporary protection (if safe), and escalation record |
Your schedule should be “audit-ready”: each inspection produces a consistent record, and each repair closes out with evidence. This protects you operationally and helps when warranties, insurers, or stakeholders ask what was done and when.
| Field | What to capture | Why it matters |
| Site/roof ID/zone | Named roof, plan reference, and zone grid | Enables repeatability and defect tracking |
| Date/weather / recent events | Rain/wind conditions; any recent storms or works | Improves diagnosis and prioritisation |
| Inspector and competence | Name, company, role; evidence of competence (as per contract) | Supports governance and contractor accountability |
| Access method and controls | How access was achieved; key controls in place | Demonstrates a safe system of work |
| Checklist results | Drainage, penetrations, seams, rooflights, edges | Consistent condition assessment |
| Defects and severity | Location, description, rating (Good/Fair/Poor), photos | Enables prioritised action |
| Actions and close-out | Repair recommendation; timescale; follow-up date; completion evidence | Prevents repeat issues and “open loops” |
Add a rule to your schedule: “No unapproved penetrations.” Require any contractor proposing new rooftop works to submit details and update your roof plan and penetration register on completion.
If you are procuring a contractor, a simple specification table prevents ambiguity and makes quotations comparable. Use the template below as a starting point and edit it to match your roof types, constraints and risk profile.
| Item | What to specify | Deliverable | Acceptance / QA check |
| Planned inspection visits | Number of visits per year, which roofs/zones included; trigger-event attendance process | Inspection report per visit | Report includes photos, defect locations, severity ratings, and recommendations |
| Drainage clearance | Which outlets/gutters are included, the disposal method, and any access restrictions | Before/after photos and notes | Evidence that outlets and overflows are clear and discharge routes are unobstructed |
| Minor repairs (if included) | Define what counts as “minor” (materials, labour limit, exclusions) | Repair record and close-out | Repair photographed; location added to defect register; any follow-up specified |
| Safe system of work | Method statement, risk assessment, rescue planning approach, exclusion zones, access/edge protection | RAMS submitted and agreed | Matches site rules; aligns to HSE guidance and work-at-height hierarchy |
| Competence and supervision | Named supervisor/lead; competence evidence; training expectations | Competence pack | Accepted before works start; kept on file |
| Reporting and asset data | Report format, photo standards, roof plan mark-up, defect register updates | Digital records pack | Records are searchable and usable by the client |
| Standards and references | State which standards/guidance are used as references (check current editions) | Compliance statement | References are current; any assumptions are declared |
To procure roof maintenance properly, gather the right information first, request comparable proposals, and lock in reporting and close-out requirements in your contract.
How often should industrial roofs be inspected?
A common baseline is two competent inspections per year plus event-driven checks after storms, leaks or rooftop works. Increase frequency for high-risk roofs (complex drainage, high foot traffic, known defects, or sensitive operations).
What should I do if I see ponding water on a flat roof?
Record the location and persistence (e.g., still present after a reasonable drying period) and check drainage components. Repeated ponding should trigger a competent review of drainage performance and local falls; avoid improvised “quick fixes”.
Can our team do roof checks in-house?
Yes for lower-risk monitoring (internal/ground-based checks and reporting), but roof access and any work near edges, rooflights, or potentially fragile areas should be planned and done by competent people under a safe system of work.
How do I stop “unapproved penetrations” from causing repeat leaks?
Introduce a penetration control rule: no new rooftop fixings without approval, a method statement, and an as-built update. Maintain a penetration register and require photo evidence for every change.
Do green roofs need different maintenance?
Yes. They require vegetation and drainage-layer care as well as protection of the waterproofing system. Follow system-specific guidance such as the GRO Code. For BioSolar roofs, GRO guidance includes a minimum maintenance expectation – see the GRO BioSolar Best Practice Design Guide.
What should I ask for in a maintenance quotation?
Ask for a clear scope, planned visit schedule, safe access approach, sample reporting, competence evidence, response arrangements, and a transparent process for additional works and close-out evidence.
Where can I find authoritative safety guidance for roof work?
Use HSE resources as your starting point, including Roof work, Fragile surfaces, and Assessing all work at height.
