Roof drainage storm turnover record

Direct answer

A roof drainage storm turnover record should prove the visible drainage chain before the roof is released to the owner for storm exposure. It should identify the roof area, phase, drain area, primary roof drain, secondary overflow drain or overflow scupper, leader, conductor head, downspout, nozzle, splash pad or splash pan, discharge point, ponding evidence, debris condition, roof membrane or flashing tie-in, correction, retest or follow-up basis, maintenance handoff, and open exceptions.

The record should be more specific than roof drains cleared or drainage accepted. A useful packet lets the owner find Roof Area B, Drain RD-4, Overflow Scupper OS-4, Leader L-4, the splash pan below the leader, the ponding mark upslope of the sump, the strainer condition, the before-cleaning photo, the corrected photo, the maintenance note, and the final release decision without guessing which opening was reviewed.

This record is not a roof-drain sizing calculation, code ruling, structural rain-load review, warranty approval, water-test procedure, leak investigation, or permission to access the roof. The adopted code, AHJ, plumbing design, structural design, roof consultant, manufacturer instructions, warranty provider, owner procedure, and site safety plan control those decisions. The purpose here is narrower: preserve the observed drainage evidence before storm turnover so the next reviewer can see what was accepted, what was excluded, and what still needs attention.

Define the storm turnover boundary

Start by naming exactly what is being turned over. A strong boundary says Building 2, Roof Area B, grids C through F and 5 through 9, drains RD-3 and RD-4, overflow scuppers OS-3 and OS-4, leader L-4, the north splash pan, and the adjacent parapet pocket. A weak boundary says roof drainage complete and leaves the owner to determine whether the record applies to one roof area, all roof areas, a temporary phase, or a previous repair.

Storm turnover also needs a time boundary. State whether the roof is being released after membrane installation, after coating, after a repair, after drain replacement, after housekeeping, after a storm-leak response, or before the first owner-maintained storm season. If a roof phase is still under temporary tie-in, partial dry-in, or night-seal protection, do not let a final-sounding drainage record cover work that remains temporary.

Name the exclusions as clearly as the inclusions. A record can accept primary drain RD-4 and overflow scupper OS-4 while holding the wall counterflashing, a blocked underground storm connection, a damaged downspout at grade, a structural ponding review, or an interior stain investigation. Bounded acceptance protects both sides: the owner knows what was checked, and the contractor is not accidentally accepting conditions outside the reviewed drainage path.

Separate roof areas and drainage paths

A low-slope roof may have multiple drain areas that look similar in photos. Separate them by roof area, drain ID, overflow ID, leader ID, and discharge point. Do not let one clean drain photo represent every drain on the roof unless the project record plainly says a representative sample is being used and the responsible reviewer accepts that limit.

Primary and overflow paths should be documented separately. The primary path may be a roof drain to interior storm piping, a scupper to a conductor head, or a gutter to a downspout. The overflow path may be a higher drain with a water dam, an overflow scupper through a parapet, a separate overflow leader, or another project-specific arrangement. The record should show which path is normal drainage and which path is emergency or secondary overflow.

Also separate visible drainage from hidden drainage. The roof record can show the sump, strainer, clamping ring, overflow opening, sleeve face, leader, conductor head, downspout, splash pad, and discharge surface. It cannot prove the hidden storm piping, underground connection, wall cavity, drain bowl interior, or structural rain-load capacity unless those items were exposed, tested, or reviewed under the controlling procedure.

Start with source documents

Collect the approved roof plan, plumbing roof-drain plan, roof details, drain schedule, overflow scupper details, tapered insulation layout, sheet-metal details, coating or membrane detail, manufacturer instructions, warranty closeout form, owner standard, maintenance plan, punch list, and safety plan before walking the roof. The field photos should be compared to the accepted basis, not used to create a new drainage design.

The source set reviewed for this package supports that split. WBDG UFC roofing material points to positive drainage and plumbing coordination, while the Holcim Elevate design guide places adequacy of drainage provisions, placement, sizing, and number of drains with the owner or design professional. Zurn roof-drain material gives hardware and selection context but also points actual applications back to local codes. Those sources support careful documentation without turning the article into a sizing manual.

