Five Best Practices for Product Recalls
Here are five ways to prepare for the inevitable:
1. Create an R-team. Designate a recall task force of managers from sales, customer service, manufacturing and IT. Tap people from supplier relations, say, or transportation, as needed. Everyone should be trained in how to query each other’s core applications, and how their respective data meshes to tell the story of how a product went bad, the scope of the problem and where it lives inside the supply chain.
2. Study up. Read the investigative procedures of the CPSC, FDA and USDA to understand what data inspectors will request during a recall. IT should work with plant managers to figure out how quickly and completely they can supply the data.
3. Practice. Do a mock recall. Along with disasters and terrorist attacks, recalls are one of the risks the IT group at Procter & Gamble practices handling, says Steve David, former P&G CIO. Choose a batch number for a real group of products, he advises. Then, using supplier, manufacturing, distribution and transportation systems, run reports to try to account for what was made, shipped and received. How accurate were those practice reports? Where and when did manual work, such as questioning the plant manager in person or calling the trucking company, become necessary? How long did it all take?
4. Study the masters. Pharmaceutical and aerospace companies can trace the pedigree of their finished products back to the component level. They even know what the temperature in the factory was when the widget or pill was made. They can do this because federal regulations require that level of detail for public safety. Evaluate whether practices and procedures they follow could work for you.



