If you do inspections for a living, you know a sloppy report costs time, money, and credibility. This guide is for inspectors, property managers, and field operators who need a clear, repeatable way to record what they find.
Here you'll get a practical template for how to write inspection report, a photo strategy that actually helps decision makers, and examples you can copy the next time you walk a site. No fluff—just the steps we use in the field to get repairs scheduled and closed.
Start with the right header: what to include and why it matters
The header is the first thing people read. If it's vague or missing, your whole report looks amateur. Use the header to set accountability and scope.
What belongs in the header
- Report date and inspector — who was there and when. If there's a dispute later, this is your anchor.
- Exact location — address, building identifier, unit or roof zone. Be specific. "Roof" is lazy; "Roof, north slope above bay 3" is useful.
- Purpose and scope — routine inspection, tenant move-out, hail claim, mold follow-up. List excluded items if needed.
- Reference documents — permit numbers, previous report IDs, or lease clauses that matter for this visit.
On our reports we put the header data in a compact block at the top and repeat the most critical bits (site, unit, inspector) on every page footer. It saves guesswork when pages get printed or split into emails.
Write findings like a technician, not a novelist
Field notes should be short, factual, and locational. Your audience is the trade that will do the work and the manager who will approve budgets. Write for both.
Use a repeatable sentence structure
- Item: what you inspected (door, gutter, drywall)
- Location: building/unit/zone
- Condition: objective observation (cracked, sagging, wet)
- Impact: what the condition means (water entry, trip hazard, inoperable)
- Recommended action: what to do next (repair, replace, monitor)
Example: "Exterior stair handrail, Bldg A, south entry: loose at mid-span; fasteners missing and paint corrosion present—creates fall risk. Recommend re-anchor existing rail and replace missing fasteners; verify with torque or weld per contract." That one sentence tells a tech exactly what to check and a manager what to approve.
Photos are evidence, not decoration
Photos win and lose claims. Bad photos are worse than none because they create doubt. Take photos that show context and the detail. Name them so anyone can find the spot without asking you questions. For camera settings and composition best practices, consult inspection report photos that work.
Photo strategy that works on site
- Two-shot rule: always take a context shot that shows where you are, then a close-up of the defect.
- Include a marker: use a unit number card, a tape measure, or a small placard in the frame so viewers know orientation and scale.
- Keep originals: do not crop or heavily edit originals. Save an untouched folder and a working folder for the report images.
- Name consistently: use a file name that includes site identifier, area, brief defect tag. For example: BuildingA_Corridor_EastPipeLeak.jpg
On a recent multifamily turn inspection, our photo set did the heavy lifting. The context shots showed the unit number and the entry sequence; the close-ups showed fiberglass underlayment compression under the tub and the exact seam where tile grout failed. The maintenance supervisor approved the repair scope from the photos — saved a return trip.
Severity and prioritization: make triage obvious
Not every defect needs the same response. If you don't rank urgency, everything becomes urgent and nothing gets done. Use a simple severity system and stick to it.
What a usable severity system looks like
- Immediate: safety, structural failure, active water intrusion. Stop work or evacuate if needed.
- Repair soon: defects that will get worse or cause damage if not fixed.
- Maintenance or monitor: cosmetic or minor items to address on regular cycles.
Label each finding with one of those tags. Then sort the priority list in the report so the client sees the Immediate items first. For claims and insurance work, Immediate items are what you escalate straight to the carrier.
Scope the repair recommendation so trades can price it from the report
Vague recommendations delay approvals. If your recommendation is "repair roof," you’ll get questions. Give trades a scope they can estimate from.
What to include in a recommended action
- Method: replace, patch, re-anchor, test, or monitor.
- Extent: one unit, whole roof slope, corridor length. Be explicit about limits.
- Access/constraints: scaffolding, tenant notice, shut-off requirements, or weather limitations.
- Verification: how you or the contractor will prove the work is done (photos, signatures, gauge readings).
Example: Instead of "re-seal window," write "remove existing sealant at sill, clean substrate, apply full-depth polyurethane sealant, tool bead to match adjacent profiles. Re-caulk interior if signs of moisture. Validate with dry interior surface photos 24 hours after cure." That gives the contractor the how and the owner the expected deliverable.
Use templates but customize the scope box
Templates save time. But the most-common mistake I see is a canned report dumped on a job it doesn't fit. Use templates for structure, not content.
What to customize every time
- Scope of inspection: list what you looked at and what you did not. If you didn't open panels, say so.
- Limitations: weather, locked areas, or tenant refusal to allow access. Call these out so you don't get blamed later.
- Assumptions: any things you presumed, like utility shut-off availability or that finishes are original.
We keep three templates: routine maintenance, tenant turn, and insurance claim. Each has the same sections but different checklists and evidence fields. Use the right one or combine them when a job crosses categories. You can adapt a construction daily report template for routine site logs and phone workflows.
Mini case: Hail claim on a warehouse roof
Quick field story so you can see the report structure in practice. We got called to a warehouse after a storm. The client wanted a fast assessment for the carrier and a contractor bid.
What we did on site
- Header: listed report date, inspector name, warehouse address, roof zone IDs, and that the visit was a hail damage survey.
- Photos: context shots from ground for roof zone orientation and close-ups of panel dents and seam separations. Each file named by zone tag and viewpoint.
- Findings: recorded dented panels, seam separation at east gutter, and several penetrations with backer damage.
- Severity: marked seam separation as Immediate because it allowed water entry; panel dents as Repair Soon because they affect warranty and insulation over time.
- Recommendation: temporary tarpaulin at the seam, then contractor scope to replace affected panels and re-flash penetrations. Included access needs and staging space for materials.
The carrier requested the photos and the Immediate tag. The client used our recommendation to get an emergency tarp onsite within the same day. The contractor then quoted from our scope without asking for a re-inspection. We also logged each image with photo logs with GPS timestamps to match files to roof zones during the claim.
Formatting, signatures, and version control
Paper copies still show up. But the key is version control so everyone references the same report. Name files, track versions, and capture sign-offs.
Simple version control approach
- Name the file with site ID, date, and version: for example, SiteID_ReportDate_v1 (use your naming standard).
- Keep original photos and a working copy folder tied to each report version.
- Get sign-off: at minimum the inspector signs. If a client approval is required, capture their name, role, and date in the report body or footer.
When you revise a report, add a revision section that lists what changed and why. Don't overwrite the original final report—create v2 and keep v1 for disputes. If you need a workflow for sorting images, review organize site photos before writing.
Common mistakes that waste time (and how to avoid them)
We see the same dumb errors on every site. Call these out in pre-job training so your crew stops doing them.
Top repeat offenders
- Poor photo context: close-ups without context. Fix it with the two-shot rule.
- Vague locations: "kitchen" is too broad. Use building, floor, and landmark.
- Opinion dressed as fact: avoid phrases like "seems to be" or "probably." Stick to what you can verify.
- Missing constraints: not noting locked areas or weather when they limit access.
Train junior inspectors to write one-line findings in the field using the sentence structure above. Review examples together once per week and correct wording on real reports. Also train your crew on 7 field documentation habits during weekly reviews.
Key takeaways
- Use a clear header with report date, inspector, and exact location so the report is accountable and searchable.
- Write findings in a repeatable, factual sentence structure: item, location, condition, impact, recommended action.
- Take evidence-grade photos: context plus close-up, include a marker, keep originals, and name files consistently.
- Prioritize with simple severity tags so immediate hazards get action first and contractors can price from your recommendation.
FAQ
How many photos should I include in a report?
Include a context shot and at least one close-up for every distinct defect. The goal is to prove location and detail, not to inflate the gallery. Keep originals and reference file names in your captions.
Should I estimate repair costs in the report?
Only provide cost estimates if you have the expertise and the client asked for it. If you do include costs, label them as budget estimates and explain the basis. Otherwise, leave pricing to contractors who will bid the defined scope.
How do I handle limited access during an inspection?
Note the limitation in the report header and the limitations section. Describe what you couldn't inspect and why. If the issue could be material, recommend follow-up access and flag it in the severity column so it doesn't get missed.
What record-keeping should I keep after closing a report?
Keep the final report, original photos, any revision history, and sign-offs. Store them in a folder named with the site ID and report date for easy retrieval. This avoids rework and preserves evidence for claims or disputes.