Trust, Verification, and Cyclospora: What the Taylor Farms Inspection Gap Reveals About Agricultural Water Risk

‍Last week, news broke that Taylor Farms had gone seven years without a federal inspection. A gap that long can happen for all kinds of practical reasons — not enough funding, too few inspectors, shifting priorities, or simple logistical challenges inside the system. It could also reflect something less tangible, which is a deep, long‑standing confidence in Taylor Farms as a reliable operator, the kind of place regulators might have viewed as a “sure thing” — until it wasn’t.

‍This is where the theory of “trust but verify” stops being a catchphrase and starts becoming a real‑world necessity. When you’re dealing with something like Cyclospora — an organism that hangs around in the environment, shrugs off common sanitizers, and moves quietly through supply chains — you can’t rely on trust alone. Verification has to be consistent, predictable, and built into the system, not something that happens only when it’s convenient. This is where the risk mentality comes in- just because something hasn’t happened, doesn’t mean that it won’t. The possibility is there. 

‍That leads to the bigger question that many of you were probably thinking, because I know I was, and that is who is responsible for making sure the verification actually happens? Should Taylor Farms have raised their hand and asked for an inspection to show everything was in good shape as a show of integrity? Or should the FDA have found another way to check in — remote reviews, targeted sampling, risk‑based follow‑ups — even when traditional inspection schedules slipped?

‍The seven‑year gap makes one thing clear, and it’s that trust is helpful, but verification is what keeps the food system honest. When verification slips, risks like Cyclospora have room to move. When verification weakens, biological hazards step into the empty space and they spread across fields, water sources, and supply chains faster than most people realize.

‍The ties to this go far beyond the FDA. There’s a direct connection to supplier‑verification practices, EPA water‑safety regulations, USDA’s agricultural standards, and even LACF guidance for regulators reviewing post‑harvest commodities. This outbreak didn’t just raise questions about one inspection gap — it sparked a noticeable shift in posture across the entire system. Every agency and every part of the food ecosystem is now tightening its stance, reassessing assumptions, and looking more closely at how agricultural water risks are managed and verified.

‍In today’s blog, I’m going to tie a few things together that many industry leaders may not consciously connect but absolutely should. If the FDA is sharpening its regulatory posture around fresh‑cut produce, biological hazards, and risk analysis, then the natural question becomes when will the other agencies step their game up? I actually posted an article about this on LinkedIn last week highlighting past precedence, possible next steps, and the financial impact of it all.

‍The reality is that Taylor Farms went seven years without an FDA inspection because the agency’s risk‑based prioritization model pushed them further and further down the queue. That model is designed to funnel limited inspection resources toward facilities with repeated violations, emerging hazards, or unstable controls, however, when a plant has a long history of compliance, stable documentation, and no recent red flags, it gets labeled “low‑risk” and quietly deprioritized. When budgets tighten, when staffing fluctuates, and when risk scores aren’t recalibrated often enough, those low‑risk facilities can go years without in‑person oversight.

That gap is exactly why “trust but verify” must be a non‑negotiable principle in every supply chain. Trusting your suppliers, your processes, and your partners is important, but trusting without verifying is how gaps form, how hazards slip through, and how integrity erodes one step at a time. To keep you from living the nightmares I have in the industry, I’m going to break down what to do, what not to do, and how to build a step‑by‑step monitoring structure that actually protects your supply chain instead of simply documenting it. Integrity isn’t a value you declare; it’s a sequence of actions you repeat, verify, and reinforce until your entire chain reflects it.

Let’s begin!

Identifying Biological Hazards in Agricultural Water Systems

‍ 1. Define the Biological Hazard

‍ In this case, the biological hazard is Cyclospora. The organism spreads through contaminated water and fresh produce, and its oocysts are remarkably resilient. They withstand common sanitizers, persist in the environment, and survive long stretches of supply‑chain movement without losing infectivity. Agricultural settings can unintentionally support Cyclospora’s persistence when conditions like human sewage contamination, labor‑camp runoff, or weak sanitation practices allow oocysts to enter open water sources. Once they’re in the system, they can remain viable long enough to contaminate crops, irrigation water, and harvest environments. So once the biological hazard is identified, the proper controls can be deployed and implemented. That means strengthening agricultural hygiene practices, protecting water sources, verifying supplier sanitation programs, and applying targeted preventive controls that interrupt Cyclospora’s environmental and supply‑chain pathways.

‍2. Map All Agricultural Water Contact Points

