Home Inspection Report Summary: AI Repair-Request Lists for Buyers

A realtor can use AI to turn a buyer's inspection report into a sourced list of observed defects, open questions and repair requests. Obtain permission before uploading, remove unnecessary personal details, keep page and photo references, then compare every AI line with the original. The buyer chooses priorities; the inspector explains findings; qualified advisers handle specialist or contractual advice.

The useful output is a short evidence ledger, not a second inspection report. It should say what the inspector actually observed, where the statement appears, what the inspector recommended, and which decision remains with the buyer. A polished paragraph that silently changes “further evaluation recommended” into “replace the system” is worse than an untidy but faithful note.

Follow me on Instagram@sagnikteaches

Agree the buyer's question before opening the PDF

Ask the buyer whether they need a plain-English reading guide, a list of questions for the inspector, or a draft of matters they may want to raise with the seller. These are different jobs. A reading guide explains the report; a repair-request list selects findings for discussion; a formal request can have contractual consequences. Keep the last step under your brokerage's process and the buyer's instructions. Do not let the AI pick the buyer's negotiating position.

Connect on LinkedInSagnik Bhattacharya

Write the scope in one sentence before uploading anything: “Extract reported findings and recommendations, cite their pages, and leave all severity, price and negotiation choices open.” That instruction prevents a familiar drift. AI summarisation tools often compress a caution, an observation and a recommendation into one confident claim. An agent needs to preserve the distinction because a buyer may act differently on an active leak, a component that was inaccessible and a cosmetic mark.

Subscribe on YouTube@sagnikteaches

The inspector's report remains the source. InterNACHI's Home Inspection Standards of Practice describe a general inspection as an observation of accessible areas on a particular date, not a prediction of future conditions. They also say that a component being near or past the end of its useful life is not in itself a material defect, that the inspector is not required to estimate repair costs, and that the inspection does not determine whether the purchase is advisable. Your summary should keep those limits visible, even if the inspector worked under a different standard or agreement.

Get the complete report and any addenda rather than a screenshot of its summary page. Check the document's page count, inspection date, property identifier, photograph labels and appendix references. If the report mentions a specialist assessment delivered separately, note that the document is missing; do not pretend the main report contains its result. For report-writing and inspector responsibility, the companion tutorial on inspection narratives and liability checks covers the inspector's side. Here the agent is converting a completed report into a buyer-facing decision aid.

Prepare only the material the assistant needs

Read the buyer's permission and your brokerage's approved AI policy first. An inspection PDF can contain a property address, buyer name, access information, signatures, photographs of personal belongings and contact details. Remove data that is unnecessary to extract findings, while retaining the page number, room or system label, observation, recommendation and image reference. Redaction means removing the data from the file, not putting a black rectangle over text that remains searchable underneath. If you cannot reliably redact, use a manual excerpt with exact quotations and page references instead of the whole PDF.

For example, an illustrative 42-page report includes a title page with the buyer's telephone number and a photograph showing a key-safe code. A safe working copy deletes the telephone number and replaces that photograph with a note such as “photo 17 withheld; see original page 26”. Keep the original in the authorised transaction file. The AI copy still has enough context to map the inspector's words, but it does not carry the code into another system.

ChatGPT is one possible document assistant. OpenAI's file-upload guidance says it can read text and images in PDFs, tells users to review the response, and notes that availability depends on plan limits and account or workspace settings, and that embedded images are not always picked up. Its data-controls guidance says personal-account users can turn off “Improve the model for everyone”, and that business workspaces are not used for model training by default. A training switch is only one part of confidentiality: check your workspace's access, retention and sharing rules, and obtain the buyer's permission before uploading.

If the PDF is scanned, inspect the extracted text before asking for a summary. Search for a distinctive room label and a number such as “photo 12” in the assistant's view; compare the result with the page. A bad scan can turn “no visible leakage” into “visible leakage”, drop a negative word or shift a comment to the next photograph. When text extraction fails, ask the inspector for an accessible copy or transcribe the small relevant passage manually. Do not ask the model to infer a finding from an unclear image.

Extract an evidence ledger before setting priorities

Give the assistant a narrow first task: one row per discrete finding. Make it copy the inspector's level of certainty and use “not stated” where the report is silent. The ledger is an internal review tool, not buyer advice. Use columns for the report page, system or room, observation, inspector recommendation, photo reference, limitation, and a blank buyer-decision field. If the same defect appears in a summary and a detailed section, merge those references into one row after verifying they describe the same observation.

