Groups standardise protective clothing for good reasons and then discover the cost of doing it badly. A single product specified from head office is convenient to audit and often wrong for half the sites; a completely local approach produces six versions of the same requirement and no leverage with suppliers. The workable middle is a floor that applies everywhere, expressed in performance terms, with site-specific requirements added where the assessment calls for them.
Why the Programme Outlives the Product Choice
There is also a mobility argument that groups with high staff turnover or frequent transfers find compelling. Where a worker moves between two sites of the same employer, a common requirement means the garment issued at one site is the correct provision at the other, and the records travel with the person rather than being rebuilt on arrival. Where each site specifies by brand, the same worker can arrive with equipment that is compliant in one place and not in another, and the resolution is usually an exception rather than a rule.
Sites change, managers move and suppliers are replaced. What survives is the requirement: the hazard statements, the performance levels, the documentation format and the care rules. A group standard built on those outlasts any particular garment, and it allows a new site to be brought into the group without redesigning its protective clothing programme from scratch.
The commercial case is about comparability rather than price. When requirements are written as performance levels, several suppliers can quote against the same specification, quotations can be compared on the same basis, and volume can be consolidated where it makes sense. The same standard also makes internal audit possible: a group can check whether its sites are meeting the requirement using one template, instead of translating between six local habits.
Assessment, Selection and Issue
It is worth writing the group’s minimum as a performance requirement rather than as a product. A requirement expressed as a standard and a level allows a site to choose a model that fits its workforce and its supply chain, while a requirement expressed as a brand ties every site to one product and one route. Where a group has already standardised on a product for good operational reasons, that decision should be recorded as a procurement choice rather than presented as the safety requirement.
The assessment belongs to each employer and each site, because it depends on the tasks, the processes and the conditions there. The group’s role is to define how the requirement is expressed and what the minimum is, not to override the local assessment.
| Element | Group level | Site level |
|---|---|---|
| Hazard and performance requirement | Minimum level per hazard family | Additional requirements from the local assessment |
| Documentation | Common fields and format for issue and inspection records | Local filing and retention arrangements |
| Product choice | Performance criteria and evaluation method | Model, fit and local availability |
| Size range | Requirement to fit the workforce properly | Actual sizes and fitting arrangements |
| Care and retirement | Rules and record requirements | Laundry arrangements and storage |
| Procurement | Specification language and change control | Ordering route and stock levels |
Read across the table, the group sets the boundary and the site makes the decision inside it. That division is what keeps a multi-site programme both consistent and workable, and it gives a site that faces an unusual hazard a legitimate route to specify above the floor.
Training and Competence Evidence
Where the group operates across several markets, the training should also explain that marking conventions differ. A worker who has only ever seen one framework can misread a garment from another market as having a property it does not carry, and that misunderstanding is more likely to appear in a group with sites in different countries than in a single-market employer.
Training content can be standardised to a degree, particularly the explanation of what a marking means and when a garment must be withdrawn. What cannot be standardised is the task-specific element: the local trainer has to explain how the requirement applies to the work performed at that site, and which garments are issued for which task.
Competence evidence should follow the group format, because that is what makes an audit possible, but it should be delivered and recorded locally. Where a group has several languages or several shift patterns, the format should accommodate that rather than forcing a single delivery method that only works at head office.
Inspection Frequency by Hazard Class
One practical detail is worth standardising as part of the inspection rule: what happens to a garment that fails. A group requirement that every site has a quarantine location with a named owner, and that a withdrawn garment is never returned to the rack, removes the most common reason withdrawn equipment reappears. That single rule is easy to write and difficult to enforce unless it is checked.
The inspection logic is a good candidate for standardisation, because it is the part of the programme that is easiest to leave to interpretation. A group rule can state the levels of inspection, who performs each, and what must be recorded, while the site sets the intervals for its own conditions within stated guidance.
- Pre-use checks by the wearer, with a defined withdrawal route.
- Periodic inspection at an interval set against the manufacturer’s instructions and the site’s conditions.
- Post-wash inspection where garments pass through a managed laundry.
- Event-based assessment after an incident or an exposure beyond the garment’s specification.
- Retirement criteria applied consistently, with the reason recorded.
Where a group standardises the record rather than the interval, sites keep the flexibility they need while head office retains a consistent view. That combination is what makes a multi-site audit a comparison rather than an investigation.
Record Keeping for Audits and Incidents
Where a group uses several suppliers, the record should also identify the supplier and the batch where possible. That gives the group the ability to trace a problem across sites rather than within one, which is often how a wider issue becomes visible: the same early failure appearing at three sites points to a product or a laundry question that one site alone would treat as bad luck.
The record fields are the most valuable thing a group can standardise. If every site records the same items in the same structure, an auditor can compare them directly, and an incident investigation can establish what was issued to whom, against which requirement, with which care history.
The useful field set is small: the requirement the garment was purchased against, the model and size issued to each worker, the issue and replacement dates, the inspection results, the laundering history where it affects the claim, and the retirement reason. Where a group operates across several jurisdictions, the record should also capture the framework each requirement was written against, since the standards and the marking conventions differ between markets. How a procurement specification is written and evaluated is covered in Shield Wings’ PPE procurement guide, which owns that topic.
Retirement, Replacement and Stock Control
Where the group operates in several countries, the retirement rule also needs to accommodate different laundering arrangements, since a site with a managed service will see different wear patterns from one where workers wash their own garments. The criteria can remain the same while the inspection points differ, and that distinction should be explicit so that neither site is measuring itself against the other’s process.
It is also worth stating how a site may deviate and who approves it. Where local conditions genuinely require something different, a documented exception with a review date keeps the programme honest, and it prevents the informal drift that otherwise happens when a requirement cannot be met in practice. The exceptions themselves become a useful input when the standard is next reviewed.
Retirement criteria are worth standardising in full, because they are the point where local discretion most often reduces protection. If one site retires garments on holes and another on hardening and contamination, the group’s understanding of its own performance is inconsistent, and a recurring failure at one site may not be visible.
Replacement and stock control, by contrast, are best left local, with a group requirement to hold enough stock to replace a garment when it is withdrawn. Consolidated purchasing can still be used for common items, but the site needs the ability to re-equip a worker on the day a garment fails, and that depends on local stock rather than on a group order cycle.
Making the Programme Survive Contact With Operations
Finally, the standard should say how it will be reviewed. A group document that has no review cycle ages into a description of how things were done when it was written, and the sites that follow it faithfully will be working to a requirement that no longer matches their processes. An annual review, triggered by any change in task, process or regulation, keeps it current at modest cost.
The failure mode to design against is the standard that exists only in a document. A group requirement works when supervisors can see what it means for their area, when the records are short enough to complete, and when the local assessment has a visible route to add requirements. It fails when a template is issued without explanation and the sites quietly continue their previous practice.
Shield Wings manufactures protective clothing across the body protection range, including FR, arc-rated, anti-static and high-visibility families, and supports multi-site groups with specification language, size range planning and the documentation that a standardised programme needs. For groups writing a standard for the first time, the most useful first step is to express the minimum in performance terms, because everything else in a multi-site programme follows from that.
The test of a group standard is whether two sites facing the same hazard can show the same requirement, the same record and the same retirement rule, while a third site facing something different can explain why its provision differs. Where both are true, the standard is working.
Frequently Asked Questions
What should be standardised across sites?
The parts that should not vary: the minimum performance requirement for each hazard family, the documentation fields used to record what was issued, the care and retirement criteria, and the way requirements are expressed. Product models, size ranges and local features are better decided locally, because the conditions, the workforce and the supply routes differ between sites.
Does a group standard replace local risk assessments?
No. The assessment is the employer’s and is specific to the tasks and conditions of that site, so a group standard sets a floor rather than a substitute. Where a site’s assessment identifies a hazard the group standard does not cover, that site specifies for it and records the reasoning; where a site’s assessment shows a lower requirement, the group floor still applies.
How does standardisation affect procurement?
It makes requirements comparable, which is what allows volume to be consolidated and quotations to be assessed on the same basis. The gain is not only price: a specification written in performance terms can be met by more than one supplier, which keeps competition alive, and a common documentation format means a group can audit its sites against one template rather than several.
What is the biggest risk in a group standard?
Setting the requirement at the level of the most hazardous site and applying it everywhere. That inflates cost and reduces comfort in low-hazard locations, and it often leads to local deviations that are not recorded. The more durable model is a floor that applies everywhere, with additional requirements added by the sites that need them.
How should a group standard be implemented?
Start with one or two sites, write the requirement in performance terms, test whether the documentation format works in practice, and then extend it with a stated transition for existing stock and garments. Implementation succeeds when the field documents are usable and the change is explained to supervisors, and it fails when a template is issued without the process behind it.
Writing a group standard for protective clothing?
Send the hazard families, the sites involved and the record format you use. Shield Wings confirms the performance levels available, the specification language and the documentation each product line carries.
External references: 29 CFR 1910.132 hazard assessment and equipment selection, 29 CFR 1910 Subpart I, UK HSE personal protective equipment guidance, CCOHS PPE answers, CEN-CENELEC standards portal, Regulation (EU) 2016/425.
{“@type”:”FAQPage”,”@context”:”https://schema.org”,”mainEntity”:[{“@type”:”Question”,”name”:”What should be standardised across sites?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”The parts that should not vary: the minimum performance requirement for each hazard family, the documentation fields used to record what was issued, the care and retirement criteria, and the way requirements are expressed. Product models, size ranges and local features are better decided locally, because the conditions, the workforce and the supply routes differ between sites.”}},{“@type”:”Question”,”name”:”Does a group standard replace local risk assessments?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”No. The assessment is the employer’s and is specific to the tasks and conditions of that site, so a group standard sets a floor rather than a substitute. Where a site’s assessment identifies a hazard the group standard does not cover, that site specifies for it and records the reasoning; where a site’s assessment shows a lower requirement, the group floor still applies.”}},{“@type”:”Question”,”name”:”How does standardisation affect procurement?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”It makes requirements comparable, which is what allows volume to be consolidated and quotations to be assessed on the same basis. The gain is not only price: a specification written in performance terms can be met by more than one supplier, which keeps competition alive, and a common documentation format means a group can audit its sites against one template rather than several.”}},{“@type”:”Question”,”name”:”What is the biggest risk in a group standard?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Setting the requirement at the level of the most hazardous site and applying it everywhere. That inflates cost and reduces comfort in low-hazard locations, and it often leads to local deviations that are not recorded. The more durable model is a floor that applies everywhere, with additional requirements added by the sites that need them.”}},{“@type”:”Question”,”name”:”How should a group standard be implemented?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Start with one or two sites, write the requirement in performance terms, test whether the documentation format works in practice, and then extend it with a stated transition for existing stock and garments. Implementation succeeds when the field documents are usable and the change is explained to supervisors, and it fails when a template is issued without the process behind it.”}}]}