‍To understand Cyclospora risk, you have to understand the process flow. Water touches produce at multiple points throughout the agricultural cycle — irrigation systems, spray applications, fertigation lines, harvest‑crew handwash stations, and post‑harvest rinsing, hydrocooling, and flume operations. Each of these points carries its own potential for contamination. That’s why every water touchpoint must be mapped, documented, and evaluated with care. When you know exactly where water enters the process, how it moves, and where it can pick up or carry hazards, you’re in a position to identify risks early and put the right controls in place.

3. Assess Agricultural Water Sources and Upstream Land Use

Surface water includes rivers, canals, and reservoirs which carry inherently higher risks. Cyclospora contamination often reflects what’s happening upstream such as nearby housing or labor camps, stressed sewage systems, flooding that stirs up protozoa (tiny parasites that survive in water and soil), shared water channels between farms, or areas where wildlife tends to gather. Groundwater is generally lower risk, but it isn’t immune, especially when wells are shallow, aging, or poorly maintained. Also, there is the need to know how to read and interpret water‑test reports and treatment records. Understanding what those results mean, and how they connect to real contamination pathways, is essential for making informed decisions about water safety and verifying that controls are actually working.

4. Review Water Treatment Documentation with Protozoa in Mind

Most water treatment programs are built around reducing bacteria, not protozoa and that’s why a proper review has to look beyond basic microbial claims. It should confirm that the treatment method in use — whether UV, filtration, ozone, or chlorination — is actually appropriate for the risks present. It should include validation studies that show the system can handle Cyclospora‑like oocysts, along with continuous monitoring logs, corrective‑action records, and proof that calibration and maintenance are being done on schedule. One practical tip is to keep monitoring logs that are simple, clear, and easy to maintain. This makes it easier to audit and speak to when describing your process. I also have a ready‑to‑use template available in my on‑demand document library on my website. Simplicity also helps when you’re determining when to deploy the chemical‑residue critical control point during risk analysis, because you can quickly see whether treatment performance is drifting, inconsistent, or showing signs that additional controls may be needed.

‍ 5. Evaluate Water Testing Protocols and Laboratory Methods

Cyclospora testing is specialized and sits outside standard microbial panels, which means strong programs have to be intentional about how they approach it. Seasonal sampling should align with rainfall patterns so results reflect real environmental shifts. qPCR methods (DNA‑based detection that identifies the organism with high sensitivity) are the preferred approach because they offer accuracy for protozoan targets. Testing should be performed by accredited laboratories with experience in protozoa analysis, and programs should include clear action thresholds with documented response plans. All testing strategies should reflect FDA’s agricultural water rule expectations and current outbreak trends, ensuring that verification keeps pace with the risks emerging in the field.

6. Environmental Monitoring Across Agricultural and Facility Zones

Environmental monitoring helps reveal how contamination moves through the supply chain, even when Cyclospora rarely shows up in facility swabs. Repeated positives in wash systems, seasonal spikes during monsoon or rainy periods, and patterns that match flooding or sewage overflow all point to water‑driven contamination routes. Environmental data tells the story of how hazards travel, where they gather strength, and which parts of the system are most vulnerable.

7, Validating Supplier Agricultural Practices and Field‑Level Hygiene

Supplier verification has to go beyond paperwork. Strong programs include field‑level assessments that look closely at worker hygiene, restroom placement, harvest‑crew sanitation, water‑system integrity, cross‑connection risks, soil‑amendment handling, and the way adjacent land use affects runoff. Many Cyclospora outbreaks trace back to human hygiene failures in agricultural settings, which is why verification must be grounded in what is actually happening in the field, not just what is written in a supplier’s documentation.

8. Assessing Facility Design for Water‑Driven Cross‑Contamination

Fresh‑cut operations depend on facility design that prevents contaminated water from moving across zones. Drainage patterns, pooling tendencies, wash‑line layout, water‑turnover rates, ice production, and ice‑storage practices all influence how water behaves inside the building. Raw‑to‑RTE (ready-to-eat) separation must be strong enough to compensate for the fact that fresh produce has no kill step. When water moves freely, contamination moves with it, so design choices become part of the food‑safety system.

9. Verifying Preventive Controls with Protozoa‑Specific Rigor

Preventive controls must be validated with Cyclospora in mind. Water‑treatment systems need protozoa‑specific evidence, supplier verification must reflect real agricultural conditions, hygienic zoning must prevent water‑driven movement, temperature control must support sanitation practices, and employee training must address the unique risks associated with protozoa. Generic microbial claims are not enough. Controls must be built and verified with the organism’s resilience and environmental behavior in view.

10. Documenting Hazard Identification with Agricultural Precision

