A recall notice arrives, and the first question sounds simple: do we have the affected product? Answering it may involve purchasing records, storage locations, trays already distributed, equipment in another department, and people working on different shifts.
A sterile processing mock recall drill lets a team practice that information path before a real notice makes it urgent. The most useful exercise tests whether staff can connect a specific notice to specific items, communicate their status, and account for what remains unresolved.
This article provides an original tabletop exercise for SPD leaders. It is a planning suggestion, not an FDA-required drill format or a substitute for the facility's recall policy. Use fictional records, obtain the appropriate local approval, and keep the exercise clearly separate from clinical operations.
First, distinguish a product recall from a processing recall
A manufacturer product recall begins with a notice about a device or product problem. An internal processing recall may arise from a concern about the facility's own processing activity. Both require reliable information, but the trigger, scope, and governing instructions can differ.
The FDA explains that medical device recalls can involve correction or removal. A recall does not always mean returning a product. The actual notice may require an inspection, repair, labeling change, or another specified action. Read the notice rather than deciding what to do from the word “recall” alone.
For the exercise below, choose a fictional manufacturer notice involving a limited group of reusable devices. Do not combine it with a failed sterilization-monitoring scenario. A narrow starting point makes the information and decision gaps easier to identify.
Define the question the drill will answer
A useful objective is: can the team use the notice and available records to identify potentially affected items and explain the status of each one? That objective tests traceability and communication without pretending to validate the whole recall program.
Write down the boundaries. Specify whether the exercise ends after identification, after simulated containment, or after a documented reconciliation. Explain that participants must not contact patients, submit reports, move clinical inventory, or send vendor communications as part of the tabletop exercise.
Assign a facilitator who can clarify the fictional facts and stop the exercise if it creates confusion. Name a separate operational contact in case participants discover a real concern. A real safety question should enter the facility's actual response process, not wait for the exercise debrief.
Build a small fictional inventory
Use an invented product name, identifiers, and locations that cannot be mistaken for a current safety notice. Mark every page and message as an exercise. Include enough variation to require careful matching, but avoid a complicated puzzle that rewards guessing.
For example, create a fictional device family called Training Instrument A with two model variants and a defined affected lot. Place sample records in simulated storage, a case cart, a repair location, and a completed-use category. These are training records only; no actual devices need to move.
Prepare an answer key for the facilitator. It should show the intended scope and explain any deliberate uncertainty. A participant who flags missing information should receive credit for identifying it, even when the answer key eventually supplies the missing detail.
Make the fictional notice precise
The notice should state the affected identifiers, the issue being simulated, and the exercise-only action requested. It should also provide an invented reference number and a named internal role for questions. Avoid copying a live recall letter into an exercise without clear separation and review.
Decide whether your scenario requires simulated removal from availability or a simulated correction. Keep that choice consistent throughout the exercise. If the goal is basic traceability, do not add complex clinical risk language that participants are not being asked to evaluate.
Ask an appropriate colleague to review the exercise packet before use. They should be able to tell which records are affected and which are outside scope using only the supplied information. If the facilitator must explain every identifier verbally, the packet needs revision.
Invite the people who own the handoffs
SPD rarely controls every part of a product's path. For a locally approved exercise, consider the relevant roles in purchasing, the operating room, other receiving departments, quality, infection prevention, and clinical engineering when equipment is involved.
Invite people because they own a step, not because the meeting needs a large attendance list. A focused exercise can begin with a few participants and document where additional input is required. Do not assume one supervisor can answer for every department's records or authority.
Include a perspective from outside the most visible shift. A notice received when the regular coordinator is unavailable tests different weaknesses than a daytime meeting. You can explore that scenario in discussion without sending a surprise alert into live operations.
Use a simple reconciliation table
This original table tracks the fictional items through the exercise. Adapt the fields to the local process rather than treating it as an official recall form.
| Exercise record | Initial location | Scope assessment | Simulated status | Remaining question |
|---|---|---|---|---|
| Training item A1 | Storage | Identifiers match | Simulated hold recorded | Who confirms the status in the receiving system? |
| Training item A2 | Case cart | Identifiers match | Receiving team contacted in the exercise | Has the team acknowledged the message? |
| Training item B1 | Repair record | Similar name, different model | Outside the fictional notice's scope | What evidence supports exclusion? |
| Training item A3 | Completed-use record | Identifiers match | Referred to the designated clinical review role in discussion | Who owns the next decision? |
| Training item A4 | Location unresolved | Match not yet confirmed | Open investigation in the exercise | Which record or person can resolve identity? |
The table should make uncertainty visible. Do not mark an item “complete” merely because someone sent an email or searched one location. Record what was established and what remains open.
Run the first pass without rescuing every pause
Give participants the fictional notice and ask them to describe their next actions using the actual policy as a reference. Let them identify which records they would need and which roles they would contact. The facilitator can provide the corresponding simulated records when requested.
Record pauses that reveal a process gap: an unclear owner, an inaccessible reference, a missing backup contact, or a confusing item description. Do not immediately explain away every delay. Those observations are the reason for the exercise.
At the same time, keep the discussion respectful. A drill should not become a public test of one person's memory. If a participant says the policy is difficult to locate, examine that access problem. Telling them to remember the document better will not help the next unfamiliar staff member.
Check how the team excludes similar items
Finding an obvious match is only part of the task. Ask participants to explain why a similar item is outside the fictional notice's scope. The explanation should point to the supplied identifiers or other applicable criteria, rather than a familiar name or location.
This step can uncover an inventory problem. Perhaps the purchasing record includes the identifier but the local tracking view uses only a nickname. Document that mismatch as a retrieval issue. Do not expand or narrow a real recall's scope based on this example.
If the simulated record lacks enough detail to decide, keep it unresolved and identify the next source to consult. A table that preserves uncertainty is more useful than a completed table built from assumptions. Accuracy of scope matters more than making every row look finished.
Practice acknowledgment, not just notification
A sent message proves that someone attempted communication. It does not establish that the receiving team understood the affected items or changed their status. In the drill, ask the receiving role to repeat the action and identify the records to which it applies.
Use an exercise-only communication channel or a facilitator-mediated exchange. Never send an unlabeled mock recall through a channel where staff could act on it as a real event. Keep the mock notice's wording unmistakable even if a message is forwarded without its original context.
A useful observation is whether the receiving role can explain the next action without another long discussion. If not, improve the message around identity, required action, ownership, and acknowledgment. A shorter, precise message can work better than forwarding a large packet without direction.
Include an unresolved location without turning it into a hunt
Add one fictional item whose last recorded location does not establish its current status. Ask which records or people could narrow the gap. This tests the team's method for investigation, not its ability to guess the facilitator's intended answer.
Have the participant distinguish “not found in the first location” from “not present anywhere in the facility.” Those statements have different meanings. A real response needs accurate descriptions of the search completed and the information still missing.
The facilitator can then provide an additional simulated record, such as a transfer acknowledgment. Observe whether participants update the earlier status and preserve the reason for the change. The exercise should teach a traceable progression from uncertainty to evidence, rather than a sequence of overwritten guesses.
Keep clinical and reporting decisions with their owners
A completed-use record can be included to test whether staff know where to escalate it. It should not ask SPD participants to decide patient harm, patient notification, or legal reporting obligations from a fictional timeline.
The FDA's guidance on reporting reprocessing problems includes reporting resources and distinguishes user-facility reporting responsibilities from voluntary reporting. In an actual event, involve the designated clinical, quality, and reporting personnel through the facility's process.
For the drill, record the role and information needed for that handoff. Stop at the agreed boundary. You can learn whether the escalation path is clear without generating a real report, using patient records, or reaching a simulated medical conclusion that someone later mistakes for guidance.
Test the difference between an answer and closure
After participants reconcile the fictional inventory, ask what would support closing the exercise record. An answer such as “all messages sent” leaves important questions open. The record should explain the disposition of the simulated matches and the owner of any remaining uncertainty.
Closure in this educational exercise is not the same as termination of a manufacturer's recall. Avoid using regulatory terms loosely in internal paperwork. The exercise only demonstrates what participants did with the fictional scenario and what needs improvement locally.
Ask a person who did not participate to read the final table. Can they identify which items matched, which were excluded, and why? Can they tell which action was only simulated? This independent reading is a practical way to find ambiguity before the exercise materials are filed away.
Measure retrieval and clarity without rewarding shortcuts
You may choose to record how long it takes to locate a policy, identify the responsible contact, or reconcile a fictional item. If you do, describe these as local exercise observations. They are not industry benchmarks or evidence that the facility would perform identically during a real recall.
Pair any timing observation with an accuracy check. A fast answer based on the wrong model is not better than a slower answer that correctly identifies missing evidence. Do not turn the drill into a contest for the fewest open rows.
Useful measures can be very simple: whether the notice matched the record, whether the receiving role acknowledged the action, and whether unresolved items had owners. Choose measures that answer the drill's objective rather than creating a large dashboard for a small exercise.
Turn the debrief into a short repair list
Start by asking what made the work easier. Perhaps a controlled document was easy to locate or a cross-department contact list was accurate. Preserve those strengths when planning improvements. A debrief that records only failures can miss the systems people relied on successfully.
Then select a few gaps with clear owners. Replace “improve communication” with a concrete action such as clarifying the backup contact in an existing policy. Replace “fix inventory” with a defined question about which identifier is missing from a particular view.
For each action, write what evidence will show completion. Updating a document may be necessary, but a brief repeat exercise can reveal whether the revision is understandable. Keep the follow-up proportionate to the problem and within the facility's change-control process.
Repeat one failed handoff, not the whole performance
Suppose the team found the affected fictional items but could not establish whether the receiving department understood the simulated hold. The next exercise can focus on that communication step. There is no need to repeat every earlier activity just to demonstrate that a message improved.
Use a different fictional identifier so participants must read the revised message rather than remember the earlier answer. Ask for acknowledgment and a clear explanation of the simulated status. Record what remains confusing and refine the process through the appropriate owner.
This approach gives the team a manageable next step. It also keeps the exercise from becoming paperwork that is completed once and forgotten. The value lies in repairing a specific gap and showing that the repair works under the conditions you actually tested.
Frequently asked questions
Is a mock recall drill the same as a real product recall?
No. A mock recall is a controlled learning exercise using clearly identified simulated information. A real recall requires action under the actual notice, applicable instructions, and the facility's response process.
Does every medical device recall require returning the product?
No. A recall may involve a correction or removal, and the required action depends on the specific notice. Do not infer the action from the word recall alone.
Should a tabletop drill use real patient records?
Use fictional records for this exercise. Testing an escalation path does not require patient information, and any separate review of real clinical records belongs in an authorized facility process.
What if an item cannot be located during the exercise?
Keep its simulated status unresolved, document the search or record review completed, and assign the next investigation step. Do not mark it complete because one location has been checked.
Does completing this drill prove regulatory compliance?
No. It provides evidence about a limited exercise and the gaps observed. It does not certify compliance, replace the facility's recall program, or predict performance in every real event.
Connect the exercise to everyday leadership
A drill works best when people can raise an incomplete record without embarrassment. Read more about building a culture of quality in sterile processing and use the exercise to make that expectation concrete.
Choose one traceability question to test
Start with a fictional notice and a small set of records. Ask whether another person can follow the evidence from the affected identifier to the final simulated status. If your team needs help reviewing SPD workflows and education needs, explore ATS consulting and bring that specific question to the conversation.
