InterNACHI and ASHI report standards vs state formats for inspectors

What to take away

What the two standards actually require

Both associations publish a standard of practice. Each defines the minimum scope of a home inspection and the reporting duties that follow it.

The ASHI standard organizes work by systems and components, then states what the inspector shall inspect, shall describe and shall report. InterNACHI splits residential and commercial work into separate documents with separate scopes.

Read either one closely and the absence stands out. No report template. No page order. No photo count. No required cover page. They govern conduct and content, not layout.

That gap explains why two inspectors in the same city can hold the same membership and hand clients documents that look nothing alike.

The reporting language is deliberately narrow in both. You report conditions observed, identify systems not inspected and the reason, and avoid engineering opinions. Neither standard requires a repair estimate, a code citation or a life expectancy figure. Vendors add those fields because clients ask, not because a standard demands them.

Membership carries its own obligation. An inspector advertising ASHI membership agrees to follow the ASHI standard, and a client can file a complaint with the association. InterNACHI runs member disputes through its own process. State boards answer to statute instead, which is a separate track entirely.

Your marketing claim and your template should match. If the cover page says the inspection followed the InterNACHI standard, the narrative sections should track that document's inspection list. Reviewing how your reports hold up against service standards is a reasonable first audit before you shop for new software.

Where state formats diverge from the associations

About half the states license home inspectors, and those that do tend to legislate report content the associations leave open. The divergence lands in three places: mandated disclaimers, required signatures and record retention.

Texas is the clearest case. The Texas Real Estate Commission licenses inspectors and publishes a Standards of Practice plus separate reporting requirements. Texas requires a written report, names the items that must be reported as deficient, and sets rules for the inspector's signature and the client's acknowledgment. It also covers delivery when the client is not present.

Florida takes another route. Inspectors licensed under the state's home inspector program follow a statutory standards of practice, and the report must disclose certain limitations in writing. Florida also regulates how findings interact with wind mitigation work, a separate discipline with its own form.

California does not license home inspectors statewide, but it requires a published standard of care and a written report. The state's contract and disclosure regime shapes what appears on page one.

New York licenses inspectors and requires a written report identifying the systems inspected and any material defects, with a pre-inspection agreement signed before work begins. Illinois licenses through the state and requires a written report plus a signed agreement. Arizona, Georgia and Washington each license inspectors and attach their own reporting language, though the details differ.

A report that satisfies ASHI or InterNACHI can still fail a state audit if the cover page, disclaimer or signature block is wrong. The association tells you what to inspect. The state tells you what the paperwork must say.

How software maps to licensed-state formats

Reporting software sits between the two rule sets. Vendors build a base template from one or both associations, then layer state fields, disclaimers and signature blocks on top. Your job is checking which layers your subscription includes.

Take an inspector in Texas with InterNACHI membership. The InterNACHI template supplies the inspection list and narrative prompts. The Texas template supplies the deficient-item language, the inspector signature line and the client acknowledgment. Mapping means confirming the Texas fields survive when the InterNACHI narrative blocks load, and that both appear in the exported PDF.

Most platforms handle the common states well. Texas, Florida and New York templates ship standard in the larger products because those markets are large. Smaller states may get a generic template carrying the association language but not the state disclaimer.

Run this before signing a renewal:

If your current tool fails more than two, comparing software options reviewed against your state list costs less than rebuilding templates by hand.

ASHI and InterNACHI reporting language side by side

The two standards read differently even where they cover the same ground. ASHI favors shorter, more prescriptive sentences. InterNACHI favors longer clauses with more defined terms. Neither is stricter in a way that changes your exposure much, but the wording shapes how your software prompts you.

Both associations use the phrase about a visual, non-exhaustive inspection to cap the inspector's duty, and both expect it in the report or the agreement. Templates usually place it in the pre-inspection agreement rather than the report body. That works in most states, not all.

The structural differences matter more for software. ASHI's system-by-system list maps cleanly to a tabbed interface. InterNACHI's longer defined terms push vendors toward expandable narrative blocks. Switch associations and the template structure changes even when the field work does not.

Neither standard requires a severity scale, a numeric rating or a color code. Those are vendor inventions. Useful for clients, not evidence that a standard was met.

