Commercial Reroof Quality-Control and Closeout Checklist

A commercial reroof is not ready for owner handover simply because the new membrane is in place. The project also needs a clear record of what was approved, what was installed, how concealed conditions were handled, which deficiencies were corrected, and which documents the owner will need to operate and maintain the roof.

The most useful quality-control process starts before tear-off and continues through final documentation. It also keeps responsibilities separate. The contractor checks and documents its own work; a consultant or other designated reviewer performs the reviews assigned by the contract; a manufacturer may inspect only for its warranty program; testing providers report within their defined scope; and the owner accepts the work through the contractual process.

This guide gives owners, property managers, strata councils, and project managers a phase-by-phase checklist for a commercial reroofing project. It is a planning tool, not a substitute for the project specifications, contract, manufacturer requirements, applicable code, safety plan, or advice from the project's qualified professionals.

Start by defining quality control, quality assurance, and acceptance

These terms are sometimes used interchangeably, but they describe different functions.

• Contractor quality control (QC): The contractor's internal process for supervising installation, checking work, recording conditions, and correcting its own deficiencies.
• Owner-side quality assurance or field review: Independent observations or reviews performed for the owner under a defined scope. Depending on the project, this may be handled by a roof observer, consultant, architect, engineer, or another qualified party.
• Manufacturer inspection: A review associated with a particular manufacturer's requirements or warranty process. Its scope and authority depend on that program; it does not automatically replace contract administration or owner acceptance.
• Testing: A specific procedure used to assess a defined condition, such as seam quality, fastener pullout resistance, membrane integrity, moisture, or adhesion. A test result answers only the question the method and test area support.
• Owner acceptance: The contractual decision that the work has reached the required stage for payment, completion, or handover. The contract should say who recommends or confirms acceptance and what evidence is required.

For projects seeking a RoofStar Guarantee, the current RCABC Roofing Practices Manual sets program-specific standards. RCABC describes independent field reviews as one part of its quality-assurance framework, alongside published standards, qualified installers, member requirements, and accepted materials. Those requirements apply to projects enrolled in that program; they should not be presented as the universal acceptance process for every roof.

Before work begins, write down who can issue instructions, who receives reports, who identifies deficiencies, who confirms corrective work, and who has contractual acceptance authority. Without that separation, a site comment can be mistaken for a design change, a manufacturer's visit can be mistaken for final acceptance, or a contractor's completed-item note can be mistaken for independent closure.

Phase 1: Preconstruction controls

The preconstruction meeting should turn the proposal and contract documents into a field-ready plan. It is the best time to resolve missing information while the roof is still intact and alternatives remain available.

Confirm the governing documents

• Executed contract, scope, drawings, specifications, addenda, accepted alternates, and defined exclusions
• Approved roof assembly and attachment method for each roof area
• Current manufacturer details and installation requirements that apply to the selected system
• Required warranty or guarantee program, including inspections, notices, tests, and submittals
• Code, permit, consultant, and authority requirements identified for the specific project
• Process for requests for information, substitutions, contemplated changes, change orders, and concealed conditions

Do not rely on a generic detail if the contract documents contain a project-specific one. RCABC notes that its online manual is the authoritative source for RoofStar program standards and explains how conflicts are handled within that program. For other projects, the design authority and project team should identify the governing hierarchy in the contract documents rather than assuming one source always controls.

Assign the review and reporting roles

• Owner representative and decision authority
• Contractor project manager, superintendent, and QC lead
• Design authority or consultant, if retained
• Independent observer or testing provider, where specified
• Manufacturer technical or warranty contact, where required
• Mechanical, electrical, sheet-metal, structural, and other trade interfaces
• Distribution list for daily reports, field reports, test results, change records, and urgent notices

The owner should also confirm which site observations are periodic and which milestones require notice before work is covered. A reviewer cannot assess a deck, air/vapour-control transition, fastening pattern, or concealed flashing after the next layer hides it.

Establish the project record

• Label roof areas consistently across drawings, photos, reports, and invoices
• Record existing membrane, flashings, drains, penetrations, equipment, walls, and adjacent surfaces before work
• Photograph interior areas or assets that could be affected by construction, where appropriate and authorized
• Identify approved access routes, staging zones, material storage areas, and protection requirements
• Create submittal, request-for-information, change, test, deficiency, and photo logs
• Agree on file names, drawing revision conventions, and the owner handover format

Phase 2: Substrate and concealed-condition review

Tear-off can reveal conditions that were not visible during bidding: deteriorated deck areas, unexpected roof layers, trapped moisture, abandoned penetrations, irregular slopes, damaged blocking, or interfaces that differ from available drawings.

Before covering a newly exposed area, the project team should apply the contract's review and change process.

