Talk through your US SDS project+48 453 584 042Support daily, 2:00 AM–4:00 PM ET
OSHA implementation guide · expert review required

Treat every SDS update as a documented impact assessment.

A new date in Section 16 is not enough. Teams need to identify what changed, which products and outputs are affected, and who approved the revised information.

Direct answer: Decide whether product or source changes require SDS revision.

01

Monitor meaningful change signals

New hazard information, formula changes, supplier revisions, changed properties, new uses or regulatory updates can all initiate review.

02

Determine scope before editing

Identify affected products, languages, labels, customers and workplace records. A change in one raw material may propagate across many finished products.

03

Compare source and released versions

A structured difference report should distinguish editorial changes from values or classifications that alter safety communication.

04

Review linked outputs

Section 2, labels, controls and emergency information should be checked together. Do not assume only the section receiving new data is affected.

05

Distribute and archive

Release a controlled version, preserve the prior version and record recipients or downstream actions according to the organization’s documented process.

EX

Practical example

A supplier changes a raw-material acute toxicity estimate. The system identifies every mixture using that grade, reruns the affected hazard review, and leaves unaffected sections unchanged unless consistency checks find an impact.

Release checklist

  • Capture the change source and date
  • Find every affected product
  • Reassess hazard and operational impacts
  • Approve linked SDS and label output
  • Archive and distribute the controlled revision

Common mistakes

  • Updating the revision date without impact analysis
  • Overwriting the previous source record
  • Changing the SDS but not reviewing the label

Frequently asked questions

Does every supplier revision require a new finished-product SDS?

Not automatically. It requires review to determine whether relevant information or conclusions changed.

Should old SDS versions be deleted?

No. Retain controlled history according to the organization’s record policy and applicable requirements.

Can software decide that a change is immaterial?

It can identify differences and rules, but a named reviewer should approve the impact decision.

What is a useful update record?

Source, date, affected data, assessment, linked outputs, reviewer and released version.

A controlled next step

Turn the guide into a controlled product workflow.

Create a US account or discuss the evidence and product portfolio that need review.

Create a US accountTalk it through+48 453 584 042