Most attention goes into getting the safety data sheet right. Less goes into proving the right version reached the right customer, which is the part an auditor or an incident will actually test. This article is practical guidance, not legal advice.
The half of the duty people forget
When certain changes require a revision, there are duties to provide the updated safety data sheet to recipients you have supplied within a defined period. In other words, revising the document is not the end of the obligation. Getting it to the right people, and being able to show that you did, is part of the same duty. It is the part that does not produce a nice new PDF, so it tends to get less attention, and it is the part that is hardest to prove after the fact. It is the natural companion to keeping the document itself current, covered in safety data sheet version control.
The record problem
Ask most suppliers who holds the current version of a given safety data sheet and you will get a pause. They can produce the current document instantly. They cannot reliably tell you which of their customers received which version, and when. The document is controlled; the distribution is not. That gap is the real exposure, because it is precisely what you are asked to evidence when it matters.
Distribution living in scattered inboxes?
We build a distribution record that captures every send and lets you answer who holds which version in seconds. A short technical call, no pitch.
Book a technical callWhat good traceability looks like
- One current version per product, clearly the authoritative one, so there is no ambiguity about what "the latest" is.
- A record of which version went to which customer, when, and by what route, captured at the time of sending rather than reconstructed later.
- A trigger that, when a revision is issued, identifies which past recipients are in scope and prompts the re-send.
- The ability to answer "did customer X receive the current version?" in seconds, not days.
Practical steps
- 1Fix the source first. Traceability of a document that is itself out of date is worthless. Get one authoritative current version per product before worrying about distribution.
- 2Capture the send, not just the document. Record every issue of a safety data sheet as an event: product, version, customer, date, route. The document is not the record; the send is.
- 3Define the re-send trigger. Decide, for each type of revision, which recipients are in scope and how the re-send happens, so it is a defined process rather than a judgement call under pressure.
Frequently asked questions
Do I have to re-send a safety data sheet when it changes?
There are duties to provide an updated safety data sheet to recipients you have supplied within a defined look-back period when certain changes occur. What applies depends on the change and your role. Confirm the specifics with HSE or ECHA. This is practical guidance, not legal advice.
How do I prove a customer received the current version?
With a record captured at the time: product, version, customer, date and route. If that record does not exist, you cannot demonstrate the duty was met, however good your current document is.
Is an email good enough as proof?
An email trail is better than nothing, but scattered inboxes are hard to search and easy to lose. The point is a reliable, findable record, whatever system holds it.
Where does this usually go wrong?
At scale. Sending the current document is easy; knowing, months later, exactly who holds which version across hundreds of customers is where manual processes break down.
Sources
The distribution and update duties for safety data sheets are set in regulation. Confirm the specifics for your role against the source. This article is practical guidance, not legal advice.