• Identify the roof area and exact location
• Record the condition with dated photographs and measurements where useful
• Protect the opening and maintain the required temporary dry-in
• Notify the party authorized to review or direct the affected work
• Separate base-scope work from proposed extra work
• Record the agreed disposition, drawing, detail, or change authorization
• Confirm the substrate is ready for the next layer under the applicable project requirements

Substrate acceptance should also be specific. A note such as "deck okay" is less useful than a location-based record that addresses the conditions relevant to the assembly, such as surface condition, dryness, securement, openings, transitions, drain elevations, blocking, and repaired areas. The required checks depend on the roof system and contract.

Phase 3: Daily installation quality control

A daily roofing report should explain what happened, where it happened, and what remains exposed or incomplete. It is not a marketing recap. It is a contemporaneous project record.

Record the daily context

• Date, report author, roof area, and approximate work limits
• Weather conditions relevant to the work and any weather-related stoppages
• Crew size and other trades working in or near the roof area
• Materials received or installed, including product identifiers or lot information where required
• Approximate quantities installed or removed
• Equipment, access, or operational constraints that affected the planned sequence

Record the installation

• Layers installed and the attachment or application method used
• Locations of perimeters, corners, drains, curbs, penetrations, walls, expansion joints, and tie-ins completed that day
• Required in-process checks, measurements, seam reviews, or samples
• Photographs before details or concealed layers are covered
• Temporary seals, water cut-offs, edge conditions, and end-of-shift dry-in
• Areas left open, restricted, protected, or scheduled for follow-up

Record exceptions and decisions

• Discovered conditions and who was notified
• Field instructions, clarification requests, and referenced drawing or detail revisions
• Non-conforming work or deficiencies identified
• Corrective work completed and supporting evidence
• Materials rejected, quarantined, damaged, wet, or otherwise withheld from installation
• Incidents affecting the roof, including unauthorized traffic or work by another trade

Safety records are separate from roofing acceptance. WorkSafeBC's current roof-work guidance addresses fall-protection options and other requirements for roof work. This quality-control checklist is not the contractor's site-specific hazard assessment, safe-work procedure, or fall-protection plan.

Phase 4: Field observations, testing, and deficiency closure

Field observations are most useful when they are tied to the project documents and delivered promptly. Each observation should identify the roof area, work in progress, documents referenced, conditions observed, photographs, required follow-up, and any limitations on the review.

The report should not blur observation with continuous supervision. A periodic visit cannot confirm every concealed condition or every metre of installed work. The contract should define the review frequency, notice requirements, and hold points appropriate to the project.

Testing also needs a written purpose. Depending on the assembly and specifications, a project may call for seam probing, sample cuts, adhesion checks, fastener pull tests, membrane-integrity testing, flood testing, or other procedures. The project team should confirm:

• What question the test is intended to answer
• Which standard, manufacturer procedure, or project specification applies
• Who is qualified and authorized to perform it
• The test area, timing, environmental conditions, and exclusions
• How results and marked locations will be reported
• Who completes repairs and whether repaired areas are retested

Electronic leak detection is a good example of why method boundaries matter. It can help locate breaches in compatible assemblies, but it does not suit every membrane or roof configuration and does not replace visual or moisture investigation. Raven's guide to electronic leak detection for commercial roofs explains those limitations.

Use one deficiency log

Every open item should have enough information to be found and closed:

• Unique item number
• Date and source of the observation
• Roof area and precise location
• Description and photograph
• Contract drawing, specification, manufacturer detail, or other requirement referenced
• Responsible party and target date
• Corrective action taken
• Closure evidence, review status, and closure date

A verbal assurance that an item was addressed is not the same as traceable closure. Evidence may include a follow-up photograph, revised detail, test result, site-review note, or other record required by the contract. Closure also should not imply a performance guarantee; it means the documented item was reviewed through the agreed process.

Phase 5: Punch list and final review

The punch-list stage should begin after the contractor has completed its own review and corrected readily identifiable items.

The final roof review commonly considers:

• Field membrane, seams, laps, surfacing, and visible damage
• Perimeters, corners, terminations, and sheet-metal transitions
• Drains, scuppers, overflows, gutters, and drainage paths
• Curbs, penetrations, hatches, expansion joints, walls, and tie-ins
• Walkways, protection pads, pavers, ballast, and other specified protection
• Sealants and exposed maintenance items identified in the project documents
• Removal of temporary materials, debris, labels, abandoned fasteners, and construction protection
• Completion of specified testing and closure of related repairs
• Roof access, keys, labels, and owner operational requirements

