Commercial Roof Leak Incident Log: What Property Managers Should Record

August 24, 2026•Raven Roofing Team

roof leak incident log commercial roof leak report property management roof leak documentation

A commercial roof leak incident log gives property managers one consistent record of what happened, where it appeared, when it was active, and how the building was affected. The most useful log captures safety actions, the precise interior location, weather and timing, photographs, operational impacts, previous incidents, and the handoff to the roofing team.

The log is not a diagnosis. Water can move through roof assemblies and building components before it becomes visible indoors, so the drip location may not be the entry point. What the record does is preserve evidence that can narrow the investigation, show whether incidents repeat under similar conditions, and reduce confusion when tenants, managers, vendors, and roofers are involved.

This guide provides an on-page incident form that a commercial property team can copy into its work-order or building-management system. It is designed to complement—not delay—life-safety action, active-loss control, and a professional commercial roof leak investigation.

Safety and Active-Loss Response Come First

Documentation should begin only after immediate hazards are addressed. If water is near electrical equipment, ceilings appear unstable, materials are falling, or there is any concern about structural safety, keep people out of the affected area and use the building's emergency procedure. Call 911 where there is an immediate threat to life or safety.

Do not enter standing water or approach electrical equipment in a wet area. The Government of Canada's flood safety guidance advises against attempting to shut off electricity once water is present and calls for qualified electrical review before re-entry where electrical systems may have been affected. The exact response should follow the building's emergency plan and the direction of qualified personnel.

Roof access is also a separate safety decision. A tenant or property manager should not go onto a wet, icy, wind-exposed, or otherwise hazardous roof to improve the incident record. The RCABC Roof Maintenance guide puts safety first and identifies hazards that should be checked before roof access, including fallen electrical lines and potentially unsafe roof loading. Rooftop review should be left to authorized people with appropriate training, access controls, and fall-protection procedures.

Once the area is controlled, record the immediate actions taken:

Time the incident was first reported
Areas isolated or occupants relocated
Building operations, equipment, or utilities affected
Water-containment or contents-protection measures used
Emergency, electrical, restoration, roofing, or other qualified parties contacted
Name of the person coordinating the response

Avoid wording that assigns blame or states a cause before investigation. Record observable facts: “water dripping from the west ceiling tile during rain” is more useful than “the roof membrane failed.”

The Minimum Useful Commercial Roof Leak Record

Create one incident number for each event, then keep all messages, photographs, work orders, and follow-up notes attached to that record. A practical minimum record includes:

Incident ID: A consistent identifier, such as building-roof area-date-sequence
Reported by: Name, company or tenant, role, and reliable contact information
Date and time: When water was first noticed, when it was reported, and when it stopped or changed
Building and interior location: Address, floor, suite, room, and a fixed reference point
Observed condition: Drip, stain, damp material, flowing water, ponding, odour, ceiling damage, or another visible symptom
Weather: Rain, wind, snow, thaw, temperature change, or dry conditions before and during the event
Operational impact: Affected occupants, equipment, inventory, access, or business area
Immediate action: Area control, contents protection, calls placed, and temporary measures taken by authorized parties
Photos and plan references: File names tied to the same incident ID
Prior history: Earlier incidents or repairs in the same area, including dates and work-order numbers
Handoff and follow-up: Who received the record, site access details, findings, repair reference, and monitoring notes

Use local time and include the timezone. A record such as “August 24, 2026, 2:18 a.m. PT” is easier to compare with weather, building alarms, and contractor records than “last night.”

How to Describe the Interior Location Precisely

“Leak in Unit 204” is rarely enough for a large suite. Use stable references that another person can find without the original reporter present.

Record:

Floor, suite, room, bay, corridor, stairwell, or grid line
Approximate distance and direction from exterior walls, columns, doors, or fixed equipment
Ceiling type and approximate height where relevant
Whether the symptom is below a roof, wall, terrace, mechanical room, or upper-level space
A marked floor plan, even if it is a simple screenshot of the property plan
Any nearby plumbing, HVAC, sprinkler, drain, or envelope component, without assuming it is the source

For repeated incidents, use the same location name each time. Switching between “north office,” “accounting,” and “Room 2A” can hide a recurrence that would be obvious in a consistent record.

Record Weather and Timing Without Guessing

Weather context can help distinguish patterns, but it should be factual. Capture what the reporter observed and, if useful, add verified public weather data afterward.

Useful details include:

