Documents to share with customers: a chemical supplier checklist

When should a chemical supplier use a document sharing checklist?

A chemical supplier should use a document sharing checklist whenever a document or record is about to leave the company for a customer: a first shipment, a new contact at an existing account, a customer audit, a complaint, a trial, or a request for "everything you have" on a product. The checklist sorts each item into one of four groups before anyone presses send. Share by default covers what the customer needs to use the product safely and to receive it against the agreed specification. Share on request covers items that are useful to some customers but carry conditions, such as a confidentiality agreement or a matching lot. Share under an NDA covers composition detail beyond the SDS for a named recipient. Keep internal covers records whose value depends on staying inside the company or that belong to someone else.

The readers are technical service engineers, quality staff, customer service and account managers, because each of them sends documents and each sees a different part of the file. The checklist does not replace legal advice on a specific confidentiality claim, and it does not decide what a supply agreement says; it records which rule or condition applies and who owns the decision. It fits chemical suppliers and distributors selling in the US and EU, where safety data sheet duties come from 29 CFR 1910.1200(g) and REACH Article 31, and contracts and confidentiality agreements decide most other documents. The editable Word checklist is at the end of this page.

Which documents must a chemical supplier give every customer?

A chemical supplier must give every customer that receives a hazardous chemical a current safety data sheet (SDS), and in practice also shares the current technical data sheet (TDS), the agreed product specification and the certificate of analysis (CoA) for the lots that customer receives. Only the SDS duty comes from regulation; the other three come from the supply relationship, and the supply agreement or quality agreement usually names them. Sending the default set at the first shipment, and again whenever a revision is issued, means a customer's own audit does not find a missing or outdated SDS. The table below decides what goes into the default customer-facing set.

The key row is the SDS: in the US, chemical manufacturers, importers and distributors must provide it with the initial shipment and with the first shipment after it is updated (29 CFR 1910.1200(g)(6)(i), (g)(7)(i)). In the EU, Article 31(5) adds that the SDS is supplied in an official language of the Member State where the product is placed on the market, unless that state provides otherwise (REACH Article 31(5)).

Which documents should a supplier share only on request or under NDA?

A supplier should share test reports, certificates, regulatory declarations, audit results and any composition detail beyond the SDS only on request, and composition detail only under a confidentiality agreement (NDA). These documents are often true and useful, but each carries a condition that the default set does not: it covers a specific product version, a specific test, a specific date or a disclosure the supplier has chosen to protect. The table below sorts them.

The key row is composition. A request for the full formula from a customer's safety team is often answerable with the SDS, which must already disclose properties and effects even where an identity is withheld (29 CFR 1910.1200(i)(1)(ii)). When more is genuinely needed, a named recipient under an NDA keeps the disclosure narrow. Certificates and declarations need the same care for a different reason: they expire or are replaced, so the version a customer holds can become wrong without anyone changing it. Send each one with its issue date and validity, and record who received it so a replacement reaches the same people.

Which records should a chemical supplier keep internal?

A chemical supplier should keep internal its formulations and exact compositions, cost and margin, other customers' data, supplier and manufacturer links, and its own complaint and investigation notes until a conclusion is reached. These records either lose their value once they are shared or belong to someone other than the customer asking.

Formulations are the clearest case because their legal protection depends on keeping them secret. Under the EU Trade Secrets Directive, information is a trade secret only if, among other conditions, "it has been subject to reasonable steps under the circumstances, by the person lawfully in control of the information, to keep it secret" (Directive (EU) 2016/943, Article 2(1)(c)). US federal law uses a similar test, requiring that the owner "has taken reasonable measures to keep such information secret" (18 U.S.C. 1839(3)(A)). This suggests that a formulation sent without an NDA weakens a later trade secret claim, because the supplier did not take reasonable steps in that instance.

Supply chain links are also sensitive. REACH Article 118(2) lists the links between a manufacturer or importer and its distributors or downstream users among the information whose disclosure is normally deemed to undermine commercial interests; that article governs access to information the European Chemicals Agency holds, not supplier correspondence, but it shows how regulators rate this data (REACH Article 118(2)(d)). Other customers' site data, prices and names belong to those customers under their own agreements and never go into a different customer's file.

What should you check before sharing a document with a customer?

Before sharing a document with a customer, check that it is the right document, the right version, for the right recipient, and that it contains nothing that belongs in the keep internal group. Many sharing errors are not decisions to disclose; they are a correct decision applied to the wrong file.

Run the checks in this order. First, the recipient: confirm the customer account and the named contacts, and whether the item should go to the whole account or only to a chosen contact such as the quality lead. Second, the version: compare the revision date with the current master copy, because REACH Article 31(9) requires suppliers to update an SDS without delay when new hazard or risk management information becomes available and to send the revised version to everyone supplied in the preceding 12 months (REACH Article 31(9)). Third, the match: for a CoA, the lot number on the certificate is the lot on the delivery note.

