Start with scope and limitations
The first section of a defensible report is not a finding — it is the boundary of the inspection. State what was inspected, what was not, and why. Attic not entered because of insulation depth, crawlspace inaccessible due to standing water, panel not opened because the cover was painted shut: each of these belongs in writing, on the day, not in a phone call later.
Treat limitations as structured items rather than a paragraph of prose. When they are checklist entries, they cannot be skipped, and they appear in the same place in every report you issue.
Score conditions consistently
Clients cannot triage a report where every finding reads with the same weight. Pick a small set of condition levels and apply them the same way on every job.
- Serviceable — functioning as intended at the time of inspection
- Monitor — functional but aging or showing early wear
- Repair — deficient and should be corrected
- Safety hazard — an immediate risk that should be addressed before occupancy
Attach the evidence to the finding
A photo appendix at the back of a report is nearly useless to a reader deciding what to negotiate. Put the captioned photo directly beside the finding it documents, so the observation and the evidence are read together.
Captions should describe what the reader is looking at and where it is, not repeat the finding text.
Write the summary for the person paying you
Buyers, agents and lenders read the summary. Keep it short, order it by severity, and avoid recommending a specific contractor unless you are prepared to defend that referral. Recommendations should describe the outcome needed — evaluate, repair, replace, monitor — not the price.
Deliver in a way you can prove
Delivery disputes are avoidable. Send the report through a system that records when it was sent, whether it bounced, and when it was accessed. Expiring share links let you give agents and lenders access without emailing the PDF around indefinitely, and revocation gives you a clean way to end that access.