What is a computerized roof management program?

It is a maintained record of an owner's roofs: an inventory of each roof area, its construction, its documented condition, and the full history of repairs, leaks and alterations. Held in one consistent format, the record supports maintenance planning, repair-or-replace decisions and multi-year capital budgets rather than reactive, leak-driven spending.

How is this different from simply inspecting the roofs each year?

An inspection produces a snapshot. A management program keeps those snapshots, ties them to numbered roof areas on a plan, and adds every repair, warranty claim and equipment tie-in. Over time the accumulated record shows rates of deterioration and recurring problem locations, which a single inspection report cannot reveal.

How does the data support a repair-versus-replace decision?

For each roof area the record shows age, construction, extent and type of deterioration, whether moisture has entered the system, deck condition and prior repair history. Continuing maintenance cost can then be weighed against replacement cost and the consequence of an interior failure, with the reasoning documented for review.

Does Inspec perform the roof repairs identified by the program?

No. Inspec is a consulting engineering and architecture firm. We inspect, test, investigate, document conditions, prepare repair and replacement designs, and observe construction. The work itself is carried out by contractors, which keeps our assessment of what a roof needs independent of who is paid to do it.

Computerized Roof Management: Turning Data Into Savings

Article by Fred King

Read the full article (PDF)

Background on this topic from Inspec

Most roof money is spent reactively

On a portfolio of any size, roof spending tends to follow leaks. A tenant reports water at a ceiling tile, a contractor is called, a patch is made, an invoice is paid, and the file closes. Repeat that across a dozen buildings over a decade and the owner has spent a substantial sum without ever knowing which roofs are near the end of their service life, which are failing early, or which repairs were made twice in the same place.

A computerized roof management program exists to break that cycle. It is not software for its own sake. It is a structured record of what is on each roof, what condition it is in, what has been done to it and what it is likely to need next — held in one place, in a consistent format, so that decisions can be made from evidence rather than from the most recent complaint.

What the program actually holds

Inventory

Each roof area is identified and measured: membrane or covering type, deck type, insulation, attachment, slope, drainage, flashing conditions, penetrations, rooftop equipment and access. Roof areas are numbered and drawn on a plan so that everyone — owner, facility staff, engineer, bidding contractor — refers to the same area by the same name.

Condition

Condition is recorded from a physical roof inspection, not from an office. Defects are located on the plan, described, photographed and rated. The difference between a blister that should be watched and a wet insulation area that is spreading is the difference between a maintenance line item and a capital project, and only a documented walk distinguishes them.

History

Every repair, warranty claim, leak call, tie-in for new equipment and re-roof is logged against the roof area it affected. History is what turns a database into an argument: a roof with four repairs at the same curb in three years has a design or workmanship problem, not a maintenance problem.

Where the savings come from

Savings in roof management rarely come from buying cheaper work. They come from four places.

Repairs made before water reaches the deck. A membrane defect corrected while the insulation is dry is a maintenance cost. The same defect found after two winters may mean tear-off, deck repair, interior finishes and business disruption.
Re-roofing at the right time. Replacing a roof that still has serviceable years left wastes the remaining life; running one past failure imports damage into the building below. A condition record makes the timing of replacement a judgement supported by evidence.
Scope written from data. Bids priced against a measured, documented scope are comparable to one another and carry fewer change orders than bids priced from a walk-through.
Bundled work. When several roofs across a portfolio are scheduled from one dataset, related areas can be combined into a single project rather than mobilized separately.

Repair, restore or replace

The value of a roof management program is that it converts an argument into a comparison. For each roof area, the record shows remaining service life, the extent and type of deterioration, whether moisture has entered the system, the deck condition and the history of prior work. Against that, the cost of continuing to maintain the roof can be weighed against the cost of replacing it and the consequences of an interior failure.

Where the data is ambiguous — widespread staining, a deck of uncertain condition, repeated leaks with no obvious source — the program identifies where further investigation is warranted rather than guessing. Moisture surveys, test cuts and forensic roof investigation are targeted at the areas the record has flagged.

A budget that survives review

Capital requests for roofing are often declined because they arrive as a number without a story. A managed roof program produces the story: this roof area, this size, this age, this condition, these documented defects, this recommended year, this consequence of deferral. When budgets are cut, the same record shows which deferrals are tolerable and which import risk into the following year.

Multi-year plans built this way also smooth spending. Rather than three roofs failing in the same budget cycle, replacements are sequenced across years according to condition and consequence.

Keeping it alive

The common failure of roof management programs is that the data ages. An inventory captured once and never updated becomes misleading within a few years, particularly on buildings where rooftop equipment changes. The program needs a recurring inspection cycle, a discipline for logging every repair and equipment tie-in, and a single owner of the record.

Inspec maintains this kind of data for owners through our building envelope management system and through customized facility asset management programs that extend the same approach across walls, windows and other enclosure assets. As consulting engineers and architects, we inspect, document and advise; the repair work itself is performed by contractors under a scope we help the owner define. To discuss setting up a program for your portfolio, contact us.