Read only the attached inspection report. Produce a table with one row for each
reported defect, limitation or recommended follow-up. Columns: page, section,
exact short quotation or faithful close paraphrase, inspector recommendation,
photo ID, and uncertainty. Preserve words such as "may", "appears" and
"not inspected". If a page or recommendation is unclear, write "CHECK SOURCE".
Do not diagnose, rank severity, estimate cost, suggest a negotiating position,
or turn an observation into a confirmed defect. Do not use outside knowledge.

In a sample output, the assistant might write “Page 18: water heater failed, replace immediately.” Suppose the report actually says “Water heater did not respond to the normal control during the inspection; have a qualified contractor evaluate before use.” The corrected ledger uses that wording and records “function not confirmed” as the uncertainty. “Failed” and “replace” are diagnoses the inspector did not make. This small correction can change the buyer's next call from demanding replacement to asking for an evaluation.

Inspect every row against the PDF. Use a simple mark: verified, needs clarification, or remove. Ask the assistant to identify where each line came from, then open that page yourself. A model can produce plausible page numbers and photo IDs, so the citation is a navigation aid, not proof. When a section is long, read the paragraph before and after the quoted sentence; limitations often sit there. Ask the inspector when wording is ambiguous. The agent should not reinterpret a technical report on the inspector's behalf.

Keep a separate “not inspected” list. If an attic hatch was blocked by stored goods, the ledger should say “attic not accessed” and retain the stated reason. It should not say “attic is sound” or “attic has a defect”. That distinction gives the buyer a practical question: whether access or a further inspection can be arranged under the transaction's timetable. For more on tracking those dates, see contract deadlines and contingencies with AI; the report assistant should never calculate a deadline from memory.

A 42-page report becomes a nine-line discussion list

Consider an illustrative buyer who receives a 42-page report containing 18 comments and 31 photographs. After the first extraction, the agent finds nine comments that might affect a buyer decision. Three are observations with explicit recommendations, two are conditions needing clarification, two concern items the inspector could not access, and two are maintenance notes. The numbers are for this example, not a benchmark for a real report. The agent spends 20 minutes building the ledger, 25 minutes checking nine source passages and photographs, and 15 minutes discussing the shortlist with the buyer. Those are illustrative working times, not a service promise.

Suppose the report says the kitchen sink waste connection dripped during testing on page 14, with photo 9 and a recommendation for repair. It also records an active stain below a roof penetration on page 8, with a recommendation for specialist evaluation of the source. A third passage on page 23 says the electrical panel cover was not removed because access was obstructed; no condition of the hidden components was determined. The three rows must not be presented as three confirmed repair jobs. One is an observed leak with a repair recommendation, one calls for investigation, and one records an inspection limit.

The other five example rows are a loose exterior handrail, a cooling system that could not be tested under the reported conditions, a window seal with fogging, a bathroom extractor that did not operate, and a routine note to monitor surface drainage. The report's exact wording controls each entry. The buyer may decide that only four of the nine deserve a request. The table deliberately has no “urgent”, “minor”, or price column because those labels can sound like professional assessments when the report did not provide them.

After the buyer selects four items, the agent creates a request list with four source references, not a new 42-page report. In this illustration, the buyer asks for the sink connection to be repaired, the stain to be evaluated by an appropriate specialist with a written finding, the handrail to be secured, and the panel to be made accessible for a further look. Whether each action is feasible, who chooses the contractor, the wording of any credit, and the timing of any follow-up are left for the buyer and the transaction professionals. Do not call a requested evaluation a completed repair.

If the buyer asks “how much should we demand?”, separate two questions. First, what does the original report establish? Second, what response does the buyer want after speaking to appropriate contractors or advisers? The inspection report does not usually establish a repair price, and a model-generated number is not a quote. In the illustration, a contractor's written estimate of $240 for the sink connection would be labelled as a separate, dated estimate; it would never appear as though it came from page 14 of the inspection report.

Use buyer choices to draft a request, then remove assumptions

Once the buyer has chosen items, give the assistant only verified ledger rows and the buyer's stated preferences. Ask for neutral wording that identifies the observation, the report reference and the requested next action. Keep any formal notice, deadline or remedy language aligned with the actual contract and brokerage process. The AI should leave placeholders where those details have not been supplied. A draft is especially useful for spotting whether two findings have been conflated, but it is not authority to send the request.

Draft a buyer repair-request list from the four verified rows below.
For each item give: report page and photo, what the inspector observed,
what the inspector recommended, and the buyer's requested action.
Use only the buyer choices supplied. Leave [contract deadline] and
[delivery method] as placeholders. Do not add a price, diagnosis,
code claim, warranty, seller obligation or legal conclusion.
At the end list any missing information that prevents a faithful draft.

