Your System Is Documented. But Is It Actually Being Followed?

There is a question that can make a food safety team uncomfortable:

“Show me how you actually do this.”

Not: “Show me the procedure.”

Not: “Show me the training record.”

Not: “Show me the last audit report.”

Just: “Show me what happens.”

That question moves the conversation from documentation to implementation. And sometimes, that is where the real story begins.

The organization may have a complete food safety manual. The procedures may be approved. The forms may be controlled. Employees may have signed training records. Internal audits may be completed. The certification may be current.

Yet, when someone watches the process, the actual operation does not completely match what the system says should happen.

Maybe employees perform a step differently. Maybe a monitoring frequency has changed. Maybe a different form is being used. Maybe a supervisor has developed an informal workaround. Maybe employees know the procedure but do not consistently follow it. Maybe the process changed months ago and nobody updated the documentation.

The system is documented. But is it actually being followed?

That is a much more important question than whether the documents exist.

Documentation proves intent. Implementation proves behavior.

Documentation has an important role in a food safety management system. It establishes expectations, defines responsibilities, provides instructions, creates records, supports verification, and provides evidence for management, customers, regulators, and certification bodies.

But documentation primarily describes what the organization intends to do. Implementation demonstrates what the organization actually does.

Those two should align. When they do, the system becomes reliable. When they do not, the organization has an implementation gap.

That gap can be small, or it can affect an important food safety control. Either way, it deserves attention.

The procedure may be sitting on the shelf while another process is happening

Imagine an organization has a detailed sanitation procedure specifying cleaning steps, responsible personnel, frequency, chemicals, concentrations, verification, corrective actions, and required records. Everything looks appropriate on paper.

Then someone observes the actual sanitation process:

• The employees perform the steps in a different order;
• One step is routinely skipped;
• The verification happens later than the procedure specifies; and
• The team uses a locally created checklist instead of the official form.

Nobody thinks there is a problem. This is exactly the kind of situation that can remain hidden when the organization reviews documents without observing implementation.

The procedure exists. The process exists. But they are no longer the same process.

Why people stop following procedures

It is tempting to assume that employees simply ignore procedures. Sometimes that happens, but it is not always the best explanation. People may stop following a procedure because:

• the process or equipment changed;
• the procedure is outdated or difficult to understand;
• the required form is inconvenient;
• employees were not trained properly;
• supervisors provide conflicting instructions;
• the procedure is unrealistic under production conditions;
• responsibilities are unclear; or
• employees developed a workaround that seems more practical.

That is why the first question should not always be “Who failed to follow the procedure?” A better question is: “Why isn't the documented process being followed?” The answer can reveal whether the problem is behavioral, procedural, organizational, or systemic.

“We know how to do it” is not the same as controlled implementation

Experienced employees often know their jobs extremely well and can perform a process correctly without looking at the procedure. That can be a strength, but it can also create a hidden dependency.

When experienced employees teach new people based on memory rather than controlled procedures, the process can gradually drift. One employee explains it slightly differently, the next person learns from them, and another develops a shortcut.

Eventually, the organization has an informal version of the process. This is how tribal knowledge slowly replaces controlled documentation. The employees may still perform the activity well, but the organization loses consistency and becomes dependent on individuals.

Watch the process instead of asking whether people follow it

One of the simplest ways to test implementation is observation. Do not ask: “Are you following the procedure?”

Instead, say: “Show me how you perform this task.”

Then watch what happens first, what tools are used, what information is checked, what decisions are made, what gets recorded, and what happens when something is different.

Compare what you observe with the documented procedure. People may sincerely believe they are following the procedure; observation shows whether the procedure and behavior actually match.

Records can tell you another part of the story

Records are also useful for determining whether a procedure is being implemented.

Suppose a procedure requires a monitoring activity every two hours. You review several weeks of records, and they consistently show monitoring every three hours.