An inspection during dry weather cannot prove that every reported interior leak is resolved or predict how the roof will perform under every future storm. If verification under particular conditions is contractually required, define the method and acceptance criteria rather than substituting a broad visual statement.

The contract should distinguish substantial completion, final completion, warranty inspection, and owner acceptance where those milestones apply. Payment certification or occupancy decisions may involve parties and requirements beyond the roofing contractor.

Phase 6: Closeout documents and owner handover

A closeout package is useful only if the owner can navigate it later. Organize the files by a consistent index instead of sending an unlabelled folder of PDFs and photographs.

Recommended closeout index

• Final contract scope, approved changes, and relevant clarifications
• Approved product data, shop drawings, samples, and substitutions
• Final roof plan or as-built markups showing roof areas, drains, equipment, penetrations, transitions, and material changes
• Daily reports and organized photo records
• Consultant, observer, manufacturer, and testing reports within their respective scopes
• Concealed-condition records and authorized dispositions
• Final deficiency log with closure evidence
• Product identifiers and maintenance information
• Contractor workmanship warranty and manufacturer warranty or guarantee documents, where applicable
• Required inspection confirmations, certificates, and final test reports
• Recommended inspection and maintenance activities, including owner responsibilities and reporting contacts

Warranty paperwork should be read, not simply filed. Coverage, start dates, exclusions, notice procedures, maintenance obligations, and authorization rules vary. Manufacturer review does not automatically mean every contract requirement is complete, and owner acceptance does not expand the written warranty. See Raven's guide to manufacturer and contractor roof warranties for the distinctions.

At handover, the property team should know where the roof records live, who may authorize roof access, how future penetrations or equipment work will be controlled, what maintenance records should be retained, and how a suspected issue is reported. That turns closeout from an administrative exercise into the beginning of responsible roof ownership.

One-page phase checklist for owners

Use this summary to structure project meetings and records. Adapt it to the actual contract and roof system.

Before mobilization

• Confirm scope, drawings, specifications, assembly, details, and exclusions
• Assign QC, field-review, testing, instruction, and acceptance roles
• Approve required submittals and identify hold points
• Record existing conditions and create the project logs
• Confirm warranty or guarantee notices and inspection requirements

During tear-off and substrate work

• Label exposed areas and photograph concealed conditions
• Follow the written review and change process before covering affected work
• Record deck or substrate repairs and retained conditions
• Maintain temporary protection and dry-in appropriate to the work

During installation

• Complete location-based daily reports
• Photograph concealed layers and critical details
• Track materials, quantities, weather, tie-ins, and open areas
• Issue observation and test reports promptly
• Add deficiencies to one log and retain closure evidence

Before final review

• Complete the contractor's own QC review
• Finish specified testing and corrective work
• Check drains, details, protection, housekeeping, and access items
• Confirm the punch-list process and contractual completion milestones

Before owner handover

• Close or clearly identify every outstanding deficiency
• Deliver indexed as-builts, reports, photos, tests, and change records
• Deliver applicable warranty or guarantee documents and maintenance requirements
• Transfer roof plans, access controls, contacts, and record-keeping responsibilities
• Store the final package with the building's long-term asset records

Plan the controls before the roof is open

Quality-control problems are easier to prevent than reconstruct from incomplete records at the end of a project. The practical approach is to define roles, documents, hold points, tests, deficiency closure, and handover requirements before tear-off begins—then keep those controls active as each roof area progresses.

If your team is planning a commercial reroof in Metro Vancouver, the Fraser Valley, or the Sea-to-Sky corridor, review the commercial roofing proposal evaluation guide and contact Raven Roofing to discuss the roof condition, project scope, or appropriate inspection milestones for the specific building.

Frequently asked questions

Who is responsible for quality control on a commercial reroof?

The roofing contractor is generally responsible for controlling and documenting its own work. Owner-side consultants, observers, manufacturers, and testing providers may perform separate reviews under defined scopes. The contract should identify who can issue instructions and who has acceptance authority.

Is a manufacturer inspection the same as owner acceptance?

No. A manufacturer inspection is normally tied to that manufacturer's requirements or warranty process. It may not review every contract requirement, related trade, concealed condition, or owner deliverable. Owner acceptance should follow the process set out in the project contract.

What should a daily roofing report include?

A useful report identifies the date, roof area, weather, crew, work limits, materials, quantities, details completed, in-process checks, photographs, temporary dry-in, discovered conditions, instructions, deficiencies, corrective work, and areas left open or protected.

What belongs in a commercial roof closeout package?

The package commonly includes as-built roof information, approved changes, product data, daily and field reports, test results, photographs, concealed-condition records, a closed deficiency log, warranty documents, and maintenance requirements. The exact contents should follow the contract and selected warranty or guarantee program.