Hazard and Precautionary Statements Explained

Hazard and precautionary statements are standardized sentences used under CLP (and GHS-aligned systems) to tell users what the hazard is and what to do about it. On EU labels and in SDS Section 2, they are not creative copy. They are controlled communication elements tied to classification outcomes.

ECHA’s CLP labelling pages explain how label elements—including hazard and precautionary statements—fit the broader labelling duty: CLP labelling. For how CLP relates to the UN model system, see GHS vs CLP explained.

What are hazard statements (H-statements)?

Hazard statements describe the nature and degree of the hazards of a substance or mixture. They are commonly shown as codes such as H225 or H317 plus the standardized phrase text in the required language.

Examples of what they communicate (illustrative categories, not a full list):

• Physical hazards (flammability, explosivity, oxidising behaviour)
• Health hazards (toxicity, sensitisation, aspiration, specific target organ toxicity)
• Environmental hazards (aquatic hazards and related statements)

Authors should not invent “clearer” hazard wording to replace an applicable H-statement. If classification applies, the corresponding statement set applies. Supplemental information may be allowed in defined cases, but it does not replace obligatory hazard statements.

What are precautionary statements (P-statements)?

Precautionary statements describe recommended measures to minimise or prevent adverse effects from storage, handling, or emergency response. They are coded (for example P210, P280, P501) with standardized text.

P-statements are often grouped by type:

• Prevention — how to avoid creating or increasing the hazard
• Response — what to do after exposure, spill, or fire-related events
• Storage — how to keep the product safely
• Disposal — how to dispose of contents/container appropriately

CLP and supporting guidance address selection and precedence so labels do not become unreadable walls of every possible P-statement. Teams still need a documented selection method—especially when mixtures trigger many statements and packaging space is tight.

How do H/P statements connect labels and SDS?

Classification is the parent decision. Label elements and SDS Section 2 are child projections of that decision.

A healthy control loop:

1. Classify under CLP criteria (and harmonized entries where applicable).
2. Generate the label element set (pictograms, signal word, H/P statements, identifiers).
3. Mirror the hazard communication in SDS Section 2 and keep related sections consistent.
4. Translate using controlled phrase libraries for standardized statements.
5. Release SDS and label language packs together for each market.

When label artwork and SDS diverge, customers and inspectors notice. Cross-check routines belong in your SDS review habits described in safety data sheet 16 sections explained. Language packing rules are covered in EU SDS and label language requirements.

Why is free paraphrase a compliance risk?

Marketing and generic translation workflows optimize for tone and brevity. H/P statements optimize for legal and technical interoperability.

Risks of paraphrase:

• Obligation strength changes — “must” becomes “should,” or a response action is softened.
• Cross-language mismatch — DE/EN/FR statements no longer mean the same thing.
• Search and system breaks — codes and standard phrases cannot be validated automatically.
• Label truncation errors — cutting a clause to fit a box can remove the action that mattered.

For multilingual production controls that protect meaning, see translating SDS and CLP labels without losing legal meaning.

How should mid-market teams govern H/P content?

Practical governance beats heroic individual expertise:

• Store codes, not only text — H225 plus language-specific approved phrase.
• Own a phrase library aligned to official language versions where available.
• Gate artwork so designers cannot edit statement text in Illustrator without a compliance pull request.
• Diff language packs on statement codes before release, not only on file dates.
• Train sales and customer service not to “simplify” label text in emails or sell sheets in ways that contradict the CLP label.

This is document control applied to hazard phrases. Treat it with the same seriousness as SOP effective dates.

What changes when mixtures trigger many H/P statements?

Mixtures are where statement governance gets stressful. Multiple ingredients can drive overlapping hazards, long P-statement lists, and label real-estate conflicts.

Practical tactics:

• Maintain a rules-based selection procedure aligned to CLP guidance on precedence and redundancy.
• Record why a statement was included or omitted for a given mixture revision—future you will need that rationale.
• Stress-test the smallest commercial pack size early; do not discover unreadable type after artwork is approved for launch.
• Prefer reducing redundant precautions over inventing shorter unofficial sentences.
• Ensure SDS Section 2 still carries the full required hazard communication even when the on-pack set is reduced under applicable rules.

Customer questionnaires sometimes ask for “all H/P codes” in a spreadsheet. Supply codes from the controlled library tied to the approved classification, not from a designer’s text box export. Spreadsheet drift is a common source of portal vs label mismatches.

Training for new regulatory staff should include a live exercise: take one mixture, generate the statement set, compare EN/DE/FR phrase library outputs, and reconcile against the label proof. That exercise surfaces process gaps faster than slide decks.

How do EUH statements fit beside H- and P-statements?

CLP also uses EUH supplemental hazard statements for EU-specific information that is not always mirrored one-for-one in the UN GHS phrase set. Examples include certain reactivity or use-condition messages that still appear on labels and in SDS Section 2 when applicable.

Treat EUH codes with the same control discipline as H- and P-codes:

• Keep them in the phrase library with official language text.
• Tie them to the classification or supplemental-labelling decision that triggered them.
• Diff them across language packs the same way you diff H225 or P280.
• Do not let marketing “clarify” an EUH phrase into informal wording.

When customers ask for a single spreadsheet of “all hazard phrases,” include H, P, and applicable EUH codes from the approved classification package—not from free-text scraped off artwork.

FAQ

Do we print both the H/P code and the full sentence?

Labels typically present the statement text; codes are widely used in SDS and internal systems. Follow CLP labelling rules and your market’s practice guidance for what appears on-pack. Internally, always retain codes so translations and updates stay traceable.

Can we drop P-statements if the label is too small?

Label size and layout constraints are real, but dropping obligatory communication without a rules-based selection approach creates compliance and safety risk. Use CLP-aligned selection/precedence methods, consider packaging redesign, or market-specific label strategies—not silent deletion of inconvenient precautions.