A flat roof rarely announces trouble. Water ponds, a seam opens, a drain slows, and the first visible sign is often a stain on a ceiling tile below. This campaign reminds property managers twice a year, sends a ponding-photo report they can actually read, and turns findings into a clear repair-priority list.
System 7 from the Leveraged Owner Starter Pack
A property manager walks a warehouse in March and the roof looks fine from the hatch: gray, flat, nothing obviously wrong. By July a tenant is putting a bucket under a drip and asking why nobody caught it. Nobody caught it because nobody was scheduled to look, and flat roofs do not reward casual looking anyway — the problems start small, wet, and out of sight. A twice-yearly commercial flat roof inspection reminder fixes the scheduling part. It is the same calm-calendar discipline as appointment confirmation texts: a known building, a known contact, and a short message that arrives early enough to book the work before it becomes urgent.
On a sloped roof, many problems announce themselves: a missing shingle, a visible stain, water running where it should not. On a flat roof, water moves slowly and damage hides in layers. Ponding water sits in low spots long after rain ends. Seams and flashing take the weather at the joints. Drains clog gradually, so each storm leaves a little more water standing for a little longer. By the time moisture shows inside the building, it may have traveled far from the entry point, which makes the indoor stain a poor map to the outdoor cause.
That quiet pattern is exactly why reminders beat waiting for a call. The manager is not ignoring the roof; the roof is simply not part of their daily view, and their job pulls them toward tenants, budgets, and buildings that are actively complaining. Your reminder gives the quiet building a turn. Frame it that way — as scheduled care for an asset they manage — not as a warning that something is already wrong.
Run two inspection rounds a year for each commercial building: one in spring, after winter weather has done its work, and one in fall, before winter arrives again. Adjust the exact months to your climate, but keep the rhythm fixed — the same two windows every year, building by building. Store the schedule in your CRM (customer relationship management software — your database of customers, buildings, contacts, and service history), with one record per building, not just per company. A manager with six buildings needs six inspection dates, six reports, and six priority lists, even if one email covers all of them.
For each building record, keep the fields the campaign runs on: roof type and approximate age if known, last inspection date, access notes for the hatch or ladder, the manager's preferred contact method, and any areas flagged last time for monitoring. Log completed visits in your FSM (field service management software — the platform running your scheduling and job records) so the next round starts from last round's findings instead of from a blank page. A building whose ponding spot was marked "monitor" in spring should be photographed first in fall.
Property managers live in email, so lead with email about 45 days before each inspection window, then send one short text or a brief follow-up email about two weeks later to anyone who has not booked. Keep the ask small: pick a window, confirm access, and tell you who will meet the crew or where the key or hatch access is. Do not attach a repair pitch to a reminder. The inspection earns the repair conversation later, with photos.
Email — the seasonal reminder (about 45 days out)
Subject: Spring flat roof inspections for [Building Name]
Hi [First Name], [Business Name] here. We inspect the flat roof at [Building Name] twice a year, and the spring round is coming up in [Month]. The visit checks ponding areas, seams, flashing, and drains, and you receive a photo report with a repair-priority list after we finish. Reply with a week that suits your tenants and the best access arrangement, and we will confirm a day and window. If another contact now handles roof access, reply with their name and we will update our records. — [Your Name], [Business Name]
Text — the short follow-up (about 14 days later, no reply)
Hi [First Name], [Business Name] following up on the spring flat roof inspection for [Building Name]. We are booking [Month] visits now. Reply BOOK and we will send two window options, or LATER and we will move you to the fall round. Reply STOP to opt out.
If you text, follow the standard business-texting rules. A2P 10DLC registration (Application-to-Person messaging on a standard 10-digit number, registered with the carriers) is required before sending business texts — expect roughly 1–7 days for approval and about $15–$20 one-time. Include opt-out language in the first text, and observe TCPA quiet hours: no marketing texts before 8am or after 9pm in the recipient's local time. This is general information, not legal advice. Email contacts who changed jobs are a normal part of commercial work, so treat a bounce or an auto-reply naming a successor as a records task, not a dead end.
The report is what separates this campaign from a reminder service. Managers approve work they can see, and most will never go up on the roof themselves. Run the visit from a one-page SOP (standard operating procedure — written steps your team follows the same way every time): photograph the whole roof in sections, photograph every ponding area with something in frame for scale, photograph seams, flashing, drains, and any damage up close and from a distance, and note where each photo was taken on a simple roof sketch or in the photo captions.
Send the report within two business days of the visit, while the booking conversation is still warm. Keep it short and structured: building name and inspection date, a one-line overall condition note, the ponding photos with plain captions — where the water sits and roughly how large the area is — then the other findings in the same photo-plus-caption format. Write captions a non-roofer can understand: "Water standing near the drain at the northwest corner, still present two days after rain" beats a string of trade terms with no location.
End every report with the findings sorted into three plain buckets. Fix now: active leaks, open seams, failed flashing, or blocked drains — anything letting water in or holding it against the roof today. Plan this season: wear and damage that is not leaking yet but will not survive another year of weather without getting worse. Monitor: minor ponding, surface wear, or aging details to photograph again next round and compare. Each item gets a photo reference, a location, and a separate price or a clear next step for pricing — never one bundled total that forces the manager to approve everything or nothing.
This list respects how property managers actually work. They answer to owners and budgets, so an itemized list lets them approve the urgent work now, carry the seasonal work into a budget request with your photos attached, and show the owner a monitoring plan for the rest. You become the crew that makes their budget meetings easier, which is a stronger position than being the crew that sends the biggest quote.
Track buildings due, reminders sent, inspections booked, reports delivered, and priority items approved — in that order. Report delivery matters more than most shops expect: an inspection with no report inside two days teaches the manager that the program is casual, and the next reminder gets ignored. Here is a worked example. Example: a commercial roofing crew manages inspection reminders for 24 buildings across nine property managers. The spring round sends 45-day emails building by building, books most visits inside the window, delivers photo reports within two days, and sorts every finding into the three priority buckets. A few managers defer to fall, and those buildings are logged with a new date instead of being dropped. Use your own building count and inspection pricing in the math; the durable return is a twice-yearly rhythm where no managed roof goes a full year unlooked at, and every finding has a photo, a bucket, and a next step.
The scheduled-reminder pattern here is the Pillar D pattern from appointment confirmation texts. Its closest relatives are the fire sprinkler inspection reminder campaign, which runs the same commercial-building cadence for a different system, and the roof moss treatment campaign — together they keep a roofing crew in front of the same buildings on a calendar instead of on a crisis.
The full setup SOP, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.
Free. The full 8-system Starter Pack is $27 if you want everything else.
This post is System 7 from the Leveraged Owner Starter Pack — the done-for-you version with the full multi-step SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems. The Pack's reminder kits include the twice-yearly cadence setup, the ponding-photo report template, and the three-bucket repair-priority sheet this campaign runs on.
Stats sourced as labeled: no third-party statistics are cited in this post; inspection intervals, roof condition findings, and repair recommendations should always follow the roof manufacturer's guidance and what your crew documents on site.
Related guides from the Leveraged Owner blog:
Keep waterproofing customers covered with an annual inspection text, a battery-backup test reminder, and a dehumidifier check before small issues flood.
Book first-time fence staining with a water-bead readiness test, a weather-window schedule, and repairs quoted in writing before stain day arrives this spring.
Which business system should contractors automate first? The 5-minute self-audit: find your biggest leak, match it to the right system, install in order.