An illustrative AI draft might say, “Seller must replace the leaking roof before closing.” Compare that with the source: a stain beneath a roof penetration and a recommendation for specialist evaluation. A faithful revision is, “Regarding the stain described on page 8, photo 3, buyer requests a qualified specialist's written evaluation of the source and recommended remedy; buyer will review that finding before choosing a further request.” Whether that request is appropriate under the contract is for the buyer and qualified transaction advisers to decide. The agent's contribution is traceable wording.

Another illustrative repair line might state, “Repair all plumbing leaks in the property.” The report identifies one observed drip at the kitchen sink waste connection. Replace the broad line with that exact location and page. “All plumbing leaks” sounds efficient but creates an unsupported promise and a scope dispute. A seller may otherwise answer that an unrelated tap was repaired while the buyer expected the sink connection. Narrow wording also makes a later reinspection easier to compare with the request.

Send the buyer a choice sheet before converting anything into formal language. For each row, offer “ask a question”, “seek an evaluation”, “request repair”, “discuss a documented credit”, or “take no action”, subject to the contract and professional advice. The buyer can select a different path for two similar looking findings. If the buyer wants to negotiate a credit, obtain a documented basis and record its date; do not ask AI to invent a market price. If a request depends on a specialist's opinion, describe it as conditional rather than treating a tentative observation as settled.

Six report details that change the right wording

Age is not failure. Imagine page 11 states that a heating unit appears older and recommends budgeting for future replacement, while also recording that it operated during the inspection. An AI draft of “heating failed; replace now” is wrong twice. The buyer-facing line can say “the inspector noted age and suggested planning for future replacement; operation was observed on the inspection date.” The buyer can then decide whether to ask for service history or a specialist review. Do not convert a planning note into an observed failure.

Stain is not a known source. A ceiling stain on page 8 may be near a roof vent, but the inspector may not have established whether the mark is active or where water entered. The summary should state the observed stain and any recommendation for investigation. If the assistant writes “roof flashing leaks”, ask it to show the exact report line. If it cannot, remove that cause. An evaluation request can be legitimate without claiming that the cause is already known.

Inaccessible is not clear. In a different illustrative report, stored boxes prevent access to a crawl space. The model may omit the limitation because it is not labelled as a defect. Add a row saying the area was not inspected, quote the reason and ask the buyer whether a further inspection should be requested. The request needs to be about access and inspection; “repair crawl space damage” would assert damage no one observed. A limitation can matter to a buyer even when there is no defect to rank.

A photograph is not a diagnosis. Suppose photo 22 shows a dark patch around a window, but the caption says only “discolouration observed; source not determined”. Do not call it mould, rot or active water ingress from the image. The camera may exaggerate colour, and the inspector may have had a reason to avoid a diagnosis. If the image and written note seem inconsistent, send a precise clarification question to the inspector: “Does the page 29 observation refer to photo 22, and was moisture measured?” The answer belongs in the record before any request is drafted.

Testing conditions matter. A cooling unit may be marked “not tested due to conditions at inspection”. An AI summary can mistakenly put it in a “broken equipment” group. Correct the line to “operation not verified” and preserve the stated reason. The buyer can ask about a later test, a service record, or another way to understand the condition. Neither the agent nor the model should infer a defect from the absence of a test.

Maintenance notes need their own lane. An inspector may advise cleaning gutters or monitoring surface drainage without reporting an active defect. Put those items on a maintenance or follow-up list, separate from the buyer's selected requests. If every routine note appears in the seller request, the buyer may lose sight of the matters they actually wanted to discuss. The division is an organisational aid only: the buyer still decides what to raise.

Check the request against the report, the buyer and the clock

Use a three-pass review. Pass one is source fidelity: open every cited page, confirm the exact component, room, condition, limitation, recommendation and photo ID. Pass two is buyer authority: compare each action with the buyer's written selection and remove items the buyer did not choose. Pass three is transaction fit: check the current contract, notice method, recipients and actual dates with your brokerage or qualified adviser. A model may produce fluent contract language that belongs to a different form or agreement. Do not trust it with the final deadline.

For example, the assistant may label a finding “page 19, bathroom fan” because a PDF viewer counts the cover separately, while the printed report labels it page 18. Check both references and use the report's visible page label, adding the PDF page if your team needs it internally. If a photo appendix repeats the finding with a new number, verify that it depicts the same component. A request that points to the wrong page is easy to dispute and difficult for the buyer to follow.

