How mid-sized manufacturers can leapfrog in quality and food safety.
Why the spreadsheet-and-shared-drive patchwork strains under 2026’s outbreaks, recalls and standard changes, what leapfrogging really means, and the five foundations to get right first.
On this page
- Why do so many mid-sized plants still run quality on a patchwork?
- What changed this year?
- How do you know if your patchwork will hold up?
- What does leapfrogging actually mean?
- What five foundations does every plant need?
- Why does the production floor remain the source of truth?
- Where should a plant start?
- How CERTI helps
- FAQs
Why do so many mid-sized plants still run quality on a patchwork?
Because the software was never built for them. The big quality systems cost too much, took months to roll out, and assumed ten sites and an IT department. So quality teams built their own: spreadsheets, paper records, shared drives, and the knowledge of a few experienced employees.
These approaches can support compliance, and plenty of these plants pass their audits every year. But fragmented information makes it harder to spot trends, retrieve evidence, and act quickly when something goes wrong. As supplier networks grow and expectations rise, quality teams spend too much time finding information and too little time preventing problems. Passing an audit matters, but it is not the same as having a resilient food safety system that keeps improving.
What changed this year?
2026 has tested that patchwork from several directions at once.
- Outbreaks are harder to trace. The US recorded 15,716 lab-confirmed Cyclospora cases acquired since May 1, as of CDC's August 18 update, against 1,180 for the same period in 2025 (Centers for Disease Control and Prevention [CDC], 2026a, as cited in HortiDaily, 2026). The largest cluster was traced to processed iceberg lettuce grown in central Mexico (HortiDaily, 2026). The CDC noted how hard sources are to identify for this parasite (CDC, 2026b). For a manufacturer, the lesson is simple: when an ingredient is suspected, you need to know within hours which of your lots used it.
- Small deviations become big recalls. On October 17, Kayem Foods recalled more than 1.5 million pounds of ready-to-eat meat and poultry after products stored in a warehouse cooler experienced temperature deviations (Food Safety News, 2026). The firm's investigation started from a retail customer's complaint about warm product on delivery, and the production window ran from March 31 to October 7. No illnesses were reported (Food Safety News, 2026). It's a reminder that a complaint is only useful if it links quickly to the batch, the storage record, and everything else that shared them.
- Allergens now lead US recalls. BRCGS's Recalls: A Review of 2025 found global food recalls rose 5% last year, and undeclared allergens accounted for 43% of US recalls, overtaking microbiological causes (BRCGS, 2026a, as cited in Food & Drink Technology, 2026). Most of those start as a mismatch between a specification, a recipe change, and a label.
- The standards keep moving. BRCGS updated its standards to meet GFSI's 2024 benchmarking requirements, with changes applying to audits from August 10, 2026 (BRCGS, 2026b). SQF Edition 10 audits begin no earlier than January 2, 2027 (Safe Quality Food Institute [SQFI], 2026). FSSC 22000 version 7 applies to all audits from May 1, 2027 (United Kingdom Accreditation Service [UKAS], 2026). And FSMA 204's traceability records are enforced from July 20, 2028 (U.S. Food and Drug Administration [FDA], n.d.); FDA held a public meeting on lot-level traceability on November 6 (FDA, 2026).
- Regulators are using data too. FDA is shifting more routine domestic inspections to state partners and working on AI models to predict foodborne illness risk and flag high-risk imports (Keller and Heckman LLP, 2026).
Meanwhile, quality teams are no bigger than they were. Every hour spent pulling records together is an hour not spent improving anything.
How do you know if your patchwork will hold up?
Try this before an auditor, an inspector, or a recall does. Pick one product, one line, one day from last month. Then pull:
- The receiving record and supplier certificate for each ingredient
- The storage and temperature records for where it was held
- The line checks and sanitation records for that shift
- The training record for the person running the line
- Any complaint, deviation, or corrective action that touched that batch
Time how long it takes, and note every point where the answer is "ask Mara" or "it's in the other folder." Those are the points where the patchwork depends on one person's memory and where an auditor, or a recall, will find it.
What does leapfrogging actually mean?
It doesn't mean buying the largest enterprise platform you can afford. It means choosing practical, scalable tools that connect your existing processes and make reliable information available when people need it.
In practice, that looks like this:
- Records connect. A customer complaint links to the finished-product lot, the production records, the ingredient suppliers, and the related corrective action. When an ingredient is under suspicion, as with this summer's lettuce, you can follow the trail in minutes instead of days.
- Checks are captured when they happen, on the line or in the cooler, not typed up at the end of the week. A reading outside the limit opens a corrective action straight away.
- Changes are followed through. When a supplier changes a formulation, the tool shows every specification, allergen assessment, and label it touches. That is where many of the allergen recalls BRCGS counted begin (BRCGS, 2026a).
- The legwork is done for you, and a qualified person decides. AI-enabled tools can help retrieve documents, flag missing or inconsistent supplier information, summarize complaint trends, or prepare a draft root-cause investigation for review.
The distinction matters. AI can support analysis and documentation, but it cannot on its own establish that a product is safe, validate a critical control, approve a deviation, or replace an authorized release decision. Its outputs must be checked against source records and the requirements that apply. So the test for any tool is simple: can it show you where each finding came from?
What five foundations does every plant need?
In our experience, these projects rarely fail because of the software. They fail because the foundations weren't in place. Whatever you choose, get these five right.
- Assess before automating. Map your current processes, risks, data quality, and regulatory obligations: FDA or USDA requirements, HACCP or FSMA preventive controls, and your certification scheme (SQF, BRCGS, or FSSC 22000), including which version your next audit will use. With Edition 10, FSSC v7 and FSMA 204 all due by mid-2028, plan the order deliberately. Prioritize the biggest bottlenecks rather than digitizing every form at once. The one-day test above is a good start.
- Keep qualified people accountable. Assign competent, trained people at the facility to oversee implementation, verify records, investigate exceptions, and work with auditors and inspectors. With more inspections moving to state agencies (Keller and Heckman LLP, 2026), that inspector may be a new face. SQF practitioners, preventive controls qualified individuals (PCQIs), HACCP team members, and other designated experts carry different responsibilities depending on the operation. Agree those responsibilities in writing, including that the data stays with the company. Technology supports these roles; it does not take on their accountability.
- Make food safety everyone's responsibility. Quality cannot succeed in isolation. Procurement manages supplier specifications. Production follows and documents controls. Sanitation verifies cleaning. Maintenance and engineering protect equipment and hygienic design. Warehousing owns the storage records. Leadership provides resources and reinforces expectations. Name a project owner, involve department leaders early, and review progress regularly.
- Protect technical rigor and data integrity. Build in access controls, version history, traceability, record retention, and review and approval steps. Test AI-supported outputs for accuracy, completeness, confidentiality, and consistency with your approved procedures. Complex issues, such as pathogen trends, allergen cross-contact, process deviations, or root-cause analysis, still need the right scientific expertise and, where necessary, validation or verification.
- Measure improvement, not just adoption. Track a small set of meaningful indicators: overdue CAPAs, repeat deviations, complaint rates, supplier document compliance, environmental monitoring trends, how quickly records are reviewed, and how long it takes to retrieve audit evidence. Set a baseline, assign owners, and use the results to improve processes, not just to fill a dashboard.
Why does the production floor remain the source of truth?
No software can replace observing a changeover, speaking with operators, checking allergen segregation, or confirming that sanitation works in real conditions. That's still where food safety is won or lost, and it's where auditors increasingly look. Under Edition 10, sites need a documented plan for assessing food safety culture, and an auditor may well ask an operator what it means in practice. Digital records should make floor work more visible and actionable, not turn food safety into a desk exercise. Food safety culture grows when employees understand why controls matter, feel able to raise concerns, and see leadership respond. That matters as much to successful modernization as any technical feature.
Where should a plant start?
Start small, prove value, and scale deliberately. Choose a workflow such as complaints, supplier approvals, CAPA, or document control. Given this year's recalls, complaint-to-batch tracing and allergen change control are strong candidates. Define what success looks like, pilot it with the people who use it, verify the outputs, and expand only once the process works reliably.
The opportunity for mid-sized manufacturers is not to imitate yesterday's large-company systems. It is to build a connected, risk-based, people-led approach that fits today's operation and can grow with tomorrow's demands.
The goal is not more automation. Technology can accelerate food safety management, but competent people, effective processes, and organizational accountability are what make it successful.
How CERTI helps
CERTI is an AI-native quality platform for food and packaging manufacturers, built for exactly this kind of plant.
- It starts from what you already have. CERTI reads your existing drives, spreadsheets, and documents as they are. No migration, no re-templating.
- It maps them clause by clause to the standards you're certified to, including SQF Edition 10, BRCGS, and FSSC 22000, and to your customers' specifications, and shows the gaps.
- Every finding shows its source, so your team can check it against the record instead of taking it on trust.
- Nothing is filed without a named person's approval. CERTI drafts the corrective action, the revised procedure, or the evidence pack. Your team decides.
Want to see where you stand? Send us one procedure, and we'll show you which Edition 10 requirements it covers and what's missing before you commit to anything. Interested? Book a demo.
See it automated GFSI Compliance Your existing documents mapped clause by clause to your standard, with every gap shown and every finding linked to its source. See CERTI do this →
FAQs
What does "leapfrogging" mean in food safety?
Skipping the heavy, slow-to-install quality software that large manufacturers adopted years ago, and moving straight to practical tools that connect a plant's existing records and take on routine work for qualified people to review and approve.
Do we have to replace our spreadsheets and shared drives?
Not with every tool. Some systems require you to move your records in before they're useful. Others, like CERTI, work on the files you already have. Ask any vendor what happens to your existing records on day one.
Which standard changes are coming, and when?
BRCGS changes for GFSI's 2024 benchmarking requirements apply to audits from August 10, 2026 (BRCGS, 2026b). SQF Edition 10 audits begin no earlier than January 2, 2027 (SQFI, 2026). FSSC 22000 version 7 applies to all audits from May 1, 2027 (UKAS, 2026). FSMA 204 traceability records are enforced from July 20, 2028 (FDA, n.d.). Confirm your own audit dates with your certification body.
Do we need to renumber our procedures for SQF Edition 10?
SQFI doesn't require your procedures to follow code numbering (SQFI, n.d.). If your documents cite SQF clause numbers, those references will need updating.
What's the most common cause of US food recalls now?
Undeclared allergens: 43% of US recalls in 2025 (BRCGS, 2026a).
Can AI replace our SQF practitioner or PCQI?
No. AI can help retrieve records, flag gaps, and draft documents, but it can't establish that a product is safe, approve a deviation, or release a product. A qualified person has to verify the records and stand with the auditor or inspector.
How do we know if a new system is working?
Set a baseline before you start, then track a few indicators such as overdue CAPAs, repeat deviations, complaint rates, and how long it takes to retrieve audit evidence. If those don't improve, the system isn't working yet, however many people log in.
What's the first step?
Run the one-product, one-line, one-day test above. Where it breaks is where to start.
About our co-author
Dr. Rob R. Unal
Dr. Rob R. Unal is an accomplished food safety and quality assurance executive with a Ph.D. in food microbiology and extensive leadership experience across the food and beverage industry, specializing in regulatory compliance, quality management systems, and operational excellence. He is passionate about advancing food safety through scientific innovation, strategic leadership, and artificial intelligence to drive continuous improvement, reduce risks, and strengthen organizational performance.
References
- BRCGS. (2026a). Recalls: A review of 2025 [Report].
- BRCGS. (2026b). Important update: BRCGS alignment with GFSI Benchmarking Requirements 2024. https://www.brcgs.com/about-brcgs/news/2026/important-update-brcgs-alignment-with-gfsi-benchmarking-requirements-2024/
- Centers for Disease Control and Prevention. (2026a). Cyclosporiasis: Cases. https://cdc.gov/cyclosporiasis/cases/index.html
- Centers for Disease Control and Prevention. (2026b). Domestically acquired cyclosporiasis, 2026 [Health Alert Network notice]. https://cdc.gov/han/php/notices/han00531.html
- Food & Drink Technology. (2026, March 3). Allergens and pathogens surge as global supply chain pressures mount. https://www.foodanddrinktechnology.com/news/64778/allergens-and-pathogens-surge-as-global-supply-chain-pressures-mount/
- Food Safety News. (2026, October 17). More than 1.5 million pounds of hot dogs, bacon, sausage, turkey breasts and more meat products of various brands recalled. https://www.foodsafetynews.com/2026/10/more-than-1-5-million-pounds-of-hot-dogs-bacon-sausage-turkey-breasts-and-more-meat-products-of-various-brands-recalled/
- HortiDaily. (2026, August 24). U.S. Cyclospora cases reach 15,716 as lettuce outbreak continues. https://www.hortidaily.com/article/9865484/u-s-cyclospora-cases-reach-15-716-as-lettuce-outbreak-continues/
- Keller and Heckman LLP. (2026, July 29). FDA continues shift of inspections to states and development of AI tools. The National Law Review. https://natlawreview.com/article/fda-continues-shift-inspections-states-and-development-ai-tools
- Safe Quality Food Institute. (n.d.). Edition 10 FAQ. Retrieved November 13, 2026, from https://www.sqfi.com/the-sqf-code/comply-with-the-code/edition-10-faq
- Safe Quality Food Institute. (2026, March 3). How to get your site ready for SQF Edition 10 before the 2027 deadline. https://www.sqfi.com/news/blog/view/sqfi-blog/2026/03/03/how-to-get-your-site-ready-for-sqf-edition-10-before-the-2027-deadline
- United Kingdom Accreditation Service. (2026, August 27). FSSC 22000 v7 transition [Technical bulletin]. https://www.ukas.com/resources/technical-bulletins/fssc-22000-v7-transition/
- U.S. Food and Drug Administration. (n.d.). FSMA final rule on requirements for additional traceability records for certain foods. Retrieved November 13, 2026, from https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods
- U.S. Food and Drug Administration. (2026). FDA public meeting: Challenges and solutions for lot-level food traceability [Public meeting, November 6, 2026]. https://www.fda.gov/food/workshops-meetings-webinars-food-and-dietary-supplements/fda-public-meeting-challenges-and-solutions-lot-level-food-traceability-11062026