Start with the asset decision, not a fixed visit interval
A maintenance plan should answer which roofs need attention, what should be monitored, where repair planning starts and what evidence is missing. Define buildings, planning period and decision-maker before choosing an inspection pattern. A standard interval without condition or consequence can misdirect effort.
Record current concerns, critical areas, known leaks and planned building changes. State whether the output supports facilities work, budgeting, a repair programme or asset decisions. Inspection scope and frequency can then reflect the assets rather than a universal promise.
Create a roof register that people can keep using
Give every building and roof zone a stable reference. Record the known covering, evidenced age, drainage, rooflights, plant, access, previous repairs and drawings. Add warranty or guarantee conditions only from current documents.
Keep unknown fields visible. Link photographs, reports and work orders to the same zone and date. Distinguish current evidence from superseded information so future users know what was observed, reported by others or still needs checking.
Set inspection priorities from condition and consequence
Consider both deterioration and consequence. Repeated water entry, vulnerable rooms, loose materials, blocked drainage, ageing details, frequent access and hard-to-reach areas may need different attention. The organisation should identify critical operations and seasonal constraints.
Use that context to propose inspection scope and order. Some zones need defect investigation; others need a condition baseline or monitoring. A record review can identify gaps but is not a current roof inspection.
Separate housekeeping, monitored defects and repair scope
A clear plan separates facilities observations from roofing work. Debris near outlets, vegetation, unsecured items, surface damage, open joints and staining may be recorded, but action depends on access controls, roof system and authorisation. Staff should not step onto roofs for a checklist.
Mark each item for monitoring, authorised housekeeping, investigation or candidate repair. Record areas not viewed. This prevents minor observations becoming unapproved instructions and recurring defects disappearing into a generic recheck note.
Prioritise by urgency, impact and dependency
Explain every priority. Separate immediate building-management concerns, short-term investigation, planned repair and renewal without unsupported response times. Include affected use, evidence, risk of wider damage, access lead-in and dependencies.
A drainage survey may precede membrane work, shared access may serve several repairs, or plant changes may alter details. Group related actions while retaining zone records and marking items provisional until opening-up or closer assessment.
Turn condition findings into repair and budget packages
Group work by roof area, defect type, access arrangement and sensible sequence. A package should state observed quantities, assumptions, exclusions, further investigation and the outcome it is intended to achieve. Separate confirmed scope from provisional items so procurement can compare returns without pretending concealed conditions are known.
Use priorities to build planning scenarios rather than a single unexplained total. One scenario may address active defects and investigation gaps; another may combine access-dependent work or planned renewal. Prices and programme availability require a specific enquiry and evidence review, so the maintenance record should organise decisions without presenting estimates or dates that have not been supplied.
Report change and close the loop after approved work
Define the completion evidence before a repair is instructed. Useful records can include the original zone and defect reference, approved scope, dated photographs where appropriate, variations, inaccessible details, completion status and future observations. Required product, maintenance or warranty information should be listed and confirmed for the particular package.
Update the roof register after technical and client review rather than simply marking the work order closed. Preserve unresolved items, record any changed roof build-up or access route and set the basis for the next review. This makes later leakage or deterioration easier to compare with what was actually known at handover.
Prepare a planned maintenance enquiry
Send the asset list, building uses, roof-zone references, known systems, safe photographs, leak and repair history, access information and available reports. Add critical operational areas, the planning horizon, procurement route and whether the organisation needs a condition baseline, prioritised actions, repair packages or updated asset records.
Identify the facilities contact who knows the history and the person who will approve priorities. Flag missing records and roofs that have not been accessed rather than estimating their condition. The enquiry can then establish what review or assessment is appropriate and what evidence, timing and access still need confirmation.
