Case Study: Material Safety Data Sheet (MSDS/SDS) Management System for Chemical Production & Shipping Compliance
What was breaking in chemical compliance documentation before this project?
The client was a chemical production and shipping company handling highly toxic and hazardous chemicals. Federal regulations require accurate Material Safety Data Sheets (now also known as Safety Data Sheets under the OSHA HazCom 2012 standard aligned with the Globally Harmonized System) for every chemical the company handled. The data on each chemical had to be exact: composition, hazard classifications, handling requirements, storage conditions. A single error on a manifest or a shipping label is not a paperwork problem. It is a regulatory violation that can halt operations, trigger reportable incidents, and expose the company to liability.
The existing system was built on Visual Basic 6 and needed to be revitalized to handle multiple regulatory updates and the package deployment requirements of several chemical production and shipping clients. The system also needed to produce compliant output across a full range of formats: SDS documents for regulatory files, manifests for transportation, labels sized to specification for containers, and signage for storage locations. Managing all of that from a single database without manual reconciliation between systems was the core requirement, and the existing architecture was no longer sufficient to the regulatory pace the operation faced.
For a chemical production and shipping operation, the consequences of weak SDS infrastructure are operational and direct. A label that does not match the manifest can stop a shipment at a checkpoint. A batch record that cannot be traced to a delivery creates audit exposure. A manifest with a hazard classification error can result in a regulatory citation and a reportable incident. The compliance documentation is not separate from the business. It is the business, when the business is moving hazardous chemicals across regulated supply chains.
What did PCG actually build for the chemical compliance environment?
PCG designed an extensive Visual Basic program and database system that gave the company direct, fast access to every chemical record in their inventory. The architecture was built around a single source of truth for chemical data, with output formats produced from that source rather than maintained in parallel. Each component was built so that the regulatory documentation the operation produced every day reflected the actual chemical and batch data, not a manually entered summary that might drift from the physical record.
Every chemical the operation handled was recorded in a central database with full composition, hazard classification, handling requirements, and storage conditions. The search engine allowed operators to locate any compound quickly by exact chemical data. Adding, editing, updating, and searching chemicals happened from one interface rather than across separate documents.
Each batch of chemicals was tracked through to its associated shipments, maintaining a complete chain of custody from production through delivery. That linkage is what makes the system defensible in a regulatory review. When an inspector or auditor asks for the documentation associated with a specific shipment, the answer comes from the linked batch record rather than from a manual reconstruction across separate files.
The system produced MSDS and SDS documents directly from the underlying chemical records. Composition, hazard classifications, handling requirements, and storage conditions appeared on the generated documents exactly as they appeared in the database. The risk of drift between the source record and the regulatory output was eliminated by making the output a query rather than a separately maintained document.
The same chemical record that produced the SDS document also produced the transportation manifests for shipments, the container labels sized to specification, and the signage for storage locations. Every regulatory output that referenced a chemical drew from the same source, which kept the manifest, the label, the SDS, and the storage signage internally consistent without manual cross-checking.
The system was designed to support several chemical production and shipping clients with their own package deployment requirements. Each client could operate its own configured deployment of the system without forcing the architecture to fragment. Updates to handle new regulatory requirements deployed across all client installations through the same maintenance workflow.
Chemical compliance fails in a specific way. The data exists. The chemical records are filed. The SDS documents have been written. The manifests have been produced. What does not exist, until someone audits the operation, is the guarantee that the SDS, the manifest, the container label, and the storage signage all reference the same chemical record with the same data. Drift between those documents is invisible until a regulator finds it during inspection. A system that produces every output format from the same source eliminates the drift category at the architectural layer rather than asking compliance staff to catch it manually.
The decision to support multi-client package deployment from one system was deliberate. The client served several chemical production and shipping operations, each with its own deployment requirements. Building separate systems per client would have multiplied the maintenance burden without delivering value to any of them. A single architecture configurable per client kept regulatory updates manageable across the full operation while letting each deployment match its specific operational context.
What changed after the system went into production?
The most immediate change was that every regulatory output format the operation produced drew from one chemical record. Manifests, container labels, SDS documents, and storage signage all reflected the same source data by construction. The cross-checking work that had previously absorbed compliance staff time disappeared because the documents reconciled by architecture rather than by manual review.
| Outcome | Result | How it was achieved |
|---|---|---|
| Cross-format documentation consistency | Single source of truth | SDS, manifests, labels, and signage produced from the same chemical record |
| Chain of custody documentation | Production through delivery | Batch-level tracking linked to shipment records across the operation |
| Chemical lookup and search | Exact-match across full inventory | Direct search engine for chemical composition, hazard classification, and handling data |
| Regulatory output formats supported | SDS, manifests, labels, signage | Single chemical record drives every regulatory output the operation requires |
| Multi-client deployment | Configurable per client | Package deployment architecture supported several chemical production and shipping clients from one codebase |
| Regulatory update absorption | Deployed across all clients | Maintenance workflow propagated regulatory changes through every client installation |
The strategic value of the system extended beyond the immediate compliance posture. Once chemical inventory, batch tracking, and regulatory output operated as one platform across multiple client deployments, the operation gained the kind of reusable infrastructure that smaller chemical compliance shops cannot build from scratch. Each new client deployment started from a working foundation rather than a custom build, which changed the economics of expanding the chemical compliance service line.
What capabilities does this kind of system provide for chemical compliance operations?
The infrastructure built for this chemical production and shipping operation addresses a problem class that appears across every operation handling regulated chemicals under federal HazCom, OSHA, DOT, EPA, or international GHS frameworks. The capabilities below apply to chemical manufacturers, chemical distributors, hazmat shippers, industrial hygiene firms, environmental services companies, and any operation where Safety Data Sheets, transportation manifests, container labels, and storage signage have to remain internally consistent under regulatory review.
One database structure containing complete chemical composition, hazard classification, handling requirements, and storage conditions. Cross-format outputs draw from the same source rather than being separately maintained, which eliminates the document drift that produces audit exposure.
Batch-level tracking linked to shipment records across the operation. Inspectors and auditors who request documentation associated with a specific shipment receive a query result from linked records rather than a manual reconstruction.
MSDS and SDS documents, transportation manifests, container labels sized to specification, and storage location signage produced from the same chemical records. Every regulatory output that references a chemical reflects the same source data by construction.
One configured architecture supporting multiple chemical production and shipping clients with their own deployment requirements. Regulatory updates propagate across all client installations through the same maintenance workflow, keeping the operation aligned without parallel rebuilds.
Technology stack
| Component | Technology |
|---|---|
| Application layer | Visual Basic 6 with Microsoft Access database back-end |
| Programming | Visual Basic for Applications (VBA) for application logic and reporting |
| Chemical inventory | Centralized database with exact-match search across composition, hazard, and handling data |
| Chain of custody | Batch-level tracking linked to shipment records from production through delivery |
| Document generation | MSDS, SDS, manifests, container labels, and storage signage produced from chemical records |
| Regulatory framework | OSHA HazCom 2012 / GHS, DOT transportation, EPA, and federal hazmat alignment |
| Deployment | Multi-client package deployment supporting several chemical production and shipping operations |
Does this apply if your chemical operation is smaller than a multi-client production and shipping company?
The architecture scales down as well as up. A single-site chemical manufacturer, a regional hazmat shipper, an industrial hygiene firm, or a small chemical distributor faces the same core problems as a multi-client chemical production and shipping operation: regulatory documentation that has to remain consistent across multiple output formats, chain of custody gaps that surface during inspection, and a regulatory pace that legacy systems cannot absorb cleanly. The engineering decisions on this project transfer directly to chemical operations of any size.
What makes this project transferable is not the multi-client dimension. It is the problem class. Any operation handling regulated chemicals is carrying the same documentation drift risk this client was carrying before the system went live. The drift accumulates invisibly until an inspector finds it during an audit, a manifest mismatch stops a shipment at a checkpoint, or an OSHA enforcement action surfaces inconsistencies between the SDS, the label, and the storage record. A system that produces every output from the same chemical record eliminates the category of error that drives those incidents.
PCG has built chemical, hazmat, and environmental compliance infrastructure for industrial operators, chemical companies, and regulatory service firms since 1995. The work documented here is one of more than 500 production applications PCG has delivered, with environmental and regulatory compliance representing approximately one-third of that volume across 31 years.
Frequently asked questions about MSDS and SDS chemical compliance management systems
Allison has been building custom software since the early 1980s, including work as a data analyst for the U.S. Air Force before founding PCG in 1995. The MSDS and SDS chemical compliance work documented here is one of more than 500 custom applications PCG has delivered, with environmental and regulatory compliance representing approximately one-third of that volume across 31 years. Her direct involvement in every project is not a policy. It is how PCG operates. When you call, she answers.
Project details documented with client permission. Specific identifying details about the chemical production and shipping company have been generalized at client request. System capabilities and architecture reflect the actual production deployment.
PCG founded 1995. Allison Woolbert's personal experience in software development predates PCG's founding.