Report writing craft

The inspection summary page, writing the only page everyone reads

Agents skim, buyers panic, attorneys quote. How to write summary entries that inform all three, and why the summary should build itself while you walk.

By Owen Murray, founder of InspectorKit · Updated July 6, 2026

Every inspector learns the same uncomfortable truth early. You write forty findings and most readers consume five, the ones on the summary page. Agents say it openly, buyers reveal it in their questions, and negotiations quote the summary as if it were the report. Fighting the behavior wastes energy. Writing for it is the craft, and it starts with accepting that the summary page is your report's front door, headline, and closing argument in one screen.

Reading depth funnel, everyone reads the summary, most read the defects, few read every item.

What the summary is for

The summary answers one question for a stressed buyer, what actually needs attention in this house, in what order of urgency. That is its entire job. It is not a table of contents, not a liability recital, and not a proof of thoroughness, the body handles all three.

Which sets the inclusion rule. Safety items always lead, because injury pathways outrank everything. Defects follow, the things that are broken and need a trade. Marginal items appear only when you genuinely advise action, the aging water heater worth budgeting for, not the scuffed door that merely exists. Functional items stay in the body entirely, and a summary shorter than the buyer feared is itself information, most of this house works.

The anatomy of a strong entry

Each summary entry carries three elements, the item, the condition label, and the summary note, and the note is where the writing happens.

The note is one compressed line, action-forward. Repair damaged roof flashing to prevent water intrusion. Add GFCI protection at required locations. Evaluate moisture at the north foundation wall. Verb first, specific object, consequence or purpose where it strengthens. No hedging language, no narrative restatement, no cost guesses, and nothing you would not stand behind if an attorney read it aloud slowly, since the summary is the page attorneys quote.

Compare a weak entry, roof has some issues, see report. It sends the reader hunting, commits to nothing, and reads as either evasion or laziness. The strong version tells them what and why in nine words, and the full three-part narrative waits in the body with the photos for anyone who clicks through.

Writing it while you walk, not at the desk

The summary's traditional failure mode is timing. Written last, at the kitchen table, it becomes a tired retyping session where entries drift from their narratives and the worst findings get the most exhausted prose.

The fix is structural. Write the summary note at the moment you write the finding, while the condition is in front of you and the wording is fresh. In InspectorKit that is a dedicated summary-note field on every item, sitting under the narrative field in the builder, and the summary page assembles itself from those notes as you walk. By the time you reach the driveway, the page every reader will judge you on already exists, written at full attention, entry by entry, with nothing left to compose.

That mechanism is also why summary quality correlates with on-site completion. Inspectors who finish reports at the house write summaries in the same session as the findings, and the coherence shows.

Reading your summary like its audiences do

Three audiences, three read-throughs, ten minutes total, worth doing on your next report.

Read as the buyer, scared and non-technical. Does each entry say what to do next in words a first-time homeowner parses. Is the list short enough to feel actionable rather than catastrophic. Does safety-first ordering tell them where to look before anything else.

Read as the agent, between showings, on a phone. Can they brief their client from your summary alone in ninety seconds. Will your entries survive being read aloud in a negotiation, verbatim, because they will be. Agents route future referrals to inspectors whose summaries make them look competent in that exact moment, and the report example dissection shows the whole page in context.

Read as the skeptic, the seller's contractor or a future attorney. Does any entry promise an outcome, name a price, or diagnose beyond the visible. Does every entry trace cleanly to a body narrative that supports it. The summary and the narrative must agree exactly, since daylight between them is what cross-examination is made of.

When the summary is longer than the buyer hoped

Some houses produce heavy summaries, and the writing question becomes composure. Resist softening real findings to shorten the list, since a curated summary that omits defects is the most dangerous document you can sign. Instead, let the ordering do the emotional work, safety items first with their mechanisms named, defects grouped by system so four plumbing lines read as one project rather than four crises, and the marginal tail clearly marked as budgeting rather than emergency. A long summary organized this way reads as a house with a to-do list. The same content disordered reads as a disaster, and the difference was editorial, not architectural.

The habits that compound

Three practices turn summary craft from effort into default. Write the note with the finding, never after, letting the tool assemble the page. Keep a summary-note voice in your comment library alongside the narratives, so recurring findings carry pre-refined summary lines with them. And end every job with one phone-screen read of the assembled summary before sending, the ninety-second quality gate that catches the entry that drifted.

The body of your report proves you inspected the house. The summary is where you prove you can communicate, and communication is what gets remembered, referred, and re-hired. Write it like the front page it is.

Common questions

What belongs on the summary, everything or only the big stuff?

Defects and safety items, always. Marginal items, selectively, when action is genuinely advised. Functional items never, because a summary that lists everything summarizes nothing. The full detail lives in the body for anyone who wants it.

Should summary entries repeat the full narrative?

No. The summary note is the finding compressed to its actionable core, one line of what and what-to-do. The full observation-implication-recommendation narrative lives with the item, one tap or one scroll away.

What order should summary items appear in?

Safety first, then defects, then any marginal entries you elevated. Within each group, follow the report's system order so readers can map summary lines to body sections without hunting.

Keep reading