ANVILFIELD Get Field Notes

Field Notes

Scupper overflow opening records before storm leak punchlist closeout

A useful storm leak closeout packet ties the punch item, roof area, primary and overflow paths, scupper opening, sleeve, flange, liner, debris, ponding evidence, repair, follow-up, photos, limits, and reviewer decision together.

Direct answer

Before closing a storm leak punchlist item involving a scupper or overflow opening, record the punch item ID, interior symptom, storm date, roof area, drain area, primary drainage path, overflow path, scupper or overflow ID, approved detail basis, opening location, observed opening condition, throat or sleeve condition, liner, flange, collar, collector head, downspout or leader status, membrane or coating tie-in, sealant, fasteners, wall or parapet interface, debris or blockage evidence, ponding or stain line, repair made, test or follow-up method, photos before and after correction, remaining limits, responsible reviewer, and closeout decision.

The record should prove what was visible and what was closed. It should not turn a storm-response note into a roof-drain sizing calculation, code ruling, hydraulic approval, warranty acceptance, or promise that every future storm will perform the same way.

Use this as documentation guidance only. The project drawings, plumbing design, roof consultant, designer, manufacturer, AHJ, owner, warranty provider, water-test professional, and site safety plan control the actual drainage design, repair method, test method, and punchlist closeout.

Storm closeout needs a drainage boundary

A storm leak punch item is weak if it only says scupper cleared or leak fixed. The next reviewer needs to know which roof area was involved, which interior symptom was tied to the exterior work, which storm started the ticket, and which drainage opening was inside the closeout boundary.

Set that boundary in field language. Name the building, roof level, gridline, parapet elevation, drain area, scupper number, overflow opening, leader, downspout, collector head, room below, ceiling stain, wall line, and punch item. If the roof has several similar openings, do not let one close-up stand for all of them.

Also name the exclusions. A closeout can apply to overflow scupper OS-2 while the primary drain RD-4, a wall counterflashing condition, a coping joint, a mechanical curb, or an interior condensation question remains open. Bounded closeout is more useful than broad language nobody can defend.

Separate primary and overflow paths

Primary drainage and overflow drainage are not the same record item. The packet should show where the roof is intended to drain first, where emergency overflow is intended to happen if the primary path is restricted or exceeded, and which opening was related to the storm complaint.

For each path, record the visible route from roof surface to outlet. That may include drain sump, scupper throat, overflow opening, water dam, sleeve, leader, conductor head, downspout, discharge point, splash block, grade area, or storm connection. If only part of that path was inspected, write the limit.

Do not size or approve the drainage system from a field photo. The record can document observed location, condition, obstruction, repair, and closeout decision. Drainage capacity, rainfall intensity, overflow sizing, structural rain load, and code acceptance belong to the design documents and qualified reviewers.

Photograph before cleaning or repair

The most important photos often happen before anyone makes the opening look better. Photograph the scupper or overflow opening before cleaning, clearing, sealant work, metal repair, coating repair, sleeve reset, or downspout adjustment.

The first photo should locate the condition. Take a wide roof-area photo, a parapet or wall elevation photo, and a marked plan or sketch if available. Then take closer photos of the opening, throat, sleeve, flange, liner, fasteners, sealant, membrane tie-in, coating, collector head, leader, downspout, and discharge point.

Keep the failed condition visible in the packet. Leaves, ballast, granules, roof-coating bridge, dropped fasteners, construction debris, membrane wrinkle, blocked throat, crushed downspout, loose sleeve, cracked sealant, ponding stain, or water line may explain why the repair was made.

Record the assembly, not just the hole

A scupper opening is an assembly. The record should identify the visible parts: through-wall sleeve, metal liner, welded sleeve where used, roof-side flange, closure flange, rounded corners, membrane flashing, coating or liquid detail, sealant, fasteners, parapet wall, collector head, conductor, leader, downspout, splash pan, and discharge area.

If the opening is an overflow scupper, say so. Record whether it is separate from the primary drain, paired with a primary drain, above a water dam, above the roof surface, or tied to a dedicated downspout. Record only what is observed or shown in the approved documents.

If hidden parts were not opened, do not write them as verified. A closeout photo of a clean exterior face does not prove the hidden sleeve, wall cavity, membrane lap, or pipe connection unless those items were exposed and reviewed under the project procedure.

Preserve storm and ponding evidence