Sheet-metal sources matter because storm drainage often leaves the membrane field. WBDG UFGS flashing and sheet-metal material covers gutters, downspouts, scuppers, conductor heads, splash pans, roof-drain flashing, repairs to finish, and field quality-control documentation. The copper sheet-metal UFGS has useful language for downspouts, scupper linings, splash pans, and documenting quality-control observations. The project documents still control the installed materials, but the record should follow the same component logic.

Build a roof drainage map

The drainage map is the index for the turnover packet. Mark roof areas, drains, overflow drains, scuppers, leader routes, conductor heads, downspouts, nozzles, splash pads, splash pans, grade discharge areas, ponding marks, and held conditions. Use the project IDs if they exist. If they do not exist, create temporary field IDs and state that they are field record IDs, not design document revisions.

The map should let a maintenance person stand at the roof hatch and find each drainage item without interpreting a pile of photos. For example, RD-2 can mean primary roof drain at Roof Area A, north sump, served by interior storm piping. OS-2 can mean overflow scupper through the north parapet, paired with RD-2, discharging to conductor head CH-2 and downspout DS-2. SP-2 can mean splash pad at the bottom of DS-2. Each ID should appear in the photo captions and checklist.

Name partial roof areas in field terms as well as drawing terms. A drawing grid can be precise, but a storm-response technician may search by roof hatch, penthouse, parapet run, loading dock, canopy, stair tower, mechanical screen, or tenant space below. Good records include both: Roof Area B, grids C through F and 5 through 9, north of Air Handler 2, draining toward RD-4 and OS-4. That wording helps people find the drainage area quickly during rain without turning the turnover note into a new drawing.

Keep the map honest when construction changes occur. If a leader was rerouted, a splash pan was added, a scupper liner was replaced, a drain strainer changed, or a ponding mark was created during a later storm, update the map or add a dated markup. Do not hand over a clean map that no longer matches the roof. The owner will use that map during a storm call, not during a drawing-room review.

Record primary roof drains

Each primary roof drain record should show the drain ID, roof area, sump condition, drain bowl or visible throat, clamping ring, bolts where visible, flashing clamp or gravel guard, dome strainer, debris condition, membrane or coating tie-in, nearby seams or patches, surrounding slope, and direction of view. If a drain is hidden under temporary protection or snow, state that the drain was not fully visible rather than implying full review.

UFGS TPO material reviewed for this package includes roof-drain flashing, tapered insulation at drain sumps, water block, membrane secured in a clamping ring, debris removal, closeout submittals, and drain test context. Holcim Elevate application material also describes drain preparation, clamping ring work, water block seal, clean mating surfaces, and debris removal. Zurn material identifies roof drain components such as a body or sump, flashing clamp or gravel guard, and dome strainer. These sources support a component-level photo record.

The record should not say the drain is adequately sized, code compliant, or structurally sufficient. It can say the visible drain components were photographed, the strainer was present or missing, debris was removed under the project procedure, the membrane tie-in was accepted by the responsible reviewer, and the drain was included or excluded from the storm turnover boundary. Capacity belongs to the plumbing design, structural design, adopted code, and reviewer of record.

Record overflow drains and scuppers

Overflow devices deserve their own line in the record, not a footnote under primary drains. Record the overflow drain or scupper ID, paired primary drain if any, visible inlet elevation relationship if it is part of the accepted record, water dam or opening condition, sleeve, liner, flange, corners, membrane tie-in, metal interface, collector or conductor head, and discharge route.

Holcim Elevate application material reviewed for this package states that scuppers can refer to primary and overflow devices for roof drainage and lists drain and scupper details including overflow drains and overflow through-wall scuppers. UFGS flashing and sheet-metal material discusses scupper liners, scuppers projecting through walls, conductor heads, and splash pans. Zurn material includes main roof and overflow drains, scupper drains, parapet scupper sleeves, downspout adapters, and downspout covers. Those are strong anchors for documenting the visible overflow chain.

Do not treat an overflow photo as proof that the system is designed correctly. The record can preserve what was observed: the opening exists, the throat was clear or blocked, the conductor head was present, the leader was connected, and the discharge was visible. It cannot approve the number, size, location, inlet elevation, rain-load capacity, or structural consequences of overflow water unless the qualified reviewer has made that determination in the controlling record.

Trace leaders, conductor heads, and downspouts

