Ask The Expert

The People Who Carry Food Safety

By Azure Edwards, M.S.
No Comments
October 7, 2026


• Categories: Ask The Expert, Food Safety Consortium, Food Safety Culture Club, Food Safety Think Tank

Food safety usually begins as a requirement: something regulators, customers, and certifiers expect before a product can be bought or sold. Responsibility for meeting their expectations is assigned inside the organization, but understanding food safety’s relationship to business decisions does not always move inside with it. This article explores what that disconnect asks of the people holding the responsibility, how it shows up at the interfaces between functions, and why it matters to profitability, risk, growth, and brand trust.

Nearly everyone in food safety has a gut-punch of a story, and we share them at networking events and conferences. It usually goes like this: a food safety decision was made outside their knowledge or control and the consequences landed in their lap, or they were pressured to go along with something they knew was not okay. Some left their jobs because of it. Some were let go. Most of the time, they were told this is just how it is and how it has always been done. But when a pattern is repeated across roles and organizations, it describes something more pervasive than any one person’s experience, and that deserves our attention.

A company’s first contact with food safety is as a condition of doing business. It must meet the requirements that allow it to produce and sell food, and those requirements establish controls, verification, documentation, and internal accountability. Inside the facility, people translate them into daily practice. The business depends on that translation, whether it recognizes the work as operating capability or treats it as something imposed from the outside.

The difficulty comes when responsibility for food safety is designated inside the organization but still treated as external to its operational priorities. When the authority, resources, and support to meet those requirements do not accompany that designation, Quality can be cast as the organization’s in-house regulator, not only carrying the responsibility for compliance but also absorbing the frustration the business feels toward rules it perceives as unnecessary and imposed on it from the outside. Compliance ends up positioned against production rather than as part of the operation’s ability to reliably meet customer expectations and produce safe food, and the people hired to hold that responsibility find themselves standing between the business and its own commitments. The familiar “food police” label captures that dynamic well. Treating Quality as the group that asks inconvenient questions, delays work, and enforces rules the business already agreed to follow separates those rules from the work and the people they are meant to protect.

The friction between compliance priorities and operational priorities is most often experienced when a decision has both food safety and business implications. Exploring reasonable paths forward is sound decision-making; however, intense organizational pressure can erode the support required to uphold standards, shifting the burden of unresolved risk onto individuals. The people entrusted with safeguarding food should never be pressured into ethical compromise.

Formal policies and programs set expectations, but the reality of an organization’s values is revealed by how it responds to issues raised under pressure. When the person who brought forward a concern is treated as an obstacle, people notice. When reported issues fail to produce meaningful action, they notice that too. Over time, they begin to weigh the value of speaking up against the personal cost. And when that cost is too high, problems remain hidden, systems weaken, and risk compounds. That is food safety culture, and it is learned by watching.

Much of this friction happens at the interfaces, the places where one part of the operation hands something to another: where Quality meets production, maintenance work triggers sanitation work, a concern has to travel up from the floor to someone who can act on it, and a sales commitment travels back down as a production and food safety demand the floor has to execute. Each function can be doing its part while responsibility, authority, information, and resources do not meet at the same point in the work. A decision made in one place can have consequences that land in another, often on people who were not part of the decision.

The people working at those interfaces see it first. Operators, sanitation, maintenance, and line supervisors know how the work is actually being done. They see when a written procedure and the realities of a shift conflict, when temporary repairs are failing, or when demand is stretching operations beyond what the system can reliably support. They can bring it forward in context, before risk or cost grows, but whether they do or not depends on what they have seen happen at that interface before.

When food safety is viewed as an expense imposed by third parties, or as a policing function, organizations lose sight of what it holds together. Many quality challenges stem from upstream decisions about equipment, scheduling, staffing, supply chain, and product design, yet their financial toll shows up in Quality’s budget. The expense view also misses the burden placed on the workforce and the risk carried by individuals. Much of what keeps the system stable lives in people: the reasoning behind specific controls, historical attempts at solutions, recurring pain points, and informal workarounds that have become standard practice. That dependence often goes unnoticed until the person whose mind it lives in leaves. When a business relies on an individual to sustain a system it hasn’t fully embraced, the value of that expertise, and its role in business continuity, only becomes clear once it’s gone.

The stories food safety professionals share describe a pattern, and a pattern gives a business reason to look more closely at the conditions it can change. Food safety as business infrastructure starts by backing the people, at every level, who carry it: asking whether those nearest the work can voice what they see, and whether that input reaches leaders empowered to act on it. Public health isn’t the only thing that depends on the answer. So do a company’s profitability, risk profile, growth trajectory, and brand reputation.