Resource

What Happens When a Garment Fails Inspection?

6 min read · March 2026

A structural jacket arrives on the inspection table. The inspector finds a moisture barrier defect. What happens next — and how quickly — determines whether a firefighter goes on shift tomorrow with a compliant set or without one.

The scenario

Inspector Priya Kaur is working through a batch of structural jackets that came off the wash hall 90 minutes ago. She scans garment VX-041872 — a Bristol Uniforms structural jacket, size L, allocated to wearer Dave Hendricks at Greater Manchester FRS. The guided inspection checklist loads automatically based on the product type.

Priya works through the checklist: outer shell condition, seam integrity, reflective trim adhesion, zip function, hook-and-loop closure. Each item is assessed and recorded. Then she reaches the moisture barrier.

Step 1: Hard fail detected

Priya identifies delamination on the moisture barrier at the left shoulder seam. She selects FAIL on the moisture barrier checklist item and records the location and extent of the defect.

The moisture barrier is a hard-fail item. In the compliance engine, hard-fail items are defined at the product-type level. A structural jacket has specific items that trigger immediate condemnation if they fail: moisture barrier integrity is one of them. There is no “minor defect” classification for a moisture barrier. It either passes or the garment is condemned.

Priya does not make this decision. The system makes it. The checklist item is configured as a hard-fail trigger, and the compliance rule fires automatically.

Step 2: Automatic condemnation

Compliance rule R-003 fires. The garment status changes to CONDEMNED. There is no confirmation dialog. No “are you sure?” prompt. No override button. A hard-fail on a critical item means the garment is withdrawn from service immediately.

This is a deliberate design decision. If an inspector can override a hard-fail condemnation, the condemnation is not automatic — it is advisory. An auditor reviewing your records needs to see that hard-fail condemnations happen without human discretion. The rule applied. The garment was condemned. The record is immutable.

Step 3: Condemnation certificate generated

The system generates a condemnation certificate immediately. The certificate contains: the garment UID VX-041872, the product type and manufacturer, every checklist item Priya assessed (not just the failed item), every measurement recorded, the inspector’s name and competency reference, the compliance rule that triggered the condemnation (R-003), the ISO 23616 clause reference, and the timestamp.

This certificate is a write-once record. It cannot be edited, amended, or deleted after generation. If a barrister asks about this garment three years from now, this certificate is the definitive record of what happened and why.

Step 4: Protection Engine fires

Within seconds, the Protection Engine runs its event-driven recheck. The condemnation of VX-041872 triggers a coverage recalculation for every wearer affected.

Dave Hendricks was entitled to two structural jackets. One is in service with him. The other — VX-041872 — has just been condemned. Dave now has one compliant structural jacket. His coverage status changes from GREEN to AMBER. If this were his only jacket, coverage would drop to RED: no compliant jackets, firefighter at risk of going on shift without protection.

Step 5: Buffer stock check

The system checks buffer stock for a size L structural jacket. There is one available in zone Z11, bin 14. It was inspected last week, is within wash life limits, and has a current compliance status.

If buffer stock were empty, the system would flag this as a critical shortfall. The operations manager would see it on the Command Centre dashboard, and the client would see the coverage gap in their portal. There is no hiding it and no delay in surfacing it.

Step 6: Replacement order created

A replacement order is created with URGENT priority. Dave’s next shift is at 06:00 tomorrow. The garment needs to arrive at his station before then.

The order specifies the replacement garment from buffer stock, the wearer, the station, and the delivery window. It is added to the emergency dispatch queue or the next scheduled route — whichever gets it there first.

Step 7: Delivery and coverage restored

The replacement jacket is delivered to Dave’s station. Proof of delivery is recorded. The logistics module confirms receipt. The garment is allocated to Dave in the system, and his coverage status returns to GREEN.

The client portal updates automatically. Dave’s station commander can see that the replacement was issued, when it was delivered, and that Dave’s entitlement is now complete. No phone calls. No emails chasing a status update. The record exists because the process generated it.

All of this happened automatically

Priya failed one checklist item. Everything else — the condemnation, the certificate, the coverage recheck, the replacement order — happened without anyone making a phone call, filling in a form, or opening a spreadsheet. Minutes, not days.

In a manual operation, this flow takes days. The inspector writes down the defect. Someone transfers it to a spreadsheet. The quality manager approves the condemnation. Someone checks the stockroom. Someone raises a purchase order. Someone arranges delivery. Someone updates the wearer record. Each handoff is a delay. Each delay is a shift where Dave goes on duty without a compliant set.

The only manual step in Vorrex is putting the replacement garment on the van.

See it on your data, or start with the checklist.

Either path works. Pick whichever fits where you are today.

Download ISO 23616 Checklist