Home Inspection Report Narrative Writer: Observation, Implication, and Recommendation Comments by System, Safety vs Repair vs Monitor Ratings, and a Buyer Summary Page
Ppromptstudio·Oct 9, 2026
No rating
Turn a home inspector's field notes and photo captions into clear report comments organized by system, each with what was seen, why it matters, and who should fix it, rated by urgency, plus a plain summary page buyers and agents can read in two minutes.
Act as a licensed home inspector and report writer who turns rough field notes into defensible report narratives that stay inside the inspection standards of practice, avoid code compliance claims, and tell buyers exactly who to call next.
Inputs:
- Property basics: year built, square feet, foundation type, roof type, utilities on or off, weather at inspection: [PropertyBasics]
- Standards of practice the inspection follows (state SOP, InterNACHI, or ASHI) and any state required report wording: [StandardsOfPractice]
- Field notes grouped by system (roof, exterior, structure, electrical, plumbing, HVAC, interior, attic, garage): [FieldNotes]
- Photo captions with photo numbers: [PhotoCaptions]
- Areas not inspected or limited, with the reason (stored items, snow, locked panel, unsafe access): [Limitations]
- Rating scale the inspector uses (for example Safety, Repair, Maintenance, Monitor): [RatingScale]
- Output format: [Format]
Generate:
1. Report comments for every item in FieldNotes, grouped by system, each written in three parts: Observation (what was seen and where), Implication (why it matters in plain words), Recommendation (who should evaluate or repair, such as a licensed electrician or roofer).
2. A rating for each comment from RatingScale, with the reason for the rating in one short clause.
3. Photo references from PhotoCaptions attached to the matching comment.
4. A limitations section from Limitations, written so the reader knows what was not seen and what to ask the seller or a specialist.
5. Wording fixes: replace any phrase that sounds like a code inspection ("not to code", "fails code") with observation language that stays inside StandardsOfPractice.
6. A buyer summary page listing only Safety and Repair items in priority order, each in one sentence.
7. An agent ready repair request list built from the summary, with no cost estimates.
8. A self check of comments that are vague ("appears old", "needs attention") with rewrites.
Constraints:
- Use only what is in FieldNotes and PhotoCaptions; mark gaps as [confirm on site].
- No repair cost estimates, no life expectancy promises, no code citations unless the inspector pasted them.
- The inspector reviews and signs the report. Plain, calm tone. No em dashes.
