Technical library

Professional Roofing "ROOFER Program Is Introduced to the Private Sector"

The ROOFER program gave private owners a roof condition index. How distress type, severity and density become a 0-100 score, and what that score cannot decide.

Article by Dick Phillips

Read the full article (PDF)

Background on this topic from Inspec

Where the ROOFER program came from

ROOFER was developed by the U.S. Army Construction Engineering Research Laboratory as an engineered management system for low-slope roofing. The problem it was built to solve is a familiar one: an organization holds far more roof area than it can fund in any single year, the roofs are of different ages and assemblies, and the people who inspect them do not all describe what they see the same way. Without a common measure, the roof that gets money is often the one whose occupant complained loudest.

When the approach moved into the private sector, it gave building owners something they had generally lacked — a repeatable, numeric description of roof condition that does not change depending on who walked the roof that morning.

What a roof condition index actually measures

A condition index is a summary of observed distress. It is not an opinion about remaining life, and it is not a cost estimate. Indexes are reported on a scale of 0 to 100, where a high score means little distress was found and a low score means a great deal was found.

Distress type, severity and density

The field work is a structured distress survey rather than a walk-and-narrate. The inspector identifies each distress by type — blistering, splitting, ridging, open laps, surfacing loss, ponding, deteriorated flashing terminations and so on — then records how severe each occurrence is and how much of the sampled area it affects. Type, severity and extent are converted into deductions from a perfect score. Scattered, minor defects cost a roof a few points; the same defect type, severe and widespread, costs it many. Because the deductions are defined in advance, two qualified inspectors surveying the same roof should arrive at broadly the same number.

Separate indexes for membrane and flashing

Scoring the field membrane and the flashing system independently is one of the more useful habits the method encourages. A roof whose field sheet is sound but whose base flashings, curbs, pitch pockets and drain sumps are failing tells a very different capital story than a roof with the opposite profile, and a single blended number hides that difference at exactly the moment an owner is deciding how much to spend.

Sampling and consistency

Large roofs are divided into sections that share an assembly, an age and a drainage pattern, and each section is scored on its own. This is what makes the output useful across a portfolio: a 1970s built-up section over a wing that was added later does not get averaged into the newer membrane surrounding it. Section boundaries drawn carelessly are the single most common way an indexing program loses its value, because every later comparison inherits the error.

Comparing roofs that are not alike

The practical value of indexing shows up when an owner has to choose between assets that have nothing in common. A modified bitumen roof on a warehouse and a single-ply roof on an office building cannot be compared by age, by warranty status or by how bad the last leak was. Scored on the same distress framework, they can at least be ranked against each other and against the money available.

The same logic works for a single building. One score means little in isolation, but a section re-surveyed on a set cycle produces a trend line, and a trend line is what tells an owner whether a roof is aging steadily or falling off a cliff. Two sections with the same score and different slopes on the trend line do not deserve the same place in the budget.

Turning scores into a budget conversation

Scores are most useful when they change the shape of the discussion rather than settle it. Sections in the upper range typically justify housekeeping and preventive maintenance. Mid-range sections are where repair spending buys the most time, because the distress is real but the assembly is still intact. Low-scoring sections are candidates for replacement, and grouping several of them into one procurement is usually easier to fund than a string of emergency repairs spread across a fiscal year.

A defensible capital plan also needs the things an index does not contain: what is under the membrane, what the deck is doing, and what the building is used for. That is where a commercial roof inspection and the engineering judgment behind it earn their place.

The limits of a number

A visual index scores what can be seen from the surface. It does not identify wet insulation, which requires moisture detection services and their own interpretation. It does not evaluate wind uplift resistance, attachment, code-driven upgrades or the structural capacity of the deck. It does not tell you where water is entering the building — a low score and an active leak are related but not the same question, and tracing a leak to its source is a separate investigation.

Used as the only input, an index can also encourage a false precision. A roof that scores well can still be the wrong roof for the occupancy below it, and a roof that scores poorly may be worth keeping for a few more seasons if the owner is about to sell or reprogram the space. Where a failure has already caused damage or a dispute, a forensic roof investigation answers questions no scoring system was designed to answer.

Building indexing into an ongoing program

Indexing pays off when it is repeated on a schedule and the results are kept somewhere they can be compared year over year. That is the idea behind a building envelope management system and behind customized facility asset management programs, both of which treat condition data as an asset rather than as a one-time deliverable. Owners who want the same discipline applied beyond the roof line can extend it through facility condition assessments, and owners who need help interpreting what the scores are pointing at can start with roof consulting.

One caution worth stating plainly: the score belongs to the survey that produced it. Changing inspectors, changing section boundaries or changing the sampling approach mid-program breaks the comparison the program exists to make, and rebuilding that history takes longer than getting the first survey right.

Read the full article (PDF)

Common questions

What does the ROOFER program actually produce?

It produces numeric condition indexes derived from a structured field survey of roof distresses. Membrane, flashing and insulation condition are evaluated as separate factors on a 0 to 100 scale, so an owner can compare roofs across a portfolio consistently and see which assemblies are deteriorating fastest rather than relying on narrative impressions.

Is a condition index the same as a roof inspection report?

No. The index is a scoring output used for ranking and budgeting. An inspection or forensic report explains causes, documents specific defects, evaluates the deck and insulation, and recommends corrective work. Owners generally need both: the index to prioritize the portfolio, and detailed investigation of the roofs the index flags.

Why score membrane and flashing separately?

They fail differently. Field membrane can be serviceable while base flashings, curbs, drains and penetrations are deteriorated, or the reverse. Scoring them together hides that distinction and can push an owner toward full replacement when targeted flashing repair would extend service life for several more budget cycles.

Can this approach apply to walls and waterproofing too?

Yes. The underlying idea — consistent field data, stored over time, driving capital planning instead of reactive spending — applies to exterior walls, windows, plazas and below-grade waterproofing. Inspec applies that structure through its building envelope management and facility asset management work for owners managing multiple buildings.

Who developed the ROOFER program, and why?

It came out of the U.S. Army Construction Engineering Research Laboratory, which needed a consistent way for installation engineers to manage very large inventories of low-slope roofing on constrained budgets. The goal was to remove personality and complaint volume from funding decisions and replace them with a measure that different inspectors could reproduce on the same roof.

How does a field observation become a number?

The inspector records each distress by type, rates its severity, and notes how much of the sampled area it covers. Those three variables are converted into point deductions from a perfect score using predetermined values, so widespread severe distress costs far more than isolated minor defects. What remains is the index, reported on a 0 to 100 scale.

Is there a score that automatically means replace?

No. An index summarizes visible distress. It knows nothing about your holding period, the tenant below, deck condition, trapped moisture, or code upgrades that replacement would trigger. Low scores tell you where to concentrate attention and engineering time. The repair-versus-replace decision still rests on judgment about the assembly, the building and the owner's plans.

What has to be in place before the first survey?

A usable roof inventory: section boundaries, areas, assembly types where known, drainage layout and safe access. Original drawings, previous repair records and warranty documents help the inspector interpret what is found. Without defined sections, scores get averaged across dissimilar roof areas and lose most of the value that indexing is supposed to provide.