The FDA increasingly evaluates the quality and completeness of documentation. Strong programs explicitly list Cyclospora in hazard analyses, include clear schematics of agricultural water systems, maintain seasonal risk assessments, preserve supplier‑verification evidence, and keep treatment‑validation reports organized and accessible. Precise documentation is your strongest defense during inspections and outbreak investigations because it shows not only what you did, but how you justified it and how you verified it over time.

Breathe easy, because chances are you’re already doing most of this work. You’ve been managing biological hazards for years, even if you weren’t thinking about Cyclospora specifically. The shift isn’t about reinventing your entire program. It’s about increasing posture — tightening the lens, sharpening documentation, and making sure your controls speak directly to all biological hazards that apply to your commodity.

That’s the heart of the new view, and it’s exactly what FDA expects: a clear understanding of how each hazard behaves, how it moves through your system, and how your controls are designed to stop it. When you frame your existing practices with that level of precision, you’re already aligned with where the industry is heading.

Now let’s look at the opposite!

What Not To Do When Reviewing Biological Hazards in Agricultural Commodities

Even strong food safety programs can unintentionally weaken their own hazard‑identification efforts when they rely on outdated assumptions or incomplete verification practices. These gaps create blind spots and they undermine the accuracy of agricultural water assessments. A few areas deserve a closer look.

1. Do not assume bacterial controls cover protozoa. Controls validated for E. coli or Salmonella do not automatically apply to Cyclospora. Protozoa behave differently, survive differently, and require their own validation data and treatment expectations. Know your hazards and how to properly apply their preventive control.

‍2. Do not rely solely on supplier declarations. A supplier simply saying their water is treated, safe, or monitored is not verification. Without documentation, validation studies, and field‑level observations, declarations become a false sense of security. All documents must be dated, and the acceptable age of those documents can range anywhere from one to five years depending on the commodity, the guarantee being made, and the soil base. It’s important to understand which timeframes apply to which materials, so you know exactly what evidence supports your supplier’s claims.

‍3. Do not ignore upstream land use. Most water contamination often begins upstream, in places like labor camps, sewage systems, housing developments, or shared canal networks. If upstream land use is not evaluated, the true source of contamination stays hidden.

‍4. Do not treat surface water as equivalent to groundwater. Surface water carries significantly higher biological risk. Water source type must be one of the first risk differentiators in any assessment.

‍ ‍5. Do not accept water‑treatment logs without context. Logs showing that a system is running or treatment is active are not enough. Without calibration records, corrective actions, and protozoa‑specific validation, logs can hide system failures. ‍

6. Do not assume seasonal trends are coincidental. Outbreaks and spikes often align with rainfall, flooding, or agricultural labor‑migration patterns. Seasonal patterns should guide sampling frequency and control adjustments.

7. Do not overlook human hygiene in field operations. Cyclospora is a human‑origin parasite, and it’s not the only one. Other human‑source parasites — including Giardia and Cryptosporidium — can enter agricultural water systems the same way. Poor restroom placement, limited handwashing access, and sanitation issues in labor camps directly influence contamination risk. When human hygiene breaks down, these parasites have a clear pathway into fields, wash systems, and ultimately the supply chain.

8. Do not treat documentation as a paper exercise. Hazard identification is not about filling binders, it’s about producing accurate, defensible evidence. Missing hazard analyses or incomplete water‑system schematics weaken regulatory standing. ‍

9. Do not assume negative test results mean no risk. Cyclospora testing is specialized and not always sensitive, and the same is true for many hard‑to‑detect biological hazards. A negative result does not guarantee absence, it simply means the organism was not detected at that moment, under that method, with that sample. Strong programs treat negative results as one piece of information — not a final answer — and rely on trends, environmental signals, upstream land‑use patterns, and validation data to understand true risk.

10. Do not forget that agricultural hazards move. Water systems are dynamic, which means that hazards migrate through canals, reservoirs, shared irrigation networks, and runoff pathways. If water moves, contamination can move with it.

‍ Now, what happens after the product leaves the field? Once it moves into the facility, into cans, jars, or containers, and eventually into stores, the final risk becomes imminent. This is where agricultural controls meet consumer exposure, and where post‑harvest oversight carries just as much weight as field practices. The next section is dedicated to the regulators and programs that operate in this space — the point where agriculture meets the largest consumer base. This is where LACF steps in.

Regulatory Expectations for Biological Hazards in Agricultural Commodities Used in LACF Foods

When agricultural commodities move from the field into low‑acid canned food (LACF) operations, the regulatory focus shifts in a big way. FDA and state regulators aren’t just looking at what happens inside the plant — they’re paying close attention to whether the product arrived at the facility with its agricultural risks already under control. By the time a commodity reaches a can, jar, or container, regulators want to see that upstream hazards were understood, managed, and documented long before the product entered any cooking, canning, or purified system.