A storm turnover packet should follow water beyond the roof opening when the visible path is part of the handoff. Photograph conductor heads, leaders, downspouts, straps, offsets, boots, nozzles, hinged covers, screens, elbows, transitions through walls, and discharge points. If the route disappears into a wall, below grade, or behind cladding, say where visibility stops.

WBDG UFGS 07 60 00 gives sheet-metal context for gutters, downspouts, conductor heads, supports, drainage connections, splash blocks, and splash pans. The copper sheet-metal UFGS discusses downspouts, leader heads, leader straps, basket strainers, splash pans, and documenting quality-control observations. Zurn material includes downspout boots, downspout nozzles, downspout covers, and scupper drain accessories. Together, those sources support a full visible-path record.

Leader discharge is often where a clean roof record becomes weak. A scupper may look acceptable at the parapet while the conductor head is loose, the downspout strap is missing, the lower elbow is crushed, the boot is displaced, or the discharge dumps onto an unprotected roof surface. The turnover record should show the complete visible path that the owner is expected to maintain.

Document splash pads, splash pans, and discharge

Where a leader or downspout discharges onto a roof surface, canopy roof, grade area, or paved surface, photograph the landing condition. Name whether the accepted detail calls it a splash pad, splash pan, splash block, roof pan, apron, outlet pad, boot, nozzle, or other project term. The field record should use the project language and then show the actual discharge location.

Splash protection is not decorative in the closeout record. It shows where water will land during a storm, whether that landing area is protected, whether the discharge can erode ballast or soil, whether it directs water back toward a wall, whether the lower roof membrane is protected, and whether maintenance can see the outlet. UFGS sheet-metal sources reviewed for this package specifically include splash pans and downspout discharge onto roof surfaces, which makes them useful support for photographing this part of the path.

Do not claim that the splash pad is correctly sized or hydraulically adequate unless the approved detail or responsible reviewer says so. A field photo can show location, material, damage, missing condition, displacement, blockage, relation to the outlet, and correction. It should not become a design approval for water velocity, erosion, overflow rate, or downstream storm connection.

Preserve ponding and stain evidence

Ponding evidence is a baseline, not automatically a failure or an acceptance. Photograph water, dirt rings, algae lines, sediment, stain marks, roof-surface depressions, high rings around sumps, membrane wrinkles, displaced walkway pads, low spots near walls, and signs that water has bypassed or stopped short of a drain. Include a wide photo that shows the condition relative to the drain and a close photo that shows the mark.

WBDG UFC roofing material reviewed for this package emphasizes positive drainage and drainage-system maintenance, and it warns that debris and excessive ponding can create serious risk. Holcim Elevate design material discusses drainage and slope, positive drainage, existing deck deflection or ponding water, and the responsibility of the owner or design professional for drainage provisions. The Holcim tapered insulation source discusses drain proximity, back slope, crickets, and areas where ponding may occur. These sources support documenting ponding evidence without approving it.

Record the time context. A photo taken during rain, six hours after rain, two days after rain, after a plugged drain was cleared, or after a temporary roof phase does not mean the same thing. The field note should state when the observation happened and what changed afterward. If the owner or consultant requires a follow-up after the next rain, list that as an open item instead of treating the first dry-weather photo as final evidence.

Photograph before cleaning

The best drainage evidence is often present before housekeeping. Leaves, membrane scraps, fasteners, ballast, granules, coating skins, loose insulation facer, drink bottles, sediment, bird-stop debris, or construction waste may explain why water did not move. If the first photo shows only a clean strainer, the packet may lose the condition that justified the correction.

Take a before-cleaning photo for each affected drain, scupper, conductor head, leader inlet, splash pan, and discharge area. Then take an after-cleaning photo from the same general angle. When the site safety or emergency response procedure requires immediate clearing, write who directed the action and photograph the condition as soon as practical. Do not delay urgent water removal only to make a better packet.

Cleaning evidence should be tied to maintenance handoff. If a roof was clean at turnover but surrounded by trees, construction dust, masonry work, loose ballast, or rooftop equipment work, the owner needs to know what routine inspection or cleaning obligation remains. The record should not imply that one cleaning makes the drainage path self-maintaining.

Capture strainers, guards, and debris

