Direct Answer
Installation deficiencies are documented before they become roof failures through systematic field observation, photographs, location-specific notes, measurements, testing when required, and written comparison against the approved drawings, specifications, manufacturer requirements, and applicable installation standards. The goal is to identify nonconforming work while the affected area is still accessible and can be corrected without removing completed roofing.
IIBEC describes Registered Roof Observers (RROs) as quality-assurance professionals who monitor roof installation for compliance with project specifications, design intent, and industry standards. Their documentation commonly includes written observations, photographs, measurements, and material information. :contentReference[oaicite:0]{index=0}
Who This Applies To
- Commercial property owners and developers
- General contractors and construction managers
- Roofing contractors and roofing subcontractors
- Owner’s representatives
- Architects and building-envelope consultants
- Registered Roof Observers (RROs)
- Facility and property managers
- Owners of projects requiring manufacturer warranty inspections or third-party quality assurance
Not for: This FAQ explains how roofing installation deficiencies are identified and documented during construction. It is not primarily about diagnosing leaks in an existing roof or performing a post-failure forensic investigation.
1. Start With the Contract Documents
A deficiency cannot be documented effectively unless the observer knows what the installation is supposed to look like. Before construction begins, the project team should establish the applicable drawings, specifications, approved submittals, manufacturer requirements, details, testing requirements, and agreed quality-control procedures.
The observation record can then identify the specific requirement that is not being met instead of simply stating that an installation “looks wrong.” The CRCA/IIBEC/NRCA roofing submittal guidelines emphasize project-specific protocols extending through design, bidding, preconstruction, construction, and closeout. :contentReference[oaicite:1]{index=1}
2. Observe the Work While It Is Still Exposed
The most useful documentation happens while the relevant roof component can still be inspected.
For example, an observer may document:
- Substrate conditions before insulation or membrane installation
- Insulation type, thickness, layout, and attachment
- Fastener patterns or adhesive application
- Membrane seams and welds
- Flashing installation
- Perimeter and edge conditions
- Penetrations and rooftop equipment curbs
- Drainage details
- Temporary weather protection
- Material storage and handling
- Workmanship that does not conform to the approved details
This timing matters because a deficiency that is discovered after several layers have been covered may require destructive investigation or removal of completed work. IIBEC notes that continuous quality-assurance observation allows deficiencies to be identified and corrected as the assembly is installed. :contentReference[oaicite:2]{index=2}
3. Use Photographs to Establish Exactly What Was Observed
A useful photograph should do more than show that someone was on the roof. It should establish the condition, its location, and enough surrounding context to allow another person to understand the observation later.
A strong photographic record can include:
- A wide photograph showing the roof area
- A closer photograph showing the deficiency
- A measurement or scale where useful
- A nearby gridline, roof penetration, drain, parapet, or other landmark
- The date and project phase
- A photograph after correction when appropriate
IIBEC’s RRO information specifically identifies photography, written notes, and measurements as common components of daily observation reports. :contentReference[oaicite:3]{index=3}
4. Locate the Deficiency on a Roof Plan
Photos alone can become difficult to manage on a large commercial roof. The deficiency should therefore be tied to a recognizable location.
For example:
| Documentation | Example |
|---|---|
| Roof area | Roof Area B |
| Grid/location | Between Gridlines 4 and 5 |
| Landmark | 12 feet east of RTU-6 |
| Condition | Membrane seam not fully welded |
| Reference | Approved detail / manufacturer requirement |
| Action | Remove affected section and correct before covering |
IIBEC quality-assurance guidance recommends identifying deficient items on the roof and roof plan and using photographs to communicate the problem areas. :contentReference[oaicite:4]{index=4}
5. Describe the Deficiency in Objective Language
The report should describe what was actually observed rather than assigning blame.
Instead of writing:
“The roofing contractor installed the membrane incorrectly.”
A stronger observation would be:
“At Roof Area B, approximately 18 linear feet of membrane seam was observed without continuous weld coverage. Condition photographed and marked on the roof plan. Corrective action requested before the area is covered.”
This makes the record more useful to the contractor, owner, designer, and future reviewer because it separates the observed condition from assumptions about why it occurred.
6. Connect Each Deficiency to a Corrective Action
Documentation should not end with identifying the problem. The responsible project team should establish what must happen next.
A deficiency log can track:
- Deficiency number
- Date observed
- Roof area and exact location
- Description of condition
- Specification or drawing reference
- Photographs
- Responsible party
- Required corrective action
- Date correction was requested
- Date correction was completed
- Verification photographs
- Final disposition
This creates a traceable record rather than a collection of disconnected inspection photographs.
7. Verify the Correction Before Closing the Item
A deficiency should not automatically be considered resolved because the contractor says it was repaired. The observer or designated quality-assurance party should verify the correction when the project scope requires that verification.
For example, the record might show:
- Deficiency observed on September 14.
- Photographs taken and location identified.
- Corrective action issued to roofing contractor.
- Correction completed on September 15.
- Follow-up observation performed on September 15.
- Corrected condition photographed.
- Item marked closed.
This creates a useful chain from observation → notification → correction → verification → closeout.
8. Escalate Deficiencies That Could Affect Roof Performance
Not every visual imperfection has the same consequence. The project team should distinguish cosmetic conditions from deficiencies that can affect watertightness, wind resistance, durability, drainage, flashing performance, or warranty compliance.
Examples of conditions that may warrant prompt escalation include:
- Improperly welded or bonded membrane seams
- Missing or incorrectly installed fasteners
- Inadequate perimeter securement
- Improper flashing termination
- Unsealed penetrations
- Blocked or improperly configured drainage components
- Wet or damaged insulation that should not be incorporated into the assembly
- Unapproved materials or substitutions
- Installation performed contrary to manufacturer requirements
- Roof areas left inadequately protected from weather
For wind-sensitive assemblies, IIBEC notes that continuous quality-assurance observation can provide an opportunity to observe the entire assembly and take corrective action when deficiencies are identified during installation. :contentReference[oaicite:5]{index=5}
9. Use Daily Reports to Create a Construction Record
Daily or periodic observation reports should establish what work was observed, what materials or installation activities were encountered, what deficiencies were identified, what corrective actions were requested, and what limitations affected the observation.
A well-maintained record can also document conforming work, not just failures. This is important because the purpose of quality assurance is not simply to create a list of problems; it is to establish evidence that the installed roof was observed against the applicable requirements.
IIBEC describes the RRO as a link between the designer, contractor, and owner and identifies observation and documentation procedures as core RRO activities. :contentReference[oaicite:6]{index=6}
10. Keep the Documentation Through Closeout
Deficiency records should become part of the project’s permanent roofing documentation when appropriate. The final record may include observation reports, photographs, deficiency logs, corrective-action records, testing results, approved submittals, warranty documentation, and closeout materials.
That history can become valuable later if a leak develops, a warranty question arises, ownership changes, or the building requires another roof assessment. It can help distinguish an original installation issue from later damage or modifications.
Practical Deficiency Documentation Checklist
| Item | What to Record |
|---|---|
| Location | Roof area, gridline, elevation, or nearby landmark |
| Condition | Objective description of the observed deficiency |
| Evidence | Photographs, measurements, test results, or samples when applicable |
| Requirement | Drawing, specification, approved submittal, manufacturer requirement, or applicable standard |
| Risk | Potential effect on watertightness, durability, wind resistance, drainage, or warranty |
| Action | Required correction or further investigation |
| Responsibility | Party responsible for addressing the item |
| Verification | Evidence that the correction was completed and accepted |
Bottom Line
Installation deficiencies are best prevented from becoming roof failures by documenting them while the work is still visible and correctable. A strong process combines field observation, location-specific photographs, objective descriptions, measurements or testing where appropriate, contract-document references, corrective-action tracking, and verification of completed corrections. This creates an auditable quality record and gives the project team an opportunity to correct installation problems before they become concealed defects, leaks, warranty disputes, or premature roof failures.
For projects requiring formal quality assurance, an RRO can provide structured observation and documentation of installation against the project’s specifications and design intent. :contentReference[oaicite:7]{index=7}
Related Questions
- What does an RRO look for during commercial roof installation?
- What should a commercial roof observation report include?
- How does RRO observation during construction protect a developer’s warranty position?
- What causes commercial roofing punch-list delays, and how can GCs prevent them?
- What should a GC expect from daily RRO observation reports during roof installation?
- How should a roofing deficiency be handled before final roof acceptance?
- What roofing closeout documents should a GC collect before turnover?
Sources
- IIBEC – Registered Roof Observer (RRO)
- IIBEC – Registered Roof Observer Information Sheet
- IIBEC – Quality Assurance, A to Z
- IIBEC – Wind Uplift Resistance Testing of Newly Installed Roof Assemblies
- NRCA – Roofing Project Submittal and Protocol Guidelines
Last reviewed: September 2026
Related Resources
- What Documentation Should Be Kept Throughout a Leak Investigation?
- What Reporting Should a Roofing Vendor Provide Each Month?
- What Roof Documentation Will an Insurance Engineer Request?
CTA: Need professional oversight or documentation for a commercial roofing project? Review ShieldLine Roofing’s commercial roof repair services in Florida.