Storm closeout should keep the weather context without pretending the field note is a meteorology report. Record the reported storm date, approximate time window, rain or wind context if available from the project record, interior symptom timing, and whether the follow-up happened after cleaning, repair, water test, later rain, or only visual observation.

Ponding and stain evidence matters around scuppers. Photograph water lines, dirt rings, algae lines, scupper apron staining, wall staining, roof-surface depressions, high rings, blocked valleys, displaced walk pads, low parapet pockets, and nearby seams or patches.

Do not erase the evidence during housekeeping. If debris is removed before photos are taken, the packet loses the condition that may have connected the storm complaint to the opening. If emergency response forced immediate clearing, write who directed it and photograph the condition as soon as practical.

Keep the repair and follow-up chain

The closeout packet should preserve the sequence: punch item, storm or complaint, observed condition, initial photos, hold or emergency action, repair basis, repair, cleaning or debris removal, test if required, later storm follow-up if used, remaining exceptions, and closeout decision.

If a water test is performed, record the responsible reviewer, tested boundary, water source, duration if specified by the reviewer, interior watch location, result, and limits. Do not invent a water-test procedure inside the field note. If no test was performed, state the accepted closeout basis, such as visual repair acceptance, owner direction, manufacturer direction, consultant signoff, maintenance monitoring, or later storm observation.

Keep failed and corrected evidence together. A passing follow-up is stronger when the packet still shows the blocked throat, loose sleeve, open sealant, ponding stain, or failed test that triggered the correction.

Minimum scupper overflow closeout packet

Use the consultant report, warranty form, service ticket, owner punchlist system, and manufacturer closeout form first. Add this field packet where the required form does not connect scupper evidence to the punchlist decision clearly enough.

Record itemField detailWhy it matters
Punch boundaryPunch ID, storm date, interior symptom, room, roof area, gridline, elevationConnects the exterior opening to the actual storm leak item
Drainage pathPrimary drain, overflow scupper, emergency drain, leader, downspout, discharge pointSeparates normal drainage from overflow drainage
Approved basisRoof plan, plumbing plan, scupper detail, manufacturer detail, consultant directionShows what the field condition was checked against
Opening conditionLocation, observed throat, sleeve, liner, flange, collar, apron, water dam, clear openingPreserves the condition before it is changed
Obstruction evidenceLeaves, ballast, granules, coating bridge, dropped material, damaged strainer, collapsed leaderExplains whether the storm issue was blockage, damage, or unresolved design review
Roof tie-inMembrane, coating, flashing, sealant, fasteners, corners, laps, parapet or wall interfaceCaptures water-entry details around the opening
Ponding evidenceStain line, dirt ring, water mark, low area, high point, nearby seam, prior patchKeeps visible storm evidence from disappearing during repair
RepairCleaning, sleeve repair, sealant repair, membrane patch, coating detail, hardware resetShows what actually changed before closeout
Test or follow-upWater test boundary, later storm observation, visual acceptance, monitoring period, limitsDefines what the closeout can and cannot prove
DecisionClosed, partially closed, held for design review, assigned to drainage, assigned to wall reviewPrevents a narrow scupper repair from closing unrelated leak paths

Before storm leak punchlist closeout checklist

Run this check before closing a storm leak punch item tied to a scupper, overflow scupper, or overflow drain opening.

  • Confirm the punch item ID, interior symptom, storm date, roof area, drain area, and closeout boundary.
  • Attach or reference the approved roof plan, plumbing plan, scupper detail, manufacturer detail, or consultant direction.
  • Name the primary drainage path and the overflow path separately.
  • Photograph the roof area wide enough to locate the opening and close enough to show the throat or sleeve condition.
  • Photograph the scupper or overflow opening before cleaning, clearing, coating, sealant work, or metal repair.
  • Record sleeve, liner, flange, collar, fasteners, membrane or coating tie-in, sealant, parapet, collector head, downspout, and discharge condition.
  • Photograph debris, blockage, ponding stains, dirt rings, water lines, wall staining, or roof low areas before correction.
  • Record who authorized emergency clearing if the opening had to be cleared before full documentation.
  • Keep failed photos, repair photos, final condition photos, and retest or follow-up photos together.
  • State the test or closeout basis and its limits.
  • List remaining holds for drainage design, wall review, coping, counterflashing, primary drains, interior repairs, or monitoring.
  • State whether the item is closed, partially closed, or held, and name the responsible reviewer.

Weak and strong notes

Weak note: scupper cleaned, storm leak closed.

