Lubinpla

How to write a technical bulletin for chemical customers

Summary

A customer technical bulletin takes 5 steps: rule out a change notice, name products and customers, state the change, list actions, cite the SDS. The steps fit news that informs customers without asking them to approve anything. A change that could affect product characteristics, performance or regulatory compliance usually goes as a formal change notification under the customer's terms.

  • In the United States, a safety data sheet preparer who becomes newly aware of significant hazard information adds it to the SDS within three months (29 CFR 1910.1200(g)(5), OSHA, 2024).

  • In the EU, a revised SDS identified as "Revision: (date)" goes to all recipients supplied within the preceding 12 months (EU REACH, Article 31 paragraph 9, 2025).

  • One coatings maker asks its suppliers for notice of any proposed change at least 90 days before the planned production date (PPG, 2022).

  • A state transportation department template says a technical bulletin should generally not exceed 2 pages, front and back (NCDOT, 2007).

This guide covers bulletins a chemical supplier or distributor sends to industrial customers about products already supplied. It does not replace a customer's change notification procedure, a quality agreement, or a recall or safety alert; where those apply, their form and deadlines come first.

What do you need before writing a technical bulletin?

Start with the facts of the change or finding, the evidence behind it, the affected products and the customers who bought them, and the current SDS and technical data sheet for each product. Without the customer list, the bulletin reaches the wrong readers. Without the evidence, it reads as an opinion.

In practice that means collecting four items. First, the product codes, grades and pack sizes affected, plus any lot or date range if the news applies to only part of the supply. Second, the sales or shipment record showing which customers received those products. Third, the test result, field report or regulatory text that supports the bulletin. Fourth, the current SDS revision date for each product, which tells you whether the bulletin needs a new SDS.

Also check whether a bulletin on the same subject has already gone out. A North Carolina Department of Transportation template asks authors to research similar bulletins before writing one, and to update an existing bulletin by starting from the original distributed version and adding the revision date (NCDOT, 2007). A second bulletin that quietly contradicts the first is harder to fix than a revised one.

When is a technical bulletin the right document, and when is a change notification needed?

Use a technical bulletin when the news informs customers without changing what they buy. Use a change notification when the change could affect the product's characteristics, performance or regulatory compliance. No standard draws this line for chemical bulletins, so the split below is reasoned from published customer requirements; it is not a rule.

Published customer requirements show where the formal route begins. One coatings maker asks suppliers to notify it at least 90 days before a planned production change and to obtain its acceptance before implementing any change that could affect the characteristics, performance or regulatory compliance of its products (PPG, 2022). Its minimum list includes a new raw material source, a formulation or ingredient change, a new manufacturing site, a changed specification or test method for a certified property, an SDS change and a packaging change (PPG, 2022). Biopharmaceutical buyers list similar areas, including materials, process, testing, packaging and labeling (BioPhorum, 2021).

The table below sorts news by the document it needs; each row is an illustrative case.

News to send

Document

Why

Formulation, raw material source or site change (illustrative)

Change notification

Customer acceptance may be required first

New handling or storage advice, same product (illustrative)

Technical bulletin

Informs; unless the customer's terms list storage or shelf-life changes (BioPhorum, 2021)

Corrected value on a technical data sheet (illustrative)

Technical bulletin

Product unchanged; unless the corrected value is a certified property in the customer's terms (PPG, 2022)

New hazard information on an SDS (illustrative)

Both, if the contract lists SDS changes

Revised SDS plus the customer's notice

The formulation row is the one most often sent the wrong way. If a customer's terms list formulation changes, a bulletin does not replace the notice and approval that customer asks for.

How do you write a technical bulletin step by step?

The work runs in five steps, and each one produces a part of the bulletin the customer can check.

  1. Rule out a change notice. Compare the news with the change notification terms of each affected customer. Any customer whose terms list it gets the formal notice; the rest get the bulletin.

  2. Name products and customers. The title block carries the product names, codes and grades, with any lot or date range. Address the bulletin to the customers on your shipment list.

  3. State the change and its evidence. The first paragraph says what is new, from which date, and why. The evidence follows in plain terms: the test, the method and the result. Internal cost, margin and investigation notes stay out; what to leave out of a technical report for a customer covers the same choice for longer documents.

  4. List actions. Write numbered actions: what the customer should do, by when, and whom to contact. If the customer needs to do nothing, say so in one sentence.

  5. Cite the SDS. Give the applicable SDS revision date and say whether a revised SDS is attached.

Keep it short. The NCDOT template says a bulletin should generally not exceed 2 pages, front and back, so that the target audience reads it in full (NCDOT, 2007).

