The third leak call in a week, from three different buildings, can mean the roofs are being managed one phone call at a time. Each call gets a patch, each patch gets an invoice and nobody sees that two of the three buildings have the same drain problem and the third has run out of life. A multi-site program replaces that pattern with one set of records, one calendar and one ranking, so an owner or manager with many roofs can see them together. For portfolios in West Jordan, UT and across the Salt Lake Valley, where snow melt and freezing nights stress every roof on roughly the same schedule, a shared program makes seasonal work easier to plan and easier to afford.
What failed first: the baseline survey
The program starts with a baseline: a hands-on survey of each roof across the portfolio, using one format. For each roof section we record system, approximate age, drainage, penetrations, repair history and visible condition, and we rate it. The same rating scale runs across all buildings, so a warehouse and an office can be compared directly.
Surveys are scheduled geographically, to keep travel down and to give the owner a complete picture in a short window. Where records exist, we reconcile them against the roof. Where they do not, we start the file. The result is a ranked list of every roof section, with photographs, from the one that needs work first to the one that can wait.
Condition findings are grouped by cause as well as by building. If four roofs show lifted edge metal and two show ponding at the same kind of drain, the program treats those as patterns and prices them as batches. A pattern also tells us something about how the roofs were built or maintained, and that shapes what the owner should specify the next time a roof is replaced.
Repair boundary: spending in order of risk
With a ranked list, the budget conversation changes. Instead of asking what each building needs, the owner asks how much of the list the budget can reach this year. Roofs rated fix-now get repairs. Roofs rated plan get a place in a multi-year schedule, supported by a roof capital plan. Roofs rated watch get a scheduled visit and nothing more until evidence changes.
Bundling pays in practical ways. Crews mobilize once for several small repairs in the same area, material is bought together and follow-up visits are combined. The savings come from fewer trips and cleaner scheduling, and the program reports them in plain terms.
Reporting stays simple. Each quarter, the owner receives a one-page status: roofs repaired, roofs watched, items deferred and the reason for each deferral. A manager can forward it to an owner or a lender without translating anything. When a deferred item fails, the report shows that it was on the list and what the risk was, which keeps the conversation factual.
Seasonal timing: one calendar for every roof
Winter snow and freeze-thaw periods in the Salt Lake Valley set the rhythm. Salt Lake City airport normals give a regional picture, so the program does not claim identical conditions at every building, since elevation and exposure change across the valley. What it does is put the same checks on every roof at the same times: a spring walk after melt, a fall cleanup before the first storm and an after-event check following heavy snow or wind.
Each visit produces a dated entry and photographs for every building. Over a few years, the entries show which buildings keep the same trouble spots and which roofs hold up, and that history guides where capital money goes.
Weather-driven triggers sit alongside the calendar. A heavy snow, a stretch of high wind or a rapid melt calls for a quick drive-by or walk of the roofs rated most vulnerable, not the whole portfolio. The call list is built from the ranking, which means attention goes where the evidence says it is needed.
Roof-walk notes: access, tenants and vendors
Portfolio work lives or dies on coordination. We keep a contact list for every building: who holds roof keys, how access works, which tenants must be notified and which trades service rooftop equipment. Visits are scheduled with property managers, and tenants receive notice. When another trade opens a roof, the program calls for a roof walk after they leave, because an unflashed curb or a crushed drain strainer is a leak in waiting.
An emergency roof repair call fits into the program too. The crew that responds knows the building from the file, and the temporary work is logged for the permanent fix. Owners get one record of both.
Vendor coordination extends to the roof's other trades. Where a mechanical contractor changes a unit, an electrician runs conduit or a telecom firm adds an antenna, the program asks for notice and schedules a follow-up walk. The cost of that walk is small beside the cost of a leak at an unflashed curb. Over time, trades learn that the roof has a file and a gatekeeper, and the number of surprise penetrations falls.
Mixed portfolios in West Jordan and nearby
Portfolios in the area can include a range of building types. Warehouse roofing, shopping center roofing and school or office roofs each have their own drainage patterns, equipment loads and tenant constraints. The general plan in West Jordan backs regional commercial, service, office and mixed-use building and sets aside planned station areas, including Gardner Village and Old Bingham Highway, so owners holding property near them should expect the surroundings to change over time.
The program handles that by recording what each building needs and updating the file as conditions change. A property that moves from hold to sale shifts from a long-life plan to a clean-record plan, and the file shows the change.
The city's economic development office lists Danone, Oracle, PayPal, Amazon, Boeing and Sysco among the companies doing business in West Jordan, so a portfolio manager here may serve occupiers with very different operations. Each tenant's operations set its own constraints on roof work, from dock hours to quiet periods, and the program records them building by building.
Next check: how to begin
To begin, send a building list with addresses, approximate roof areas if known, repair invoices and any warranty papers. Tell us where water appears, when it appears and how roof access works at each site. We will schedule the baseline walks, deliver the ranked file and propose a calendar. For a single building, roof asset management uses the same records, and for a first look in West Jordan we can start with the buildings that cause the most calls.
Commercial Roofing Questions
How many buildings make a program worthwhile?
Three or four roofs are enough for shared records and a ranked list to pay off. Larger portfolios gain more from combined scheduling.
Can the program include buildings in different cities?
Yes, within the valley. We group visits by area to keep travel efficient and use the same format for every building.
Who decides which roofs get money first?
You do. The ranked list shows condition, cost ranges and what waiting risks, and the owner chooses what the budget reaches.
What happens when a leak call comes between visits?
We respond using the file, make the repair or temporary fix and add the entry to the record so the next visit builds on it.
Does the program replace tenant reporting?
No. Tenant reports still matter. The program adds a way to compare them with the roof and spot patterns.
Send the building list and the leak history
Tell us where water appears, when it appears and how access works at each building. We will walk the roofs, build one ranked file and propose a seasonal calendar.