Fourth, the content: search the file for other customers' names, sites, prices, internal comments and tracked changes, which are common in reports built from an earlier report. Fifth, the owner: write who owns the item and when it is next reviewed. An item with no owner stays shared after it has gone out of date, because nobody is responsible for withdrawing it.

When should you stop sharing a document with a customer?

A supplier should stop sharing a document with a customer when it is superseded, when it no longer applies to what the customer buys, when its validity ends, or when the person or account it was shared with no longer has a reason to see it. Stopping is a decision to record, not only a file to delete, because the customer may have downloaded the earlier version.

Six triggers cover most cases. A new SDS or TDS revision supersedes the old one; withdraw the old version and send the new one, which in the EU must reach every recipient supplied within the preceding 12 months (REACH Article 31(9)). A product is discontinued or reformulated; the old specification and TDS stop applying to new deliveries. A certificate or declaration expires or is replaced. A new edition of a standard, such as ISO 9001:2026 replacing ISO 9001:2015 (ISO, 2026), follows the certification body's transition rules: share the current certificate with its expiry and transition dates, and replace it when the new one is issued. A contact leaves the customer or changes role; their access ends even if the account continues. A supply agreement or NDA ends; items shared under it stop being shared. An error is found in the shared item; withdraw it and send the corrected version to the same recipients.

Record the date, the reason and what replaced the item, so anyone who finds the old version can tell which one is current.

What does an illustrative customer document sharing decision look like?

An illustrative customer document sharing decision shows how the checklist sorts a mixed request; the customer, product and dates below are illustrative and do not describe a real case. A machine shop's new environmental, health and safety manager asks a coolant supplier, on 2026-10-05, for "the SDS, the full formula, your last three audit reports and the lab results from the plant down the road that uses the same product".

The supplier sorts each item. The SDS is share by default; the current revision goes to the manager and to the existing quality contact the same day. The full formula is composition beyond SDS section 3; the supplier offers a call with its product safety specialist, explains what section 3 already discloses, and offers an NDA if a named substance is needed for the customer's own assessment. Any withheld identity is still disclosed at once to a treating health professional in a medical emergency, as US rules require (29 CFR 1910.1200(i)(2)).

The audit reports are share on request; the supplier sends the summary of its most recent third-party quality audit and its current certificate after checking edition and expiry. The other plant's lab results are keep internal: they are another customer's data. The supplier records the decision per item, the owner, and a review date tied to the next SDS revision.

Why do supplier document sharing decisions go wrong?

Supplier document sharing decisions go wrong through version, recipient and reuse errors, and a checklist catches all three before a file is sent. Four patterns are worth checking for.

An outdated SDS or TDS stays in a shared folder or an email template after a revision, so a customer keeps working from it. The fix is an owner and a review date on every shared item, and withdrawal of the old version when the new one is issued, with the revision sent to recent recipients as REACH Article 31(9) requires in the EU (REACH Article 31(9)).

A CoA for the wrong lot is sent because the request named the product and not the delivery. The fix is matching the lot number on the certificate to the delivery note before sending.

A report built from another customer's report keeps that customer's name, site or results in a table, a header or the document properties. The fix is a content check before every send, including tracked changes and comments.

A whole account is given access when only one contact should see an item, such as a complaint investigation or an NDA disclosure. The fix is choosing the sharing scope per item and per contact. Internal complaint notes are a special case: share the concluded report, not the working notes, which may hold early guesses that the investigation later ruled out.

Customer document sharing checklist for chemical suppliers

The customer document sharing checklist below is the text version of the Word checklist; run it once per item before it leaves the company. The Word checklist has seven sections.

1. Item: name, revision or lot, date, owner.

2. Group: [ ] share by default, [ ] share on request, [ ] share under NDA, [ ] keep internal.

3. Rule or condition: for an SDS, the jurisdiction and paragraph (29 CFR 1910.1200(g), REACH Article 31); for other items, the agreement or reason.

4. Recipient: [ ] customer account confirmed, [ ] named contacts chosen, [ ] whole account only if every contact should see it.

5. Version: [ ] matches the current master copy, [ ] superseded versions withdrawn.

6. Match: [ ] CoA lot equals delivery lot, [ ] certificate edition, scope and expiry checked.

7. Content: [ ] no other customer's names, sites, prices or data, [ ] no cost or margin, [ ] no tracked changes or internal comments, [ ] trade secret items withheld or covered by an NDA.

8. Language: [ ] SDS in the official language where the product is placed on the EU market (REACH Article 31(5)).

9. Record: [ ] date shared, scope, review date, and reason when sharing stops.

10. Sign-off: checked by; approved by for items on request or under NDA.

Use the four groups in step 2 as the default for each document type, and record any exception with its reason. In Lubinpla, field care shares each item with a whole customer account or with chosen contacts, and the supplier can withdraw sharing at any time. Whichever system holds the shared set, the checklist decides what belongs in it.