When must a technical bulletin point to a revised SDS?

A bulletin must point to a revised SDS when the news is new hazard information, new information that may affect risk management measures, or, in the EU, an authorisation decision or a restriction on the substance. In those cases the SDS update is a legal duty with its own deadline, and the bulletin only explains it.

In the United States, the preparer who becomes newly aware of significant information about a chemical's hazards, or ways to protect against them, adds it to the SDS within three months (29 CFR 1910.1200(g)(5)). Manufacturers and importers, and distributors passing the product on, then provide the updated SDS with the first shipment after the update (29 CFR 1910.1200(g)(6)(i), (g)(7)(i)). For labels, the rule allows six months after the supplier becomes aware of the new information (29 CFR 1910.1200(f)(11)(i)).

In the EU, REACH Article 31(9) requires suppliers to update the SDS without delay on three occasions (European Union, consolidated 2025): new information that may affect risk management measures or new hazard information, an authorisation granted or refused, or a restriction imposed. The text continues: "The new, dated version of the information, identified as ‘Revision: (date)’, shall be provided free of charge on paper or electronically to all former recipients to whom they have supplied the substance or mixture within the preceding 12 months." (Regulation (EC) No 1907/2006, Article 31(9))

Give the revision date in the bulletin and attach the revised SDS. Do not rely on a summary of hazard changes in the bulletin alone.

How do you check a technical bulletin before it goes to customers?

Check the draft against the five steps: the right document type, named products and customers, a dated change with evidence, actions with owners and dates, and the correct SDS revision. The table shows whether the draft goes out as a bulletin, goes as a change notification instead, or goes back for rework.

Check

Pass

Fail and what to do

Document type

No affected customer's terms list this change

Send the formal change notice to those customers

Products named

Product names, codes and lot or date range in the title block

Add them; a reader must match the bulletin to stock

Customers named

Shipment records support the distribution list

Rebuild the list from shipments

Change and evidence

First paragraph states what, from when and why; evidence named

Rewrite the first paragraph; add the test or source

Customer actions

Each action has an owner and a date, or "no action" is stated

Add owner and date, or state no action

SDS

Revision date given; revised SDS attached if hazard information changed (29 CFR 1910.1200(g)(5); REACH Article 31(9))

Update the SDS first, then send both

Length

2 pages or fewer, front and back (NCDOT, 2007)

Move detail to an attachment

The document type row decides everything below it. A draft that fails it is a change notification, and rewording will not fix it.

The SDS row comes second. A bulletin that announces new hazard information while the old SDS is still in circulation leaves the customer with two documents that disagree.

Have the check run by a second person who did not write the draft. The author already knows what the bulletin means and will read past gaps where a customer would stop.

In Lubinpla, document writing drafts a bulletin as the "other" document type, using only what was settled in the conversation, and once a person approves it, registers the PDF to that customer.

What are the most common technical bulletin mistakes?

The mistakes that come up most are using a bulletin in place of a change notice, leaving out the product codes, burying the change under background text, and sending hazard news without the revised SDS. Each one leaves the customer asking a question the bulletin should have answered.

A bulletin used in place of a change notice is the costliest mistake, because a customer whose terms ask for acceptance before a change, as some buyers do (PPG, 2022), may treat the change as unapproved.

Without product codes or a lot range, every customer has to ask whether their stock is affected.

A first paragraph that opens with company background hides the news. Put the change, its date and the reason first.

Describing a new hazard without attaching or dating the revised SDS leaves the customer with two documents that disagree. The SDS carries the legal hazard information, so the bulletin points to it, not the other way around.

An undated, unnumbered bulletin cannot be superseded cleanly. Give it a number and a date, and when you revise it, add the revision date after the original date, as the NCDOT template does (NCDOT, 2007).

Frequently asked questions

Is a technical bulletin the same as a technical data sheet update?

A technical bulletin is not the same as a technical data sheet update. The data sheet is the reference document for the product, and the bulletin tells customers what changed in it, from when, and what to do. Send the revised data sheet with the bulletin so both carry the same values.

Who should sign off a customer technical bulletin?

A customer technical bulletin needs sign-off from the person responsible for the product's technical content and from whoever owns regulatory and SDS matters, so the technical statement and the hazard information agree. Sales can check the distribution list but should not change the technical content.

Should a technical bulletin go to customers who stopped buying the product?

A bulletin carrying new hazard information should go with the revised SDS to recent former customers wherever the law requires the SDS to reach them: in the EU, the revised SDS goes to all recipients supplied within the preceding 12 months (EU REACH, Article 31 paragraph 9, 2025). For other bulletins, follow your shipment records and the customer's terms.

Related posts