This section is for all the PCQIs, QA Teams, HACCP Managers, and Food Protection Managers.

1. Identify hazards before the product enters the plant. Regulators want to see that biological hazards were understood and addressed in the field, not treated as something the facility will “fix later.” Post‑harvest regulators confirm this by reviewing agricultural hazard analyses, checking supplier‑verification records, looking at water‑system documentation, and making sure the processor can show how field‑level risks were identified and controlled before the commodity ever reached the facility. Their role is to verify that upstream hazards were recognized early and managed correctly. ‍

2. Show proof that raw‑material risks were controlled. Regulators look for real evidence — supplier records, water‑safety documentation, harvest‑crew sanitation practices, and clean transport conditions — not assumptions or verbal assurances.

3. Classify the product correctly. Whether a commodity is LACF, acidified, high‑acid, or mixed‑pH determines the rules that apply. Regulators check that the classification is accurate and defensible. The easiest way to think about this is every commodity must be placed in the right “bucket” before processing begins. To do that, processors should check the product’s natural pH, understand whether any acid is added, and confirm whether the final formulation stays low‑acid, becomes acidified, or qualifies as high‑acid. Once the category is set, processors must follow the matching regulatory requirements. Regulators simply look for proof that the classification was done correctly and that the processor is following the right rulebook for that specific product.

4. Provide a process that is fully validated — and easy to understand on paper. Make sure processes are filed, supported by a recognized process authority, and backed by clear validation records. A regulator should be able to read documentation immediately and understand how the process delivers safety under normal and worst‑case conditions. Keep records organized, dated, and complete. ‍

5. Document careful handling of raw commodities before cooking or canning. Show, through records, that raw materials were protected from contamination the moment they arrived. Include receiving logs, inspection sheets, handling procedures, and any corrective actions. The documentation should make it clear that safety started early — not at the canning step. Regulators reviewing from behind a desk must be able to see that upstream handling was controlled and intentional. This can be found in the food safety plan, HACCP Plan, and process flow diagram.

6. Maintain strong, traceable records for all water systems. Because regulators cannot observe the manufacturer’s wash lines or blanch tanks in person, the paperwork must tell the full story. Keep validation studies, monitoring logs, calibration records, sanitation documentation, and corrective‑action notes organized and easy to follow. Records should clearly show that water used for washing, blanching, or filling was safe, monitored, and never allowed to become a contamination source. This can be found in their food safety plan, process flow chart, critical control points, and hazard analysis.

7. Maintain clear, defensible documentation. Records must be complete, organized, and aligned with 21 CFR 113 and 114. These are the FDA regulations that govern how low‑acid canned foods (113) and acidified foods (114) must be processed, documented, and verified. They outline the rules for filing processes, keeping records, maintaining equipment, and proving that the product was made safely. When regulators say documentation must align with 21 CFR 113 and 114, they’re simply asking for records that match the requirements for whichever category your product falls into. Regulators look for documentation that shows what was done and why — not just paperwork for the sake of paperwork.

8. Keep all teams aligned. Agriculture, supplier verification, processing, quality, and regulatory groups must work together. Biological hazards move across the supply chain, so your controls must move with them.

The next, and final, section is dedicated to how to accurately verify agricultural commodities coming in from overseas or better known as imported foods.

How Agricultural Biological Hazard Identification Connects to FSMA & FSVP

Biological hazards in agricultural commodities sit at the heart of FSMA’s preventive‑controls mindset. They shape how regulators evaluate domestic processors, foreign suppliers, and anyone moving product from field to facility. Here’s how these expectations translate into everyday practice. ‍

1. FSMA requires hazards to be identified at the source. Processors must understand and document biological hazards before ingredients arrive at the facility. Strong hazard identification starts in the field, not at the receiving dock. This information should be in the food safety plan, hazard analysis, and the earliest steps of the process flow diagram.

2. FSVP requires importers to verify foreign agricultural practices. Importers must confirm that foreign suppliers manage hazards the same way domestic growers would — through water controls, sanitation, land‑use awareness, and documented verification. You can verify this by reviewing the FSVP program, supplier approval files, and foreign supplier verification records.

3. Agricultural hazards shape supplier‑approval decisions. Supplier approval requires proof that farm‑level hazards were identified, controlled, and verified. This can be found in the supplier approval packet, agricultural documentation folder, and the supplier risk‑ranking matrix.

