If you do roof work, you write roof inspection reports. They’re the record that protects you, the property owner, and the crew. This article shows you how to write a roof inspection report that’s clear, defensible, and useful on the next site visit.
This guide is for inspectors, property managers, contractors, and project leads who need a practical template. You’ll get a step-by-step field workflow, photo strategy, exact phrasing you can copy, and a short checklist to use the minute you walk back on site. If you want a ready-made form, use our inspection report template that beats Word to speed delivery.
This article answers the question how to write a roof inspection report in plain field terms: we give the format, the photo rules, exact sentence templates, and the minimum deliverables to hand the file to a contractor or insurer without reopening the inspection.
Plan the job before you climb
What to gather and why
- File info: address, owner/PM contact, permit numbers or claim numbers if present.
- Tools: camera or phone with good resolution, measuring tape, moisture meter, ladder, PPE, and note app or voice recorder.
- Records: any past reports, warranty info, and the roof’s installed system name if you can get it.
Walk approach and safety brief
We always brief the crew before we touch the ladder. Check access points, fall hazards, and skylights. Note any restricted access areas and record them in the report. If we won’t walk the roof, we state that and explain why.
Before climbing, confirm gate codes, tenant notifications, and any lockout/permit requirements. If a permit or HOA rule limits access or work hours, note it in the inspector notes. These are common reasons a claim or contractor will question why someone couldn’t access a location.
Move through the roof in a repeatable pattern
Start with a perimeter sweep
Walk the eaves first. Look for missing drip edge, loose gutters, and obvious edge damage. Name locations in a way someone else can find them: "East eave, bay 3 over trash enclosure." Don't say "front" or "back" without specifying orientation.
Then do the field zones
Break the roof into zones: eaves, field, ridges, hips, penetrations, and transitions. Move clockwise so your photos and notes follow the same order. A repeatable pattern keeps you from missing spots and makes the narrative faster to write.
Use a map and mark progress
Sketch the roof quickly on a tablet or paper and mark each zone as you inspect it. If you get pulled off the roof mid-inspection, another tech can pick up where you left off without hunting. Note ladders or staging you used so future crews know how you accessed problem areas.
Take photos that prove the problem (not just pretty shots)
Photo strategy and naming
- Shoot a wide establishing shot for each zone. This tells where the close-ups belong.
- Then shoot close-ups of defects with a marker (chalk, tape, or an arrow in the photo). You must show scale—include a tape or coin if the defect size matters.
- Name files so they map to the report: siteaddress_zone_detail_01.jpg. Example: 123Main_ewes_missingshingle_01.jpg.
- Capture the same detail from multiple angles when possible. Some inspectors take 2–3 angles per defect to prevent interpretation issues later.
For tips on framing and photo composition for evidence, see inspection report photos that work.
How many photos is enough?
Don’t shoot thousands of filler photos. For a typical single-family roof we aim for a consistent batch: an establishing photo per side, then a close-up and a scale shot for each defect. For larger sites like multifamily or industrial, increase proportionally. The point is to show context, detail, and scale for every item you list.
Also make a simple photo index at the end of your photo package: filename, brief caption, and associated finding number. That saves contractors time and reduces emails where they ask "which photo shows that leak?" Teams that organize site photos before writing the report find review and contractor handoff much faster.
Write clear, field-friendly findings
Use a consistent sentence structure
We use a simple three-part sentence for each finding: location, condition, impact. Example: "South field, near ridge vent — two adjacent asphalt shingles missing exposing underlying underlayment; potential for water intrusion at wind-driven rain." Keep it to one clear sentence and avoid speculation about the cause unless you saw it happen.
What to document for each issue
- Exact location using compass or building coordinates if you have them.
- Observed condition: what you see and how it reads (wet stains, cracked flashing, blown-off cap sheet).
- Severity and urgency: immediate (leaking now), short-term (needs repair), or routine maintenance.
- Recommended action: repair detail. Say what to do, not just "replace." Example: "Remove damaged shingles, install new step flashing lapped under siding, reinstall 2 rows of shingles sealed with modified asphalt adhesive."
Keep a short code or numbering system for findings so you can reference them in photos and the sketch. For example: Finding A-1, A-2, B-1. Put that ID in the photo caption so there is zero guesswork when a contractor later scopes the work. Adopt the 7 field documentation habits to make your findings consistent and professional.
Include interior (attic) checks and cross-reference photos
Don’t skip the attic
Attic conditions prove roof performance. Look for daylight, rot on framing, wet insulation, or staining. Photograph the corresponding interior stain and label it to match the roof photo. That link makes your claim or repair recommendation credible.
How to phrase interior findings
Keep interior notes short and tied to a roof location: "Attic above Unit 2, west bay — light visible at roof deck seam; roof deck perforation aligns with missing shingle at west field (photo 5, photo 12)." The cross-reference prevents someone from arguing the stain came from a different spot.
Use a moisture meter and note readings when you can. If you can’t get a meter reading because insulation blocks access, state that limitation. Moisture numbers are useful, but the presence of active drip or visible wetness is the strongest evidence.
Common phrases that get you in trouble — and what to say instead
Avoid blaming weather or guessing age
Don't write "hail damage" unless you observed hail or the property owner provided verified evidence. Instead: "Multiple impact marks consistent with granule loss on multiple shingle tabs; recommend confirmation of weather event and correlation with insurer claim if applicable."
Don’t overstate safety or code compliance
If you’re not a licensed code inspector, don’t declare compliance. Use neutral language: "Observed condition appears not to meet typical manufacturer installation practice for step flashing; recommended evaluation by licensed roofer for code compliance." That keeps you honest and reduces liability.
Also avoid subjective terms like "very bad" or "failed." Instead classify severity and give the reason you chose that category. A clear statement like "short-term repair recommended; continued exposure will likely lead to leak" is far more useful to owners and adjusters than emotion-based language.
Mini case: Multifamily turnover — what we did and why
The setting
We inspected a three-story multifamily building during unit turn. Tenants complained of stains on the third-floor ceilings. The roof is a steep asphalt shingle system with a step-flashed parapet at one side.
Field workflow and photos
- We started with property info and tenant locations. Then we did a perimeter sweep and shot wide shots of each roof plane.
- Defect photos: For the parapet we took four establishing shots and three close-ups showing failed step flashing and torn underlayment. Each close-up included a tape for scale and a photo of the matching interior stain.
- File naming: 321Elm_roof_parapet_close_01.jpg, 321Elm_attic_unit303_stain_01.jpg.
Report wording we used
For the parapet: "Parapet at north elevation — step flashing separation observed at 3 locations; flashing laps compromised and underlayment torn at flashing termination. Water intrusion evidenced by ceiling stains in Unit 303 directly below flashing locations. Recommend remove existing step flashing, replace underlayment at affected area, and reinstall flashing with counterflashing secured to parapet wall. Coordinate access and schedule with property management to protect interiors during work."
That sentence maps directly to the photos and the attic observations. The PM can hand it to a roofer and get a scoped bid without back-and-forth.
We also added a short addendum listing contractors who could stage work without full unit turnovers—small notes like that save the PM time and help prioritize temporary tarps or interior protection if work will be delayed.
Deliverables: what to include with the report
Always attach these items
- Photo package labeled to match each finding.
- Sketch or simple roof diagram showing zones and defect locations.
- Inspection methodology statement: walked roof, limited access, attic inspected, instruments used.
- Contact info and signature line for the inspector. If you’re licensed, include your license number.
Include a one-line summary at the top: what you inspected, access limits, and the number of days the inspection took. Add a table of photo filenames and captions right after your findings so a reviewer can scan and verify quickly. If you used thermal imaging or drone video, attach the file and note the device and operator. If you want to tighten turnaround, run the audit current report process in 30 minutes to shave steps from delivery.
On-site checklist you can use right now
Quick actionable checklist
- Confirm site info and walk/ladder safety briefing with crew.
- Shoot wide establishing photo of each roof plane before any close-ups.
- Photograph each defect with scale and from multiple angles; use consistent file names.
- Check the attic and photograph matching stains; cross-reference photo IDs in the notes.
- Write one clear sentence per finding: location, condition, impact, recommended repair.
- Attach a roof sketch and append the photo package. State inspection method and access limits.
After you leave site: upload the photos to your cloud backup immediately, sync filenames to the report, and send a short field summary to the client with expected timing for the full report. Delays in uploading cause lost files and confusion later—make backup part of your on-site routine.
Key takeaways
- Be repeatable: use a set walk pattern and file-naming standard every time.
- Use photos to prove location, scale, and condition—not to decorate the report.
- Write short, factual sentences that link roof observations to interior evidence.
- Include a sketch and inspection method statement to remove ambiguity for contractors and insurers.
FAQ
How many photos should I include?
Include an establishing photo for each roof plane and a close-up with scale for every defect you list; add multiple angles for unclear details. The goal is clear context and proof, not quantity for its own sake.
What do I do if I can’t safely walk the roof?
State it. Describe what you did instead—binoculars, ladder-access photos, drone—and explain which areas were not inspected and why. That transparency protects you later.
Should I give a cost estimate in the report?
Cost is optional. If you include a price, label it as an estimate and note that it is for budgeting only. Many clients prefer you outline the scope and let contractors provide firm bids.
How detailed should repair recommendations be?
Be specific enough for a contractor to scope a bid. Say what to remove and replace, call out materials and flashing details, and note sequencing or access needs. Avoid vague language like "fix roof."
Can I use this report for insurance claims?
Yes, if the report is factual, well-documented with photos, and includes an inspection methodology statement. For insurance use, include as much pre-loss documentation as you can and be careful about attributing cause unless verified.