Before the First Call: A Tabletop Rehearsal for Standards-Led Recall Readiness
Photo: WorldSkills UK, CC BY 2.0, via Wikimedia Commons
The rehearsal that exposes the standard
Most recall preparations rehearse the statement. They draft the holding line, agree who speaks to the trade press and identify the customer services team who will field calls. All of that matters. But a recall is first a test of the standard: whether the batch can be traced, whether the non-conformance can be characterised against the clause, whether the supplier notification path is live and whether the customer receives a technically defensible message rather than a reassuring one.
For UK manufacturers, the tabletop exercise is therefore not a communications drill with engineering invited along. It is a standards exercise with communications as one of its outputs. The distinction is important. A well-rehearsed recall does not begin with the press office; it begins with the evidence that proves what was made, to which revision, from which supplier and against which conformity route.
Setting the room
The rehearsal works best as a half-day session, away from the day job, with a facilitator who is not the quality manager. Invite a cross-section: production, quality, engineering, procurement, customer service, legal or contracts, and a senior decision-maker with authority to stop supply. Bring the standards file, the traceability system, the supplier approval records and a live product recall procedure. Do not bring a scripted answer. The point is to find the gaps before a market surveillance authority or a customer does.
The scenario should be plausible and specific: a batch of components has been found non-conforming against a dimensional or performance clause after despatch. Some product is still in the warehouse; some is with a distributor; some may be installed. The facilitator reveals the scenario in stages, not all at once, so that the room must request information rather than receive it.
Session one: traceability under pressure
The first hour tests the record, not the response. Ask the room to reconstruct the batch lineage: raw material or sub-assembly source, goods-in inspection, production route, calibration status of test equipment, final release and despatch. The facilitator should ask for the evidence in the order a regulator or customer would ask for it, and should note where the room relies on memory rather than record.
Common gaps surface quickly. A batch number may exist in the enterprise system but not on the despatch paperwork. A supplier declaration may be filed against the purchase order but not against the revision actually used. A test record may show a pass without linking to the specification against which it was judged. These are standards-file defects, not administrative ones. The follow-up action is not a new database; it is a correction to the traceability clause in the procedure and a verification that the correction has been made.
Session two: decision rights and thresholds
The second session asks who decides. When does a non-conformance become a containment action, a stop-supply instruction or a recall? Who informs the board? Who contacts the market surveillance authority or Trading Standards, and on what advice? Who owns the technical statement that accompanies the customer notification?
The facilitator should test the uncomfortable boundary: a senior manager who wants to delay notification pending further tests, and an engineer who believes the clause has been breached. The rehearsal should not resolve the fictional dispute; it should reveal whether the procedure resolves it. If the answer depends on who is in the room, the standards file needs a decision-rights annex. If the answer depends on a threshold that is not written down, the threshold needs to be written down.
Session three: supplier notification and flow-down
The third session turns upstream. Which suppliers must be told, in what order and with what technical content? Does the purchase order contain a flow-down clause that requires the supplier to notify the manufacturer of a change or non-conformance? Can the supplier trace the affected material to the same batch? Does the supplier approval record show when that supplier was last verified against the relevant standard?
The facilitator should ask for the notification to be drafted in the room, not after it. The draft need not be sent, but it should expose whether the manufacturer can state the clause, the batch and the requested action without hedging. A supplier notification that says “please investigate” is weaker than one that says “this batch is non-conforming against clause X; confirm containment by date Y.”
Session four: customer communication with technical integrity
The final session tests the outward message. Customer service should explain what the customer needs to do; engineering should supply the technical basis; contracts should confirm the notification route. The facilitator should challenge any statement that cannot be supported by the standards file. “Safe” is not a technical term unless it is defined against a clause. “No risk” is not a statement a manufacturer can make on behalf of an installed product without evidence.
The output is a short, plain-language customer notice with a technical annex. The notice should identify the product, the batch, the non-conformance and the action required. The annex should cite the standard or specification, the test or inspection evidence and the contact for technical queries. This is not a legal drafting exercise; it is a standards communication exercise.
Facilitator notes
Keep the pace brisk and the challenge evidence-led. Do not allow the room to redesign the product or relitigate the clause. Capture every gap on a flip chart under four headings: record, decision, supplier and message. At the end of each session, ask one question: what would we have to change in the standards file to make this session unnecessary next time?
Avoid blame. The purpose is to find the weak link before it is tested by an actual recall. A tabletop that ends with a list of individuals at fault has failed; one that ends with a list of controllable actions has succeeded.
Closing the loop
Within five working days, convert the flip-chart gaps into actions with owners and dates. Update the recall procedure, the traceability clause and the supplier approval record. Add the rehearsal to the standards file as a controlled record, with the scenario, attendees, findings and actions. Schedule the next rehearsal before the next revision cycle, and use a different scenario so that the room cannot rely on the previous answer.
The recall you rehearse is not the recall you will face. But the standards discipline you rehearse is the one you will rely on when the first call comes. BEMSC members can use this protocol as a starting point and adapt it to their own sector and certification route.