Commercial Roof Project Handover: Documents Owners Should Receive

The last day of roofing work should not be the last day anyone thinks about the project record. A useful commercial roof handover package explains what was approved, what was installed, what changed in the field, which deficiencies were closed, and what the owner needs to do next.

That record matters long after the original project team has moved on. It can help a new property manager identify roof areas, give a service contractor better information, support warranty administration, and reduce guesswork when rooftop equipment is altered.

The exact deliverables and acceptance process come from the contract, specifications, consultant requirements, and applicable warranty or guarantee program. This guide is an owner-side organizing checklist. It does not change the contract, establish legal acceptance, certify the installation, or replace a final field review by the responsible parties.

Start with the contract-specific closeout list

Before requesting a generic “closeout binder,” locate every handover requirement in the project documents. Depending on the job, requirements may appear in the agreement, general and supplementary conditions, Division 01 specifications, roofing sections, drawings, approved submittals, addenda, change records, and manufacturer or guarantee-program forms.

Create one register with these fields:

• Required document or item
• Contract or specification reference
• Responsible party
• Required format
• Due date or project milestone
• Review status
• Final file name and storage location
• Open comment or missing information

Canada's current National Master Specification index separates closeout procedures, closeout submittals, training, commissioning, and facility operation into distinct sections. That is a useful reminder that “closeout” can involve more than one folder, but the actual project documents remain the authority for a specific roof.

Assign one person to maintain the register and one owner representative to confirm receipt. “Sent by email” is not a useful final status if attachments are missing or nobody knows which revision is final.

A practical roof handover index

Organize the package around how the building team will use it. The following index is a starting point, not a universal contractual requirement.

Section	Typical contents	Owner check
01 — Contract record	Final scope, drawings, specifications, addenda, accepted alternates, changes and relevant clarifications	Confirm the set reflects the completed roofing scope and identifies superseded documents
02 — Approved submittals	Product data, shop drawings, samples, colours, finishes and accepted substitutions	Confirm approvals and revisions are traceable to the installed work
03 — Construction record	Daily reports, field observations, photographs, concealed-condition records and test reports	Confirm records identify roof areas, dates and limits of observation or testing
04 — Deficiencies	Final deficiency log, corrective-work evidence and closure status	Separate closed items from accepted outstanding work and assigned follow-up
05 — Record drawings	As-built roof plan, details, drain and equipment changes, penetrations and material transitions	Confirm field changes are shown and roof-area names match the other records
06 — Warranties	Issued contractor and manufacturer documents, guarantee certificate, registration evidence and claim instructions	Read coverage, dates, exclusions, notice, maintenance, repair and transfer conditions
07 — Operations	Maintenance requirements, inspection guidance, service contacts, access controls and spare-material inventory	Assign each recurring responsibility to a role and calendar

For projects enrolled in the RoofStar Guarantee Program, RCABC says the owner receives a Roof System Record that includes the guarantee certificate and Roof Maintenance Guide, along with written observation records described for the applicable program. Review the current RCABC RoofStar Guarantee information for the selected program rather than assuming its deliverables apply to every commercial roof.

Keep approved submittals tied to the installed system

A folder of product sheets is not automatically an accurate installed-system record. Retain the documents that show what was approved and make substitutions or revisions easy to follow.

Useful submittal records may include:

• Membrane, insulation, cover board, vapour-control, adhesive and accessory product data relevant to the assembly
• Fastening or attachment information required by the design and project documents
• Shop drawings for sheet metal, drainage, curbs, transitions or other project-specific details
• Approved colour and finish selections
• Samples or sample-approval records where required
• Manufacturer letters, tested-assembly information, or compatibility confirmations required by the project
• Substitution request, technical review, approval and resulting drawing or specification revision

Label withdrawn and superseded submittals clearly so a future reader can distinguish “submitted,” “reviewed,” and “installed” records.

Collect field observations, tests and deficiency closure

Closeout should preserve construction evidence and its limits. A periodic field observation is not continuous supervision, and a test result applies only to its method, conditions, and test area.

Include, where required by the project:

• Contractor daily quality-control reports
• Consultant or independent observer field reports
• Manufacturer inspection or warranty-program reports
• Dated, location-labelled photographs of concealed and completed work
• Test procedures, locations, results, limitations and repair records
• Concealed-condition notices and authorized dispositions
• One numbered deficiency log with status and closure evidence

The final deficiency register should identify any open item, the party responsible, the agreed next step, and how it will be tracked. Do not relabel an unresolved item as “closed” merely because the package is due.

For a broader phase-by-phase process, see Raven's commercial reroof quality-control and closeout checklist.

Make the as-built roof plan usable

The as-built or record roof plan is the navigation layer for the whole package. RCABC's Roof Maintenance Guide describes a roof plan as part of the Roof System Record and illustrates the value of marking features such as drains, equipment, hatches, walkways, penetrations, walls, copings and expansion joints.

Use one naming convention across the plan, photographs, reports, deficiency log and future maintenance records. For example:

• R01 — main low-slope roof
• R02 — east mechanical penthouse roof
• D-R01-01 — drain 01 on roof area R01
• RTU-R01-03 — rooftop unit 03 on roof area R01
• P-R02-02 — penetration 02 on roof area R02

This is an illustrative convention, not a Raven or industry standard. The project team can use another system, provided it is unique, consistent, documented, and practical in the field.

The final plan should reflect relevant changes discovered or made during construction, such as:

• Roof-area limits and changes in assembly or attachment
• Drains, scuppers, overflows and drainage direction where documented
• New, removed or relocated equipment, curbs and penetrations
• Expansion joints, roof-to-wall transitions and material interfaces
• Walkways, protection zones, tie-ins and areas with restricted access
• Concealed conditions that the contract requires to be recorded

Record drawings should not be described as proof that every concealed condition was verified.

Read every warranty document before filing it

The handover package may contain separate contractor workmanship, manufacturer material, manufacturer system, component, or RoofStar Guarantee documents. Their scope, start dates, registration steps, exclusions, transfer terms, notification deadlines, maintenance requirements, and rules for future alterations can differ.

At handover, confirm:

• The final document has been issued, not just applied for or represented by a sample form
• The correct owner, building address, roof system and covered roof areas are identified
• Effective and expiry dates are stated or can be determined from the document
• Registration or acceptance requirements are complete
• Claim contacts and notice procedures are recorded
• Maintenance and inspection conditions are assigned to the property team
• Rules for repairs, penetrations and third-party rooftop work are understood
• Transfer conditions are recorded for a future sale or management change

Manufacturer requirements are not interchangeable. For example, SOPREMA's current Canadian warranty and preventive-maintenance guidance tells owners to document inspections and retain observations with the warranty certificate. GAF's commercial warranty and guarantee guide says its commercial warranties and guarantees require registration under its requirements and shows that transferability varies by program. Check the actual documents for the installed system.

Raven's guide to manufacturer and contractor roof warranties explains why the documents should be reviewed separately.

Turn maintenance information into assigned work

Closeout is the start of roof operations. Convert maintenance language into a building-specific plan rather than leaving it buried in warranty attachments.

The owner record should identify:

• Inspection activities and cadence required by the project or warranty documents
• Conditions that trigger an additional review, such as a major weather event or rooftop construction
• Drainage, debris, traffic, sealant and visible-detail checks applicable to the roof
• Who may authorize roof access and how visits are logged
• Who must be notified before penetrations, repairs, equipment changes or other alterations
• Where reports, photographs, invoices and repair records are stored
• Which party is contacted for a leak, warranty question or planned alteration
• Spare pavers, membrane, sheet metal, coating or other materials actually turned over, with quantities and storage location

Do not invent a generic inspection interval if the contract or warranty sets one. The RCABC Guarantee standard makes owner maintenance and notification of modifications material conditions of its program. Other warranties may use different language, procedures, or intervals.

Future rooftop visits can be connected to a roof work permit and access log, while completed inspections and repairs should feed the building's commercial roof maintenance records.

Owner acceptance check

Use this review before the package is archived. Adapt it to the contract and have the parties with contractual authority manage acceptance.

• Compare the package against the project-specific closeout register
• Confirm each file opens, is legible, and carries a clear final revision or date
• Confirm roof-area labels match across plans, photographs, reports and logs
• Distinguish approved submittals from final installed-system information
• Confirm test reports state locations, methods, results and limitations
• Confirm the deficiency log shows closure evidence or clearly assigned outstanding work
• Confirm the record plan includes documented drains, equipment, penetrations, transitions and field changes
• Confirm final warranty or guarantee documents have been issued and required registrations are complete
• Assign maintenance, inspection, access-control and notification responsibilities
• Inventory spare materials and record their storage location
• Save an owner-controlled copy with the building's long-term asset records
• Back up the package in a format that remains accessible when staff or service providers change

Paperwork does not prove watertightness, establish contractual completion by itself, or replace required final field reviews. A visual walk-through likewise does not replace missing warranties, record drawings, test reports, or operating information.

Build the package for the next property manager

A strong package should show what system is installed, where work changed, which records apply to each area, what remains open, which warranty governs, who controls access, and what happens next. Indexed, location-based records can remain useful through staff changes, service calls, tenant improvements, and capital planning.

If you are preparing for a commercial roof replacement in Metro Vancouver, the Fraser Valley, or the Sea-to-Sky corridor, review Raven's commercial reroofing services and contact Raven Roofing to discuss the roof and project scope for your building.

Frequently asked questions

Is a closeout package the same as owner acceptance?

No. Document delivery can be one requirement within the contractual completion and acceptance process, but paperwork alone does not establish acceptance or replace required field reviews. Follow the definitions, roles, and milestones in the project documents.

What is the most important warranty check at handover?

Confirm that the final warranty or guarantee document has actually been issued for the correct owner, address, system, and roof areas. Then read its registration, maintenance, claim-notice, repair, alteration, and transfer conditions rather than relying on the headline term alone.