That note does not show the punch boundary, interior symptom, roof area, primary path, overflow path, opening condition, debris evidence, sleeve or flashing condition, repair, test, follow-up, remaining limits, or closeout authority.

Stronger note: Punch R-303 for the Level 2 corridor stain below Roof Area B west parapet was checked after the June 9 storm. Closeout boundary is overflow scupper OS-2 from grids C/7 to C/8 and the adjacent interior watch area. Primary drain RD-4, wall counterflashing beyond C/8, and coping joints were excluded and remain under separate review. Before-cleaning photos show leaf debris and roofing granules across the OS-2 throat, a dirt ring 18 inches upslope, staining below the exterior conductor head, and open sealant at the roof-side flange corner. Consultant directed debris removal and sealant repair under the approved scupper detail. OS-2 throat, sleeve face, flange corner, membrane tie-in, collector head, and downspout were photographed after cleaning and repair. Same-boundary water check was observed from the corridor with no leakage during the test period. Follow-up after the next rain is assigned to maintenance. Punch R-303 is closed only for the OS-2 obstruction and flange-sealant repair; RD-4 drainage review remains open.

The stronger note works because it keeps the storm complaint, drainage boundary, failed condition, repair, test basis, and remaining holds separate. It closes the documented scupper issue without overclaiming the entire roof.

Common mistakes

The first mistake is photographing only the clean final opening. Final photos help, but they rarely prove what blocked the throat, where water ponded, or why the repair was made.

The second mistake is mixing primary drainage and overflow drainage into one sentence. A primary drain problem, overflow scupper problem, leader problem, and wall leak problem can look similar inside the building but need separate records.

The third mistake is closing a storm punch item without a test or follow-up basis. If the responsible reviewer accepts visual closeout, later rain observation, monitoring, or owner direction, say that plainly and state the limit.

The fourth mistake is turning a field note into a drainage approval. Do not write scupper sized correctly, code compliant, or adequate for design storm unless the qualified reviewer has made that determination in the controlling record.

The fifth mistake is erasing debris and ponding evidence. Housekeeping may be necessary, but the condition should be photographed or explained before it disappears.

Questions that come up

Does a clear scupper close the storm leak punch item? Only if the responsible reviewer accepts that boundary. The record should still show the original condition, repair or cleaning, test or follow-up basis, and any excluded leak paths.

Should the field note measure the scupper opening? Record observed dimensions or status when the project form or reviewer asks for them, but do not turn the measurement into code compliance or hydraulic approval unless the qualified reviewer provides that conclusion.

What if the opening had to be cleared immediately during a storm? Record the emergency condition, who directed the action, what was removed, where it was discharged or stored if relevant, and photos taken as soon as practical.

Can a water test prove the next storm will not leak? No. It can support the tested boundary under the method used. Future rain intensity, wind, debris, primary drain performance, wall conditions, and hidden defects remain outside a generic field note.

What if the leak path might be the wall instead of the scupper? Keep the scupper closeout bounded and assign the wall, coping, counterflashing, window, or cladding question to the proper reviewer.

Related tools

RunoffRoute can help when the storm closeout boundary extends to exterior drainage, grade, discharge, or stormwater routing outside the roof edge.

FilmProof fits coating or liquid-applied repair records where film evidence around a scupper detail needs to stay tied to the punch item.

Storm Force-Account Log belongs in a separate cost record when the same storm response creates labor, equipment, and photo backup for force-account work.

Storm Material Slip can keep storm-response material tickets separate from the roof QA packet when replacement parts or emergency supplies are tracked.

Compliance and safety limits

This field note is not a roof design, plumbing design, storm-drain sizing method, rainfall analysis, structural rain-load review, code ruling, warranty approval, manufacturer inspection, water-test procedure, leak-source guarantee, or instruction to modify scuppers, drains, leaders, downspouts, walls, or roof membranes. The project documents, approved details, roof-system manufacturer, plumbing designer, roof consultant, designer, AHJ, owner, warranty provider, and qualified reviewers control the work.

Do not use this checklist to bypass fall protection, warning lines, guardrails, personal fall arrest systems, roof-opening protection, ladder and access controls, storm access limits, electrical hazards, lightning or high-wind restrictions, water discharge controls, public protection, wall-opening protection, mold or interior protection, sharp-edge handling, sealant safety data, coating safety data, PPE, or site-specific safety procedures. Do not block or plug active roof drains, scuppers, or overflow paths unless the approved test plan and weather controls allow it.

Sources checked

Related guides