Rooftop PV array-turnover warranty photo record

Direct answer

Before a rooftop PV array is turned over, the photo record should identify the building, roof area, approved array layout, racking or mounting system, roofing system, warranty contact, stanchion or attachment type, flashing boot or post flashing detail, ballast tray or bay, ballast count marker, roof pad or slip-sheet condition, wire-management block or clip, cable path, conduit support, service walkway gap, fire access pathway, roof drain and scupper clearance, roof hatch route, fall-protection boundary, open holds, witness, date, and turnover decision.

The purpose is not to prove wind resistance, structural capacity, electrical compliance, fire-code compliance, waterproofing acceptance, or warranty coverage. The purpose is to preserve visible field conditions before modules, trays, ballast, cables, conduit, and owner turnover paperwork make the roof hard to review.

A useful packet lets the roofing contractor, solar contractor, owner, engineer, manufacturer, and maintenance team answer three practical questions later: where does the array bear on the roof, where does it penetrate or attach to the roof, and what conditions were accepted or held when the array was released.

What this record covers

This record covers rooftop solar photovoltaic arrays on low-slope and steep-slope roofs where the PV installation interacts with the roofing warranty, roof access, drainage, and maintenance route. It applies to ballasted racks, attached racks, stanchions, flashed mounts, conduit supports, wire-management accessories, roof pads, slip sheets, and service paths that remain visible at turnover.

The scope is visible and traceable evidence. It connects the approved PV layout and roof warranty requirements to actual field conditions: attachment rows, flashing boots, post flashings, ballast trays, ballast blocks, roof protection pads, cable clips, conduit blocks, service walkway gaps, access pathways, and roof areas left open for inspection.

This is not a PV design article, an electrical installation manual, a structural ballast calculation, a wind-tunnel analysis, a fall-protection plan, a fire-code interpretation, or a roofing warranty approval. The adopted code, AHJ, engineer, roofing manufacturer, PV racking manufacturer, electrical contractor, roofing contractor, owner, and site safety procedure control those approvals.

Keep the scope narrow

Do not let the turnover packet drift into a design signoff. The record should show whether stanchion flashings are present, boots or caps are seated, ballast trays sit on the required protection, ballast counts match the marked design basis, wires are restrained away from roof damage points, service walkways remain usable, and warranty inspections or approvals are attached.

Do not use photos to approve the load path. FM Data Sheet 1-15 discusses wind design information, ballast resistance, clamp details, array layout, setbacks, roof zones, slip sheets, coefficients of friction, and the special risk of mechanically fastened roof covers. Those items support why the turnover record should preserve the design basis, but they do not let a photo note replace engineering.

Do not use photos to approve electrical work. A photo of cable clips, conduit blocks, bonding jumpers, labels, or rapid-shutdown equipment can support the closeout file, but electrical testing, inspection, code compliance, and energization release belong to qualified electrical people and the AHJ.

Start with the approved basis

Start the package with the documents that control the work: PV permit drawing, approved array layout, racking design package, ballast plan, attachment plan, roof warranty requirement, roofing manufacturer letter, racking manufacturer instructions, module compatibility record, electrical one-line, rooftop access and pathway plan, roof safety plan, inspection checklist, and owner maintenance handoff.

FM Data Sheet 1-15 says proposed PV review should include drawings of array layout, setback distances, panel slope, orientation, racking connections, mechanical anchors, and ballast weight across roof zones. IronRidge and Unirac materials also point installers back to engineering drawings, roof manufacturer requirements, and system-specific instructions. Those sources support a packet that starts with documents, not loose photos.

Photograph the revision block or document number used during the walk. If a field layout differs from the approved drawing, mark the difference and identify who accepted it. A photo without the drawing basis can show a tray or boot, but it cannot show whether the condition belongs in that location.

Define the turnover boundary

Define exactly what is being turned over. Examples include Array A above Roof Area R-2 only, attached stanchions S-101 through S-128, ballast trays in roof zones 1 and 2 only, conduit from combiner C-1 to roof penetration RP-4, or service path from hatch H-1 to inverter platform only.