Now there is a question: Is the employee failing to follow the procedure, or is the procedure no longer realistic?

Perhaps production schedules changed, the monitoring point moved, process risks were reevaluated, employees misunderstood the frequency, or the form makes timing difficult to track. The record identifies the difference; the investigation identifies the reason.

Training records do not prove competence

Training is another area where documentation can create false confidence. The organization may have a signed training record confirming attendance and procedure review, but the real question is whether the employee can actually perform the task.

For critical responsibilities, employees must demonstrate expected competency:

• An employee responsible for environmental monitoring should understand the sampling procedure and how to respond to unexpected results;
• An employee responsible for allergen changeovers should understand sequencing and verification requirements; and
• A supervisor responsible for corrective action should understand how deviations are controlled and investigated.

A training signature is evidence of participation—not necessarily evidence of effective implementation.

The supervisor can reveal the real standard

Employees do not take instructions only from procedures; they also take cues from supervisors.

Ask the employee: “What would you do if this happened?” Then ask the supervisor the exact same question.

If the procedure requires escalation and the employee says “I would stop and notify quality,” but the supervisor says “We usually keep running and deal with it afterward,” the organization has two conflicting standards. The employee is following the written system, while the supervisor is following the operational culture.

The production floor can expose outdated procedures

Sometimes employees are following the current physical process, but the documentation has not caught up.

This happens frequently in growing facilities when a line changes, new equipment is installed, a new product is introduced, an ingredient is reformulated, or the workflow adapts. The floor adjusts, but the binder remains unchanged.

Document control cannot be separated from change management. When operations evolve, the food safety system must evolve with them.

Internal audits should test implementation

Internal audits are an important opportunity to answer whether the system is actually being followed. A document-based audit merely confirms that procedures exist, revisions are current, and forms are available.

An implementation-focused audit goes further by asking:

“Show me the process. Show me the monitoring. Show me the record. Show me what happens when the result is unacceptable.”

This provides a much stronger assessment of true system effectiveness.

The gap may exist between shifts

A system can be followed consistently on day shift and inconsistently on night shift. One shift may have dedicated quality support and seasoned supervisors, while another operates with newer teams and fewer resources.

The procedure is identical, but the execution differs. Internal audits, floor observations, and interviews must evaluate all operational shifts to ensure safety does not depend on who is on duty.

The gap may exist between departments

Production may follow one version, quality may expect another, purchasing may use a separate supplier process, warehouse may manage its own hold status, and maintenance may modify equipment without cross-functional review.

The management system must clearly define the operational handoffs: who initiates, reviews, approves, implements, verifies, and receives the data. Clear handoffs ensure consistent cross-departmental execution.

The most dangerous gaps are the ones everyone accepts

Some deviations become so normalized that they become invisible:

• “We've always done it this way.”
• “That's just how this line works.”
• “We know the procedure isn't current, but everyone understands what to do.”
• “We haven't had a problem so far.”

The fact that an informal workaround has existed for years does not make it controlled. Unmonitored practices remain safe only until an equipment failure, new hire, or ingredient change exposes the vulnerability.

Ask what happens when the normal process fails

Following a procedure during routine operations is simple; the real test occurs when an unexpected event happens:

• What happens if a monitoring result is outside the critical limit?
• What happens if pre-operational sanitation verification fails?
• What happens if the wrong raw material arrives at the dock?
• What happens if a required daily record is missing?
• What happens if a packaging label discrepancy is detected mid-run?

If employees respond with uncertainty or hesitate on escalation steps, the organization has found a critical procedural gap.

A food safety system should be tested under normal conditions

While pre-audit walkthroughs are common, observing routine operations on an ordinary day is far more revealing.

Walk the production floor without announcing a formal inspection. Observe standard activities, check records as they are actively filled out, and converse with operators naturally. This reflects the authentic system operating in your facility.

Look for the small signals

Implementation drift often shows up through minor daily friction:

