Reading the Operational Record: A Different Way to See What Your CAPA Log Is Telling You
A woman at a conference last week asked me where she could get “one of those maps.” She had been listening as I described my work, and her question, phrased almost exactly that way, turned out to be the question the field has been carrying for some time and not quite answered yet.
There are answers in the field, working in parallel.
Three current answers, working in parallel
Food safety culture frameworks have been formalizing for nearly two decades. They survey perception, measure shared values and leadership commitment, and produce maturity scores. The major frameworks now treat culture as something measurable rather than soft, and the industry has built real assessment infrastructure around the recognition that culture shapes food safety outcomes.
Digital transformation has made a different and equally real contribution. Operational data that used to live in paper logs is now captured continuously, surfaced in dashboards and real-time alerts. The capacity to see what's happening in a facility — environmentally, procedurally, in records — is more developed than at any point in the field's history.
Governance writing, more recently, has begun naming what culture and data both depend on: leadership decisions about authority, resourcing, and escalation. That conversation is still finding its language.
Each is doing real work. None of them, on its own, reads the operational record itself — the CAPA log, the deviation history, the years of inspection observations — as a structured account of how the system is actually behaving under operational pressure.
The reading I do
Most CAPA logs get read as a list of resolved events. Each corrective action documented and signed off, each filed under the appropriate category, each reviewed at the appropriate cadence. By the standards of a responsive program, the system performs exactly as designed — and that reading is correct.
The same record can be read another way. As a transcript of what keeps coming back. The categories generating repeated entries despite the corrections that closed them. The responses cycling through under different operators and different supervisors without producing stability. The kinds of work the organization has gradually learned to absorb as routine rather than resolve at the source.
What that second reading reveals is rarely about the people on the floor. It's about the conditions those people were operating in, and the decisions and structures upstream that established and sustained those conditions.
For one such reading worked through in detail — the recurring GMP issue where storage repositioning resolved what training repetition could not — see Food Safety as Business Infrastructure, published in Food Safety Tech.
What surfaces in the data
In one five-year review of 291 corrective actions, 23% recurred — meaning nearly one in four problems returned despite documented fixes, under different operators and different supervisors, with all the appropriate paperwork closed each time.
Read the first way, that's a closure rate.
Read the second way, it's the cost of investigating, retraining, and closing out the same problem two, three, four times. The cost cycling through the operating budget that absorbs everything the formal accounting doesn't quite catch, while the condition that generated the work remains in place, still producing.
The question that follows
This second way of reading isn't a tool. The field is full of tools, and most of them do useful work — assessment instruments, software platforms, dashboards. Tools surface what they were designed to surface. The reading sits between what the operational programs produce and what the governance layer needs to receive, translating one into the other in a form that supports structural decisions rather than another round of corrective documentation.
The orientation that makes this possible isn't something an organization buys. It's something an organization develops, applied to records the organization already has.
The question this kind of reading produces is straightforward to ask and harder to sit with:
When did you last close a corrective action that changed the system rather than the person?
Most leadership teams know the answer the moment they hear the question. That recognition is where the work begins.
This piece was published in fuller form as Field Note No. 01 in Field Notes on Food Systems — a working record of how food manufacturing systems behave under pressure. New entries when there's something worth surfacing.
Azure Edwards, M.S., is the founder of Pacific Blue Horizon Group, a food safety governance advisory firm. She holds a Master of Science in Food Safety from Michigan State University.
