Direct answer: Decide and document how new information changes Canadian output.
Capture change signals
Formula, grade, new hazard data, properties, uses or regulatory guidance can initiate review.
Find the affected portfolio
One supplier revision can affect many products and both languages.
Assess classification impact
Compare source values and approved decisions endpoint by endpoint.
Review linked outputs
Open the bilingual SDS and supplier label together where identity or hazards may change.
Release and archive
Preserve prior versions, named approval and distribution context.
Practical example
A supplier revises acute toxicity data. The system finds all mixtures using that grade and reopens the affected classification and bilingual sections.
Release checklist
- Record source and date
- Find affected products
- Assess hazard impact
- Review both languages and labels
- Approve and archive
Common mistakes
- Changing only Heading 16
- Overwriting source history
- Updating English alone
Frequently asked questions
Does every supplier revision require release?
It requires documented impact review, not necessarily a new finished-product release.
Should old versions be deleted?
No. Preserve controlled history according to applicable requirements and policy.
Can software declare a change immaterial?
It can compare data, but a named reviewer should approve the decision.
What belongs in the change record?
Source, affected facts, assessment, outputs, reviewer and release.
Primary sources
Review notice: CANADIAN REGULATORY AND FRENCH TERMINOLOGY REVIEW REQUIRED BEFORE INDEXING.