Whether precipitation was active when the symptom appeared
Approximate start, stop, or change time
Wind direction or wind-driven rain only if it was actually observed or verified
Snow accumulation, thaw, or a rapid temperature change
Whether the symptom continued after precipitation stopped
Whether the area also shows moisture during dry conditions

Environment and Climate Change Canada's Historical Climate Data provides past hourly and daily records for Canadian weather stations. Note which station and observation interval were used, because the nearest station may not reproduce conditions at the roof.

Do not delay the service call while assembling a perfect weather history. A simple timestamp and “active rain,” “rain ended approximately 30 minutes earlier,” or “no precipitation observed” is enough for initial intake.

Take Photos That Preserve Context

Photographs are most useful when they move from context to detail. If it is safe to do so from the interior, take:

A wide photo showing the room and fixed reference points
A medium photo showing the affected ceiling, wall, floor, or equipment area
A close photo showing the drip, stain edge, opening, or damaged material
A photo of any container or measured spread used to track active water
A marked plan or screenshot showing where the photos were taken
Follow-up photos from the same position after conditions change

Keep original files where possible and use descriptive names, such as INC-2026-08-24-01_west-corridor_wide_0218PT.jpg. Do not edit an original in a way that removes its timestamp or context. If an annotated copy is created, retain the original as well.

Photograph only what is necessary for the building record. Avoid capturing people, confidential tenant information, computer screens, medical information, or other sensitive material. Follow the property's privacy, security, and records policies.

Connect Each Incident to Previous Leaks and Work

A single record describes an event. A consistent series of records can reveal a pattern.

For each incident, check for:

Earlier reports at the same interior location
Reports elsewhere during the same weather event
Previous repairs, inspections, tests, or maintenance near the suspected roof area
Recent rooftop equipment work, tenant improvements, deliveries, or contractor access
Drainage blockages, overflow observations, or ponding reported in the same period
Seasonal or wind-direction patterns

Link the incident to the related work order rather than rewriting history from memory. If a previous repair location is unknown, say so. An incomplete record is still useful when its uncertainty is clear.

Repeated symptoms do not prove that the same defect has returned. They may relate to an incomplete repair, a different entry point, water travelling from another area, condensation, plumbing, or another building-envelope source. A broader commercial roof inspection may be appropriate when the available evidence does not support another localized repair.

Copy-and-Use Roof Leak Incident Form

Use the following fields in a work-order platform, shared form, spreadsheet, or building log. Keep the form accessible to the people who receive after-hours tenant reports.

Incident identification

Incident ID:
Building/address:
Date and local time first observed:
Date and local time reported:
Reported by / contact:
Property-management coordinator:

Safety and active-loss actions

Immediate hazards observed:
Area isolated or occupants relocated:
Equipment or utilities affected:
Contents-protection or containment actions:
Qualified parties contacted and time:

Interior evidence

Floor / suite / room / grid reference:
Distance and direction from fixed reference points:
Condition observed:
Was water active when reported? Yes / no / unknown
When did the condition change or stop?
Photo and plan file names:

Weather and recent events

Weather observed at the property:
Verified weather source/station, if added:
Recent roof access, maintenance, alterations, or equipment work:
Similar previous incident IDs or work orders:

Operational impact and handoff

Occupants, operations, equipment, or inventory affected:
Roof access instructions and site contact:
Record sent to / date and time:
Inspection or repair work-order number:
Findings reported by qualified party:
Follow-up monitoring date and result:

Handoff to the Roofing Team

Send the incident record as one package rather than a chain of disconnected texts. Include the incident ID in the email subject, photo names, work order, and later repair record. Provide access details, known hazards, affected operating areas, and any restrictions that could affect investigation.

The package should distinguish three categories:

Observed: What people saw, heard, or measured
Reported: What a tenant or vendor said, with the source identified
Assessed: What a qualified party concluded after review

That separation preserves the original evidence and reduces the risk that an early assumption becomes treated as fact.

What the Log Can—and Cannot—Do

A consistent commercial roof leak incident log can help teams compare events, locate recurring symptoms, coordinate access, and give the roofing team a clearer starting point. It can also improve continuity when property managers, tenants, or contractors change.

It cannot identify the leak source by itself, confirm that the roof caused the water, guarantee a successful repair, determine insurance coverage, or replace emergency, electrical, structural, restoration, or roofing expertise. Retention periods and disclosure requirements should be checked against the property's contracts, warranties, insurer instructions, legal obligations, and internal records policy.

If an active or recurring leak needs investigation, Raven's commercial roof leak repair service can assess the available evidence and the building conditions to help define an appropriate next step. For condition documentation beyond a single incident, review Raven's commercial roof inspection services.