SDS

Manage safety data sheets centrally

Safety data sheets are the technical basis for many hazardous substance fields. They should be current, versioned and linked directly to the right substance.

What is the purpose of a safety data sheet?

An SDS brings together information about properties, hazards, protection, handling, storage and disposal. It is an important source for workplace documentation but does not replace a risk assessment or workplace-specific operating instructions.

Versions instead of file chaos

GHSDoku stores the SDS version and the “Revised on” date. Previous SDS revisions remain traceable while the current document is identified clearly. No “valid until” field is used.

A central SDS database for the organisation

A shared safety data sheet database assigns every PDF to the correct substance. Search, product links and permissions avoid hunting through email attachments, network drives and local downloads for the right revision.

Upload and link import

PDFs can be uploaded locally or imported server-side from a link. This keeps storage central and independent from individual workstations.

Organise retention and availability

Daily operations need a clear process for reviewing revisions, identifying the current document and making it available to authorised users. Central storage supports that process; specific retention requirements still need to be assessed for the organisation and applicable rules.

Make GHS data from an SDS usable

GHS pictograms, H/P/EUH statements and storage classes can be detected from safety data sheets and used as suggestions for product maintenance. Structured values support filtering, but they still need to be checked against the current document before saving.

Working basis

Adopt a revised SDS in a controlled way

  • Match the product identity and supplier with the existing substance record.
  • Verify the version number and revision date on the first page.
  • Review changes to classification, labelling and protection information.
  • Upload the PDF or import it from an allowed HTTP(S) source and confirm the current revision.

Practical example

Example: supplier publishes a revision

The new PDF states version 3.1 and “Revised on 14 May 2026”. Both values are recorded or suggested during upload. After technical review, the document is made current and the preceding PDF remains available as an earlier revision.

Primary sources

Review the technical basis yourself

The linked official sources are authoritative for operational and technical assessment. Product features do not replace that assessment.

FAQ

Frequently asked questions

Short answers for teams that want to structure hazardous substances documentation more clearly.

Why should an SDS be versioned?

Versions show which document state was used and when it was updated. This is important for follow-up questions and internal evidence.

Should SDS PDFs be publicly accessible?

In an operational application, documents should usually be delivered through the application so permissions and logging apply.

How does an SDS database differ from a network drive?

A structured database links the document to its product, version and revision date. In a folder, naming, assignment, search and permissions need to be maintained separately.

How are GHS and safety data sheets connected?

The SDS includes classification and labelling information. Pictograms, signal word and H/P/EUH statements should be taken from the current document and reviewed before use.

Read more

More topics around hazardous substances

Next step

Bring hazardous substance data together from scattered sources

Use your own sites and documents to assess whether GHSDoku fits your processes.