One of the types of guidance provided is about how to version SDSs when changes are made. The guidance starts by giving the text of the REACH regulation that describes versioning:
“The date of compilation of the safety data sheet shall be given on the first page. When a safety data sheet has been revised and the new, revised version is provided to recipients, the changes shall be brought to the attention of the recipient in Section 16 of the safety data sheet, unless they have been indicated elsewhere. In that case, the date of compilation identified as “Revision: (date)” as well as a version number, revision number, supersedes date or other indication of what version is replaced shall appear on the first page”.
In EU SDSs, revisions must be identified on the first page and information on the changes must be given either in section 16 or elsewhere in the SDS. The guidance suggests that an incremental numbering system be used to identify new versions of an SDS. Changes to versions requiring provision of updates according to Article 31(9) of REACH could be identified by an increment by an integer, while other changes could be identified by an increment by a decimal, for example:
Version 1.0: Initial issue.
Version 1.1: First change(s) not requiring update and re-issue to former recipients.
Version 1.2: Second change(s) not requiring update and re-issue to former recipients.
Version 2.0: First change requiring provision of update according to Article 31(9) to former recipients.
Conditions under which an SDS must be updated according to Article 31(9) of REACH include:
- As soon as new information which may affect risk management measures or new information on hazards becomes available.
- Once a REACH authorization has been granted or refused.
- Once a REACH restriction has been imposed.
Thus, for EU SDSs, if a condition described in Article 31(9) takes place, the non-decimal number must change (e.g. version 3.2 to version 4.0). Most other updates can be handled with a change to the decimal (e.g. version 3.2 to version 3.3).
If you are a subscriber and want to contribute to the blog, or if you have any comments, do not hesitate to e-mail us at firstname.lastname@example.org. Please specify the blog that you are writing about.
Photo by mightyman via Openclipart