Strainers, guards, screens, baskets, and covers are small items with large handoff consequences. Photograph whether they are present, seated, damaged, loose, blocked, temporarily removed, or excluded. Include close photos of fasteners or clips when they are visible and relevant to the accepted condition. If the strainer was removed for work and reinstalled after photos, record both steps.

Zurn roof-drain material reviewed for this package identifies dome strainers, flashing clamps or gravel guards, secondary strainers, flat strainers, downspout covers, and debris-prevention options. Holcim application material repeatedly requires clean surfaces and debris removal for roof work, and UFGS TPO material includes removal of debris, scraps, containers, rubbish, and trash. Those sources support treating debris control as a record item, not an afterthought.

A blocked strainer should not be quietly cleaned and accepted without context. Record what blocked it, whether the obstruction was construction-related or maintenance-related, whether downstream piping was checked under the project procedure, and whether the owner accepts the condition. If debris keeps returning from an adjacent trade, equipment platform, tree canopy, or wall repair, that recurrence belongs in the exception log.

Tie the drainage item to roof flashing

Drainage handoff is not only about holes in the roof. The record should show the roof membrane, coating, flashing, metal, sealant, corners, fasteners, clamping rings, water block basis where applicable, and transitions around each drain or scupper. A clear opening with a weak flashing tie-in can still be the wrong turnover record.

For primary drains, include photos of the sump transition, membrane cut, clamping ring, strainer, and nearby seams or patches where visible. For scuppers, include the roof-side flange, sleeve, liner, corners, wall interface, metal face, collector head, and any membrane or coating detail. For leaders and downspouts, include attachment points, straps, offsets, lower elbows, boots, nozzles, and splash protection.

When repairs were made, preserve the repair chain. Keep the pre-repair photo, repair basis, repair owner, corrected photo, reviewer decision, and follow-up requirement together. A final photo with no repair history forces the next reviewer to wonder whether the condition was original, corrected, temporary, or never checked.

Record test or follow-up basis

Every storm turnover record should say how acceptance was determined. The basis might be visual observation, roof consultant walk, manufacturer representative walk, owner maintenance acceptance, documented cleaning, drain test under the specification, water test under a separate procedure, later rain observation, or monitoring after the next storm. The basis should be explicit.

UFGS TPO material reviewed for this package includes roof-drain test language and specifically warns not to plug secondary overflow drains at the same time as adjacent primary drains during the drain test described there. That is a good example of why field writers should not invent a test. The project specification, consultant, manufacturer, and safety plan must define whether testing is required and how it is done.

If no test was performed, say so and name the accepted basis. Visual closeout may be appropriate for some work and insufficient for other work. Later rain observation may be useful, but it depends on the storm, boundary, and observation method. Monitoring may be an owner maintenance obligation rather than contractor completion. The record should make the decision traceable instead of hiding the basis behind accepted.

Hand the record to maintenance

Storm turnover is not complete if the owner receives a folder that cannot be used during a storm call. The handoff should include the drainage map, photo index, accepted roof areas, open exceptions, maintenance access path, safety restrictions, drain and scupper IDs, leader and splash-pad IDs, manufacturer instructions, cleaning notes, and contact or warranty routing required by the owner.

WBDG UFC roofing material reviewed for this package emphasizes operations and maintenance, periodic inspection, housekeeping, clearing drainage systems, checking drains and flashings, and removing debris to prevent excessive ponding. That supports handing over a maintenance-ready record, not just a construction closeout snapshot.

Maintenance handoff should also say what changed from construction to owner responsibility. If temporary protection was removed, a drain strainer was reinstalled, a leader was connected, a lower splash pad was set, a roof area was cleaned, or an exception was transferred to the owner, record the date and reviewer. The owner should not have to infer responsibility from a series of unlabeled photos.

Separate temporary and final storm exposure

A roof may be released for limited storm exposure before it is fully complete. That situation needs different language than final owner turnover. Temporary storm exposure might apply to a night seal, a phased reroof, a partial coating release, a repaired scupper before permanent sheet metal arrives, or a lower roof used as a discharge path while adjacent work continues. The record should say temporary, conditional, or final instead of relying on broad accepted language.

Temporary exposure records should name the temporary controls. Examples include temporary strainers, weighted covers, temporary leaders, temporary splash protection, temporary tie-ins, monitored drains, open punch items, or areas that must be checked after each rain until final work is complete. If those controls are not intended to remain through owner turnover, the packet should say when they are removed or replaced.