PV turnover often has stacked boundaries. The roof may be under a roofing warranty, the rack may have a separate product warranty, the electrical system may not be energized, the owner may still need a fire marshal inspection, and the roofing manufacturer may require a post-installation review. The photo record should separate those conditions.

Avoid broad statements such as solar complete if the actual release is only a roofing walk below the array. Write the boundary in field language with roof areas, grid lines, row numbers, module rows, rack blocks, attachment IDs, conduit runs, and open exceptions.

Roof condition before array cover

Photograph the roof surface before final module placement or before ballast blocks hide the contact points. Include membrane type, seams, patches, coating condition, standing water evidence, loose debris, gravel removal, drains, scuppers, expansion joints, curbs, penetrations, and any pre-existing damage inside the array footprint.

IronRidge ballasted roof material tells installers to comply with roofing manufacturer warranty terms and remove loose debris or gravel before installation. QuickMount guidance recommends a thorough roof evaluation and photos before work so repairs or replacement can happen before or with the installation. Those sources support a baseline roof photo set.

This baseline matters because later damage disputes often start with a simple question: was the scuff, wrinkle, cut, blister, open seam, or ponding mark present before the solar work? A wide photo, close photo, roof area label, and date can prevent guesswork.

Stanchion and attachment identity

Each attached point needs a wide photo, close photo, and ID reference. Show the stanchion or post, attachment plate, flashed mount, boot or cap, rail connection, nearby module row, roof grid, and whether the condition is in the field, perimeter, corner, or another project-defined roof zone.

The record should connect each attachment to the approved attachment schedule. If the design calls for a specific mount, base, post height, flashing type, anchor type, torque record, or roofing contractor observation, the photo should name the document or tag where that proof lives.

Do not treat attached and ballasted points as interchangeable. A stanchion or mechanically attached point changes the roof differently than a loose ballasted tray. The turnover packet should separate penetrations, nonpenetrating supports, hybrid supports, seismic anchors, and supplemental restraints.

Flashing boot condition

Photograph every representative flashing boot, post flashing, pipe-style boot, cap, clamp, pitch-pan alternative, or membrane flashing detail required by the roofing warranty plan. Show the high side, low side, lap direction, sealant line where visible, fasteners or clamps where visible, and adjacent membrane condition.

QuickMount installation material for shingle mounts shows roof-compatible sealant at drilled holes, flashed components, sealing washers, and written installation instructions. Its warranty language also states that product warranty depends on installation according to written instructions. That supports documenting the actual visible boot and flashing condition, not assuming it was done correctly because the array is standing.

For low-slope membrane roofs, do not invent a boot detail from a steep-slope source. The approved roof detail and roofing manufacturer instructions control. The field record should say which detail was used and whether the roofing contractor or manufacturer observer accepted it.

Sealant and compatibility record

Photograph sealant tubes, labels, batch information, or closeout submittals when sealant is part of the approved roof attachment detail. Tie the photo to the mount, roof type, manufacturer, and location. If the sealant is hidden, photograph the product evidence and completed condition before it disappears.

IronRidge QuickMount FAQ material warns that roofing manufacturer instructions supersede mount instructions where the mount integrates with the roofing system, and that sealant compatible with the contacted materials is important. It also warns that an unapproved sealant can affect a roofing warranty. That makes sealant evidence a warranty record item.

Do not write that a sealant is compatible because it looks clean. The packet should show the approved product basis, not a field opinion. If the wrong tube was used, the condition is a hold for the roofing manufacturer or roofer of record.

Ballast tray identity

For ballasted arrays, photograph tray or bay type, rack row, module row, ballast count, block size or tag, block condition, tray seating, wind deflector if present, under-tray protection, and nearby membrane condition. Include enough wide context that the owner can find the same row later.

