How to Write Clear, Defensible Defect Narratives

What Is a Defect Narrative?

A defect narrative is the written description of an issue found during a home inspection. It typically includes the location of the defect, a description of what was observed, the potential implication or safety concern, and a recommendation for further action. The narrative is the core of your inspection report — it's where your expertise, communication skills, and liability awareness intersect. Writing clear, defensible narratives is one of the most important skills a home inspector can develop. For broader report-level advice, see our guide on 10 tips for writing better inspection reports.

---

The Four-Part Narrative Framework

The most effective defect narratives follow a simple four-part structure:

Location — Observation — Implication — Recommendation (LOIR)

Start by identifying where the issue was found ("In the main electrical panel on the north wall of the garage..."). Then describe exactly what you observed ("...a double-tapped breaker was noted on a 20-amp circuit"). Next, explain why it matters ("Double-tapped breakers can lead to loose connections, arcing, and potential fire hazards"). Finally, provide a recommendation ("Recommend evaluation and repair by a licensed electrician"). This framework ensures every narrative is complete, professional, and legally sound.

---

Common Mistakes to Avoid

Many inspectors fall into common traps that weaken their narratives. Vague language like "appears to be in poor condition" provides no actionable information. Overly technical jargon confuses clients who don't have a construction background. Diagnosing root causes or estimating repair costs pushes you outside your scope of practice and increases liability. Emotional or alarming language ("This is extremely dangerous!") can cause unnecessary panic and may be used against you in litigation. Stick to objective, measured language that describes facts and defers specialized evaluation to the appropriate licensed professional.

If you're not sure whether your narrative hits the right tone, paste it into the Narrative Refiner — it rewrites rough notes into polished, defensible language using the LOIR framework automatically.

---

Building a Comment Library

Experienced inspectors maintain a comment library — a database of pre-written, vetted narratives organized by system and component. A good comment library saves time in the field, ensures consistency across reports, and reduces the risk of off-the-cuff wording that could create liability. Start by categorizing your most common findings (e.g., GFCI not installed where required, missing kick-out flashing, inadequate attic ventilation) and writing a polished narrative for each. Over time, your library becomes one of your most valuable business assets. RepoDeck includes a built-in comment library with AI-powered narrative generation to help you build and refine your collection faster.

---

Real-World Examples

Here are examples of weak narratives versus strong ones for common findings:

Example 1: Water Heater

Example 2: Bathroom Outlet

The strong narratives identify the location, provide specific details (type, code reference, age), explain the implication without diagnosing failure, and recommend a qualified professional for further evaluation. Not sure what a specific defect looks like? Our Defect Wiki has detailed descriptions, photos, and pre-written narratives for hundreds of common findings.

---

Pairing Narratives with Photos

A narrative without a supporting photo is only half as effective. For every deficiency you document, attach at least one clear photo — ideally a context shot and a detail shot. The narrative tells the reader what and why; the photo shows them where and how bad. Together, they create documentation that's nearly impossible to dispute. For detailed guidance on inspection photography, read our photo best practices guide.