With one building, you know the roof. You know where it leaked last spring, who fixed it and roughly how old it is. With ten or fifty buildings, nobody holds all of that in their head, and the information ends up spread across contractor emails, invoices, warranty folders and a spreadsheet that was last updated by someone who has since left.
Multi-building roof asset management is mostly about fixing that: one record per roof, kept current, that anyone responsible for the building can trust.
Start with an inventory, not a platform
Before choosing any tool, list every roof you're responsible for. For each building, break the roof into sections wherever the system, age or drainage changes. A warehouse with an original roof and a newer addition is two roof sections, not one.
For each section, write down what you can find quickly:
- Roof system and manufacturer (TPO, EPDM, modified bitumen, metal, built-up, and so on)
- Approximate area
- Installation year and the installing contractor
- Whether there's a manufacturer warranty, when it expires and what it requires
- The date of the last inspection and who did it
- Known problems right now
Gaps are fine. A blank "installation year" tells you exactly what to ask the next contractor who goes up there.
Make the record the place where work ends up
Most portfolio records go stale because updating them is an extra job. The fix is to make the record the place where inspections and repairs land by default. When a contractor finishes a service call, the report, photos and invoice should go against that roof section, not into someone's inbox.
That usually means agreeing with your contractors up front: every visit gets a short written note, dated photos of what was found and what was done, and the cost. If they won't provide that, it's worth asking why.
Rank roofs by risk, not just age
Age is the easiest number to sort by and one of the least useful on its own. A well-maintained older roof can be in better shape than a younger one that's never been inspected. A simple way to rank a portfolio is to look at four things together:
- Condition: what the last inspection found, recorded the same way each time.
- Water-tightness: any active or recurring leaks.
- Warranty: whether it's still valid and whether its inspection requirements are being met.
- What's underneath: a leak over a data room, a production line or a tenant's retail floor costs far more than one over storage.
The roofs that score badly on two or more of those are where your attention and budget should go first.
Keep warranty conditions in front of you
Manufacturer warranties often come with conditions: regular inspections by an approved contractor, prompt repair of defects, and keeping records of both. Missing them can give the manufacturer grounds to deny a claim. Across a portfolio, the only reliable way to keep up is to have each warranty's requirements and the next due date sitting in the same record as the roof.
Use the record to plan spending
Once every roof has a condition, an age and a repair history, a rough capital plan almost writes itself. Roofs that are near the end of their life and keep needing repairs go into the next two or three years. Roofs in good shape get maintenance only. The plan won't be perfect, but it replaces surprises with a list you can defend in a budget meeting.
Why the record should stay with the building
Facility managers change jobs, contractors change, and buildings get sold. If the roof history lives with a person or a contractor, it leaves with them. The record should belong to the building owner and move with the building, which is the idea behind the Roof Passport we're building at Roof Atlas.
For more on the tools side, see our guide to roof asset management software.