FM Data Sheet 1-15 discusses ballast weight, PV panel and hardware weight, load variation by array position and roof zone, and the need for design information that shows resistance in each section. Unirac manuals also tell users to verify block weights because block weight affects the number required. Those sources support a ballast photo record tied to the design basis.

A close photo of a concrete block is not enough. The record should answer which bay it belongs to, whether the count matches the layout, whether supplemental ballast was added, and whether the tray is bearing on the approved protection rather than directly scuffing the roof.

Roof pad and slip-sheet evidence

Photograph roof pads, slip sheets, sacrificial membrane pieces, or other approved protective interfaces before ballast or trays cover them. Show orientation, count, skipped bays where attachments replace pads, nearby seams, membrane type, and whether debris was cleared below the support point.

Unirac RM10 EVO material describes roof pads as a protective interface between the ballast bay and roofing material and says to consult the roofing manufacturer for requirement and compatibility. FM Data Sheet 1-15 says roof cover scraps or manufacturer slip sheets can be used between roof cover and PV pedestals to prevent abrasion and warns that slip sheets affect friction testing.

Do not add unapproved rubber, plastic, or loose pads because a field photo checklist mentioned protection. The design, roof manufacturer, racking manufacturer, and warranty requirement control the protection material. The record only preserves what was installed and who accepted it.

Ballast clearance and roof drainage

Photograph clearance from ballast trays, blocks, pads, clips, wire bundles, and conduit supports to roof drains, scuppers, gutters, expansion joints, curbs, parapets, overflow paths, and known ponding areas. Show whether the tray layout blocks inspection or cleaning access.

FM Data Sheet 1-15 sets example spacing for arrays, aisles, expansion joints, and skylights in its loss-prevention guidance. IronRidge ballasted material also directs installers to keep walkways clear and avoid obstacles under applicable fire codes. These sources support documenting clear space without turning the article into a universal spacing table.

If ballast sits in a water path, at a drain sump, across a scupper approach, or on a membrane seam that the roofing manufacturer restricted, hold turnover. The correction photo should show both the moved support and the restored drainage or inspection route.

Wire-management block

Photograph wire-management blocks, clips, strut straps, conduit blocks, raceways, module-frame clips, homerun supports, and any cable bundles that could contact roofing, flashings, tray edges, wind deflectors, array skirts, or clamps. Show both the close support and the wider cable route.

Unirac RM10 and RM10 EVO materials describe optional wire management using strut-strap solutions or strut nuts and state that conduit and wire ways should be grounded and bonded per the National Electrical Code. IronRidge QuickMount FAQ material says PV cables should be routed to prevent contact with accessories if failure occurs, using clips, conduit, raceways, or racking rails as needed.

The roofing turnover record should not approve conductor sizing, grounding, bonding, or electrical code compliance. It should show whether wires are off the membrane, away from sharp edges, restrained at predictable intervals, protected at roof transitions, and not placed where roof maintenance will pull, crush, or cut them.

Cable sag and abrasion check

Walk the array edges, module gaps, tray rows, conduit turns, and roof transitions looking for cable sag, cable loops on membrane, zip-tie tails, unsupported homeruns, conduit sweeping across walk pads, and cable contact with flashing boots. Photograph each exception with a location reference.

Cable abrasion can become a roofing problem and an electrical problem at the same time. A wire loop dragging on a membrane may damage the roof surface; a wire trapped under a tray or ballast block may become hidden damage; a wire rubbing a flashing can undermine both systems.

Do not move cables for the photo unless authorized. The record should show the found condition, the correction owner, and the rephoto method. For electrical changes, the qualified electrical contractor should make the correction and provide the closeout evidence.

Conduit supports and roof contact

Photograph conduit supports, sleepers, blocks, clamps, roof penetrations, expansion fittings, route labels, and transitions from array to equipment. Show whether supports sit on approved pads, avoid drain paths, avoid sharp membrane contact, and leave space for roof inspection.

IronRidge QuickMount component pages identify conduit mounts and conduit penetration flashing as part of rooftop solar accessory systems. That supports treating conduit route evidence as part of the roof handoff, especially where conduit crosses warranty-covered roofing.

