5 Common Mistakes in Safety Data Sheet Management (And How to Avoid Them)

Safety Data Sheets are the backbone of chemical safety management, yet many organizations struggle with keeping them accurate and up to date. Here are five common mistakes we see — and how to fix them.

1. Not Tracking SDS Revision Dates

An SDS should be updated by the supplier whenever significant new information about a substance becomes available, or at minimum every few years. Many organizations have SDS files that are 5, 10, or even 15 years old.

The risk: Outdated SDS documents may lack current hazard classifications, miss new regulatory listings (such as SVHC additions), or contain incorrect first-aid and firefighting procedures.

The fix: Implement a systematic review of SDS revision dates. Flag documents older than your threshold (most organizations use 3-5 years) and request updates from suppliers proactively.

2. Inconsistent Data Entry

When SDS data is entered manually, inconsistencies creep in. The same H-statement might be recorded as "H302", "H 302", or "Harmful if swallowed" across different products. CAS numbers may be formatted differently or contain typos.

The risk: Inconsistent data makes compliance screening unreliable. A CAS number with a transposed digit won't match against regulatory lists, potentially hiding a compliance issue.

The fix: Use standardized formats for all chemical identifiers. Better yet, automate data extraction from the SDS PDF to eliminate manual entry errors entirely.

3. Missing SDS Sections

A compliant SDS must contain all 16 sections as defined by REACH Annex II. We regularly see SDS files with missing or incomplete sections — particularly Section 11 (Toxicological Information) and Section 12 (Ecological Information).

The risk: Missing sections mean incomplete hazard information, which undermines risk assessments and may violate regulatory requirements.

The fix: When receiving an SDS from a supplier, verify all 16 sections are present. If sections are missing or state "no data available" for critical information, request a complete version from the supplier.

4. No Version History

When a new SDS replaces an old one, many organizations simply overwrite the file. The previous version is lost, along with any record of what changed.

The risk: Without version history, you cannot demonstrate to auditors what information was available at a specific point in time. This is particularly important for incident investigations and regulatory inspections.

The fix: Maintain an archive of all SDS versions with dates and change notes. Chemspark does this automatically with its SDS Version History feature.

5. Language Mismatches

Under CLP, the SDS must be provided in the official language(s) of the Member State where the substance or mixture is placed on the market. Using an English SDS in a Dutch-language workplace doesn't meet legal requirements.

The risk: Workers who cannot read the SDS in their language may miss critical safety information. This is also a regulatory compliance issue.

The fix: Ensure you have SDS documents in the correct language for your jurisdiction. Request translated versions from suppliers when needed.