4. LACF processors must show that upstream hazards were addressed. Canning does not erase agricultural problems. LACF processors must demonstrate that field‑level risks were handled correctly long before the product reached a retort or aseptic system. This should be in the scheduled process file, raw‑material handling procedures, and pre‑processing hazard analysis.

5. FSMA’s “reasonably foreseeable hazards” standard includes agricultural water. If a hazard can realistically occur, it must be addressed — and agricultural water fits that definition. Cyclospora meets every criterion for a foreseeable hazard. You can verify this by reviewing the hazard analysis, agricultural water assessment, and any supporting test reports or GLP studies.

6. Strong agricultural hazard identification strengthens preventive controls. When hazards are clearly identified early, everything downstream improves — supplier controls, water validation, environmental monitoring, and corrective‑action planning all become more effective. This should be reflected in the Preventive Controls section of the Food Safety Plan and in validation and verification records.

7. FSVP audits increasingly focus on agricultural water systems. FDA inspections now emphasize water sources, treatment records, upstream land use, and how importers verify these conditions. This information can be found in FSVP water‑system documentation, supplier water‑treatment records, and land‑use assessments.

8. FSMA and FSVP both require documentation that tells a complete story. Records must be accurate, traceable, and supported by agricultural evidence. Regulators want documentation that shows what happened in the field, not just what happened in the facility. You can verify this by reviewing the master documentation index, batch records, supplier files, and traceability folders.

9. Agricultural hazard identification supports recall prevention. Identifying hazards early reduces the chance of contamination moving downstream. Strong field‑level controls help prevent recalls and protect brands. This should be included in the recall‑readiness plan, hazard analysis, and preventive‑control justification records. ‍

10. FSMA + FSVP + LACF = one unified hazard‑identification system. When agricultural hazards are identified and controlled, they support FSMA Preventive Controls, FSVP verification, LACF compliance, and import/export alignment. This can be found in the integrated Food Safety Plan, cross‑functional supplier program, and LACF compliance documentation.

So, there you have it. I’ve walked through what to do at the farm, what not to do during harvesting, how to review post‑harvest practices, and even how to get product into the country. Not bad for a free review. In all seriousness, these protocols and parameters exist for one simple reason- safety. The regulations may feel tedious, repetitive, and occasionally unnecessary at every step of the manufacturing process, but they’re built to save lives, keep companies aligned with expectations, and keep potential risks front and center in both operational excellence and financial integrity. Real dollars are tied to mishaps, outbreaks, recalls, and illnesses — and if one consultant can help prevent any of that from happening again, I’ll gladly take the call!

Before closing, it helps to look at the financial side of agricultural water risk and biological‑hazard verification. Food safety failures don’t just show up in inspection reports or supplier files. They show up in operating budgets, retailer relationships, and long‑term profitability and when agricultural controls weaken, the financial consequences move quickly. Cyclospora outbreaks have cost companies anywhere from $2 million to more than $10 million in direct expenses. Those numbers reflect recalls, destroyed inventory, emergency sanitation, overtime, environmental testing, and regulatory follow‑ups. A major fresh‑cut recall in 2020 resulted in roughly $25 million in losses once customer attrition and supply‑chain disruption were included. Another produce grower dealing with protozoa contamination spent nearly $8 million rebuilding water systems, retraining field crews, and restructuring supplier oversight.

Some losses reach far beyond operational costs. One retailer was removed from a large conglomerate partnership after years of inactive practices, untrained personnel, outdated processes, and leadership that had mentally checked out while waiting for retirement. The removal triggered an $8 billion financial hit across the conglomerate’s portfolio. That loss wasn’t caused by a single outbreak—it was caused by complacency, weak verification, and a slow decline in operational discipline that eventually became impossible to ignore. These examples highlight the fact that agricultural hazards create financial hazards. Weak water oversight raises insurance premiums, jeopardizes retailer confidence, increases regulatory scrutiny, and forces companies into expensive corrective‑action cycles. A well‑maintained water‑treatment validation program might cost $15,000–$40,000 a year while a single recall or failed audit can cost 50 to 100 times more than that.

Strengthening agricultural water management, validating protozoa‑specific controls, tightening supplier verification, and aligning documentation with FSMA, FSVP, and 21 CFR 113/114 protects far more than food safety. It reinforces financial stability and gives companies the confidence to invest in their operations without fear of hidden risks surfacing later. The focus should remain on precise hazard identification and consistent verification, because those practices build stronger supply chains, preserve customer trust, and prevent the kinds of catastrophic losses that can reshape entire organizations.

‍Trust and verification go hand in hand — especially when you know exactly what you’re looking for. Thanks for reading and have a great week!