I've never used a form for mock recalls (though I do admit liking the one that Dorothy87 posted). In the handful I've done over the years, I've always opted for having a good SOP/Program that outlines the steps we will take and then I document those steps being taken in a hand typed report/memo format. I write the scenario, document the time the recall team is notified, assembled, and then we run through what needs to occur while I document who is doing what at what time. It includes documenting the start and stop time of the traceback steps, documents who starts reaching out to the affected customers (listing the contact emails or phone numbers we would have used in a real scenario), who pulled the press release template and filled it out, who notified FDA, our CB, and GFSI contacts, etc.
At the end, we list out what was "found" in our investigation to perform a root cause and develop the corrective action. When I was primarily consulting, we had a couple companies actually change processing SOP's for real after a root cause from a mock recall exposed some gaps. So long as the steps to take are clearly outlined in your recall program, I've never been challenged for not having a specific form to fill out so long as the written report shows those SOP steps being followed.
I do generally like to have a form for documenting the traceability step: it's helpful because you might have lower level employees doing cycle counts of existing inventory or sorting through BOL's or something, and a form helps ensure they collect all of the relevant information.