Do not use the roofing packet to certify conduit fill, wiring method, bonding, or electrical inspection. The roofing side needs to know whether conduit support is roof-safe, maintainable, and included in the warranty file.

Service walkway gap

Photograph the service walkway from the roof access point to the array, inverters, combiners, drains, scuppers, smoke vents, roof hatches, ladders, and required maintenance points. Show gaps between rows, walking pads, protection pads, warning lines, guardrails, hatch clearance, and any array edge that narrows the route.

NYSERDA rooftop access guidance gives example residential and nonresidential PV pathway scenarios and states that local code officials determine final compliance. ICC and NFPA public materials also frame roof access, pathways, and spacing as fire-service and code concerns. The field record should preserve the accepted path and the authority that accepted it.

A service path is not just a place a worker can squeeze through once. It should remain findable, usable with required safety equipment, and clear enough for the owner to inspect roof drains, flashings, electrical equipment, and array components under the approved maintenance plan.

Fire access pathway proof

Where the permit or AHJ required fire access pathways, photograph the path edges, array setbacks, ridge or roof-edge paths, ventilation spaces, pathway labels, roof hatch approach, and any obstruction such as conduit, ballast, cables, mechanical equipment, or stored material.

The field packet should not quote a dimension as universal unless the adopted code and approved drawing require that dimension for the project. Roof slope, building use, roof size, local amendments, sprinkler status, fire-service tactics, and AHJ determinations can change the accepted path.

If the fire access path is blocked on turnover day, hold the release. A path that exists only on the permit drawing will not help emergency responders or maintenance staff when the roof is full of ballast trays, conduit, and module rows.

Roof hatch and ladder route

Photograph the route from roof hatch, ship ladder, fixed ladder, stair penthouse, or access door to the PV work area. Show hatch swing, ladder landing, guardrail, warning line, walk pad, toe clearance, array proximity, and whether tools or replacement parts can be moved without crossing unprotected roof areas.

OSHA 1926.501 addresses fall protection for unprotected sides and edges, holes including skylights, ramps, runways, walkways, low-slope roofing work, and steep roofs. That supports recording the safety boundary and route condition without designing the fall-protection system in the article.

If the maintenance route depends on a key, lift, ladder, tie-off point, escort, access permit, or weather restriction, put that condition in the turnover note. A PV array is not maintenance-ready if the owner cannot safely reach the equipment it just accepted.

Skylight and roof opening clearance

Photograph skylights, smoke vents, roof hatches, roof drains, roof openings, and guarded or covered holes near the array. Show whether ballast trays, wires, conduit, module rows, and service paths leave the required clearance and do not invite workers to step onto fragile surfaces.

FM Data Sheet 1-15 includes loss-prevention spacing guidance around skylights, and OSHA 1926.501 includes fall-protection requirements around holes and skylights. These sources support making roof openings a required photo category during PV turnover.

Do not let a clean array photo hide a bad access condition. A module row that looks straight may still push work toward a skylight, blocked hatch, or unprotected roof edge. The turnover record should show both the array and the hazard boundary.

Drain and scupper access

Photograph every roof drain, overflow drain, scupper, gutter outlet, leader head, downspout route, sump, and ponding-prone area near or below the array. Show whether array components allow cleaning, inspection, and emergency water flow under the owner maintenance plan.

Roof drainage belongs in the PV turnover record because array supports can create new maintenance obstacles. A ballast tray next to a drain, a conduit block across a scupper path, or a wire bundle in a sump may not fail on installation day, but it can create a roof problem during the first storm or cleaning walk.

If the design professional or roofing manufacturer has a separate drainage review, cite it. Do not write that drainage is adequate from photos alone. The record should show visible access and obstruction status, not approve roof-drain sizing or rain load.

Expansion joints and movement zones

