SDS authoring software: control the path from source data to issued document
One ingredient record changes. Which formulations, safety data sheets, labels and recipients need attention? Use that question to evaluate authoring software. A generated PDF is one output; the buying decision also includes source data, market rules, review, retained versions and distribution.
Editorial review by Dimitris Mitsios
Founder of The QHSE Standard; product marketing at Tekmon. LinkedIn
Tekmon is a featured commercial partner. Disclosure and review scope
Authoring, library access and distribution are separate jobs
| Job | Record to evaluate | Buying question |
|---|---|---|
| Author your product's SDS | Formulation, source data, selected market rules, language and review decision. | Can a reviewer explain how this issued output was produced? |
| Maintain a workplace SDS library | The correct supplier document, revision, location and worker access method. | Can the worker retrieve the appropriate sheet in the actual work area? |
| Distribute issued documents | Document version, intended recipient, attempt and follow-up status. | Can the team distinguish an approved file from an unresolved delivery? |
Define the data and review work first
If your task is access to supplier documents, start with the SDS library management guide. For authoring, establish who owns the formulation, source evidence, applicable content and document approval. ECHA's SDS guidance explains the information exchanged through SDSs and encourages checking received information and communicating inaccuracies. That is EU/REACH context, not a worldwide legal assessment.
Ask the author to distinguish supplier data, measured values, estimates and manual overrides. Leave an unresolved value visible instead of silently substituting zero. Have your specialists choose the applicable rules and expected result before judging the software calculation.
Two authoring scopes to investigate
Official pages checked on 21 September 2026 establish advertised functions, not tested classification accuracy or equivalent license bundles. The Lisam directory profile covers a wider portfolio; this guide focuses on ExESS.
ChemGes by DR-Software
Investigate formulation-based authoring, document revisions, labels and customer-linked distribution. The vendor describes text-file exchange and tailored imports; confirm the mapping and implementation needed for your source system.
Ask to see: a changed ingredient record reaching the affected formulations, outputs and recipient follow-up without replacing the previous issued versions.
Confirm country/language configuration, deployment, review controls and maintenance terms. MSDS+ is a separately described companion for document catalogs.
Lisam ExESS
Investigate authoring with configurable approval processes, selected regulatory libraries and API or batch connections. Lisam identifies PubliChem and CDP as applications supporting distribution and data integration.
Ask to see: a regional-content change, the review of affected outputs and the proposed distribution component handling an unsuccessful delivery.
Specify ExESS, content providers, regional modules and connected applications in the quote. Features from Lisam's wider chemical or EHS portfolio do not establish ExESS entitlements.
One product, several outputs, different decisions
Use a vendor-provided training formulation named DEMO-01. Agree two fictional market configurations, A and B, with your reviewer. Create revision F02 after one source record changes. Keep a custom phrase deliberately untranslated in one output. Use test recipients only and simulate distribution; this exercise supplies no chemical classification or production-ready SDS.
Treat market and language as separate selections. An English output for Market A does not by itself validate an English output for Market B. The matrix below specifies proposed demo states, not states we have verified in either product.
Review each output, not just the product record
| Output | Formulation / configuration | State to demonstrate | Question before issue |
|---|---|---|---|
| OUT-A-EN | F02 / Market A / English | Reviewed draft; distribution not yet attempted. | Which evidence and person approved this exact version? |
| OUT-A-EL | F02 / Market A / Greek | Custom phrase untranslated; review unresolved. | Can the reviewer find the missing text and keep this output out of the approved release set? |
| OUT-B-EN | F01 / Market B / English | Earlier issued version; impact of F02 still to assess. | Can the team see both the retained issue and the outstanding revision decision? |
Test four failure scenarios before committing
An input changes while an output is under review
Revise the selected source record and identify affected formulations, SDSs and labels. Trace each output to its input and content versions. Preserve manual overrides with their rationale. Show how unresolved source data reaches the responsible reviewer.
A translated output is incomplete
Open OUT-A-EL with its untranslated phrase and compare it with OUT-A-EN and OUT-B-EN. Demonstrate how the review state and market configuration remain distinct. Identify any manual gate required to exclude an unfinished output from distribution.
An approved revision does not reach a recipient
In a test environment, simulate a distribution attempt with one successful and one failed delivery. Retrieve the issued file, recipient, time and follow-up state. Repeat the attempt without losing history. Do not treat file creation or a sent status as proof of receipt.
A connection or update entitlement is unavailable
Test the agreed disconnected authoring and export steps on the proposed installation. Review the vendor's documented maintenance-ending scenario without changing a real license or installing an update. Request written rights for existing files, printing, exports, content updates and support, then export a representative archive.
Read the maintenance condition precisely
DR-Software's download page warns that applying updates after a maintenance contract has ended can prevent printing and file output. The stated condition is an update after maintenance ends; it is not evidence that all existing installations immediately lose outputs on contract expiry. Request the applicable terms for the version you intend to run.
For each candidate, ask which content updates, language modules, support, distribution services and interfaces require continuing entitlement. A Windows installation, remote session or available PDF does not establish that the complete workflow works without a connection.
Build the quote around outputs and responsibilities
Record the evidence for both proposed configurations
Start with five common authoring questions and one scope question per product. The scorecard names ChemGes and the broader Lisam profile; specify ExESS and the quoted components in your notes. All results begin untested.
Start the SDS authoring demo scorecardSources and review boundaries
Sources checked 21 September 2026. Vendor documentation informs product scope; ECHA material provides EU context. Demo records and expected review states are editorial buying exercises. No real classification, regulatory submission, customer distribution or measured vendor test was performed. The existing Lisam profile retains its earlier source-review date.
- ECHA: safety data sheets and supply-chain information
- DR-Software: ChemGes overview and data exchange
- DR-Software: SDS versions, languages and distribution
- DR-Software: formulation records and revisions
- DR-Software: update and maintenance conditions
- Lisam: ExESS authoring, content and connected applications
- DR-Software: label templates and output