Chemical compliance responsibilities often fail at the handoff, not because nobody is working on the issue, but because several departments assume someone else has final authority. Procurement collects supplier documents, QA reviews specifications, and EHS evaluates hazards, yet a chemical can still move forward with an outdated SDS, an unapproved specification, or an unresolved regulatory question if no control has a named owner.
The fix is not to make every department responsible for everything. It is to give each decision one final owner, while requiring defined input from the other functions. That structure becomes especially important when a supplier makes a supplier change notification that affects more than price or lead time.
Chemical Compliance Responsibilities Should Follow the Decision
A useful responsibility map starts with the decision being made. Supplier selection is different from product acceptance. Hazard review is different from specification approval. Record retention is different from deciding whether a new regulatory restriction applies.
Legal requirements may attach to an employer, manufacturer, importer, processor, or distributor rather than to an internal job title. Companies therefore need an internal governance model that translates those obligations into operational ownership.
The table below provides a practical starting point.
| Compliance control | Primary owner | Required input | Release condition |
|---|---|---|---|
| Supplier approval | Procurement | QA, EHS | Approved source and required documents complete |
| SDS control | EHS | Procurement, QA | Current SDS available and reviewed for intended use |
| Product specification | QA | Procurement, Operations | Approved specification and test basis established |
| Incoming checks | QA | Receiving, Procurement | Lot documentation and agreed checks acceptable |
| Regulatory screening | EHS | QA, Procurement | Applicable restrictions and use conditions cleared |
| Supplier change management | QA | Procurement, EHS, Operations | Impact assessed before affected material is accepted |
| Compliance records | Designated document owner | Procurement, QA, EHS | Controlled, retrievable evidence retained |
The primary owner does not perform every task. The owner closes the loop, records the decision, and prevents the process from advancing when required evidence is missing.
Procurement Owns the Supplier Gate, Not Technical Acceptance
Procurement should be the commercial gatekeeper for approved suppliers. That means confirming that purchases come from authorized sources, required supplier questionnaires and declarations are collected, commercial identities match the approved entity, and purchase terms include relevant documentation and change-notification obligations.
What Procurement should not do alone is decide that a chemical is technically acceptable simply because the supplier provided an SDS, certificate, or quote. A document can be present and still be insufficient for the intended process.
Procurement also needs a clear stop rule. If QA has not approved the specification or EHS has not cleared the chemical for the intended site and use, a purchase order should not become the workaround that bypasses those reviews.

QA Owns Specifications, Incoming Evidence, and Controlled Change
QA should normally act as the technical acceptance authority for material specifications, agreed test methods, certificates of analysis, incoming inspection plans, deviations, and supplier changes that may affect product quality or process performance.
The distinction between specification ownership and purchasing ownership matters. Procurement negotiates what the supplier will provide; QA determines whether the technical definition is adequate and whether delivered material meets the approved basis.
Incoming checks should also have a defined escalation path. A missing CoA, changed test method, unexpected packaging configuration, or result near an agreed limit should not depend on an individual receiver deciding whether it “looks fine.” QA should define what can be accepted, quarantined, investigated, or rejected.
Change management belongs here because technical equivalence is rarely a purely commercial question. A changed manufacturing site, raw-material source, formulation, specification, or analytical method may require review even when the product name remains unchanged.
EHS Owns Hazard and Regulatory Screening
EHS should be the regulatory screening owner for workplace hazard controls, chemical-use approval, exposure implications, storage and handling requirements, emergency planning inputs, and applicable environmental or chemical restrictions.
For U.S. workplaces, OSHA’s hazard communication requirements require employers to maintain safety data sheets for hazardous chemicals and make them readily accessible to employees. Manufacturers and importers also carry specific duties for hazard classification, labeling, and SDS preparation or transmission. That makes SDS control more than a filing task: the current document must connect to the actual chemical, workplace use, and hazard communication program.
Regulatory screening also needs to look beyond the SDS. For example, EPA’s TSCA import requirements can impose certification and other obligations on chemical imports. A supplier statement may support the review, but the regulated party still needs a defensible basis for its own compliance decision.
The Dangerous Gaps Sit Between Departments
The highest-risk failures are usually handoff failures. Procurement assumes QA reviewed the revised specification. QA assumes EHS saw the new SDS. EHS assumes Procurement verified the supplier’s legal entity. Receiving assumes the ERP would block an unapproved material.
Those assumptions should be replaced with explicit gates. A new supplier should not be activated until technical and regulatory reviews are complete. A new chemical should not arrive onsite before use approval. A changed specification should not become effective until the impact assessment is closed. An updated SDS should trigger review when hazard information or controls have changed.
The next pressure point is system synchronization. Approved-supplier lists, specifications, SDS libraries, ERP material records, receiving instructions, and change-control logs can drift apart. Periodic reconciliation should therefore test whether the same chemical, supplier, revision, and approval status appear across all controlled systems.
One Owner Per Control Creates Defensible Compliance
Strong chemical compliance responsibilities do not require Procurement, QA, and EHS to work in separate silos. They require the opposite: shared input with unmistakable accountability.
Procurement should control who may supply the material. QA should control what technical definition is acceptable and how incoming evidence is judged. EHS should control hazard and regulatory screening for the intended use. Record ownership should then preserve a version-controlled record of what was reviewed, who approved it, what conditions applied, and when the decision changed.
The practical test is simple. For every compliance control, a company should be able to name the final owner, the evidence required, the departments that must contribute, and the event that triggers re-review. If any of those answers are unclear, the process still contains a gap.
Frequently asked questions
Who should own chemical supplier approval?
Procurement should generally own supplier activation and commercial status, while QA and EHS provide required technical and regulatory approvals. The supplier should not become usable in purchasing systems until those reviews are complete.
Should QA or EHS own Safety Data Sheets?
EHS commonly owns workplace SDS control because the documents support hazard communication and safe use. QA may still need controlled access when SDS revisions affect product specifications, supplier qualification, or formal change assessments.
Can Procurement approve a new chemical without QA or EHS?
Commercial approval alone should not substitute for technical and safety review. The required functions depend on the chemical and intended use, but unresolved specification, hazard, or regulatory questions should block release.