Photograph roof expansion joints, seismic joints, control joints, building movement zones, and adjacent array supports. Show whether racks, trays, cables, conduit, ballast, and walk pads bridge, crowd, or restrict the movement zone.

FM Data Sheet 1-15 includes example spacing around roof expansion joints in its array positioning guidance. That source supports recording expansion-joint clearance as a separate turnover item because it is easy to hide with rows and homeruns.

Do not approve a field reroute across an expansion joint unless the approved project documents do. If a cable or conduit must cross, the electrical and roofing details should show how movement, waterproofing, support, and maintenance will be handled.

Wind and ballast design packet

Attach the ballast design output, wind design basis, array zone map, roof-zone diagram, module layout, ballast block weight record, attachment schedule, and any engineer letter or manufacturer calculation used for the installed layout. Photograph the field marks that connect those documents to the actual array.

FM Data Sheet 1-15 discusses boundary layer wind tunnel testing, vertical load testing, ballast resistance, coefficients of friction, array size, roof zones, and the way slip sheets affect test data. It also warns that mechanically fastened roof covers can make wind-tunnel results less applicable and states that PV panels must be mechanically fastened over mechanically fastened roof covers.

Those are design and engineering issues. The field packet should preserve the installed evidence and the design reference. It should not recalculate wind resistance, change ballast, or accept missing attachments from a turnover walk.

Fire classification and roof assembly record

Photograph module labels, racking system identification, roof assembly information, fire classification references, and any project document that connects the PV system to the roof assembly requirement. Keep this with the permit and warranty file.

Unirac and other racking materials include system-level fire classification sections, while ICC and NFPA public sources frame rooftop PV access and fire-service concerns. These sources support keeping fire documentation in the packet, but they do not make the photo record a fire-code approval.

If the accepted fire basis depends on a specific module, rack, attachment, roof covering, roof slope, setback, or array configuration, do not let substitutions pass as a field note. Hold turnover until the AHJ, design professional, or manufacturer confirms the basis.

Mechanical connection record

Photograph representative clamps, rail splices, tray-to-module connections, stanchion heads, bolts, seismic attachments, grounding lugs where visible, and torque records or inspection forms. Show the row, rack type, and whether a qualified installer made the connection.

FM Data Sheet 1-15 calls for commissioning inspection of mechanical fasteners and maintenance inspections after commercial operation. Unirac RM10 and RM10 EVO materials call for periodic inspections for loose components, loose fasteners, damage, corrosion, and loose connections. Those sources support turning mechanical connection evidence into an owner handoff item.

Do not remove modules, open electrical equipment, or retorque connections for a photo without authorization. The record should identify the qualified party and attach the actual inspection or torque form.

Warranty coordination

Name the roofing manufacturer, roofer of record, solar installer, racking manufacturer, module manufacturer, roof warranty number, PV warranty registration, required inspection date, and any conditions that preserve or limit coverage. Photograph the letters, signoff forms, and field tags that connect those parties.

IronRidge ballasted material tells installers to comply with roofing manufacturer warranty terms and says most manufacturers require inspections and certified installers for some work. QuickMount FAQ material says roofing manufacturer instructions supersede mount instructions where mounts integrate with the roofing system and recommends consulting the roofer of record on warranted roofs.

Do not claim warranty acceptance from photos. The record preserves visible conditions and cites the warranty process. If manufacturer observation, roof consultant report, roofer signoff, or warranty registration controls the release, attach it or cite its document number.

Owner maintenance handoff

Give the owner a roof map that shows array blocks, service paths, drains, scuppers, hatch access, inverters, combiners, disconnects, roof warranty contacts, approved walk routes, and restrictions on moving ballast, lifting modules, opening flashings, or relocating wires.

The owner also needs inspection intervals and triggers. FM Data Sheet 1-15 includes one-year or pre-warranty-end inspection context, annual visual inspection context, tightness checks of accessible mechanical fasteners, and inspections after severe weather events. Racking manufacturer instructions also call for periodic inspection of loose or corroded components.

