Hi Steve, yes I'm looking to document the effectiveness of the actual mock recall performed. I believe I've created a document that tracks the traceability of the product, but are there other areas of the exercise you want to review for continuous improvement? For example, the effectiveness of your team, your current program, steps, etc?
Great that you are taking a broader view of what an effective product recall is! Many companies conducting a product recall get fixated on retrieval rate as their objective when we know that retrieval rates for many products, particularly fast moving, short shelf life product will have a very low retrieval rate. Does that mean the recall is not effective? Not necessarily!
If you frame your objectives along the lines of managing consumer safety risk and reputation risk and restoring the business after the recall, you tend to have very different measures of success. In fact I am working with a client right now that had a major incident and the focus is actually on team management. They had all the right technical expertise and very smart people that really understood their business but they got so bogged down on the technical resolution that they forgot about what was really important - maintaining the long term interests of the business. They had the answers but weren't asking the right questions! Once they refocussed, they got clarity around what they needed to achieve and were able to better coordinate resources, get the right people working on the right things.
So when you said you are looking at effectiveness of your team and the processes you are absolutely on the right track. Testing your traceability is important but you can have great traceability and still get into a crisis!
If you are interested, I just posted this video on my YouTube channel on the 5 reasons that most "mock recalls" won't actually prepare your team to effectively manage a product recall. It has a link to additional free resources if you are interested.