Skip to main content
SKYGN
Free tools

Free tool · Recall

Recall-readiness self-assessment

Seventeen yes / partly / no questions about lot coding, records, tracing speed, your recall plan, and practice. You get a weighted score, a breakdown by area, and the fixes to make first, ready to print or save as a PDF.

No login. Runs in your browser. Nothing is saved or sent.

Lot coding

  1. Every incoming ingredient and packaging receipt is recorded with the supplier's lot code.
  2. Every production batch gets its own lot code that is printed on the finished package.

Records

  1. For each batch you record which ingredient lots were actually used, not just which recipe was run.
  2. Every outbound shipment records which finished lots went to which customer, with quantities.
  3. Rework, repacks, and samples are recorded as their own lot movements.
  4. Receiving, production, and shipping records live in one system rather than separate spreadsheets or paper logs.

Tracing speed

  1. Starting from one ingredient lot, you can list every customer who received product containing it.
  2. Starting from one finished lot, you can list every ingredient lot and supplier that went into it.
  3. You could produce that customer list, with quantities, within a few hours (well inside 24).
  4. You can place a suspect lot on hold so it cannot be picked or shipped while you investigate.

Recall plan & team

  1. You have a written recall plan that has been reviewed in the last 12 months.
  2. A recall team with named people (and backups) is assigned, with after-hours contact details.
  3. Customer and supplier contact lists for recall notification are current.
  4. Notification templates (customer notice, press release, regulator contact) are drafted in advance.

Practice

  1. You have run a mock recall in the last 12 months.
  2. Your last mock recall reconciled quantities (made = shipped + on hand + scrapped) to within a small tolerance.
  3. Findings from the last drill were assigned owners and due dates, and closed out.

Your recall-readiness score

0 of 17 questions answered. Unanswered questions are left out of the score.

Answer the questions above to see your score.

How it is calculated

  • Each question has a weight from 1 to 3 based on how much it affects your ability to find and stop affected product. Lot capture and tracing speed carry the most weight.
  • Yes earns full credit, Partly earns half, No earns none. Unanswered questions are left out of the score.
  • Score = earned points / possible points for the questions you answered, as a percentage. 85 or more is Drill-ready, 60 to 84 is Gaps to close, below 60 is At risk.
  • The fix list is ordered by weight, then by No before Partly.

Doing this every day in Skygn

On Skygn's recall screen in the Quality module you pick a lot, ingredient or finished good, and see every posted customer shipment it reached, including finished goods built from it through multi-level production, with customer, quantity, date, sales order, and tracking number. The same view traces back to source lots and suppliers, and the shipment list exports to CSV.

Lot statuses are configurable, and pick lists only allocate lots whose status allows shipping, so a quarantine status keeps a suspect lot off new picks. CAPA records and supplier corrective action requests (SCARs) hold the follow-up. Skygn does not run the drill, write the notices, or certify compliance; that stays with your team and your recall plan.

Read the full guide: How to run a mock recall: a step-by-step guide for food brands.

Frequently asked questions

How fast should a trace be?
Under FSMA 204, covered firms must provide traceability records within 24 hours of an FDA request (check the rule and its compliance date for how it applies to you), and a recall decision rarely waits that long. A forward trace from one lot to a customer list should take hours, not days.
Is this a FSMA compliance audit?
No. It is a self-assessment of general recall and traceability practice. It does not determine whether you comply with FSMA, the Food Traceability Rule, or any other regulation.
How often should we run a mock recall?
At least once a year is a common expectation in food safety schemes and customer audits, and more often after a system change. Use a real lot and time it end to end.
Are my answers stored?
No. Answers stay in your browser and are not saved or sent anywhere. Print the result or save it as a PDF to keep a copy.

Stop recalculating it in a spreadsheet

Skygn is the ERP for food & beverage and CPG brands: lots and expiry, recipes and costing, quality and recall, and trade spend in one system. One plan with every module, and a 14-day free trial.