How to Write a Home Inspection Report That Doesn't Get You Sued

Learning how to write a home inspection report isn't just about listing defects. It's about creating a document that accurately communicates your findings while protecting you from the inevitable phone call that starts with "my attorney says..."

I've reviewed hundreds of inspection reports over the years — my own, other inspectors', and the ones that ended up as exhibits in lawsuits. The pattern is clear: the reports that get inspectors in trouble aren't the ones that missed something obvious. They're the ones where the language was sloppy, the scope was unclear, or the inspector wrote something they couldn't defend.

This is the guide to writing reports that serve your clients AND protect your business.

The Foundation: Scope and Limitations

Every report needs to establish what you did and what you didn't do before a single finding is mentioned. This isn't legalese for the sake of legalese — it's the framework that defines your liability.

What Your Scope Statement Must Include

• Standards of practice followed (ASHI, InterNACHI, or state-specific)
• What a home inspection IS (visual, non-invasive, general assessment of major systems)
• What a home inspection IS NOT (code inspection, engineering assessment, guarantee of condition)
• Systems and components inspected
• Systems and components specifically NOT inspected and why
• Conditions that limited the inspection (snow cover, stored items, locked rooms)

The scope statement is your first line of defense. When a client says "you should have caught the mold behind the drywall," your scope statement should clearly say the inspection is visual and non-invasive — you don't open walls.

Language That Protects You vs. Language That Sinks You

The words you choose in your report matter more than you think. Small differences in phrasing can mean the difference between a dismissed claim and a six-figure settlement.

Words and Phrases to AVOID

"Appears to be in good condition" This is the most dangerous phrase in home inspection. "Good condition" is subjective, undefined, and sets an expectation. When the system fails, the client points to your report and says you told them it was good. Instead: "The system was functional at the time of inspection."

"Minor issue" or "Minor defect" What's minor to you — an experienced inspector — might be a $5,000 repair to the client. Calling something "minor" minimizes it, and when the repair bill arrives, the client feels misled. Instead: describe the condition and recommend action. Let the client decide what's minor.

"Should be fine" or "Nothing to worry about" You're not a fortune teller. You're documenting present conditions. The moment you predict the future, you own the future. Instead: "No defects observed at the time of inspection."

"I recommend" (without qualification) Bare recommendations can imply you're guaranteeing the outcome. Instead: "Recommend evaluation by a qualified [electrician/plumber/structural engineer] for further assessment."

"Code violation" Unless you're a code inspector performing a code inspection, don't use this phrase. You're performing a home inspection to your standards of practice, not a code compliance review. Instead: "This condition does not meet current safety standards" or "This installation method is no longer considered acceptable practice."

Language That Protects You

"At the time of inspection..." This phrase is your best friend. It anchors your observations to a specific moment. "At the time of inspection, the furnace was operational and responsive to thermostat control." If it dies next week, your report said what it said — at that time.

"Recommend further evaluation by a qualified professional" This is the golden handoff. You identified something. You're not an expert in that specific trade. You're telling the client to get someone who is. This simultaneously serves the client and limits your exposure.

"The inspection does not guarantee..." Reinforcing limitations throughout the report — not just in the scope section — creates multiple touchpoints that establish expectations.

"Observed" / "Noted" / "Identified" Factual, observational language. "Observed evidence of past moisture intrusion at the northwest basement wall." Not "there's a leak" — you don't know there's an active leak. You observed evidence.

The Anatomy of a Defensible Finding

Every finding in your report should follow a consistent structure. Here's the format that holds up:

1. Location

Be specific. "Kitchen" isn't enough. "Kitchen — cabinet below the sink, left side" is defensible. If someone claims you didn't inspect that area, your specificity proves you were there.

2. Observation

What did you see, measure, or test? Stick to facts. "Observed a horizontal crack in the foundation wall, east side, approximately 3/16 inch wide, extending approximately 4 feet in length at roughly 3 feet above the slab."

3. Implication

Why does this matter? "Horizontal foundation cracks can indicate lateral soil pressure and may represent a structural concern."

4. Recommendation

What should the client do? "Recommend evaluation by a licensed structural engineer to determine cause and appropriate remediation."

5. Photo Documentation

Every significant finding should have a photo. Photos are your proof. They show what was visible, what the conditions were, and that you were actually looking at what you're writing about.

Disclaimers That Actually Work

Disclaimers get a bad reputation because many inspectors use boilerplate garbage that no one reads and no court respects. Effective disclaimers are specific, reasonable, and integrated into the report.

Pre-Inspection Agreement Disclaimers

Your pre-inspection agreement (PIA) is legally separate from your report, but they work together. The PIA should include:

• Limitation of liability clause (capped at the inspection fee in many states — check your state law)
• Binding arbitration or mediation clause (keeps disputes out of court where costs explode)
• Statute of limitations (shorter than the default in your state, where legally enforceable)
• Client acknowledgment of inspection scope and limitations

