Commercial roof maintenance log: what to record after each visit

A roof problem is easier to discuss when you can answer a few basic questions: when was the roof last accessed, what work was done, and when did the first sign of a problem appear? A short roof log keeps those details together instead of leaving them in separate emails, invoices, and people’s memories.

This is a record-keeping tool, not an inspection checklist. Building staff can note what they observe from inside or from the ground and save documents from qualified contractors. No one should climb onto a roof just to complete a log.

What belongs in a commercial roof log?

Keep one entry for each roof visit, reported condition, repair, or relevant piece of work by another trade. The National Roofing Contractors Association’s guidance on roof maintenance discusses logging roof access times and the parties working on the roof. That history can help a roofing professional understand what happened between visits.

For each entry, record:

• Date, time, and person reporting: Use the time the issue was noticed, not an estimate of when it began.
• Location: Name the building area, room, roof section, or equipment area as specifically as your records allow.
• What was observed: Describe a stain, drip, standing water seen from the ground, or other visible condition without naming a cause.
• Weather context, if known: Note when rain began or ended and the wind direction if someone observed it. NRCA has specifically recommended recording those details when a leak occurs.
• Roof access and work: Record who accessed the roof, why, and which area they worked on, using the contractor’s report or work order where possible.
• Documents and next step: Link the invoice, photos, proposal, or inspection report. Note who is following up and whether that action is complete.

For technical background, see NRCA’s discussion of roof inspection and maintenance records and its advice on recording conditions when roof leaks are observed.

Use neutral wording instead of a diagnosis

A useful log separates what someone saw from what they think caused it. Write “water mark on ceiling tile near the north wall at 8:40 a.m.” rather than “failed roof seam.” The first statement can be checked. The second guesses at a roof condition that may need a professional assessment.

Keep tenant or employee details to the minimum needed to locate the issue. A room number or area name is usually more useful than a long description of who was there. Store the log with the building’s maintenance records and restrict access according to your usual document practices.

A short example entry

Example only: September 8, 10:15 a.m. — Water mark observed on the ceiling above the receiving office. Rain began around 9:30 a.m., according to the site log; wind direction not recorded. Photo taken from the floor. Last roof service report filed under “Roof / 2026 / August.” No building staff accessed the roof. Facilities manager to contact the roofing contractor.

The example does not identify a cause or promise a repair. It gives the next person enough context to ask a better question.

Keep the record useful over time

Choose one shared location for the log and a consistent way to name supporting files, such as date, building area, and document type. When a contractor completes work, save the written scope and closeout notes alongside the entry. If another vendor needs roof access, ask them to document the visit and any work near the roof system, penetrations, drains, or rooftop equipment.

A log does not replace a roof assessment, determine warranty coverage, or prove why a condition occurred. It gives a qualified roofing professional a clearer timeline. If your building has recurring leaks or you need planned maintenance, review Alpha Commercial Roofing’s maintenance and leak service information, then contact the team with the building address and the records you have. You can also compare the proposed scope with our guide to reviewing commercial roofing quotes.