Report Writing, Editing, and Client-Ready Document Production

From Field Notes to Client Document

The inspection is not complete when you leave the property. Your client — and every professional who will evaluate your work — judges you primarily on the report you deliver. A thorough field inspection paired with a weak report is a failed inspection. This lesson walks you through converting your tagged field data and photographs into a complete, professionally formatted, client-ready narrative report that satisfies the written-report requirements of both the InterNACHI and ASHI Standards of Practice.

Structure of a Complete Inspection Report

Every report must contain certain required elements regardless of which software platform you use:

• Property information page — address, date of inspection, weather conditions, client name, and inspector name and license number.
• Scope and limitation statements — what systems were inspected, what was excluded and why, and the standard of practice under which the inspection was performed.
• System sections — one section per major system: roofing, exterior, foundation and structure, electrical, HVAC, plumbing, interior, insulation and ventilation, fireplaces and solid-fuel appliances.
• Narrative descriptions for every finding — not checkboxes alone. Both InterNACHI and ASHI Standards of Practice require that the report describe each condition observed.
• Embedded, captioned photographs — each photograph must be labeled so a reader who was not present understands exactly what they are looking at and where it is located.
• Summary page — a consolidated list of all significant findings, organized by severity classification.
• Inspector signature block — your name, credential(s), license number, and date.

Writing Clear Narrative Descriptions

Each finding entry follows the same logic: location → observation → classification → recommended action.

Weak entry: "Electrical panel issue noted."

Strong entry: "Main electrical panel (utility room, east wall): The panel cover was missing two knockouts, leaving energized bus bars accessible. Classify: Safety hazard. Recommended action: Have a licensed electrician evaluate and repair before occupancy."

The strong version tells the client where the problem is, what was seen, why it matters, and what to do next. It does not diagnose why the knockouts are missing, it does not estimate a repair cost, and it does not name a specific contractor. All three of those omissions are intentional and required.

Severity Classifications

Both InterNACHI and ASHI use a three-tier classification system. You must apply these consistently across every finding:

• Safety hazard — a condition that poses an immediate risk of injury or death (example: exposed energized wiring, inoperative smoke detectors, missing stair guardrails).
• Major defect — a condition that significantly affects the habitability, structural integrity, or a primary system of the building (example: active roof leak, failed HVAC heat exchanger, significant foundation crack with displacement).
• Maintenance item / Monitor — a condition that is not immediately dangerous or structurally significant but should be corrected or watched (example: caulking failure at a window frame, minor efflorescence on a block wall).

Misclassifying a safety hazard as a maintenance item is never a minor error — it exposes your client to real risk and exposes you to professional and legal liability.

Recommended Action Language

Your report recommends one of three actions for each finding:

1. Repair — for conditions clearly within normal trade practice to correct.

2. Evaluate by a licensed specialist — for conditions where cause or scope requires expertise beyond visual inspection (structural engineer, electrician, HVAC technician, plumber, etc.).

3. Monitor — for conditions that are not currently deficient but could develop.

Never include cost estimates. Never recommend a specific contractor by name. Both practices violate the InterNACHI and ASHI Codes of Ethics and can create conflicts of interest or implied warranties.

Language That Must Not Appear in a Report

Before you export your final PDF, review every paragraph for prohibited language:

• Warranty or guarantee language — phrases like "this roof will not leak" or "the structure is sound" imply a warranty you cannot provide and did not offer.
• Cause diagnoses requiring destructive testing — you cannot open walls; do not state causes you cannot visually verify.
• Cosmetic judgments outside scope — paint color, landscaping preference, and décor are not inspection findings.
• Contractor recommendations by name — ethically prohibited and a conflict-of-interest risk.
• Passing or failing the property — a home inspection does not pass or fail a property; it describes conditions.

The Peer-Review Step

Peer review is a professional practice, not a classroom exercise. Real inspection firms use internal QA review before reports are released to clients. When reviewing your partner's draft, use the editorial rubric systematically: check every finding for unclear language, missing or miscaptioned photographs, severity classification consistency, scope overreach, and prohibited language. Written feedback must be specific — "unclear" is not useful feedback; "this sentence could imply a warranty; suggest rewording to describe what was observed" is.

Code of Ethics Compliance Checklist

The final step before export is running the Code of Ethics compliance checklist. This is not optional. Both InterNACHI and ASHI Codes of Ethics carry consequences up to decertification for violations. Common checklist items include confirming no contractor referral language is present, no cost estimates appear, scope limitations are stated, and the report is addressed only to the client.

Safety Note

Your report is itself a safety document. A missed safety-hazard classification — or a finding omitted entirely — can result in client injury. Treat every finding entry with the same care you would give to a real client transaction. If you discover during report writing that your field notes are ambiguous about a condition, note that limitation explicitly rather than guessing at what you observed.