Final storm turnover should not rely on temporary assumptions. Before a record changes from temporary to final, verify that drain strainers are installed, scuppers and leaders match the accepted details, lower discharge is in its final condition, temporary debris controls are removed or converted to permanent controls, and open monitoring items are resolved or transferred to the owner in writing.

This distinction matters during disputes because a temporary record can be useful without being final acceptance. A temporary note can say Roof Area C is released for overnight storm exposure after drain clearing and night-seal work, with superintendent inspection required after rain. A final note should be tighter: Roof Area C drains, overflow scuppers, leaders, splash pads, ponding marks, corrections, maintenance notes, and exceptions have been reviewed under the owner turnover procedure.

Include interior and lower-roof witness points

A drainage turnover record often starts on the roof, but storm calls rarely stay there. If the owner has known interior stain locations, lower-roof discharge points, canopy roofs, loading dock aprons, exterior walls, occupied rooms, or finished areas below, identify the witness points that connect roof drainage to the owner complaint or maintenance concern. A roof-only packet can miss the place where water will actually be noticed.

Interior witness points should be factual and limited. Record room name, ceiling grid, wall line, column line, equipment below, prior stain location, active drip if present, and whether the area was included in the storm turnover walk. Do not diagnose the interior condition unless the assigned reviewer has done that work. The purpose is to connect the roof drainage boundary to the owner-visible location without turning the packet into a leak investigation report.

Lower-roof witness points matter when leaders, scuppers, or downspouts discharge onto another roof surface. Photograph the receiving roof, splash pan, membrane protection, nearby seam or flashing, ponding mark, debris trail, and path to the next drain. If water from an upper roof crosses a lower roof before it reaches a drain, the turnover record should show that route or state that the lower roof was outside the boundary.

ASTM D7053 material reviewed for this package supports defined scope, service history, adjacent construction, professional judgment, and report limitations for low-slope roof leakage evaluation. That context is useful even when this article is not a leak investigation guide. It reminds the field team to say what was included, what was excluded, and what should not be inferred from a limited roof-drainage walk.

Keep an exception log

The exception log is where the turnover record earns its value. It should list each open or corrected condition with an ID, location, photo reference, responsible party, due date or follow-up trigger, reviewer, and release status. Do not bury exceptions in paragraph notes that the owner will not find during the next storm.

Use clear status language. Accepted means the responsible reviewer accepted the item within the stated boundary. Corrected means a condition was changed and documented. Monitoring means the owner or contractor will watch a stated condition after rain or after a stated time. Held means the item is not released. Transferred means responsibility moved to another scope, reviewer, phase, or owner maintenance process.

Exceptions should be specific enough to act on. OS-4 throat cleaned is weaker than OS-4 leaf and granule debris removed from overflow throat, after photo RB-039, maintenance to recheck after first storm because adjacent tree canopy remains. SP-4 missing is weaker than SP-4 splash pan not installed at L-4 lower roof discharge, discharge currently lands on exposed membrane, held for sheet-metal completion.

The log should survive closeout. A closeout platform, warranty packet, owner maintenance file, or commissioning report may reorganize the documents. Keep the exception IDs stable so the same item can be found in the article checklist, photo index, punch list, and owner handoff note. Stable IDs are less glamorous than photos, but they are what keep a storm turnover record usable months later.

Inspection table

Use a compact table so the roofer, roof observer, plumbing reviewer, owner, and maintenance crew look at the same drainage evidence.

Storm turnover checklist

Run this checklist before releasing a roof drainage area to the owner for storm exposure.

