SDS update requirements: when and why you need to revise a safety data sheet

SDS update requirements are triggered by specific events, not by the calendar. A safety data sheet doesn’t need revision because a year has passed; it needs revision because something changed that makes the existing sheet inaccurate. 

OSHA issued 3,010 Hazard Communication citations in FY2025, making it the #2 most cited standard across general industry that year, according to OSHA enforcement data. EHS and regulatory teams managing large SDS portfolios can see dozens of update triggers fire every month, often in parallel. 

Getting this wrong in either direction carries real cost. Update too rarely and an SDS falls out of compliance, or worse, gives workers inaccurate hazard information. Update on a schedule instead of a trigger and teams waste review cycles on documents that haven’t changed. The answer is a clear, documented definition of what counts as a trigger.

The four events that trigger an SDS update

Four categories of change require an SDS revision. Distinguishing them matters because each surfaces differently in practice:

• New hazard data. New toxicological, ecological, or physical hazard information becomes available for a substance already in the formulation, often through supplier notifications or regulatory reclassifications, not internal testing.
• Reformulation. Any change to the product’s composition, including a concentration change for an existing ingredient, requires a fresh hazard assessment before the SDS can be considered accurate.
• Supplier ingredient changes. A supplier substitutes or reformulates a raw material without notifying downstream customers. This trigger is most likely to be missed because it originates outside the manufacturer’s change-control process.
• Regulatory change. A new or amended regulation changes classification thresholds, disclosure requirements, or labeling rules for a substance already in the formulation.

Each trigger should map to a defined internal process step. Teams that document these triggers in advance turn “does this need an update?” into a checklist question rather than a judgment call made fresh every time.

OSHA’s 3-month clock - and what starts it

Under OSHA’s Hazard Communication Standard (29 CFR 1910.1200), a manufacturer must update an SDS within three months of becoming aware of significant new information. The same regulatory event also starts a second clock: the corresponding label must be updated within six months of awareness, per the same standard. The two deadlines run independently, which means a triggered revision requires coordinating both document types on different timelines. 

The clock starts at awareness, not at the underlying event. The real compliance risk isn’t the three-month window itself; it’s the gap between when a trigger occurs and when a team notices it. A supplier ingredient change that goes undetected for six months before discovery has already created six months of non-compliant exposure, regardless of how fast the SDS gets updated once someone catches it.

Detection speed matters as much as revision speed in any SDS update requirements framework.

New to the 16-section SDS format itself? See 3E’s primer on OSHA SDS format requirements.

GHS Rev. 7: what changed and what it forces you to re-check

GHS Revision 7 introduced revised classification criteria for certain health and physical hazards, updated label element provisions, new small-container labeling rules, and technical amendments to SDS content requirements.

For SDS updates, the practical question is whether any substance in an existing formulation now falls under a revised classification criterion, which itself counts as a trigger event under the regulatory-change category above. 

OSHA extended the HCS 2024 substance compliance deadline to May 19, 2026, and the mixture deadline to November 20, 2026, per a January 2026 Federal Register notice, meaning the Rev. 7 trigger check is now an active requirement for most manufacturers, not a future consideration. Rev. 7 adoption timelines vary by jurisdiction, so the same formulation can require action in one market before another.

Multi-market timelines: one trigger, multiple deadlines

A single trigger event rarely stays contained to one regulatory timeline. If a formulation ships into multiple jurisdictions, the same reformulation or hazard-data change can obligate an update under OSHA’s three-month rule in the US, a different notification window under EU CLP, and a separate timeline again under other national frameworks - each running independently once the trigger fires. Managing this manually means tracking a matrix of deadlines per substance per market, not one clock per document.

Building a systematic SDS update workflow

Teams that manage large SDS portfolios well treat each trigger category as a standing workflow rather than a one-off. The workflow has three steps: trigger detection (catching supplier and regulatory changes as they occur, not months later), impact mapping (identifying which SDS and markets a given trigger affects), and update execution by the correct deadline for each jurisdiction.

3E’s SDS management capabilities support this, surfacing trigger events as they occur and mapping them to the specific documents they affect, so compliance teams spend time verifying accuracy rather than hunting for what changed.

See how 3E keeps large SDS portfolios current across every market.