The Workwear Compliance Documentation Pack: What EU and US Buyers Must Collect Before 2027
- Share
- publisher
- UniOuter
- Issue Time
- Oct 1,2026
Summary
A workwear order without its documentation pack is unfinished. This guide lists the documents EU and US buyers should hold before the first shipment, explains what each one proves, and shows how to structure a compliance file that survives a tender, an inspection and a customer audit.
Most workwear disputes are not about the garment. They are about which document was supposed to exist, for which batch, and whether anyone still has a copy.
This guide sets out the documentation pack a professional workwear programme should hold before the first shipment leaves, what each item proves, and how to structure the file so it answers a tender questionnaire, an inspection and a customer audit without a scramble. It builds on our factory audit checklist and our guide to sourcing custom workwear.
Start With the Legal Framework
Protective workwear is regulated, and the regulation determines which documents must exist. For protective garments placed on the EU market, the framework is Regulation (EU) 2016/425, which requires a technical file supporting the protective claims, conformity marking and traceability to the responsible economic operator. In the United States the equivalent expectations come through a combination of OSHA requirements and the specific performance standards referenced in them.
The practical consequence for a buyer is simple: if the garment claims protection, there must be a document behind the claim, tied to the specific product, and the buyer should hold a copy. A generic certificate for a fabric family is not a substitute.
The Core Documents and What They Prove
| Document | What it proves | Who issues it |
|---|---|---|
| Technical file | The protective claims are supported and traceable to a responsible operator | Manufacturer, reviewed by a notified body where required |
| Batch performance test report | The specific fabric or garment meets the named standard | Accredited third-party laboratory |
| Restricted substance report | The garment meets chemical restrictions for the destination market | Independent testing provider |
| Mill declaration | Fibre composition, weight, construction and finish chemistry for the batch | Fabric mill |
| Social compliance audit | The production site meets recognised labour standards | Audit body under a framework such as amfori BSCI |
| Quality inspection report | The delivered goods matched the approved specification | Buyer's inspector or third-party inspection firm |
Batch, not brand. The most common gap in a compliance pack is evidence that is real but generic. A test report for the fabric family does not cover a different dyehouse batch, a different finish recipe or a lighter weight. Every document should name the batch it applies to.
The Standards Behind the Claims
Protective claims are written against standards, and the standards are published by bodies whose pages are the authoritative reference when a claim is questioned. For high-visibility clothing the European standard is EN ISO 20471, published through ISO, with the US equivalent referenced in ANSI/ISEA 107. For heat and flame protection the reference is EN ISO 11612, and for rain protective clothing EN 343. The European classification framework that these standards sit inside is maintained by CEN-CENELEC.
Two supporting layers complete the file. Chemical compliance is normally evidenced through OEKO-TEX STANDARD 100 testing or an equivalent restricted substance report, and social compliance through a recognised audit framework such as amfori BSCI. Buyers should treat all of these as recurring costs, refreshed each season, rather than documents collected once.
Building the Pack: Six Steps
Where Compliance Packs Fail
Generic instead of batch-specific
A certificate for the fabric family is offered in place of a report for the delivered batch. It is the most common and most easily detected gap.
Expired or stale
Reports from two seasons ago are presented for a current order. Restricted substance lists change, and the report must reflect the chemistry actually used.
Missing the tape and trim
Face fabric and reflective tape are tested separately but the finished garment is not. Tape adhesion and retro-reflectivity after laundering are garment-level properties.
No wash durability statement
The claim is stated for a new garment without naming the wash cycle at which it still passes, so nobody knows when the protection ends.
Where UniOuter Fits
We supply workwear with the compliance pack assembled as part of the order: batch test reports, mill declarations, restricted substance testing and social audit evidence, filed by style and batch so any shipment can be evidenced quickly. We also tell buyers plainly when a requested claim needs a re-test rather than an existing document, because that conversation is far cheaper before production than after delivery. Send your standard list through our inquiry page and we will return the documentation scope for your programme.
Shop Certified Safety Workwear
Frequently Asked Questions
A technical file is the evidence set that supports the protective claims on a garment. Under Regulation (EU) 2016/425 the manufacturer holds it, but the buyer should have access to the relevant test reports. If your tender or inspector asks for evidence, a technical file reference is the answer you need to be able to give.
Only if the fabric, finish chemistry, dyehouse and tape supplier are unchanged and the applicable restricted substance list has not been updated. In practice that is rarely the case, so budget a re-test. A stale report is worse than none because it looks like compliance without being it.
Both should hold copies, but the buyer must hold their own. The factory generates most of the evidence, yet the buyer is the one answering a tender questionnaire, an inspection or a customer audit, usually on a short deadline.
Yes. Recognised frameworks such as amfori BSCI run on audit cycles, and an audit for one site does not cover another facility. If your programme uses more than one production site, each site needs its own valid audit.