Translate those obligations into the owner system without changing them. The turnover packet should say where the actual maintenance manual lives, which party owns each inspection, and which conditions require the roofer, solar contractor, engineer, or manufacturer before work continues.

Minimum photo packet

A minimum packet should be compact enough to use and specific enough to find conditions later. Wide photos locate the roof area. Close photos prove component condition. Document photos connect the condition to the approved basis. Exception photos show what was held.

The table below is a starting structure. Add project-specific rows for battery equipment, inverters, snow guards, lightning protection, roof anchors, public terrace restrictions, green roof interfaces, reroof phasing, or telecom equipment if those conditions affect the array turnover.

Turnover checklist

Use this checklist during the roof walk, then attach photos, documents, and exceptions to the owner turnover location. Keep the language tied to roof areas, array IDs, and responsible parties.

• Photograph the approved PV layout, roof warranty requirements, ballast plan, attachment plan, and access path plan used for the walk.
• Photograph the roof baseline inside the array footprint before supports, ballast, or modules hide the surface.
• Photograph each representative stanchion, post, boot, flashing, cap, clamp, or attachment in wide and close views.
• Photograph sealant product evidence, compatibility basis, roofer observation, or manufacturer approval where the detail requires it.
• Photograph ballast trays or bays with row ID, ballast count, block weight marker, roof pad, slip sheet, and membrane condition.
• Photograph tray clearance at drains, scuppers, expansion joints, skylights, curbs, parapets, and ponding-prone areas.
• Photograph wire-management blocks, cable clips, conduit supports, raceways, and cable sag exceptions.
• Photograph cable and conduit transitions where they cross walk pads, roof edges, flashing boots, or roof penetrations.
• Photograph the service walkway from roof access to array rows, drains, inverters, combiners, and roof maintenance points.
• Photograph required fire access pathways, ventilation spaces, setbacks, and AHJ-approved alternatives if applicable.
• Photograph roof hatch, ladder, guardrail, warning line, skylight, and unprotected edge conditions that affect access.
• Photograph drains, overflow drains, scuppers, gutters, and roof drainage paths near or below the array.
• Attach mechanical inspection, torque, ballast, attachment, electrical inspection, and commissioning records by document number.
• Attach roofing manufacturer, roofer of record, racking manufacturer, and PV warranty registration or observation records.
• Write correction notes with row, roof area, owner, required fix, rephoto method, and due date.
• Store photos, drawings, warranty contacts, inspection records, route maps, and exceptions in the owner turnover location.

Weak and strong notes

Weak note: solar roof complete, photos attached. This does not identify which array was checked, whether flashings were reviewed, whether ballast matches the plan, whether wires are off the roof, whether service paths remain open, or whether warranty observations are complete.

Stronger note: Roof Area R-2, Array A, rows A1 through A8, was walked on 2026-06-09 before owner array turnover. Photos A-001 through A-006 show approved layout SK-PV-12 and roof warranty letter RW-47. Photos A-007 through A-036 show attached stanchions S-101 through S-128 with roofer-observed membrane flashings. Photos A-037 through A-060 show ballast bays B-1 through B-24 with two roof pads per bay and ballast counts matching the design schedule. Photos A-061 through A-075 show wire clips, conduit blocks, and no cable contact with membrane at recorded locations. Photos A-076 through A-084 show hatch access, service walkway, drains RD-3 and RD-4, overflow scupper OS-2, and open hold H-1 for conduit support rephoto near Grid C-4.

The stronger note works because it names the roof, array, rows, documents, photo ranges, acceptance limits, and hold. It gives future maintenance staff a map rather than a generic closeout claim.

Common mistakes

The first mistake is photographing only the modules. Modules may be the visible product, but roof disputes usually involve hidden or low-visible items: flashings, pads, trays, ballast blocks, cables, conduit supports, service paths, drains, and warranty letters.

The second mistake is mixing design approval with field evidence. A photo can show that a tray has four blocks. It cannot prove that four blocks are correct for that roof zone, wind exposure, slip-sheet material, roof cover type, or seismic condition.

