Direct Answer
Facility managers should document roof conditions in a CMMS or maintenance-backlog system as location-specific, dated, actionable asset records rather than as general notes such as “roof needs repair.” Each condition should identify exactly where the problem is, what component is affected, what was observed, how serious it is, what action is required, who owns the action, when it is due, and whether the issue has been verified as resolved.
The CMMS should function as the operational history of the roof. NRCA guidance recommends maintaining permanent roof records that include roof-section information, inspection findings, defects identified by location and type, maintenance requirements, and completed work orders with repair costs. NRCA also notes that these records can be maintained in an electronic database. :contentReference[oaicite:0]{index=0}
For a commercial portfolio, the basic structure should be:
| CMMS Field | What to Record |
|---|---|
| Building / Asset ID | Unique building and roof identifier |
| Roof Section | Specific roof area or section |
| Location | Grid reference, elevation, drain number, penetration, curb, or other precise landmark |
| Component | Membrane, flashing, drain, curb, seam, penetration, edge, insulation, etc. |
| Condition | Objective description of what was observed |
| Severity | Urgent, high, medium, low, or the facility’s defined priority scale |
| Operational Impact | Whether the condition threatens occupants, production, inventory, equipment, or building operations |
| Photographs | Before-condition and completion photographs |
| Recommended Action | Repair, monitor, investigate, maintain, assess, or replace |
| Work Order | Assigned technician/contractor, status, due date, and completion date |
| Cost | Estimated and actual repair cost |
| Verification | Evidence that the corrective action was completed and the condition resolved |
Who This Applies To
This approach applies to facility managers, property managers, building engineers, maintenance departments, asset managers, and operations teams responsible for commercial roof portfolios.
Not for: replacing a formal roof condition assessment or engineering investigation when the condition requires specialized testing. The CMMS should preserve and manage the information; it should not turn an ordinary maintenance technician into a roof diagnostician.
1. Create the Roof as an Asset, Not Just a Maintenance Task
The roof should have a permanent asset record in the CMMS.
At minimum, capture:
- Building name and asset ID
- Roof section ID
- Roof system
- Manufacturer
- Installation date, if known
- Approximate roof area
- Warranty information
- Roof drawings or plan reference
- Roof contractor
- Inspection history
- Repair history
For larger properties, do not create only one asset called “Building Roof.” Divide the roof into manageable sections that can be inspected, maintained, prioritized, and budgeted independently.
NRCA’s planned-maintenance guidance specifically describes developing roof-section plans and maintaining permanent records for each roof section. :contentReference[oaicite:1]{index=1}
2. Record the Exact Location of Every Defect
“Leak on roof” is not an adequate CMMS entry.
A useful record should allow another technician or contractor to find the condition without relying on the person who originally entered it.
For example:
| Weak Entry | Useful CMMS Entry |
|---|---|
| Roof leaking | Building A / Roof Section R-03 / west mechanical area / approximately 15 ft south of RTU-4 |
| Damaged flashing | Roof Section R-02 / north parapet / approximately 20 ft east of roof access door / base flashing separated at termination |
| Drain problem | Roof Section R-05 / Drain D-05-03 / strainer obstructed by debris and drainage restricted |
Attach a photograph and, where useful, mark the location on the roof plan.
3. Separate the Condition From the Recommended Action
A CMMS record should distinguish between what was observed and what should be done.
For example:
- Observation: Open seam observed approximately 8 inches along the membrane seam.
- Risk: Potential water-entry point.
- Action: Evaluate and repair according to the applicable roof-system requirements.
- Status: Work order created.
This is better than entering “seam needs repair” because the original condition remains available for future comparison.
NRCA’s planned-maintenance material emphasizes that inspection reports should document findings and identify recommended corrective work rather than merely stating that something is wrong. :contentReference[oaicite:2]{index=2}
4. Use Consistent Condition Categories
The facility should establish a controlled vocabulary so that different inspectors describe similar conditions consistently.
For example:
| Category | Example Conditions |
|---|---|
| Membrane | Puncture, blister, split, open seam, deterioration, exposed reinforcement |
| Flashing | Loose, damaged, separated, deteriorated, improperly terminated |
| Penetration | Damaged boot, failed sealant, exposed opening, movement |
| Drainage | Blocked drain, damaged strainer, restricted flow, ponding observation |
| Edge | Damaged edge metal, loose components, deterioration |
| Equipment Interface | Damaged curb, flashing issue, rooftop-equipment interface concern |
| Access / Traffic | Membrane damage or inadequate protection associated with rooftop traffic |
The exact terminology should match the roof system and the inspection program. The important point is consistency.
5. Give Every Condition a Priority
Not every roof observation deserves the same response time.
A practical CMMS priority system could be:
| Priority | Meaning | Typical Management Response |
|---|---|---|
| P1 — Emergency | Active water intrusion or condition creating an immediate operational/property risk | Immediate response and temporary protection as appropriate |
| P2 — High | Defect with significant potential for near-term damage or operational disruption | Schedule prompt corrective action |
| P3 — Planned | Condition requiring repair or maintenance but not immediate intervention | Include in maintenance backlog |
| P4 — Monitor | Condition that should be observed during future inspections | Track and reassess at defined interval |
Facilities can use different names or numbers. The important requirement is that the priority criteria are defined and applied consistently.
6. Add Operational Consequence to the Record
A roof defect should not be prioritized only according to its physical appearance.
Ask what is located underneath it.
A small roof defect above a critical electrical room, manufacturing line, hospital area, pharmaceutical operation, data room, or high-value inventory area may deserve greater attention than a larger defect over a low-consequence space.
Add a field such as:
- Critical operational area: Yes / No
- Interior water intrusion: Yes / No
- Equipment exposure: Yes / No
- Inventory exposure: Yes / No
- Production impact: Yes / No
- Occupant impact: Yes / No
- Business continuity risk: Low / Medium / High
This turns the maintenance backlog into an operational decision tool rather than simply a list of defects.
7. Attach Photographs to the Individual Work Order
Photographs should be connected to the specific asset, inspection, and work order rather than stored in a general folder with filenames such as “roof1.jpg.”
A useful photo record should show:
- Overall location
- Specific defect
- Nearby identifying feature
- Condition before repair
- Repair in progress when appropriate
- Completed repair
Use consistent photo naming or CMMS metadata so that future inspectors can compare the same location over time.
8. Track the Condition Through Its Entire Lifecycle
The record should not disappear when the work order is closed.
A strong lifecycle is:
Observed → Documented → Prioritized → Assigned → Repaired → Verified → Closed → Reinspected
For example:
| Stage | CMMS Record |
|---|---|
| Inspection | Defect identified with location and photograph |
| Prioritization | P2 — High priority |
| Work order | Assigned to approved roofing contractor |
| Repair | Repair description and materials documented |
| Completion | Completion photographs and invoice attached |
| Verification | Condition checked and marked resolved |
| Future inspection | Location remains part of inspection history |
NRCA recommends maintaining completed work orders and repair costs as part of the permanent roof record. :contentReference[oaicite:3]{index=3}
9. Do Not Close a Roof Work Order Just Because the Contractor Left
The facility manager should distinguish between work completed and condition verified.
Before closing a significant roof work order, document:
- What work was performed
- Where it was performed
- Date completed
- Contractor
- Materials or repair method, where relevant
- Photographs
- Actual cost
- Whether the original symptom stopped
- Whether additional investigation is required
- Any follow-up inspection date
This is particularly important for recurring leaks. Closing three separate “leak repair” work orders without connecting them to the same roof location can hide a systemic problem.
10. Link Recurring Problems Instead of Creating Isolated Tickets
If the same location generates multiple work orders, the CMMS should make that history visible.
Track:
- Number of incidents
- Dates of incidents
- Previous repair methods
- Contractors involved
- Total repair cost
- Time between failures
- Whether the same symptom returned
A rising frequency of repairs can be an important management signal that the area deserves a deeper assessment rather than another isolated work order.
NRCA’s roof-management literature supports maintaining condition, maintenance, repair, and cost information so that roof-management decisions can be based on the accumulated record rather than isolated observations. :contentReference[oaicite:4]{index=4}
11. Connect the CMMS to the Roof Plan
For larger commercial buildings, the most useful system is not just a list of work orders. It is a map-based roof history.
Each roof section can have:
- Roof-section ID
- Inspection points
- Drains
- Roof penetrations
- HVAC equipment
- Previous leak locations
- Open work orders
- Completed repairs
- Photographs
- Condition rating
NRCA’s planned-maintenance guidance describes roof-section plans showing physical features and using those plans to identify defects by location and type. :contentReference[oaicite:5]{index=5}
12. Use the Backlog to Drive Capital Planning
The maintenance backlog should eventually answer management questions such as:
- Which roof sections have the most unresolved defects?
- Which locations generate recurring leaks?
- Where are repair costs increasing?
- Which roof sections have declining condition?
- Which problems can be handled through routine maintenance?
- Which require further assessment?
- Which should be considered for restoration or replacement planning?
- Which repairs have the greatest operational consequence?
This is where CMMS data becomes useful beyond day-to-day maintenance. NRCA’s roof-management resources describe using roof-section inventories, condition evaluation, maintenance needs, repair priorities, and permanent records to support management decisions. :contentReference[oaicite:6]{index=6}
Recommended CMMS Roof Condition Record
| Field | Example |
|---|---|
| Asset | BLDG-04-ROOF |
| Roof Section | R-04-03 |
| Inspection Date | 09/25/2026 |
| Location | Southwest corner, 12 ft east of RTU-7 |
| Component | Base flashing |
| Condition | Localized separation observed at flashing termination |
| Interior Evidence | No active interior leak observed |
| Operational Impact | Medium |
| Priority | P2 — High |
| Photo | Attached to work order |
| Recommended Action | Evaluate and perform appropriate corrective repair |
| Assigned To | Roofing contractor / responsible maintenance team |
| Due Date | Defined according to priority |
| Completion | Pending |
| Verification | Required after repair |
| Follow-Up | Next scheduled roof inspection |
Related Questions
- What Data Fields Should Be Tracked for Each Roof?
- What Roof Records Should a Property Manager Keep?
- How Do You Build a Roof Asset Inventory for a Portfolio?
- How Do You Prioritize Roofs Across a Portfolio With a Limited Budget?
- How Often Should a Roof Survey Be Updated?
- How Should Roof Data and History Be Transferred When Changing Vendors?
- What Reporting Should a Roofing Vendor Provide Each Month?
Sources
- NRCA — Planned Maintenance for Commercial Roofing
- NRCA — Roof Maintenance and Record-Keeping Guidance
- NRCA — ROOFER Engineered Roof Management System
- NRCA — Planned Maintenance for Commercial Roofing
- U.S. Government — Roof Management Programs
Last Reviewed
September 25, 2026
Important: CMMS fields and priority definitions should be adapted to the facility’s maintenance system, roof type, warranty requirements, operational risks, and inspection procedures. A CMMS record should document observed conditions and maintenance decisions; specialized roof testing or engineering evaluation may be necessary when the condition cannot be determined through routine inspection.
Related Resources
- Roof Data Fields Every Facility Team Should Track
- Building a Commercial Roof Asset Inventory
- Commercial Roof Maintenance Program for Multiple Buildings
- What Is a Roof Reserve Study?
Need to turn roof inspection findings into a usable maintenance and asset-management record? Contact ShieldLine Roofing to discuss your commercial roof documentation and maintenance program.
