Commercial Roof Commissioning and Field Quality Assurance: Who Does What?

“Roof commissioning,” “quality assurance,” “field review,” and “inspection” can sound like different names for the same site visit. They are not. Each term can describe a different scope, party, authority, and deliverable—and the same label may be used differently from one project to another.

Owners get the clearest oversight when the project documents define the work instead of relying on the label. They should identify who checks installation, compares work with the design, assesses warranty or guarantee requirements, performs tests, directs corrective work, and confirms contractual milestones.

Those questions should be answered before tender or procurement. This guide helps BC owners, developers, property managers, and project managers separate the roles and build a practical deliverables schedule. It is general planning information, not a substitute for project-specific contracts, specifications, professional advice, manufacturer requirements, or guarantee-program requirements.

Define “roof commissioning” for the specific project

On one project, roof commissioning may mean a defined series of construction observations and tests. On another, the roof may be one part of a formal building-enclosure commissioning process that begins during design and continues into occupancy. A third project may use “commissioning” informally for a final walk-through.

Formal building-enclosure commissioning is broader than a final roof inspection. ASTM E2813-26 describes a process based on the Owner’s Project Requirements, defined levels of commissioning, and a provider retained by the owner. Its scope runs from pre-design through occupancy and operations. The standard also says commissioning does not replace the contractual or legal responsibilities of designers and constructors or guarantee future enclosure performance.

Before comparing proposals, define which meaning applies. A usable scope should identify:

• the roof areas, assemblies, interfaces, and project phases covered;
• the requirements against which work will be reviewed;
• responsibility for each observation, test, decision, and report;
• planned and event-triggered visits, including hold points before concealment;
• reporting, correction, and retest procedures;
• the limits of each party’s scope and authority; and
• the evidence required for contractual completion, warranty or guarantee processing, and owner handover.

Contractor quality control versus owner-side quality assurance

The contractor’s quality-control process and the owner’s verification process are complementary, but they should remain distinct.

Contractor quality control

The roofing contractor controls its own work. Depending on the contract and roof system, contractor QC may include:

• confirming approved documents, materials, and installation requirements with the field team;
• checking the deck, substrate, environmental conditions, and first installation before covering work;
• recording specified material, attachment, application, seam, and daily-work data;
• photographing concealed layers, critical details, temporary tie-ins, and weather protection; and
• identifying non-conforming work, completing corrections, and maintaining the required records.

QC is not made independent because the contractor submits a report. It remains the contractor’s process for supervising, documenting, and correcting its own work.

Independent field review or owner verification

An owner may retain a consultant, design professional, roof observer, commissioning provider, or another qualified party for a defined review scope. That party may compare observed work with specified requirements, document observations, identify items needing action, witness tests, and report to the owner or contract administrator.

A periodic review does not become continuous supervision, and it cannot establish the condition of every concealed area. When professional engineering field review applies, Engineers and Geoscientists BC’s current Guide to the Standard for Documented Field Reviews describes field reviews as periodic and explains that they are not supervision of construction or a guarantee that every deficiency will be identified. It also places construction means, methods, supervision, and conformance responsibilities with the parties carrying out the work.

Consultant or design-professional role

A consultant or design professional may prepare the roof design and tender documents. If retained for construction-phase services, that party may also review submittals, respond to requests for information, observe work periodically, review changes, assess defined milestones, and issue reports.

The role depends on the written engagement and applicable regulatory requirements. It should not be assumed to include continuous observation, site safety review, contractor supervision, or every manufacturer and trade requirement.

For a regulated professional’s field reviews, the professional determines the review effort needed for the work and risk. The owner can coordinate notice and access but should not impose a limit that prevents necessary reviews. The scope should identify who handles structural, building-envelope, fire, energy, drainage, or other questions outside the roofing contractor’s responsibility.

Independent roof observer and RoofStar-specific review

For a project seeking a RoofStar Guarantee, the program has its own requirements. The current RCABC Roofing Practices Manual says RoofStar projects require observations by RoofStar-accepted independent observers. It identifies a first observation that includes the supporting deck surface, regular construction observations, a final observation, and written reports, along with later performance reviews required by the applicable program.

