Identify the trigger
Track new evidence, formulation, supplier or regulatory changes.
Assess impact
Determine affected hazards, sections and markets.
Create a new version
Do not silently overwrite the approved record.
Review connected outputs
Check label, transport and customer information.
Distribute and retain
Control issue dates, recipients and archived versions.
Impact example
A revised ingredient SCL can affect calculation, Section 2, Section 3 and the label.
Checklist
Trigger recorded
Impact mapped
New version created
Outputs aligned
Archive retained
Common mistakes
×changing text without impact review
×overwriting the old version
×missing linked labels
×using today’s date automatically
Frequently asked questions
Does every supplier update change the final SDS?
Not always, but every relevant change needs assessment.
Should old versions be kept?
Yes, version history supports traceability.
Does a general answer validate a specific product?
No. The actual composition, form, supplier data and intended use must be assessed.
Who should approve the result?
A competent person should review the data, method and internal consistency before supply.
Primary sources
Check the current consolidated version and the exact substance or product scope before use.