Build a Commercial Roof Asset Register
A commercial roof asset register should tell a new manager which roof section they are discussing, what is known about its construction and where to find the evidence. Build it around stable section identifiers rather than one condition score for the whole property.
Begin with a map that survives staff changes
Label each distinct roof area on an existing plan or suitable overhead image: Building A, Area A1, for example. Use boundaries that people can recognize, such as a change in elevation or an expansion joint. Ask the roofing professional to confirm the boundaries; an image alone may not reveal separate assemblies.
Keep the identifier when the roof is replaced. Add a new installation record under that identifier instead of renaming the area “new roof.” Otherwise, older leak reports become difficult to locate.
For an Austin property with several additions, a single street address is only the parent record. The register should distinguish the addition from the original building without assuming they share an installation date or warranty.
Use evidence fields, not guessed answers
| Field | Useful entry | When the information is missing |
|---|---|---|
| Roof area | A1, marked on the attached plan | Ask for boundary confirmation |
| System | Manufacturer and product from installation documents | Record “unconfirmed,” not a visual guess |
| Installation | Date and source invoice or closeout record | Separate an owner's estimate from a documented date |
| Warranty | Issued document and identifier | Record whether it has been located |
| Access | Authorized coordinator and access arrangement | Restrict keys and codes to the operational system |
| Condition evidence | Latest report, date and inspected areas | Identify inaccessible sections |
Johns Manville recommends keeping roof activity and inspection records. The table above is an organizational method, not a manufacturer-prescribed form or a technical rating system.
Keep condition outside the identity fields
“Area A1 is TPO” describes a system, if verified. “Open seam observed at A1 north curb” describes a dated finding. “Replace A1” is a proposed decision. Store these as separate records so a recommendation cannot overwrite the observation that prompted it.
Link photographs to a report and location. Do not name every photograph “roof damage.” Preserve the original file and its date, and note whether a later image was taken from a different angle. A missing photograph means evidence is missing, not that a detail is sound.
Make the register useful at the next service visit
Give the contractor the section plan, relevant history and reported problem. Ask the return report to use the same identifiers. After work, attach the completed scope and identify outstanding items; an invoice alone may not explain which section was treated.
Review the register when ownership, management or equipment changes. Keep passwords, alarm details and tenant information out of copies sent broadly for pricing. To establish a condition baseline for the register, discuss a scoped commercial roof inspection; ongoing maintenance records can then build on it.