How to write a home inspection report

To write a home inspection report, capture each finding in the field with its location, a photo and a short note, then organize findings by system, write each one as an observation, why it matters and what to do next, and assign a consistent severity. Add the limitations that affected what you could see, write a summary of the findings that need attention, and do a final review pass before you publish. The rest of this guide walks through each step and the checks that keep the report accurate.

What does a home inspection report need to include?

Before you write a word, know what the finished report has to contain. Most residential reports share the same parts, even when the layout differs.

Part	What it does for the client
Cover and property details	Confirms the address, date, client, weather and who attended
Scope and standards	States what the inspection covers and which standards of practice you follow
Summary	Lists the findings that need attention, ranked by importance
Findings by system	Roof, exterior, structure, electrical, plumbing, HVAC, interior and so on
Photos and captions	Shows each condition and where it is
Limitations	Records what you could not access or evaluate, and why
Next steps	Tells the client who to call and what to ask

Your pre-inspection agreement and your state's rules shape the scope, so the report should match what you agreed to inspect. If you haven't tightened that document recently, see what a pre-inspection agreement should cover.

Step 1: Set up the report before you arrive

A report is easier to write when the structure is ready before the inspection starts.

Open the right template for the property type: a single-family home, a condo or a new build each have different sections that apply.
Add the services booked. A home inspection with a radon test and a sewer scope may produce separate reports or separate sections.
Fill in what you already know: address, year built, square footage, client and agent names.
Note anything the client told you when booking, such as a concern about a wet basement. You will want to address it directly.

If your template doesn't fit the way you walk a house, fix the template rather than working around it every inspection.

Step 2: Capture findings in the field, not later

The single biggest source of report errors is reconstructing the inspection from memory and a camera roll at the kitchen table. Record each finding where you see it.

For every finding, capture three things on the spot:

Location. "Primary bathroom, under the sink," not "bathroom."
A photo, with a second wider shot if the close-up alone won't tell the client where it is.
A short note of what you observed, in your own shorthand if that's faster.

Use your app's checklist or the template's sections as a prompt so you don't skip a system. If you are working in a basement or a rural property without signal, an offline-capable app keeps the notes and photos attached to the inspection until it syncs. Working without signal has practical habits for that.

Step 3: Organize findings by system and location

Clients read reports in the order you present them, so present them in an order that makes sense. Most inspectors follow the house by system (roof, exterior, structure, electrical, plumbing, heating and cooling, interior, insulation and ventilation, fireplaces, garage) because it matches standards of practice and makes it easy for a contractor to find their part.

Within a system, order findings by location, then by importance. Avoid scattering one problem across three sections. If a roof leak has caused attic staining and a ceiling stain in a bedroom, write the main finding under the roof and cross-reference the other two locations in a sentence.

Step 4: Write each finding as observation, implication, recommendation

Each finding should answer three questions for the client:

What did you see? A specific, factual description.
Why does it matter? The likely consequence if it is left alone, stated with appropriate caution.
What should happen next? Who should evaluate or repair it, and how soon.

Here is the difference in practice.

Weak: "GFCI issue in kitchen."

Clear: "The receptacle to the right of the kitchen sink did not trip when tested with a GFCI tester. Receptacles near water are expected to have ground-fault protection, which reduces the risk of electric shock. Recommend a licensed electrician evaluate and correct."

The clear version is longer, but the client can act on it, and a contractor knows exactly where to go. For a deeper look at the structure and more examples, read defect narratives: observation, implication, recommendation.

Keep it within your scope

You observe and report. You don't diagnose the cause of a crack beyond what you can see, quote repair costs or guarantee how long a component will last. When something is outside what you can evaluate, say so and name the right specialist: a structural engineer, a licensed electrician, a roofing contractor or a qualified HVAC contractor.

Step 5: Assign a severity to every finding

Severity tells the client which findings to read first. Use a small, defined set of levels and apply them the same way every time. A common pattern is three tiers:

Safety or major concern: a condition that may cause injury or significant damage, or a system that isn't working.
Repair or monitor: a defect that needs correcting but isn't urgent.
Maintenance or minor: routine upkeep and small items.

Write a one-line definition of each level and put it in the report, so the client and agent read them the same way you do.

Step 6: Record limitations and items not inspected

A limitation is as important as a finding. If the attic hatch was screwed shut, the crawl space was flooded or the roof was too steep to walk, write down what you could not inspect, why, and what the client should do about it.

Good limitation wording is specific: "The crawl space was not entered because standing water was present at the access. Recommend a further evaluation once the water has been addressed." General boilerplate in the back of the report doesn't replace that.

Step 7: Write the summary last

Once the findings are written, build the summary from them. It should list the findings that need attention, highest severity first, each in one or two sentences with a link or page reference to the full finding.

Keep these points in mind:

The summary is where agents and clients spend most of their time, and it often drives repair requests.
Don't introduce anything in the summary that isn't in the body.
Say clearly that the summary is not a substitute for reading the full report.

Step 8: Do a review pass before you publish

Read the report as the client will read it. A short, consistent checklist catches most problems.

Review checklist

Property details, client name and date are correct.
Every finding has a location, a clear observation and a recommendation.
Every photo has a caption and sits beside the finding it explains.
Severity levels are consistent: similar conditions have the same level.
No reused comment describes something that isn't true of this house (wrong room, wrong material, wrong count).
Limitations name what wasn't inspected and why.
The summary matches the body, with nothing missing and nothing new.
No repair costs, guarantees or diagnoses beyond your scope.
Spelling of names and the address is right.

If you use AI to help draft wording, review it against your own observation of this home. The tool may phrase a finding well and still get a detail wrong. AI in home inspection reports covers where it helps and where to slow down.

Step 9: Publish and deliver

Decide how and when the client receives the report. Many inspectors publish an online report with a downloadable PDF, and some hold the report until the agreement is signed or the inspection is paid for. Whatever your policy is, make it known when the client books, not when they are waiting for the report.

When you deliver, include a short note: the report is ready, the summary lists the main findings, and here is how to reach you with questions.

Step 10: Learn from every report

After each report, spend a few minutes on improvement:

Save new wording you wrote twice into your comment library.
Fix any template section you skipped or worked around.
Note questions clients asked after reading the report. A recurring question usually points to wording that isn't clear.

Over time, these small edits make each report faster to write and easier to read.

How iSpector helps

iSpector inspection reports start from a residential template you can tailor, keep photos and captions with the findings they explain, include severity levels, a summary of findings and a reusable comment library, and let you release the online report and PDF immediately or once payment, a signed agreement or both are in place. The inspector app works offline and syncs when you reconnect.

Key takeaways

Capture location, a photo and a note for each finding at the moment you see it.
Write every finding as what you saw, why it matters and what to do next, and stay within your scope.
Use a small set of defined severity levels and apply them consistently.
Treat limitations as findings: say what you couldn't inspect, why and what to do.
Build the summary from the body last, then review the whole report against a checklist before publishing.

How to write a home inspection report, step by step