Real Estate Transfer Inspection Finding Disputed Response
Purpose
A disputed transfer inspection finding shows up weeks after the tech has moved on to other work, from a buyer's agent, a second inspector, or a seller who does not like what the number means for the sale price. The report was written to be read by people who never stood at the tank, so a dispute is not a failure of the inspection, it is the report doing its job under pressure. What breaks a shop here is not the finding, it is an improvised response: the original tech calling the agent back defensively, a number quietly "corrected" to keep a deal alive, or a friendly email thread that keeps going after someone has mentioned an attorney.
This SOP fixes what happens the moment a finding is challenged: who owns the response, how the original file gets checked before anyone answers, and what a re-inspection is allowed to be. It does not cover running the inspection itself, that is the transfer-inspection SOP's ground, and it does not resolve what a report legally proves in a transaction, which stays a question for the reader's own attorney every time it comes up here.
Scope
Covers the shop's response from the moment a delivered transfer-inspection finding is challenged by a buyer, seller, agent, lender, or a second inspector's conflicting report, through either standing behind the original finding or issuing a new, separately dated re-inspection. Does not cover the inspection procedure that produced the original report, owned by the system-inspection-for-a-property-transfer SOP, and does not cover general customer complaint handling on a routine, non-transaction service call.
Roles and responsibilities
| Role | Owns | The handoff |
|---|---|---|
| Office / intake | Logging the dispute in writing the moment it arrives | Hands the service manager a written record of who is disputing what, not a verbal message |
| Service manager | Every substantive response, the re-inspection decision, escalation | Owns the file from intake forward; the original inspecting tech does not respond solo |
| Re-inspecting tech (if assigned) | Running a fresh, fully dated inspection under the transfer SOP | Hands back a standalone report, never an edit to the original |
| Owner | Any legal threat, any request to alter the original document | Escalates to the shop's attorney or E&O carrier before further contact |
Procedure
Log the dispute in writing before any conversation about the finding happens. Capture who is disputing, the specific finding they contest, and whatever evidence they cite, a second report, a photo, a verbal claim from someone on site. Acceptance: a written intake record naming the disputant, the disputed finding, and the cited evidence. Wrong looks like an on-the-phone argument about numbers with nothing written down first. Stop rule: a complaint that only says "the report seems wrong" gets sent back with a request for the specific finding and evidence in writing before anything is scheduled.
Route the dispute to the service manager immediately, and take the original tech off point. The inspecting tech does not call the agent back to defend the report. Acceptance: the service manager owns every further response from this point forward. Wrong looks like the original tech fielding a same-day callback from an unhappy agent. Stop rule: none needed here; this is a standing chain-of-command control, not a conditional one.
Pull the original report and verify it carries every element the transfer-inspection SOP requires before responding to anything. Check for the named datum, the loading-test log, and the limitations block. Acceptance: confirmation, in writing, that the original report is complete against that SOP's own record requirements. Wrong looks like defending a report from memory without re-reading the file. Stop rule: if the original report is missing a required element, no datum named, no limitations block, do not defend it as authoritative; move straight to offering a re-inspection at no charge, since the gap is the shop's own and not the disputant's error.
Where the dispute cites a second inspector's report, compare methodology point by point before comparing any number. Check whether both reports used the same datum, whether both ran a loading test, and how far apart the two inspection dates and the vacancy periods sit. Acceptance: a written comparison covering datum, loading test, vacancy period, and date for both reports. Wrong looks like comparing final figures, "we said four inches below invert, they said two above," without checking whether the two tests were run the same way. Stop rule: if the two reports were not run under comparable conditions, different vacancy length, one with no loading test, dates weeks apart, say so in writing rather than either side conceding a number, since a system's condition legitimately differs between an unloaded static reading and one taken after weeks of continuous occupancy.
Verify the disputed claim against the original file's own evidence before offering anything new. Check the original photographs, the level log, and the sketch line by line against what is now being disputed. Acceptance: a documented match or mismatch between the disputed claim and the original file. Wrong looks like trusting the inspecting tech's memory of a visit from weeks earlier over the written record. Stop rule: none required; this step always runs before step 6.
Decide whether a re-inspection is warranted, and if so, run it as a standalone new report, never as a correction to the old one. A re-inspection carries its own date, its own limitations block, and stands alone; the original report is never edited, deleted, or reissued with changed numbers. Where the property still requires opening a tank or riser, the re-inspecting tech follows the gas-testing SOP before any lid comes off, since the hazard has not changed just because this is a second visit. Acceptance: a new, separately dated report on file, with the original untouched. Wrong looks like "fixing" the old report's figures because someone pushed back, which destroys the evidentiary value of every report the shop has ever issued, since a file that changes under pressure once proves nothing under pressure again. Stop rule: any request to alter the original report itself is written down and refused, and routed to the service manager rather than negotiated by whoever received it.
Where the dispute is really about who the report was written for, clarify scope in writing rather than argue the finding. Check the client name logged at the original inspection's first step against who is now disputing it. Acceptance: a written statement that the report speaks only to its named client, with any further reliance question routed to the reader's own attorney. Wrong looks like reassuring an unrelated third party that the report "covers" them or their financing. Stop rule: none; this is a standing scope clarification, not a conditional one.
Set a response deadline and send one written position to every party at once. Decide to hold the finding, issue an addendum, or offer a re-inspection, and send that single position to the client and anyone the client has authorized, on the same day, within a shop standard of three business days from intake. Acceptance: one written response, one distribution list, one date. Wrong looks like telling the agent one thing by phone and the buyer something different by email. Stop rule: a demand for a faster response than the standard window, "closing is tomorrow," routes to the owner rather than being handled ad hoc by whoever is available.
Escalate a genuine legal threat to the owner and the shop's attorney or E&O carrier before any further substantive contact. A demand letter, a claim that a missed defect later caused a system failure, or explicit mention of legal action all qualify. Acceptance: the threat logged and handed up the same day it arrives, with no further substantive response sent until the owner or the carrier has weighed in. Wrong looks like continuing a cordial email thread with someone who has just referenced an attorney. Stop rule: nothing further goes out from the shop on this file until that review is complete.
The record this produces
One dispute file layered onto the original inspection report: the intake record from step 1, the methodology comparison from step 4 where applicable, the file-verification result from step 5, any re-inspection report from step 6 filed as its own standalone document, the scope clarification from step 7, and the single written position and its send date from step 8.
The service manager reads this file before any renewed contact from any party, so the shop's position stays fixed across every conversation. The owner reads it the moment a legal threat appears, and the original, unaltered report remains the one document that shows what was actually observed on the date it was observed, which is the only thing a dispute file is ultimately built to protect.
One run of this procedure
A buyer's agent emails three weeks after closing paperwork began, disputing a transfer inspection's finding that scum sat within an inch of the outlet tee, citing a second inspector hired by the buyer who reported the tank "clean." Office logs the dispute: disputant is the buyer's agent, disputed finding is the scum measurement, evidence cited is the second inspector's verbal summary, no written report attached yet.
Routed to the service manager per step 2. Step 3: the original report checked against the transfer SOP's requirements, datum named as the riser rim, limitations block present and complete, no gap found. Step 4: the second inspector's written report is requested and arrives two days later. Comparison: the original inspection ran a full hydraulic loading test with a level log; the second report shows a single static reading with no loading test and no stated datum, taken 12 days later.
Step 4 finds the reports are not actually in conflict. A tank pumped or resting between the two visits, combined with a static reading against an undocumented datum, does not contradict a loading-test result taken under load 12 days earlier. That finding is written down rather than either side conceding, and the step 4 stop rule governs the response: the two reports measured different things at different times, not the same thing twice.
Step 8: one written position sent to the buyer's agent and the client within three business days, stating the methodology difference plainly and offering a re-inspection under load if the buyer wants a current reading before closing. The buyer's agent accepts; the re-inspection runs two days later as its own dated report under the transfer SOP, gas-tested before the tank opened, and the original report is filed unchanged alongside it.
References
- See related: the system-inspection-for-a-property-transfer SOP, which owns the inspection procedure and the original report's required elements.
- See related: the gas-testing-before-anyone-opens-a-tank SOP, followed on any re-inspection that opens a tank or riser.
- See related: the septic-real-estate-inspection-report how-to, for the report-writing conventions the original file is checked against in step 3.
- The reader's own attorney or errors-and-omissions carrier, for what a report or a signature legally proves in a specific transaction; this SOP does not resolve that question.