Build a Roof Condition File That Survives Staff Changes

Use one location system

Choose a repeatable way to identify roof areas. Aerial images, building elevations, roof-plane letters, unit numbers, and fixed features can all help when used consistently. Save a clean base image, then mark incident and repair locations on copies. Do not rely only on “over the office” or another description that may change.

Give each incident a date and short identifier. Link invoices and photos to that identifier so a new manager can follow the sequence without searching several email chains.

Separate observations, diagnoses, and actions

Use three fields. Observations state what someone saw. Diagnosis records the contractor’s explanation and any limits. Actions list temporary measures, opening, repair, or monitoring actually performed. Keeping these fields separate reduces the chance that an early guess becomes permanent property history.

For hidden conditions, preserve photographs taken before cover-up and the related approval. If the scope changed, keep both the original and revised versions rather than replacing the earlier record.

Keep a current roof map

After each repair, mark the completed boundary and date. Add nearby conditions that were reported but excluded. Note roof-mounted equipment or other trade work when it affects future coordination, without assigning blame unless the record supports it.

Review the file before authorizing another repair. The map may reveal repeated work at one transition, unrelated events on different planes, or missing closeout evidence. It does not replace inspection, but it gives the next contractor a stronger starting point and helps the owner ask precise questions.

• Can a new manager locate the exact area?
• Are facts separated from conclusions?
• Is every scope revision preserved?
• Does the roof map show completed boundaries?

Use a closeout index

Add one index page listing the incident, approved scope, changes, photos, invoice, and open monitoring item. File names should include the date and location identifier. This small step matters when records move between managers or storage systems.

Review the index after new equipment or other roof-adjacent work. Add the contractor, date, and location even when no leak occurred, because that history can clarify a later condition without relying on memory. Keep superseded maps labeled instead of deleting them.