Yes, with a clear line. Home inspectors can use AI for marketing, scheduling, client emails and summaries of findings they have already written. Drafting or deciding the findings themselves is where liability grows, because you sign the report and answer for every word. Ask your insurer in writing before changing how reports are produced.
The reason is simple: AI cannot see the crawlspace. It has no eyes on the water stain, no idea whether the crack was fresh, and it will happily write a confident sentence about a roof it never saw. Your liability has always rested on what you observed and reported, so the safe jobs are the ones where the tool never invents an observation.
Where the risk actually sits
People talk about AI liability as if the software itself were the danger. In practice the danger is narrower. A home inspector is judged on three things: did you inspect what the agreement promised, did you report what you observed accurately, and did you stay within the standards you inspect to. A tool can touch the second point and only the second, by changing how a sentence gets written.
That gives a useful test for any job you are thinking of handing over. Ask whether the output becomes a statement about the condition of a house. If it does, a person who stood in that house has to originate it or verify it line by line. If it does not, the worst failure is an embarrassing email, which you can fix before it goes out.
The sorting below uses that test. It is not legal advice, and nothing here replaces a conversation with your insurer or the person who wrote your pre-inspection agreement.
| Job | Does it state a condition? | Verdict |
|---|---|---|
| Website copy, social posts, referral emails | No | Safe: review the services listed for accuracy |
| Booking replies, reminders, reschedules | No | Safe: check dates and fees |
| Summary of your own written findings for the client | Restates yours | Safe with a read-through against the report |
| Tidying grammar in comments you wrote | Restates yours | Supervised: confirm no meaning shifted |
| Turning your voice notes into draft comments | Yes, from your words | Supervised: check every line against photos |
| Deciding severity, urgency or repair cost | Yes | Never delegate |
| Reading photos to identify defects | Yes | Never delegate as the finding |
| Answering a client's technical question after the visit | Yes | You answer; AI may only draft the wording |
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe safe jobs, with a real example for each
Marketing and referral emails
Say you run a solo inspection business and want a short note for estate agents after a busy weekend of inspections. The prompt below gives the model your facts so it has nothing to invent.
Write a 90-word email to an estate agent I have worked with twice.
Facts you may use: I am a solo home inspector; reports are delivered
within 24 hours; I offer same-week appointments; I inspect to my
standards of practice. Do not mention prices, awards or years in
business. Tone: friendly, plain, no hype.An illustrative output: "Hi [first name], thanks again for sending clients my way this spring. A quick reminder for your buyers: I can usually inspect within the same week, and the report reaches them within 24 hours. As a trusted, fully insured inspector, I work to my published standards of practice, so everyone knows what is covered. If a client is on a tight timetable, pass on my number and I will do my best to fit them in. Thanks, [your name]"
What you fix is every claim you did not supply. The model added "trusted" and "fully insured", and it invented a season for the referrals. "Fully insured" is the one to watch: it describes your policy in words your insurer never approved. Delete anything you cannot back up, and keep the facts you gave it. There is a longer treatment in referral emails written with AI.
Scheduling and booking replies
A client emails asking whether you can fit a four-bedroom house, a detached garage and a septic check into Thursday morning. Paste the enquiry and your fee sheet into a Project and ask for a reply that offers two slots. The check here is arithmetic and scope: does the reply quote the right fee for a house of that size, and does it promise a service you do not offer, such as a septic scope? Read the figures against your own fee sheet every time.
Booking tools help too. Spectora's help pages describe an AI scheduling agent and a matching feature called Match, both in free, invite-only early access in October 2026, and neither appears on its main pricing page. Treat early access as exactly that: test it on your own appointments before you let it talk to clients.
Plain-English summaries of findings you wrote
Clients often skim a 60-page report. A summary written from your own findings is a reasonable use, provided it is clearly a convenience and the report stays the record. Here is a before and after, illustrative.
Your original comment: "Shingles at the south slope show granule loss and lifted tabs near the ridge. Recommend evaluation by a qualified roofer."
A good summary line: "The roof covering on the south side is worn and some tabs have lifted. We recommend a roofer takes a look."
A bad summary line the model might produce: "The roof is near the end of its life and will need replacing within two years." You never said that. The model inferred a lifespan and a timescale. That single sentence turns a recommendation to get it evaluated into a prediction you could be held to. So the rule for summaries is that every claim must trace to a sentence in the report, and anything that does not trace gets deleted.
The supervised jobs: your words in, your eyes on the output
The grey zone is turning your own notes into report comments. Spectora's AI Comment Assist is included in both its monthly ($109) and annual ($1,090) plans, according to its pricing page, and ChatGPT or Claude can do something similar from a dictated note. Both are fine when the input is yours and you re-read the output against your photos. Neither is fine when the tool is guessing from a photo alone.
Try it with a worked example. Say you finish a 2,000 square foot house and dictate this on the drive: "Water heater, gas, about nine years by the plate, no drip pan, no seismic strap, the discharge pipe stops short of the floor, no active leaks seen." Your prompt:
Turn this dictated inspection note into one report comment of two or
three sentences. Use only what is in the note. Do not add causes,
age estimates, costs or code references. If something is missing that
a reader would need, list it after the comment under "Questions for
the inspector".
Note: Water heater, gas, about nine years by the plate, no drip pan,
no seismic strap, discharge pipe stops short of the floor,
no active leaks seen.A usable output, illustrative: "The gas water heater's data plate suggests it is about nine years old. No drip pan is installed, and the discharge pipe ends above the floor. No active leaks were observed at the time of inspection. Questions for the inspector: Is the missing strap a defect in this area? Should the discharge pipe termination be recommended for correction?"
What you fix: the model quietly dropped the strap from the comment and moved it into a question. That is good tool behaviour, but only you will notice it. Also check that "suggests" does not overstate a plate reading, and add the recommendation you would normally make. That is the pattern: AI tidies, you decide. The deeper version of this workflow, with comment libraries, is in building a comment library with AI.
The jobs to keep away from AI
Three jobs fail the test, however good the tool sounds in a demo.
Reading photos to find defects. Image models can describe a photo, and describing is not inspecting. They cannot tell a stain from a shadow, they do not know what is behind the panel cover, and they cannot be asked what they would have seen from a different angle. If a client later says there was a defect in a photo you took, "the tool did not flag it" is no defence, and "the tool flagged it, so I included it" is no better when it was wrong.
Severity and urgency calls. Whether a lifted flashing is a monitor item or a safety item depends on things the model does not have: weather history, the age and type of roof, what you saw underneath. These calls are the product you sell. Hand them over and you are selling something you did not make.
Cost estimates for repairs. A model will give a figure instantly, with no area, no scope and no access knowledge behind it. Any number you publish becomes a figure the client holds you to. If your agreement does not include cost estimates, do not let a tool add them.
Questions to ask your insurer, in writing
Do not assume your errors and omissions cover is silent on this. Policies differ, and wording that touches software or automated tools can sit in exclusions or conditions you have never read closely. Send these questions by email so you have the answers on file, and keep the reply with your policy.
- Does my policy exclude or limit claims that involve text drafted by software, if I review and sign the report?
- Do I have to disclose my use of AI tools at renewal, and is there a form for it?
- Does the policy have any condition about how I store client reports and photos, for example in cloud tools I upload them to?
- Would you want me to add wording to my pre-inspection agreement about software-assisted drafting?
- Does cover change if a tool drafts a comment and I approve it without editing?
- If a client disputes a finding, what records would you want me to hold, and for how long?
Ask the person who drafted or reviewed your agreement, too. If a lawyer or your trade association wrote the template, they may have a view you can use, and that beats guessing.
Keep your own notes: the record that protects you
The single most protective habit has nothing to do with software. Keep your own field notes, in your own words, made at the time. If you dictate, keep the audio or the raw transcript. If you use a template app, keep the raw entries before any drafting.
Here is why this matters for AI specifically. If a client disputes a comment, the question is what you observed, not what a model wrote. A timestamped note that says "stain on ceiling below upstairs bath, dry to meter at time of visit" does more for you than the polished sentence that came after. An AI-edited sentence loses the roughness that proves it came from the site visit.
A workable record set for each job looks like this:
- The signed pre-inspection agreement, with its date.
- Original photos with timestamps, not just compressed copies inside the report.
- Your raw notes or dictation, saved before anything is drafted.
- The published report, as delivered, with the delivery date.
- Any messages in which the client asked a technical question, and what you replied.
Spectora and similar platforms store most of these in the job, so check what is retained and for how long, and export what is not. Your own retention period should be at least as long as your insurer's claims window, which is another question for the list above.
Data you should never paste
Client confidentiality is a separate risk from accuracy. A report names the client, the address and sometimes the seller's circumstances. Before you paste anything into a general assistant, remove those details. Replace the name with "[client]" and the address with "[property]".
Then check the plan. On a personal ChatGPT or Claude account, find the privacy setting that lets your chats improve the models and turn it off; the business plans from both vendors leave business content out of training by default. Read the data terms for the plan you actually pay for. The plan-by-plan detail is in whether ChatGPT trains on client data.
A one-page AI policy for a solo inspector
Writing it down turns good intentions into a habit, and it gives your insurer something concrete. Here is a filled-in version, illustrative. Adjust it to your own agreement.
AI USE POLICY - [business name] - reviewed [date]
Allowed without review: website copy, social posts, internal
checklists (no client data).
Allowed with my review before sending: client emails, booking
replies, referral emails, plain-language summaries of my report.
Allowed with line-by-line check against photos: drafting comments
from my own dictated notes.
Never: identifying defects from photos, rating severity or urgency,
estimating repair costs, naming code sections I have not checked.
Data: names and addresses removed before pasting. Training switched
off on every account. Reports never pasted whole.
Records: raw notes and original photos kept [retention period].
Sign-off: I read and approve every finding before publishing.
Insurer informed: [date] / reply filed with policy.What to tell clients, and where to say it
Disclosure is a choice, and it is worth making on purpose rather than by accident. If you decide to mention software, put one plain sentence in your pre-inspection agreement or the cover page of the report, and have whoever reviews your agreement look at it first. If you are revising the agreement anyway, a plain-English summary of the pre-inspection agreement is another job AI can draft for you to check. An illustrative wording: "Software may be used to help draft or tidy text. All observations and findings are made by the inspector, who reviews and approves the report before it is issued."
Notice what that sentence does not say. It does not say the tool inspected anything, it does not promise accuracy beyond the standards you already work to, and it keeps the inspector as the author. Avoid marketing lines such as "AI-powered inspections", which suggest the opposite of what protects you. A client reading that phrase could reasonably think a machine looked at the attic.
Questions will come up in conversation too. A buyer may ask, "Did AI write my report?" A calm, truthful answer works: "I do the inspection and write the findings. I use software to help with wording and layout, and I read every line before it goes out." If that sentence would not be true for your process, change the process, not the sentence.
Using AI on the aftermath: complaints and callbacks
A client rings two weeks later, upset that the furnace failed. This is the moment to be most careful. Drafting your reply with AI is fine as a way to find a calm tone, but give it only facts from your report and notes, and never ask it to assess whether you missed something. That judgement is yours, and if it is serious it belongs with your insurer before you reply in writing. Send the insurer the record set first, then the draft.
A quick sum: what the safe jobs buy you
Take a solo inspector doing 18 inspections a month. Say booking replies, reminders and referral emails take about 20 minutes a job across the week, which is six hours a month. Summaries of findings take another 10 minutes a job, three hours. If safe-job drafting halves that, you recover about four and a half hours a month, with no new exposure on the findings themselves. The comment-drafting job could save more, but it is supervised, so budget the time to check it.
That is the honest trade. The unsafe jobs are the tempting ones because they take the most time, and the safe ones are the dull ones that actually return hours. You can see what the paid add-ons are worth in our break-even tutorial for inspection software, which uses a similar sum.
A realistic mistake and how it showed up
Here is an illustrative scenario. An inspector pastes a dictated note about a deck into a general assistant and asks for a tidy comment. The note said the ledger board connection "looks fine from the exterior, no access to the rim joist." The model returns: "The ledger board is properly attached and structurally sound." The inspector, in a hurry, publishes it.
Nothing in the note supported "properly attached" or "structurally sound", and the limitation, no access to the rim joist, vanished. The failure was not the model being malicious. It smoothed a limitation into a conclusion, which is what models do with hedged text. The fix is a prompt rule, "never remove limitations or access notes", and a habit of searching the output for the words "properly", "sound", "safe" and "fine". Those are the words to hunt for.
How to check the process is working
Once a month, pull two published reports at random and compare three things against the raw notes and photos: whether any comment says more than your note, whether any limitation was dropped, and whether any number or age appeared that you did not supply. If you find one slip in two reports, tighten the prompt. If you find none in six months, you can reduce checking time on the supervised jobs, but never remove it.
If you would rather map the safe and unsafe jobs for your own business with someone, that is what my AI implementation consultation covers. Related hub reading is in the AI guide.
The short version: let AI handle the words around your inspection, keep it away from the observations inside it, write down the policy, tell your insurer, and keep your own notes. That keeps the report yours, which is what clients and insurers are relying on.
Questions inspectors ask before trying AI
Does using AI make me liable for things I would not otherwise be liable for?
Not by itself. Your duty is set by your pre-inspection agreement and the standards you inspect to, and it does not change because a tool drafted a sentence. What changes is the chance of an error slipping in unnoticed. If you sign the report, you own every word, so treat AI text like an assistant's first draft.
Should I tell clients I use AI?
Ask your insurer and whoever wrote your agreement first, then decide on wording. One option is a single line saying software may help draft or tidy text and that the inspector reviews and signs every finding. Disclosure is a business choice, but never let it imply the tool inspected anything.
Is it safe to paste a client's report into ChatGPT?
Only on a plan whose data terms you have read, with names and addresses removed first. Consumer plans let you switch off training on your chats, and business plans do not train on business content by default. Either way, strip personal details, because the report is a client confidentiality matter.
What should I keep if a client disputes a finding?
Keep your own field notes, the photos with their timestamps, the signed agreement and the published report. If AI drafted any wording, the draft matters less than your notes showing what you saw. Contemporaneous notes in your own words are the strongest record you can hold.
Further reads
- Can ChatGPT Write Home Inspection Report Narratives? What to Check — The deeper check for report narratives drafted by ChatGPT.
- AI Home Inspection Software: What It Writes, Who Signs and What It Costs — What inspection software drafts, who signs and what it costs.
- Spectora vs HomeGauge for a Solo Inspector: What Differs, and Where AI Fits — Compare the two main platforms through an AI lens.
- Home Inspector Website: Local Pages and Sample Report Copy With AI — Website copy is a low-risk place for AI.
- Home Inspection AI Tools for the Office Side: Six Jobs, Booking to Payment — Six office-side jobs from booking to payment.
- Thermal Imaging Survey Report: Turn Scans Into Plain-English Findings — How a thermal imaging surveyor writes captions, conditions and a limits statement, uses AI to draft from structured notes and reviews every finding.
- AI-Ready Appraisal Software: What UAD 3.6 Means for Your Practice — The UAD 3.6 dates, the listed software with published prices, the AI features worth paying for and a two-report test for a solo appraiser.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Spectora pricing page (AI Comment Assist) and help pages (AI scheduling agent, Match early access); OpenAI and Anthropic privacy and business-plan pages. Insurance terms vary by policy: confirm with your own insurer.