The third mistake is treating roof access as someone else's closeout. If maintenance cannot reach the array, drains, scuppers, flashings, or equipment without stepping outside the approved route, the owner has inherited an operations problem.

Correction and rephoto

Common correction photos include reset roof pads, relocated ballast blocks, replaced damaged pads, lifted cable loops, added wire clips, moved conduit blocks, cleaned debris below trays, cleared drain access, reopened service paths, corrected flashing labels, added roof area tags, and attached warranty observations.

A correction photo should show the same location before and after. Use the same row number, roof area, attachment ID, tray ID, or drain tag. Do not submit an isolated clean clip if the original exception was a cable rubbing the roof at a different module edge.

If correction changes the approved design, do not treat the rephoto as approval. Added ballast, moved attachments, rerouted conduits, changed walk paths, or substituted roof pads should point back to the engineer, AHJ, roofing manufacturer, or racking manufacturer as required.

When to hold turnover

Hold turnover if approved drawings are missing, the installed layout does not match the accepted basis, roof warranty requirements are unknown, the roofer of record has not observed required penetrations, flashing boots are incomplete, sealant product evidence is missing, or attachment IDs cannot be tied to the schedule.

Also hold if ballast counts are not documented, block weights are unknown, roof pads or slip sheets are missing where required, trays bear on debris, wires sag onto the membrane, conduit blocks sit in drainage paths, service walkways are blocked, roof drains or scuppers cannot be reached, or required fire access pathways are obstructed.

A hold is not a paperwork failure. It is the reason the record exists. The packet should expose the exact reason the array is not ready for owner turnover.

As-built and asset updates

Update owner records when the installed condition differs from the approved layout or when the field walk creates new maintenance information. That may include the roof plan, PV as-built, CMMS asset list, warranty file, drain map, access route map, roof hazard plan, emergency response plan, and maintenance schedule.

Asset names should connect across systems. Array A, rack row A4, stanchion S-117, combiner C-1, drain RD-4, scupper OS-2, roof hatch H-1, and roof warranty RW-47 should be findable from the same owner file. If those labels are not connected, operations will rely on memory during the first leak, storm, or equipment call.

If the owner uses QR tags, roof coordinates, barcodes, or CMMS numbers, photograph the tags and include them in the handoff. The field truth should not live only in a solar contractor photo folder.

Owner operations access

Operations needs to know what they may touch. The turnover record should say who may move ballast, lift modules, remove wire clips, adjust conduit supports, open combiner equipment, inspect flashings, clean drains below the array, and call the roofing manufacturer before disturbing warranty-covered materials.

If access depends on a roof hatch key, ladder procedure, fall-protection gear, escort, lockout procedure, inverter platform key, fire department access rule, or manufacturer portal, record the access path. A PV asset that technically exists is not maintainable if the owner cannot reach or service it.

If a tenant roof, public amenity roof, green roof, or mechanical penthouse shares the area, separate public movement from maintenance access. Furniture, planters, snow guards, stored materials, and tenant equipment should not block the array path, drain path, or roof warranty inspection route.

Questions that come up

Does a straight, complete-looking PV array mean the roof turnover is ready? No. The record still needs roof baseline photos, flashing evidence, ballast protection evidence, cable routing evidence, drainage access, service route proof, warranty status, and open holds.

Can photos prove the ballast design is correct? No. Photos can show installed ballast, tray positions, block labels, and protection details. The engineer, racking manufacturer output, approved drawings, and applicable code or insurer requirements control the design basis.

Does a flashed mount photo prove the roof warranty is intact? No. It supports the file. The roofing manufacturer's instructions, roofer of record, warranty letter, inspection report, and approved detail control acceptance.

Should the roofing team photograph electrical details? Only visible roof-interface details needed for handoff: cable support, conduit support, penetrations, labels, and access. Electrical compliance belongs to qualified electrical personnel and the AHJ.

What photos cannot prove