Building science definitions behind report language

Report wording borrows technical definitions from building science. In the United States the reference point for measurement and materials is the National Institute of Standards and Technology, which publishes the standards information underpinning terms like moisture content, structural performance and material durability.

When a report says a beam shows excessive deflection, the word excessive traces to a published performance figure, not to an inspector's mood.

The NIST buildings and construction program covers the research areas inspection standards lean on: structural systems, materials, indoor air and building envelopes. Inspectors do not cite NIST in a residential report, and should not. The value is vocabulary. A term with a technical definition keeps narrative language defensible.

NIST technical publications on building science and materials record those definitions. If you write custom narrative libraries, check them before committing a phrase to a template hundreds of reports will reuse.

The Materials and Structural Systems Division handles durability and performance research for building materials. That work informs how long a roof covering, a sealant or a structural connector is expected to perform, which is exactly the claim inspectors are told to avoid unless they can support it.

The takeaway is restraint. Describe what you observed, name the component, and leave service life predictions to manufacturers and researchers. The daily SOPs breakdown shows where narrative discipline pays off across a full workflow.

Compliance settings for multi-state work

Multi-state inspectors face a template problem single-state inspectors never see. Each state wants its own disclaimer, signature block and retention period. Software handles this three ways, and the choice changes your daily workload.

Some platforms attach a state profile to a user account, so the right template loads based on who logs in. Others make you pick a template at the start of each inspection. A few merge a state addendum into a base template, which is flexible and easy to forget.

Account-based loading is safest for teams. An inspector licensed in Texas and New York logs in and the software knows which rule set applies. Manual selection works for a solo inspector with two states and a checklist habit.

Retention is the setting people overlook. Licensing states typically set a minimum period for keeping reports and records, often longer than the vendor's default cloud retention. Confirm the number in your state rule, then confirm the software will hold the file that long. Export a local archive if it will not.

Track your error rate after any template change. A report that fails a state audit usually fails because a field was dropped in an update, not because the inspector missed a defect. Reporting software and the KPIs that flag template drift is worth more than a lower subscription price.

Audit trail, disclaimers and signature blocks

Compliance is proven after the fact. When a client complains or a board asks questions, the report is the evidence and the audit trail around it decides how the conversation goes.

An audit trail should show who created the report, when each section was completed, what changed after delivery and who signed. Timestamps establish that the inspection preceded the report and the report preceded the transaction. Software that overwrites versions without keeping history leaves a gap you cannot fill later.

Disclaimers are where association and state language collide. The association expects a scope limitation. The state may require specific wording for that limitation plus disclosures about what the inspection does not cover. Put the state language in the report and the association language in the agreement, then check that the two do not contradict each other.

Signature blocks vary more than any other element. Some states require the inspector's signature, some the client's acknowledgment, some both plus a date. Electronic signature capture is standard in reporting software. The block layout is not, so verify the exported PDF rather than the on-screen preview.

HUD guidance on buying a home tells consumers the inspection report is their record of the property's condition at the time of inspection, and that choosing an inspector is the buyer's decision. That framing matches what clients already expect to receive, which makes it useful when you draft disclaimers.

Treat the report as a business record. The IRS expects business records to be retained and produced on request, and a report archive doubles as proof of work. Ask your CPA how long your business records should be kept. Clean report history serves the state, the association and your accountant at once.

For a second opinion on your own output, run a periodic service quality review against a sample of delivered reports.

Common questions

Does following the InterNACHI standard satisfy my state's report requirements?

Not by itself. The state rule governs format, disclaimers and signatures, and it applies whether or not you hold association membership. Check your state licensing board's published reporting rule.

Which states require a specific report template?

None publish a fill-in-the-blank template. Licensed states publish content requirements, and your template qualifies as long as it meets them. Confirm the current requirement with your state board.

Can one template cover both ASHI and InterNACHI?

Rarely in a single document. The inspection lists and defined terms differ, so most vendors keep separate templates and let you choose at the account level.

How long should I keep inspection reports?

Follow your state's retention rule where one exists, and keep the longer of that period and your software's default. A local export protects you if you switch vendors.