• Roof area, phase, storm exposure boundary, included drains, overflow devices, and exclusions are named.
• Approved roof plan, plumbing plan, drainage details, manufacturer instructions, and owner turnover form are attached or referenced.
• Primary roof drains have unique IDs that match the roof drainage map and photo captions.
• Overflow drains or overflow scuppers have separate IDs and are not merged with primary drain records.
• Each visible drain sump, clamping ring, strainer, gravel guard, membrane tie-in, and debris condition is photographed.
• Each visible overflow scupper or overflow drain opening, sleeve, liner, flange, water dam, and conductor head is photographed.
• Leaders, downspouts, straps, boots, nozzles, covers, and visible route limits are photographed.
• Splash pads, splash pans, splash blocks, discharge surfaces, and missing or displaced protection are photographed.
• Ponding, dirt rings, water lines, algae marks, sediment, stains, and low areas are photographed before cleaning where practical.
• Before-cleaning and after-cleaning photos are paired for drains, scuppers, leaders, and discharge areas that were corrected.
• Removed strainers, replaced hardware, cleared debris, repaired flashing, and reset splash protection are tied to correction photos.
• Test method or follow-up basis is named, or the record states that no test was performed.
• Drainage sizing, code compliance, structural rain load, and warranty acceptance are not claimed unless accepted in a controlling record.
• Owner maintenance notes include cleaning frequency basis, access limits, safety limits, and recurring debris risks if known.
• Open exceptions are assigned to a responsible party and are not hidden inside accepted language.
• Final release says which roof areas, drains, overflow paths, leaders, splash pads, and exceptions are accepted.

Weak versus strong record

Weak record: Roof drains clear, overflow scuppers open, downspouts connected, roof ready for storm.

That note does not identify the roof area, primary drain IDs, overflow IDs, leaders, splash pads, ponding marks, debris condition, before-cleaning evidence, flashing tie-ins, test basis, exclusions, or maintenance handoff. It might be true, but the owner cannot use it during a storm call without rediscovering the roof.

Strong record: Roof Area B was reviewed on June 9, 2026 for storm turnover. Primary drains RD-3 and RD-4, overflow scuppers OS-3 and OS-4, conductor heads CH-3 and CH-4, leaders L-3 and L-4, downspouts DS-3 and DS-4, and splash pads SP-3 and SP-4 are shown on markup R-B-Drainage-01. Photos RB-001 through RB-010 show the roof area, hatch access, drain map, and accepted safety boundary. Photos RB-011 through RB-030 show each primary drain before cleaning, after cleaning, strainer condition, clamping ring visibility, surrounding sump, and nearby ponding marks.

The same record says OS-4 had roofing granules and leaves at the throat before cleaning, L-4 had a loose lower strap, and SP-4 was shifted four inches away from the downspout elbow. Photos RB-031 through RB-038 show those conditions. The contractor cleared OS-4, reset the L-4 strap, centered SP-4 under the elbow, and added after photos RB-039 through RB-045. No drain sizing, code compliance, or warranty acceptance is claimed in the field note. The roof consultant accepted Roof Area B for storm turnover except for a separate interior stain investigation below grid F/7, which remains open.

The strong note works because it keeps the roof area, drainage map, failed conditions, corrections, limits, and acceptance decision in one traceable chain. It does not need dramatic language. It needs enough evidence for the next person to find the same drain during rain.

Common mistakes

The first mistake is documenting only the clean final condition. Final photos matter, but they do not explain why the drain was held, what debris was present, where water ponded, what hardware was missing, or what changed before release. Keep the before condition with the corrected condition.

The second mistake is mixing primary drainage and overflow drainage into one sentence. A primary drain, overflow drain, overflow scupper, leader, conductor head, and splash pad may all be part of one storm story, but they need separate IDs. Without separation, the owner cannot tell whether a later problem is in the normal drainage path, emergency overflow path, or discharge path.

The third mistake is overclaiming from a photo. A photo can show a clear strainer, an open scupper, a centered splash pad, or no visible water at the time of observation. It does not prove code compliance, design storm performance, structural adequacy, or long-term warranty acceptance. Those claims require the controlling reviewer and record.

The fourth mistake is losing the lower discharge condition. Roof teams often photograph the scupper opening and forget the leader boot, downspout elbow, splash block, grade discharge, lower roof pan, or pavement area where water lands. Storm turnover should follow the visible path to its visible end.

The fifth mistake is failing to state what remains open. A drainage area can be accepted for temporary storm exposure while a ponding analysis, downspout replacement, interior stain watch, underground piping concern, or warranty review remains open. Clear holds are better than broad acceptance.

Hold triggers

Hold storm turnover when the drainage path cannot be identified. If the field team cannot tell which primary drain pairs with which overflow scupper, which leader receives which scupper, or where the discharge lands, the packet is not ready. The first correction may be a map correction rather than roof work.