In-Report Disclaimers That Matter

Systems not inspected: "The following systems/components were not inspected due to [specific reason]: solar panel system (specialized equipment required), underground sprinkler system (winterized), swimming pool (covered/closed for season)."

Concealed conditions: "This inspection is limited to visible and accessible components. Conditions concealed behind finished surfaces, underground, or otherwise inaccessible are excluded from this inspection."

Environmental hazards: "This inspection does not include testing or assessment for mold, asbestos, lead paint, radon, or other environmental hazards. If concerned, the client should engage qualified environmental testing professionals."

Appliance remaining life: "The inspector does not provide estimates of remaining useful life for any system or component. Age and condition are noted where determinable, but these are not predictions of future performance."

What NOT to Write — Real Examples That Caused Lawsuits

These are composites from real cases. Learn from other inspectors' mistakes:

❌ "Roof is in great shape — should last another 10 years." The roof leaked 8 months later. The inspector's prediction became a guarantee in the eyes of the court. The client's attorney argued the buyer relied on this statement when deciding not to negotiate a roof credit.

❌ "All electrical appears fine." The panel had a double-tapped breaker that caused a fire. "Appears fine" suggested the inspector looked at everything and found nothing wrong. A detailed electrical inspection noting what was examined and what was observed would have been far more defensible.

❌ "No evidence of moisture or water intrusion." There was active staining on the basement wall that the inspector apparently didn't see — or saw and didn't report. The absence of a finding is not the same as a finding of absence. Better: list what was examined and what was observed. If you checked the basement walls and saw no staining, say "Basement walls examined; no visible staining or evidence of moisture intrusion observed at the time of inspection."

❌ "The seller disclosed that the basement has never leaked." Don't put seller representations in your report. You're reporting what YOU observed. If the seller tells you something, it's hearsay. If you include it and it's wrong, you've now vouched for it.

❌ Left the finding section blank with no explanation. Blank sections imply you inspected and found nothing. If you didn't inspect a system, say why. If you inspected it and found no defects, say "Inspected — no defects observed at the time of inspection."

Photo Documentation Best Practices

Photos are the backbone of a defensible report. Here's how to do them right:

• Photograph every significant finding from multiple angles when possible
• Include context shots — show where in the house the finding is located
• Photograph the good stuff too — photos of properly functioning systems prove you inspected them
• Photograph access limitations — if you couldn't access an area, photograph what blocked access
• Time-stamp your photos — most phone cameras do this automatically. Make sure the setting is on.
• Take more than you need — you can always remove photos from a report. You can't go back and take them later.

Structuring the Report for Clarity

A well-structured report protects you because it proves thoroughness and makes findings impossible to miss:

Summary Page First

Lead with a summary of significant findings. This serves two purposes: clients read it (many don't read the full report), and it shows you prioritized communication.

System-by-System Organization

Organize by system (roof, exterior, electrical, plumbing, HVAC, structure, interior, insulation) rather than by room. This mirrors your standards of practice and demonstrates methodical inspection.

Consistent Rating System

Use a clear, defined rating system for each component:

• Inspected — No defects observed
• Inspected — Maintenance item noted
• Inspected — Repair recommended
• Inspected — Safety concern identified
• Not inspected — [reason]

Narrative Over Checkboxes

Checkbox reports are fast but legally weak. They don't explain what you saw or why it matters. Narrative descriptions — even brief ones — give you room to be specific and show you were thinking, not just checking boxes.

The Pre-Inspection Agreement: Your Legal Foundation

Your report doesn't exist in a vacuum. The pre-inspection agreement (PIA) signed before the inspection is equally important. Key elements:

• Signed before the inspection begins — not after, not emailed later
• Client acknowledges they've read and understood the scope
• Limitation of liability — check your state. Some states cap at the fee; others allow higher limits
• Dispute resolution method — arbitration is generally faster and cheaper than litigation
• Who the report is prepared for — this limits third-party claims. The report is for your client, not for the seller, the agent, or future buyers

Building Reports That Defend Themselves

The best way to write reports that don't get you sued isn't about legal tricks. It's about being thorough, being honest, and being clear. Document what you see. Describe it accurately. Recommend appropriate next steps. Note your limitations. And take a lot of photos.

Every report should be written as if it's going to be read by an attorney two years from now — because it might be. That doesn't mean it should be written in legalese. It means it should be written with precision, specificity, and honesty.

If your current report-writing process makes thoroughness difficult — if you're rushing through descriptions because typing on a tablet in a crawl space is slow, or if you're abbreviating findings because the checkbox format doesn't give you room — consider whether your tools are holding you back. ReportWalk lets you describe findings by voice while you inspect, producing detailed narrative reports without slowing you down. The more detail in your report, the better protected you are.

Write the report you'd want defending you in a deposition. That's the standard.