Verify a landscape irrigation sprinkler or emitter product's compliance claim against the ASABE/ICC 802 Landscape Irrigation Sprinkler and Emitter Standard before specifying it on a job that references the standard.
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify that ASABE/ICC 802 is a jointly developed American National Standard (published under both ASABE and ICC identifiers), so it may be cited by either organization's name in specs or code references.
Pull the current edition of ASABE/ICC 802 from ICC's digital codes platform or ASABE's technical library rather than relying on an older cached edition.
Confirm whether the specifying document (municipal code, HOA spec, or design spec) is referencing this standard by its ASABE number, ICC number, or both, to avoid missing the citation during a document search.
Check the manufacturer's test documentation or third-party lab report showing the specific sprinkler/emitter model was evaluated against the standard's performance criteria.
Where the standard is referenced in a local plumbing/irrigation code adoption, confirm which edition year the jurisdiction has actually adopted, since code adoption often lags the standard's current publication.
Known gotchas
Because this is a dual-branded ASABE/ICC standard, a search for only 'ASABE 802' or only 'ICC 802' may miss references filed under the other organization's name.
A jurisdiction citing 'the landscape irrigation sprinkler standard' in code may have adopted an older edition than the current one on ASABE's or ICC's site — always confirm the adopted edition year rather than assuming the newest edition applies.
This standard governs sprinkler/emitter product performance, not full system design or installation workmanship — it does not substitute for a system design standard or a state irrigator license requirement.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?