Hold when visible hardware is missing or inconsistent with the accepted basis. Examples include missing dome strainers, loose clamping rings, absent conductor heads, damaged downspout straps, displaced splash pads, open scupper sleeves, unprotected lower roof discharge, or a roof detail that does not match the approved drawing. Record the condition and assign the reviewer instead of burying it.

Hold when ponding evidence suggests a design or structural question that the field team cannot answer. A water line, dirt ring, or low area does not automatically fail the turnover record, but it may require the roof consultant, plumbing designer, structural engineer, manufacturer, warranty provider, or owner to decide the next step.

Hold when testing or follow-up is required but not complete. If the specification, consultant, manufacturer, owner, or warranty provider requires a drain test, water test, later rain observation, or monitoring period, the release note should say pending rather than accepted. A checklist is not a substitute for a required test.

Photo index and file names

Photo file names should make the packet searchable. A useful pattern is roof area, item ID, condition, and sequence: RA-B-RD04-before-cleaning-01, RA-B-RD04-after-cleaning-02, RA-B-OS04-throat-03, RA-B-L04-strap-correction-04, RA-B-SP04-centered-05. The exact pattern matters less than consistency.

Each caption should answer what, where, when, and why. For example: Roof Area B, RD-4, drain sump before cleaning, looking south, June 9, 2026, roofing granules at strainer. A caption that says drain photo is not enough if the roof has ten similar drains.

Keep wide, medium, and close photos together. The wide photo locates the item on the roof. The medium photo shows its relation to ponding, parapet, slope, leader, or splash pad. The close photo shows the drain throat, scupper sleeve, strainer, clamp, debris, sealant, or repair. A close-up without context becomes a parts photo.

If the owner uses a digital closeout platform that renames files, upload a photo schedule with the packet. The schedule should cross-reference platform file names, original file names, drainage IDs, and checklist items. The record should survive outside the phone or tablet used during the walk.

What not to claim

Do not write that the roof drainage is code compliant unless the adopted code reviewer or AHJ record says so. Current ICC model-code routes are useful context, but every project depends on the adopted edition, amendments, AHJ interpretation, and the plumbing and structural design documents.

Do not write that the roof has positive drainage unless the controlling reviewer accepts that statement. If the field record only shows no standing water at one observation time, write that instead. If ponding marks remain visible, record them and state whether they are accepted, held, or assigned for review.

Do not write that drains are properly sized, overflow is adequate, or rain load is acceptable unless the design professional has made that determination. Zurn material can help identify components and selection considerations, but actual applications depend on local codes and project design. Holcim material reviewed for this package also places drainage adequacy with the owner or design professional.

Do not write that warranty is approved unless the warranty provider has accepted the condition. The field packet can support warranty closeout by showing evidence, but it does not replace the warranty provider's requirements, inspection, or decision.

Do not use the checklist as permission to access the roof, lean over edges, open drains, plug drains, remove covers, test water, move downspouts, alter scuppers, or bypass safety controls. Qualified personnel and the site procedure control the work.

Questions that come up

Does every drain need its own photo? For a serious storm turnover packet, every included drain and overflow device should have identifiable evidence unless the owner and reviewer accept a different sampling plan. If sampling is used, write the sampling limit plainly.

Is a dry roof photo enough? A dry photo helps, but it is not enough by itself when the issue is storm readiness. The record should also show the drainage map, drain and overflow hardware, visible discharge path, debris condition, ponding marks if any, cleaning or correction, and the accepted follow-up basis.

Should the packet include water testing? Only if the project procedure requires it or the responsible reviewer directs it. If water testing is performed, the record should name the test boundary, reviewer, result, and limits. The field article should not invent a universal water-test method.

Should ponding marks always block turnover? No. Some marks may be accepted, some may need monitoring, and some may indicate a design or structural question. The field record should preserve the evidence and state the reviewer decision instead of treating every mark the same.

Does a clear overflow scupper close the drainage record? Not by itself. The record should still show the paired primary path, roof area, visible opening, leader or conductor head, splash protection, ponding evidence, and any limits on what was observed.

Compliance and safety limits

Treat this article as a field documentation structure, not a final code, plumbing, structural, warranty, or safety ruling. The adopted code edition, AHJ, plumbing engineer, structural engineer, roof consultant, manufacturer, warranty provider, project specifications, owner standards, and closeout procedure control the actual acceptance requirements.