That is a program-specific framework, not the default process for every roof. Tender documents should state whether a RoofStar Guarantee is required, who retains the observer, and how reports connect with the other parties.

Manufacturer inspection is not blanket project acceptance

A manufacturer’s technical representative or field-services reviewer normally acts within the manufacturer’s program. The visit may relate to product requirements, approved details, installation observations, corrective items, or eligibility for a particular warranty or guarantee.

It does not automatically confirm compliance with every contract document, design requirement, code obligation, related-trade interface, concealed condition, or owner deliverable. Manufacturer programs also differ. GAF’s current commercial guarantee guidelines, for example, state that its inspections are for GAF’s use, that the contractor remains responsible for proper roof application, and that the owner and its representatives—not GAF—enforce contractual requirements and workmanship obligations.

Confirm the actual program’s contractor eligibility, system approval, notices, visit requirements, corrective-item records, warranty issuance, owner obligations, and rules for future alterations. A completed manufacturer visit should not be relabelled as owner acceptance or proof of future performance.

Specialized testing answers a defined question

Testing providers perform procedures selected for a specific assembly, condition, and decision. A project may call for adhesion or pull tests, seam sampling, membrane-integrity testing, moisture investigation, flood testing, or other methods. The provider’s report should identify the method, equipment, calibration where applicable, test locations, conditions, results, exclusions, and any repairs made to test openings.

The testing scope should identify who selects locations, the applicable procedure, suitability limits, acceptance criteria, reporting, repairs, and retesting.

A test result should not be stretched beyond the method. An adhesion test at selected locations does not certify all installed material. A moisture scan does not identify every moisture source. A membrane-integrity test may locate discontinuities in a compatible assembly, but it does not replace broader visual review or determine contractual acceptance. Raven’s guide to electronic leak detection explains one example of these method boundaries.

Responsibility matrix for a commercial roof project

This illustrative matrix is a starting point, not a universal assignment. Replace each role and deliverable with the parties named in the actual contracts.

Function	Typical lead	Typical evidence	Important limit or owner check
Control installation work	Roofing contractor	QC plan, daily reports, checklists, photos, test records, corrective-work records	Contractor QC is not independent owner verification
Interpret design requirements	Design authority or consultant, where retained	Clarifications, reviewed submittals, supplemental details, change records	Authority and regulated scope depend on the engagement and project
Perform owner-side observations	Consultant, roof observer, commissioning provider, or other designated reviewer	Field reports, photographs, issue log, recommendations, follow-up notes	Periodic observations do not confirm every concealed condition
Review manufacturer-program requirements	Manufacturer representative	Visit report, corrective items, warranty application status, final warranty document	Manufacturer review is not blanket contract or owner acceptance
Perform specialized tests	Qualified testing provider named for the method	Test plan, location map, results, limitations, repair and retest records	Results support only the test method, area, and acceptance criteria
Authorize changes and accept contractual milestones	Owner or the party assigned authority in the contract	Written instructions, change orders, payment certificates, completion and acceptance records	Authority should be explicit; a site comment is not automatically authorization

Set frequency, hold points, and reporting before construction

“Periodic visits” is rarely enough direction for procurement. The scope should combine planned reviews with event-triggered notice and the reviewer’s professional judgment where regulated professional work is involved.

Useful hold points may include:

• initial deck or substrate exposure;
• first installation of each assembly or attachment type;
• air- or vapour-control transitions and representative details before concealment;
• transitions between new and retained construction;
• selected testing milestones;
• completion of roof areas before protection, ballast, pavers, or overburden; and
• pre-final and final review stages.

The contract should state how much notice is required, who may release a hold point, what happens if work is covered before review, and how schedule effects are managed. It should also define report distribution and decision deadlines appropriate to the project, without confusing a reporting target with a guaranteed correction or acceptance time.

Observation frequency should respond to risk, sequencing, concealed conditions, and findings. Initial installation, unusual interfaces, or corrective work may need more attention than repetitive work. Early deficiencies may also justify revisiting the review plan.

Sample deliverables schedule

This fictional example shows how an owner can connect timing, responsibility, and evidence. It does not prescribe a standard visit count or transfer contractual authority.

