Change record: EPA aligns EPCRA Part 370 terminology with revised HazCom categories
EPA published technical amendments to EPCRA hazardous-chemical inventory reporting terminology and hazard categories.
What changed
EPA published technical amendments to EPCRA hazardous-chemical inventory reporting terminology and hazard categories.
This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.
Operating consequence
Chemical-management records need shared lineage across HazCom and EPCRA while preserving separate applicability and submission logic.
Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.
Capabilities to revisit
Chemical Inventory, SDS, And Hazard Communication
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for chemical inventory, SDS, and hazard communication.
Air, Water, Waste, And Hazardous-Material Reporting
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for air, water, waste, and hazardous-material reporting.
Regulatory Change And Applicability Management
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for regulatory change and applicability management.
Questions for operating teams
- Which exact population and effective date does the source establish?
- Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
- What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
- What test case would show whether the operational consequence has reached production?
- What record will close, defer, or supersede this review?
Evidence boundary
The source class is Official final-rule record. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.