Define the Report and Its Limits Before Booking

Write the decision questions

Clarify what buyer, seller, lender or advisor needs to understand and by what date; this guide does not provide real-estate or legal advice.

Assemble system records

Provide filings, plans, maintenance history, pumping and repair records plus known occupancy or property changes.

Verify the inspector’s role

Ask what qualification and experience match the system and intended reliance, and whether other roles may be needed.

Compare scope options

List accessible components, pumping dependency, operating observations, non-invasive or other tests, site review and exclusions.

Prepare access

Coordinate owners, occupants, lids, records, utilities, weather constraints and safe site access without opening the system yourself.

Read findings with limits

Record what was observed, conditions of the visit, inaccessible elements, follow-up and who may rely on the report. Avoid pass/fail shorthand.

Agree on the inspection purpose

Record the transaction question, property use, known system type and documents available before booking. Ask the inspector to state methods, components, tests, access requirements and exclusions so parties understand what the report can support.

• Do not promise pass or fail
• Identify reliance and distribution
• Keep advice roles separate

Prepare a neutral system history

Compile filings, pumping, maintenance, alarms, repairs, occupancy and water-use changes with source dates. Distinguish seller recollection from documentary evidence and avoid concealing or interpreting conditions that require qualified review.

• Use original service records
• Mark undocumented alterations
• Disclose inaccessible areas

Route post-report decisions

Create a table for observed condition, report limitation, recommended follow-up, responsible party and deadline under the transaction. Capacity, repair, replacement, negotiation and legal decisions may require different expertise beyond the inspection scope.

• Quote the report accurately
• Track outstanding tests
• Retain the final signed version

Create the transaction evidence schedule

List the property use, system records, component map, maintenance history, inspection purpose, agreed methods, access requirements, report limitations and outstanding tests before deadlines are set. After inspection, copy each finding accurately into a decision table with source page, follow-up role, responsible party and timing. Keep technical, contractual and legal questions with the appropriate advisors. The schedule should make missing evidence visible to all authorized participants without converting a limited inspection into a pass, guarantee of future performance, capacity determination or promise that no concealed condition exists.

• Reference report page numbers
• Separate fact from recollection
• Track unfinished tests
• Name follow-up roles
• Retain the signed final report