• A current SOP cannot be located on the floor;
• An obsolete paper form is still taped to a workstation;
• An operator asks which document version is active;
• A supervisor keeps an informal offline checklist;
• Records are filled out at the end of the shift rather than in real time; or
• Corrective actions repeatedly recur in the same production zone.

Individually, these seem minor. Together, they signal that the documented management system is drifting away from floor reality.

The solution is not always more training

When a procedure is not being followed, the default response is often to schedule mandatory retraining. Before doing so, ask:

• Is the procedure accurate and practical for floor conditions?
• Is the operator equipped with the right tools and clear forms?
• Does the supervisor reinforce the documented requirement?
• Does the employee understand why the control is critical?

If the procedure itself is flawed or unrealistic, retraining workers to execute a broken document will not solve the issue.

The solution is not always a new procedure either

Creating another procedure or adding another sign-off form often adds unnecessary complexity without solving root causes.

If the true issue is unclear ownership, an outdated machine, or poor shift communication, additional paperwork only burdens the operator. Match the corrective action directly to the root cause.

Use the “show me” method

Test your implementation across six clear diagnostic steps:

1. Show me the procedure: Can the operator find the active, approved version?
2. Show me how you perform it: Does the physical workflow match the text?
3. Show me the record: Is real-time evidence being generated accurately?
4. Show me what happens when something goes wrong: Is the deviation and hold pathway clear?
5. Show me who reviews it: Is supervisory verification happening consistently?
6. Show me what happens with recurring problems: Does CAPA permanently resolve the cause?

Compare the four versions of reality

Evaluate your critical food safety processes across four dimensions:

• What the procedure says: The documented requirement.
• What employees were trained to do: The communicated curriculum.
• What employees actually do: The physical line execution.
• What the records show happened: The documented evidence.

Where these four dimensions diverge, you pinpoint the exact source of your system breakdown—whether in training, supervision, document accuracy, or data integrity.

Verification should close the loop

A corrective action is not finished because a document was revised or a briefing was held. The organization must verify whether the intervention changed behavior on the floor.

Did simplified log sheets result in cleaner records? Did revised sanitation steps eliminate re-cleaning delays? Always verify operational effectiveness.

What if the system is not being followed consistently?

Inconsistent execution does not mean the entire quality system has failed. Prioritize controls tied to significant food safety hazards and Critical Control Points (CCPs).

Systematically evaluate documentation, training, supervisor coaching, monitoring ease, verification, and change control to build a structured, risk-based roadmap for improvement.

Build a system that is easier to follow

Improving compliance is rarely about demanding that workers try harder; it is about designing systems that make compliance intuitive.

Clear instructions, ergonomic workstations, straightforward logs, accessible tools, and supportive supervision make standard operating procedures the path of least resistance.

The real test happens when nobody asks

A mature food safety system operates reliably when no auditor is present, when schedules are tight, across night shifts, during onboarding of new hires, and when unexpected equipment deviations occur.

That is the difference between a system that exists only on paper and one that is deeply embedded in daily operations.

Start with one critical process

Pick one critical control point or sanitation routine. Read the procedure, observe the execution, interview the operator, review the training, inspect the completed records, and ask what happens during a deviation.

Comparing the documented standard against actual execution will immediately show where your system is working well and where it needs practical support.

When the documents say “yes” but the floor says “not exactly”

FoodSafetySystems.co helps organizations develop, implement, evaluate, and maintain practical food safety management systems, including FSSC 22000 readiness and implementation, HACCP and food safety plan development, food safety training, internal audits, CAPA, document control, supplier verification, food safety culture, process control, sanitation, environmental monitoring, and ongoing compliance management.

If your system is well documented but you are not sure whether employees are consistently following it, start with observation rather than another document review. Ask people to show you what they do, compare what you see with what the system says should happen, and close the gap before it creates a food safety risk.

A procedure sitting in a controlled document system does not control food safety by itself. The people who use it do.