Distinguish ASSE 6020 Medical Gas Inspector from ASSE 6030 Medical Gas Verifier roles on a project
domain: asse-plumbing.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm ASSE Standard #6020 (Medical Gas Systems Inspectors) applies to the individual who inspects the installation of medical gas/vacuum distribution piping — typically observing during construction, before concealment, checking labeling and witnessing the installer's initial pressure/leak tests
Confirm ASSE Standard #6030 (Medical Gas Systems Verifiers) applies to the individual who performs final testing and verification of the completed, operational system (the full NFPA 99 test battery) before it is placed into service
Note that a 6020 Inspector or 6030 Verifier is required to perform the pre-concealment system inspection, and a 6030 Verifier performs the final acceptance verification and issues the verification report
Confirm with the project's specifications or AHJ which credential (or both) is required at each project milestone, since some jurisdictions/specs call for an inspector at rough-in and a separate verifier at final
Verify that whichever role is used, the individual is independent of the installing contractor — this independence requirement applies to both 6020 inspection and especially 6030 final verification
Known gotchas
6020 and 6030 are distinct, separately-earned credentials (not tiers of the same certification) — confirm which one a given individual actually holds rather than assuming interchangeability
Requirements for which credential is mandatory at which project stage can vary by state/AHJ; confirm locally rather than assuming a single national rule
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?