Every major food safety headline begins long before anyone writes it.
Before an outbreak is identified, a recall announced, or an investigation launched, countless quieter decisions shape what happens throughout the food system. A supplier is approved. A specification is accepted. Equipment is maintained. An unusual result is investigated or dismissed. A worker decides whether to speak up.
Most of these decisions will never become news, and when they are made well, that is precisely the point. The third annual Global Glove Safety Day today is an appropriate time to think not only about the failures that make headlines, but also about everything that happens before them. The most important question may not be simply, “What went wrong?” It may be: What are we assuming is safe today?
The danger of assumed safety
More than three decades in food safety have taught me that failures rarely begin at the moment we discover them. They have a history. Somewhere upstream, a hazard may not have been recognized, a specification may have gone unchallenged, a supplier assurance may have been accepted without sufficient verification, or a worker may not have felt empowered to stop a process.
Individually, these decisions can appear small. Collectively, they can determine whether food reaches a family safely. This is why prevention demands more than compliance. Regulations, standards, audits, testing programs, and documentation are essential, but the existence of a control is not the same thing as evidence that the control is working as intended.
A certificate, specification, training record, or audit is not, by itself, prevention if the assumptions behind it remain unexamined. Leaders should continually ask: How do we know? How do we know a supplier is consistently meeting our safety expectations? How do we know a material is appropriate for its intended use? How do we know a recurring deviation is an isolated event rather than an early warning?
That distinction between assuming and knowing is where prevention often begins.
A glove is a small thing — until it isn’t
Food handling gloves provide a useful example. Consumers see someone preparing food while wearing gloves and understandably associate them with cleanliness and protection. But a glove does not become an effective food safety control simply because it came out of a box. It must be appropriate for its intended use, sourced and stored appropriately, and used correctly. Employees must also understand when gloves need to be changed and that gloves do not replace proper handwashing or sound food-handling practices.
We should not confuse the appearance of protection with evidence of protection.
That principle extends far beyond gloves. It applies to sanitation programs, supplier assurances, environmental monitoring, training, traceability, and other controls throughout the food system. Are they working because we have evidence that they are working, or do we believe they are working because they are familiar, documented, and have not obviously failed?
Food safety leadership should sometimes be uncomfortable. Familiarity can create confidence. Confidence can become assumption. Assumptions that are never challenged can become vulnerabilities.
Prevention is a leadership system
Food safety cannot belong only to people with “food safety” or “quality assurance” in their titles. Procurement influences safety through purchasing requirements and supplier decisions. The operations team influences safety when production pressures compete with sanitation or investigation. Executives influence safety through priorities, resources, and the behaviors they reward. Frontline employees influence safety every time they follow a procedure, notice something unusual, or raise a concern.
Safety really is in our hands, but that should never become an excuse to place the burden solely on the individual worker. Consider something as simple as changing a glove. We can ask whether an employee changed it at the appropriate time, but leadership should ask whether the right glove was purchased, expectations were clear, training was effective, supplies were available, and employees could stop when something appeared wrong without fearing that production mattered more than safety.
That is the difference between treating food safety as a behavior and treating it as a system. Strong organizations create conditions in which people can act on their responsibility. They also recognize that compliance is the floor, not the ceiling. Meeting a legal requirement answers one question. Responsible leadership asks another: Have we done what we reasonably can to prevent foreseeable harm?
The stories no publication can report
Modern food safety has extraordinary capabilities for finding problems. Advances in laboratory science, epidemiology, whole genome sequencing, surveillance, and traceability have transformed our ability to identify hazards and respond to outbreaks. Those capabilities save lives, but finding a failure faster is still different from preventing it.
Readers come to Food Safety News in part because this publication documents the realities of food safety failures: outbreaks, recalls, investigations, regulatory actions, and their consequences. That reporting matters because the food system must learn from what went wrong.
But there is another category of food safety story that no publication can fully report: the failures that never happened.
We never read the headline for the outbreak prevented because someone acted on an early warning. Nobody posts recall notice for contaminated product stopped before entering commerce. We rarely hear about the supplier questioned before a vulnerability became a crisis, the employee whose concern was taken seriously, or the leader who accepted a production delay because an unanswered safety question mattered more than the schedule.
Imagine the strangest possible food safety headline: “BREAKING NEWS: NOTHING HAPPENED.” No outbreak. No recall. No illnesses. No families harmed.
Of course, “nothing happened” is not news. In food safety, however, it can represent extraordinary and intentional work. The public may never know what was prevented, but invisibility should not mean insignificance. Organizations should identify these moments, study them, and recognize what made the right decision possible.
The public may never read the headline – The organization should still learn the story
Sept. 18 has a deeply personal meaning for me. It is the birthday of my son, Riley, who was born in 1991. He died in 1993 during the Jack in the Box E. coli outbreak. This year, he would have turned 35.
More than three decades later, his birthday reminds me why prevention can never remain an abstraction. Behind every outbreak number is a person. Behind every case count is a family that expected the food they ate to be safe. Some consequences cannot be undone after a hazard is identified.
That is why Sept. 18 became the date for Global Glove Safety Day. The day focuses attention on gloves, but the responsibility it represents is much larger. It is about looking at something ordinary and asking whether we know as much about its safety as we think we do. It is about questioning routine, demanding verification, and creating workplaces where people can raise concerns before they become incidents.
Before someone writes the headline
We cannot prevent every food safety failure by focusing on one product, one procedure, or one day. But we can build organizations that are better at questioning assumptions. We can make safety part of purchasing decisions, ask suppliers for evidence rather than reassurance, learn from near misses and successful interventions, and give employees both the responsibility and authority to raise concerns.
Leaders throughout the food system should keep asking: What are we assuming is safe simply because nothing bad has happened yet?
The next major food safety headline may already have a history. Somewhere today, a decision is being made that could become part of that history or prevent it. Identify the assumption, question it, verify it, and fix it if necessary.
Do it before someone else has to write the headline.