Stage	Contractor deliverable	Owner-side or specialist deliverable	Decision or record
Before tender	Not applicable	Owner requirements, review scope, preliminary test plan	Roles, standards, budget responsibility, and authority defined
Before mobilization	QC plan, submittals, work plan, sample forms	Submittal review and observation schedule	Approved baseline and contact matrix
Initial installation	First-work checks, daily report, concealed-work photos	Field report and any test or mock-up record	Proceed, correct, clarify, or revise through the contract process
Ongoing work	Daily QC, material and weather records, corrective evidence	Periodic reports, test results, and issue tracking	Open items assigned and monitored
Pre-final review	Contractor self-review and proposed deficiency closures	Punch-list or pre-final report	Outstanding work and required evidence identified
Handover	Final QC record, as-builts, warranties, manuals, and closeout files	Final reports, test records, and status of deficiencies	Owner follows contractual completion and acceptance process

For more detail on construction records and closeout, see Raven’s commercial reroof quality-control checklist and roof project handover guide.

From observation to verified closure: an example workflow

The following fictional workflow shows how one observed condition can move through the project record without blurring roles.

1. Observe and locate. An owner-side observer records an incomplete membrane termination at R02-W03, with a date, wide location photo, close-up photo, and reference to the applicable project detail.
2. Issue the finding. The report identifies what was observed and routes the item to the party assigned under the contract. The observer does not invent a field redesign or direct the contractor’s means and methods.
3. Clarify if needed. If the detail does not fit the actual condition, the contractor submits a request for information and the authorized design party responds through the documented process.
4. Correct and record. The contractor completes the agreed work, records the materials and location, and provides dated photographs before the termination is concealed.
5. Review or retest. The designated reviewer evaluates the submitted evidence, revisits the location, or requests a specified retest according to the closure procedure.
6. Close with limits. The issue log records the closure basis and date. “Closed” means the documented item completed the agreed process; it does not guarantee that no future leak can occur.

One shared deficiency log helps prevent the contractor’s list, consultant’s report, manufacturer’s items, and test provider’s findings from becoming disconnected. Each item should carry a unique number, exact roof location, source, referenced requirement, responsible party, status, due date or milestone, corrective evidence, and closure authority.

Questions to answer before tender

Before procuring roof commissioning or field-quality services, ask:

• What does “commissioning,” “quality assurance,” “field review,” or “inspection” mean in this contract?
• Is the process limited to the roof, or part of broader building-enclosure commissioning?
• Who can interpret or change the design, and who supervises the contractor’s work?
• Who acts independently for the owner, and what are the limits of that review?
• Does a regulated professional scope apply, and how will required field reviews be determined?
• Is a RoofStar Guarantee or manufacturer warranty required, and what observations or notices apply?
• Which details or layers require review before concealment, and which tests or retests apply?
• Who receives reports and maintains the master issue log?
• Who may direct corrective work, approve changes, release hold points, and confirm completion milestones?
• Which reports, test records, as-builts, warranties, and deficiency records must be handed over?

Define the oversight before procurement

A useful roof-quality plan does not make every party responsible for everything. It gives each party a clear task, reference standard, reporting path, limit, and authority. Contractor QC controls the work. Owner-side review provides independent evidence within a defined scope. Design professionals address the responsibilities in their engagement. Manufacturer representatives apply their program requirements. Testing providers answer specified questions. The owner follows the contract to authorize changes and accept milestones.

If you are preparing tender documents or planning a commercial roof project, start with Raven’s commercial roofing proposal evaluation guide and commercial reroofing services. Contact Raven Roofing to discuss the roof system and contractor scope for your building; any consultant, commissioning, professional-review, testing, manufacturer, or guarantee-program roles should be separately confirmed for the project.

Frequently asked questions

Is roof commissioning the same as a final roof inspection?

Not necessarily. A formal commissioning scope may begin during design and continue through construction and occupancy, while a final inspection is one event near completion. Define the phases, requirements, deliverables, and authority instead of relying on either label.

Does independent field review guarantee a leak-free roof?

No. Field review can add documented, independent evidence and identify observed non-conforming work within its scope. Periodic review cannot confirm every concealed condition or guarantee future performance.