When NSF/ANSI 61 Is the Wrong Requirement
NSF/ANSI 61 is the right standard for potable contact, and the wrong one almost everywhere else. Specifying it where it does not apply adds cost and distracts from the standards that actually matter.
It is the wrong requirement whenever the tank holds non-potable, industrial, wastewater or process liquids that never contact drinking water.
NSF/ANSI 61 is a potable-water health-effects standard. Applying it to non-potable duty is over-specification: it addresses a risk (leaching into drinking water) that does not exist there.
Key Characteristics, Components & Types
Non-potable water: Fire-water, irrigation (non-potable), raw intake and reclaimed-non-potable tanks do not need it.
Industrial and process: Process chemicals, cooling water, and manufacturing liquors are outside its scope.
Wastewater and sludge: Sewage, industrial effluent and sludge duty are governed by corrosion and containment standards, not potable health effects.
Cost of over-spec: Certification effort and cost with no corresponding risk reduction.
Applications & Use Cases
Fire-protection reserves, industrial process tanks, wastewater and sludge treatment, and reclaimed-water (non-potable) storage, where other standards apply.
Technical Considerations
Over-specifying NSF/ANSI 61 on a wastewater or industrial tank diverts attention from the real requirements: coating grade for H2S and acid (ISO 28765 / AWWA D103-09 for enamel tanks), structural design, and containment. A sludge digester, for example, needs a zoned high-grade enamel and gas-tightness far more than it needs a potable certificate it cannot use.
The right move is to match the standard to the duty: potable contact gets NSF/ANSI 61 (or WRAS/ACS regionally); corrosive non-potable duty gets the coating and structural standards that protect the asset and environment.
Advantages & Limitations
Advantages:
Avoiding NSF/ANSI 61 where it does not apply saves cost and focuses engineering on the standards that actually govern the duty.
Limitations:
The line is not always obvious, a tank may later be re-used for potable duty, so document the intended service. Mistaking a potable path as non-potable is the real risk.
Comparison & Selection Guide
Duty | NSF/ANSI 61? | Use instead |
Fire-water (non-potable) | No | NFPA 22, structural |
Industrial process liquor | No | Chemical compatibility |
Wastewater / sludge | No | ISO 28765, AWWA D103 |
Reclaimed non-potable | No | Local reuse code |
Potable contact | Yes | NSF/ANSI 61 (+WRAS/ACS) |
Best Practices & How to Choose
Confirm the intended service and any future reuse before specifying. Reserve NSF/ANSI 61 for potable contact; use coating, corrosion and structural standards for non-potable duty. Document the decision so the tank is not later mis-applied.
NSF/ANSI 61 is the wrong requirement for non-potable, industrial, wastewater and process tanks, where coating and structural standards govern. Reserve it for genuine potable contact and save cost and focus.
Frequently Asked Questions (FAQ)
Is NSF 61 needed for a fire-water tank?
Usually no, if the fire reserve is non-potable. Fire-water tanks are governed by standards such as NFPA 22 and structural requirements, not potable health effects.
Do wastewater or sludge tanks need NSF 61?
No. They need corrosion and containment standards (such as ISO 28765 and AWWA D103-09 for enamel tanks), because the risks are H2S, acid and leakage, not drinking-water leaching.
Why is over-specifying NSF 61 a problem?
It adds certification cost and effort with no risk reduction, and can distract from the standards that actually protect a corrosive or containment-duty tank.
Can a non-potable tank later be used for potable?
It can be re-purposed only if its wetted materials are then certified; document the original service so it is not mistakenly used for potable duty without certification.
Which standard replaces NSF 61 for industrial tanks?
There is no single replacement; it depends on duty, chemical compatibility, corrosion (ISO 28765 / AWWA D103-09 for enamel) and structural design govern instead.