Photos are strong evidence for visible roof condition, stanchion location, flashing boot condition, ballast tray position, roof pad presence, slip-sheet placement, wire-management support, conduit support, service path status, drain access, scupper access, labels, and exceptions. They are weak evidence for hidden waterproofing condition, structural capacity, wind resistance, seismic performance, electrical compliance, fire classification, grounding and bonding continuity, or warranty coverage.

Keep those limits visible in the packet. If the release depends on an engineer letter, AHJ inspection, manufacturer observation, electrical test, thermographic inspection, roofing warranty letter, torque report, ballast calculation, fire marshal approval, or safety plan, attach that document or cite its number.

This protects both sides of the handoff. Construction can show what was visible and accepted at turnover, while operations can see which approvals must be found elsewhere.

Compliance and safety limits

This field note is not a PV design, structural review, wind design, seismic design, ballast calculation, electrical design, grounding or bonding test, rapid-shutdown approval, fire-code approval, roof warranty approval, waterproofing inspection, fall-protection plan, OSHA compliance plan, stormwater review, or authorization to open electrical equipment or roof assemblies. The adopted code, AHJ, engineer, electrician, roofing manufacturer, racking manufacturer, module manufacturer, roofer of record, owner, and site safety procedure control the work.

Do not use this checklist to move ballast, remove modules, open combiner boxes, retorque clamps, alter wiring, cut roof membrane, change flashings, bypass fall protection, walk on skylights, block roof drains, relocate access pathways, or accept hidden damage without authorization. The packet preserves visible array-turnover evidence. It does not make the rooftop PV system safe, compliant, warranted, energized, or approved by itself.

Sources checked

• FM, Data Sheet 1-15 Roof-Mounted Solar Photovoltaic PanelsUsed for rooftop PV layout, spacing, roof-cover protection, ballast, wind design, slip-sheet friction, mechanically fastened roof-cover, and inspection context.
• Unirac, RM10 EVO flat roof racking product pageUsed for official product context around RM10 EVO ballasted racking, roof pads, and wire-management accessories.
• Unirac, RM10 and RM10 EVO roof pad technical bulletinUsed for roof pad function, quantity, and roof-surface compatibility context while leaving actual requirements to the project documents.
• Unirac, technical libraryUsed as the current official Unirac document source for install manuals, product data, certification, wire-management, and roof-pad references.
• IronRidge, Ballasted Roof Mount Installation ManualUsed for ballasted roof mount warranty, roof manufacturer coordination, debris removal, protective barriers, walkway clearance, wire clips, and inspection context.
• IronRidge, Ballasted Flat Roof Documents and ResourcesUsed for current document source context for IronRidge ballasted flat roof mounting systems.
• IronRidge, QuickMount ComponentsUsed for QuickMount component context, conduit mounts, wire clips, flashing-equipped products, sealant guidance, and roof warranty coordination.
• IronRidge, QuickMount Product DocumentsUsed as the current official QuickMount document source for roof attachments, flashing, conduit, and legacy mount references.
• Quick Mount PV, QMCS SolarMount-I installation guideUsed from cached installation text for flashing, roof-compatible sealant, written-instruction warranty limits, and shingle mount documentation context.
• NYSERDA, New York Solar Guidebook Section 11 Rooftop Access and VentilationUsed for rooftop PV access pathway examples and for the limit that final compliance belongs to the local code official.
• ICC, 2021 International Fire Code, Section 1205.2 Access and pathwaysUsed for official rooftop PV access and pathway context while leaving adopted-code interpretation to the AHJ.
• NFPA, Providing Access to Roofs with a PV SystemUsed for fire-service roof access and PV accessway context.
• OSHA, 29 CFR 1926.501, Duty to have fall protectionUsed for roof access safety boundaries, unprotected sides and edges, holes and skylights, walkways, low-slope roofing work, and steep roof context.
• OSHA, Fall Protection in ConstructionUsed as plain-language OSHA support for construction fall-protection duties and roof-work safety context.

Related guides