REACH downstream-user duties need a role-and-measure record

Classify the organization's role for the activity

The direct answer is to identify the downstream-user role before assigning a generic chemical-compliance task. Record the legal entity, site, substance or mixture, supplier, received product, activity, intended use, supply-chain position, applicable role, reviewer, source guidance version, evidence, uncertainty, and effective date. The same organization can act in different roles for different products or activities, so a corporate-level downstream-user flag should not silently govern every process. ^[1]

Preserve the facts supporting the role and keep unresolved questions visible. A site that uses a supplied mixture in its own operation presents a different responsibility map from a formulator that supplies mixtures onward or an organization producing articles. Role classification should route the correct records and qualified review; it should not be treated as proof that a use is covered, measures are sufficient, or the organization complies with every applicable requirement. ^[1]

Connect received measures to implementation evidence

ECHA's overview says all downstream users identify and apply appropriate measures in the safety data sheet and exposure scenario. The operating record should therefore identify the supplier and document versions received, the measures relevant to the activity, the procedure or control that implements each measure, responsible owner, location and equipment, training or communication, effective date, verification method, exception, change history, and retained evidence. Document receipt and measure implementation are different states. ^[1]

Do not infer a site conclusion from an SDS-present badge or a completed inventory row. Qualified chemical-safety, occupational-health, environmental, operations, regulatory, and legal owners must decide which received measures apply and what evidence demonstrates implementation. If the document, activity, or operating facts are unclear, preserve the gap and interim direction. This role-and-measure record can inform a workplace assessment without replacing the assessment's hazard, exposure, worker, task, and control decisions.

Give supplier communications and chemicals of concern their own states

ECHA identifies an all-downstream-user responsibility to inform suppliers when the user has new hazard or risk information. Preserve the observed information, substance or mixture, affected use or condition, source and date, reviewer, significance assessment, communication content, sender and recipient, transmission and receipt, supplier response, interim controls, resolution, and downstream changes. A message sent status does not establish supplier receipt, agreement, or closure. ^[1]

The overview also identifies compliance with regulatory requirements for chemicals of concern. Link the role record to the applicable substance identity, candidate or other governing status, source instrument and version, concentration or other relevant facts, article or mixture scope, obligation assessment, communication or notification, owner, deadline, evidence, and decision. Do not use the high-level page to invent a specific duty; use current controlling requirements and complete facts for that determination. ^[1]

Test a role change and new hazard information

A representative evaluation should begin with a site using a supplied mixture, add a formulation activity that supplies a customer, introduce new hazard information from operations, and identify a Candidate List substance in an article. Reviewers should reconstruct the role assigned to each activity, the safety-data and exposure-scenario measures received, implementation records, supplier communication and receipt, chemicals-of-concern assessment, additional formulator or article-producer work, unresolved facts, approvals, and effective dates.

The exact current ECHA roles page supports the role-level responsibilities described here. It does not display a publication or last-updated date, establish whether a particular use or condition is covered, decide which measure is appropriate for one site, determine a substance-specific duty, or prove compliance. The exact URL rendered in Chrome on October 7, 2026; native HTTP and web-reader 403 responses remain part of the evidence record, and no clean news comparison is claimed. ^[1]

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Safety Operations Standard will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.