Do not use this checklist to size roof drains, locate overflow scuppers, calculate rainfall intensity, calculate ponding instability, approve positive drainage, approve structural rain load, approve storm piping, or certify warranty compliance. Those decisions belong to qualified reviewers using the controlling documents.

Do not access a roof, approach a roof edge, step near skylights or openings, remove covers, open drains, plug drains, perform water testing, clear debris during unsafe weather, move sheet metal, alter leaders, or work near electrical or mechanical equipment unless the site safety plan and qualified personnel allow it. OSHA fall-protection requirements, site-specific controls, and the employer's safety program control the work.

If a condition appears unsafe, outside the approved details, hidden from view, or beyond the field team's authority, record the visible facts and hold the item for the proper reviewer. A good turnover record does not make uncertain conditions look certain. It makes the uncertainty visible enough to manage.

Sources checked

• ICC Digital Codes, 2024 International Building Code, Chapter 15Used as current official model-code route context for roof assemblies, roof drainage, secondary overflow drains or scuppers, and AHJ/adopted-code framing.
• ICC Digital Codes, 2024 International Plumbing Code, Chapter 11Used as current official model-code route context for storm drainage and plumbing-code coordination.
• WBDG, UFC 3-110-03 RoofingUsed for positive drainage, IPC Chapter 11 coordination, roof maintenance, clearing drainage systems, drain inspections, working drains during reroofing, debris removal, and fall-protection context.
• WBDG, UFGS 07 54 23 Thermoplastic Polyolefin RoofingUsed for roof drain flashing, drain sump tapered insulation, clamping rings, water block, debris removal, closeout submittals, roof drain test context, and secondary overflow drain test limits.
• WBDG, UFGS 07 60 00 Flashing and Sheet MetalUsed for gutters, downspouts, scuppers, conductor heads, splash pans, roof-drain flashing, quality-control documentation, and repairs to sheet-metal finish.
• WBDG, UFGS 07 62 13 Copper Sheet Metal Flashing and TrimUsed for downspouts, leader heads, leader straps, scupper linings, splash pans, downspout discharge onto roof surfaces, and field quality-control observation records.
• Holcim Elevate, UltraPly TPO Roofing Systems Application GuideUsed for roof drains, clamping rings, water block seal, debris removal, scuppers as primary and overflow drainage devices, welded watertight sleeves, and drain/scupper detail context.
• Holcim Elevate, UltraPly TPO Roofing Systems Design GuideUsed for drainage and slope, positive drainage, owner/design-professional responsibility for drainage provisions, existing ponding analysis, and manufacturer drainage-design limits.
• Holcim Elevate, Tapered Insulation Design SolutionsUsed for tapered insulation, drain proximity, back slope, crickets, and ponding-potential context around roof drains.
• Zurn, Roof Drains Engineering GuideUsed for roof drain bodies, sumps, flashing clamps, gravel guards, dome strainers, overflow drains, scupper drains, downspout boots, downspout covers, and local-code sizing limits.
• ASTM D7186-25, Standard Practice for Quality Assurance Observation of Roof Construction and RepairUsed for QA observation, visual monitoring, recording, reporting, contract-document comparison, repairs, scheduled maintenance, and observer scope limits.
• ASTM D7053/D7053M-17(2024)e1, Standard Guide for Determining and Evaluating Causes of Water Leakage of Low-Sloped RoofsUsed for leak-evaluation scope, service history, adjacent construction, professional judgment, report limitations, and realistic expectations for defined-scope roof reviews.
• IIBEC, Secondary Drainage and Ponding Requirements in the IBC and IEBCUsed for industry discussion of secondary drainage, scuppers, leaders, conductors, ponding, positive drainage, and code-path differences for roof work.
• OSHA, 29 CFR 1926.501 Duty to Have Fall ProtectionUsed for roof-work safety limits around walking and working surfaces, unprotected edges, holes, low-slope roofing work, and fall-protection duties.
• OSHA, 29 CFR 1926.502 Fall Protection Systems Criteria and PracticesUsed for guardrails, covers, warning lines, personal fall-arrest systems, and fall-protection system criteria.

Related guides