Another failure is double counting. The summary page may list “loose handrail” and the detailed exterior section may explain the same handrail with two photos. The AI may create two repair items. Merge them into one ledger row with both source references after manual checking. Conversely, two loose handrails in different places should remain separate. Use the room or location description to distinguish them; do not let a generic noun decide the merge.

Keep the agent's short note, the original report, the verified ledger, the buyer's selections and the sent request together in the authorised transaction record. Label the AI output “draft” until a person checks it. Record who verified the source and when, especially if a revised inspection report arrives. If a new addendum changes a finding, update the ledger and ask the buyer to reconsider the affected choice before sending. For a wider file-review process, brokerage compliance file checks gives a separate workflow.

Do not assume a seller's response resolves the underlying issue. If the response says “repaired”, identify which request item it addresses and what evidence the buyer wants to see. If it says “credit offered”, show the buyer the exact amount and any conditions without claiming it covers all future work. If it disputes the finding, return to the inspector's wording and request clarification where useful. The buyer, not the AI summary, decides what response is acceptable with the proper professional advice.

A concise note for the buyer after verification

The buyer does not need to read an AI transcript. They need a faithful route back to the report and clear choices. The following illustrative note assumes the four selected items from the 42-page example have already been checked. It avoids saying the property is safe, unsafe, a bargain or a bad purchase. It also avoids presenting a suggested request as an inspector's instruction.

Hi [first name], I checked the proposed list against the inspection report. The inspector recorded a drip at the kitchen sink waste connection (page 14, photo 9), a stain below a roof penetration requiring specialist evaluation (page 8, photo 3), a loose exterior handrail (page 27), and an electrical panel interior that could not be inspected because access was obstructed (page 23). These are report observations and limits, not diagnoses from me. Please tell me which items you want to raise, whether you prefer questions, evaluations or repair requests, and any points you want to discuss with the inspector. I will then put your choices into the transaction's required format for review before anything is sent.

The note is deliberately shorter than the ledger. It tells the buyer what was observed, what remains uncertain and what decision they must make. If the report says something different, the original wins. If the buyer asks about structural safety, electrical compliance or the probable cost, direct that question to the inspector or an appropriate qualified professional. If the buyer asks about contractual rights or the form of a notice, use your brokerage process and qualified legal advice. A home inspection report summary is successful when the buyer can see the evidence and make an informed request without mistaking an AI draft for professional advice.

Questions before sending an inspection summary

Can the agent decide which inspection findings are serious?

The agent can organise the inspector's stated findings and help the buyer compare options, but should not diagnose a defect or invent a risk rating. Where seriousness is unclear, preserve the inspector's exact description, ask the inspector for clarification and let the buyer choose what to pursue with appropriate specialist input.

Should the full inspection report go to the seller?

Check the buyer's instructions, the inspection agreement and the applicable transaction process before sharing. A targeted request can identify the relevant report finding and page without automatically circulating unrelated observations or personal information. Have the broker or qualified adviser review the proposed disclosure where there is uncertainty.

What if the AI cannot read a report photo or scanned page?

Mark the affected finding unverified. Read that page and its caption yourself, or ask the inspector to clarify it. Do not use a generated visual interpretation as the basis of a request. Attach or refer to the original page only after confirming the buyer has authorised that use.

Further reads

• Home Inspection Report Template: Build a Comment Library With AI — See how inspectors structure comments before an agent extracts them.
• AI Home Inspection Software: What It Writes, Who Signs and What It Costs — Understand what inspection software drafts and who owns the report.
• Home Inspection Pre-Inspection Agreement: A Plain-English Summary With AI — Check the inspection scope and the agreement's limits.
• AI Transaction Coordinator: Which Real Estate Tasks to Automate — Keep the request and response in the transaction workflow.
• Home Inspection AI Tools for the Office Side: Six Jobs, Booking to Payment — Separate the inspector's office automation from the buyer summary.
• How Much Does Home Inspection Software Cost? Break-Even With AI Add-Ons — What solo inspectors pay for home inspection software, which AI features cost extra, and the inspection count where each pricing model breaks even.
• Spectora vs HomeGauge for a Solo Inspector: What Differs, and Where AI Fits — Spectora and HomeGauge compared for one inspector: prices over three years, desktop against web writing, the import path, and where AI fits in each.
• How to Get More Home Inspections: Realtor Referral Emails Written With AI — Three emails for agents (introduction, thank-you, quarterly check-in) with AI prompts and drafts, consent points to check and a sheet that tracks every booking.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: InterNACHI, Home Inspection Standards of Practice (accessed 4 November 2026); OpenAI Help Center, Uploading files and audio to ChatGPT and Data controls in ChatGPT (accessed 4 November 2026).