The Procedure Was Written. Nobody Used It.

The procedure looked good on paper. The title was clear. The sections were organized. The responsibilities were listed. The forms were attached. Someone reviewed it. Someone approved it. The document was saved. Then production continued. Employees went back to doing things the way they had always done them. The procedure stayed in the folder. Nobody used it. Months later, someone discovers the gap. The procedure says one thing. The operation does another. The employees know the real process. The document describes a different process. And suddenly the business has a question that is much bigger than a missing signature: Why did we create a procedure nobody actually uses?

A procedure is not successful because it was written

This is one of the easiest mistakes to make in food safety management. A company identifies a requirement. Someone writes an SOP. Management approves it. The document is stored. The task is marked complete. But a procedure is not the finished product. The procedure is supposed to control or support an activity. If employees do not understand it, cannot use it, or have developed a different way of performing the task, the document is not doing its job. The existence of the SOP is evidence that someone documented a process. It is not necessarily evidence that the process is being implemented.

The employee usually has a reason

When employees do not use a procedure, the first reaction can be: “They are not following the SOP.” Sometimes that is true. But sometimes the better question is: “Why isn't the SOP being used?”

• Maybe the procedure is too complicated.
• Maybe it describes an old process.
• Maybe employees were never properly trained.
• Maybe the form does not match the actual workflow.
• Maybe the procedure requires information employees do not have.
• Maybe the task changed after the SOP was written.
• Maybe the employee created a faster method that management never incorporated into the document.
• Maybe nobody explained why the procedure matters.

The gap may be a people problem. But it may also be a system-design problem.

The procedure may have been written for an operation that no longer exists

This happens frequently as food businesses change. A procedure is written when the company has one production line. Six months later, equipment changes. A new ingredient is introduced. The manufacturer changes the process. Responsibilities move from one employee to another. The company adds another product. The SOP remains untouched. Now the employee follows the process that actually works. The procedure describes the old process. Nobody intentionally violated the procedure. The system simply failed to keep the document aligned with reality. That is why document review is not merely about proofreading. It is about asking: “Does this still describe what we actually do?”

A procedure cannot control what it does not understand

Imagine an SOP says the employee checks the process every hour and records the result on Form A. But on the production floor, the employee:

• Uses a digital system instead of Form A
• Performs the check at a different point in the process
• Records additional information
• Has a supervisor perform the review
• Escalates deviations differently

Which process is correct? The answer should not automatically be “the SOP.” The organization needs to determine whether the SOP is still appropriate and whether the actual process meets the applicable requirements. If the real process is appropriate, the document may need to be updated. If the real process is not appropriate, the operation may need to change. Either way, the mismatch needs to be resolved.

The most dangerous SOP may be the one everyone thinks is complete

A missing procedure is obvious. Everyone knows something needs to be created. An outdated procedure can be harder. The document exists. It has a title. It has an approval date. It looks official. It may even look professional. That can create a false sense of security. Someone sees the SOP in the compliance folder and thinks: “We have that covered.” Meanwhile, the employees are doing something else. The business now has documentation that creates the appearance of control without necessarily supporting the actual process. That is why document effectiveness matters.

Ask the employee to explain the procedure

One of the simplest tests is also one of the most revealing. Take an employee who performs the task. Do not hand them the SOP and ask them to read it. Instead, ask: “Show me how you perform this activity.” Watch what they do. Then compare it with the procedure. You may discover that the employee follows it almost perfectly. Excellent. You may discover a few minor differences. Worth reviewing. You may discover that the employee has never seen the procedure. Important. Or you may discover that the SOP and the actual operation are completely different. Now you know where the problem is.

The procedure should make sense to the person using it

Compliance professionals sometimes think about procedures in terms of requirements. Employees think about procedures in terms of work. That difference matters. An employee may not care that a procedure has twelve beautifully formatted sections. They need to know:

• What do I do?
• When do I do it?
• What do I check?
• What result is acceptable?
• What do I record?
• What do I do if something is wrong?
• Who do I tell?

A procedure that answers those questions clearly is much more likely to be used.

More detail does not automatically mean better

A common response to a procedure problem is to add more information. The SOP becomes longer. Then longer again. Then it includes definitions, background information, references, explanations, exceptions, notes, and additional forms. Eventually, the employee has a 25-page procedure for a task that takes five minutes. The document may be technically impressive. But is it usable? That is the better question. A procedure should contain the level of detail necessary to control the activity effectively while remaining practical for the people who use it.

The form can reveal whether the procedure works

Sometimes the procedure looks fine. The problem is the form. The SOP says employees should record five things. The form asks for twelve. Or the form is missing a field the procedure requires. Or employees have to calculate information manually. Or the form is difficult to access. Or the form does not match the terminology employees use. Then employees create their own notes. A sticky note. A spreadsheet. A notebook. An email. A separate log. Now the official procedure and the actual recordkeeping process have separated. That is a warning sign.

When employees create their own workaround

A workaround is often treated as evidence of noncompliance. Sometimes it is. But a workaround can also reveal something valuable: the existing process may not fit the operation. Imagine an employee has to enter the same information into three different forms. They create a spreadsheet to manage it more efficiently. The spreadsheet works. The official system does not. Instead of simply eliminating the spreadsheet, management should ask: Why did the employee need it? Maybe the underlying process needs redesign. Good compliance systems learn from the people who actually perform the work.

Training is where the procedure becomes real

A procedure sitting in a document-management system does not train anyone. Employees need to understand how the procedure applies to their responsibilities. Training should make clear:

• What the procedure covers
• Who performs the activity
• How the activity is performed
• What records are required
• What constitutes an acceptable result
• What happens when there is a deviation
• Who needs to be notified

Training records can then provide evidence that the organization has communicated the applicable expectations. But training should not become “Here is the SOP. Sign this form.” That may produce a training record. It does not necessarily produce understanding.

The “teach it back” test

A useful approach is to ask the employee to explain the process in their own words. For example: “What do you check?” “When do you check it?” “Where do you record it?” “What happens if the result is outside the requirement?” “Who do you notify?” If the employee can explain the process clearly, that is a good sign. If they cannot, the issue may be training. If they explain a process completely different from the SOP, the issue may be document alignment. If several employees give different answers, the system may lack standardization.

The procedure should connect to corrective action

A good procedure should not stop at “perform the check.” It should also establish what happens when the expected result is not achieved. Employees need to know:

• What is a deviation?
• What immediate action is required?
• Who needs to be notified?
• What needs to be documented?
• How is the affected product handled?
• Who determines the corrective action?
• How is the issue followed through?

For facilities subject to FDA's preventive controls requirements, corrective actions and recordkeeping are components of the broader food safety system. That means the procedure, record, and corrective action process should work together.

The procedure should connect to verification

The question is not only whether employees perform the procedure. The organization should also have a way to verify that the system is functioning as intended. That may involve reviewing records, observing activities, checking documentation, or performing other appropriate verification activities. This creates a chain:

Procedure → Training → Implementation → Record → Review → Corrective action when necessary → Verification

If one link is missing, the system becomes harder to manage.

What happens when the procedure is never reviewed?

A procedure can slowly become irrelevant. The business changes. Employees change. Equipment changes. Products change. Suppliers change. Responsibilities change. The SOP remains. That is why procedures should have defined review triggers and, where appropriate, periodic review. A significant process change should prompt the question: “Does this procedure still describe the process?” A new product should prompt: “Does this procedure apply to the new operation?” A corrective action may prompt: “Does the procedure need to change?” A recurring employee mistake may prompt: “Is the procedure clear enough?” Review should be driven by the operation—not merely by a calendar.

The procedure should be written for the real workplace

This sounds obvious. But it is easy to write procedures from a conference room. Someone looks at the regulatory requirement. Someone creates a policy. Someone writes an SOP. Then the document reaches the production floor. The employee looks at it and thinks: “That's not how we do this.” That is where the document should go back to the people doing the work. Ask them:

• What actually happens?
• What makes this task difficult?
• What information do you need?
• Where do mistakes occur?
• What do you do when something goes wrong?

Their answers can make the procedure more practical.

A good SOP does not tell employees to do something impossible

This is an important test. If the procedure requires information that employees cannot access, it will not be followed. If it requires equipment that is not available, it will not be followed. If it requires a form that nobody can find, it will not be followed. If it requires a review from someone who is never available, it will not be followed. If it requires a process that conflicts with production realities, employees will create workarounds. The solution is not always stronger enforcement. Sometimes the procedure needs to be redesigned.

What if the employees are doing the right thing anyway?

Then the situation may be easier to solve. If employees are consistently performing the appropriate activity but the procedure is outdated, the organization may need to update the documentation to reflect the effective process. The goal should be alignment. What the procedure says. What the employee does. What the record shows. Those three should tell the same story.

The three-way alignment test

Choose one important procedure. Then compare three things.

1. The procedure

What does the SOP say should happen?

2. The employee

What actually happens?

3. The record

What does the documentation show happened?

If all three match, you have strong alignment. If the procedure and employee match but the record does not, you have a records problem. If the employee and record match but the procedure does not, you have a document-control problem. If the procedure and record match but the employee does not, you may have a training or implementation problem. If none of them match, the process needs a deeper review. This simple exercise can reveal a great deal.

The goal is not to make employees “follow the paperwork”

That is the wrong mindset. The goal is to create a documented process that helps employees perform the work correctly and consistently. The paperwork should support the process. The procedure should explain the process. The training should teach the process. The records should demonstrate the process. The verification should evaluate the process. That is a functioning compliance system.

What happens when nobody uses the procedure?

Eventually, the organization becomes dependent on tribal knowledge. One experienced employee knows how things are really done. A supervisor knows which shortcuts are acceptable. The quality manager knows which parts of the SOP are outdated. The manufacturer knows what the brand actually expects. The written system becomes secondary. That may work temporarily. But it becomes fragile. What happens when the experienced employee leaves? What happens when a new supervisor starts? What happens when the company adds another facility? What happens when production expands? The organization has to teach the process again from scratch. A well-maintained procedure prevents that.

Your SOP library should evolve with the business

A growing food business may eventually need procedures covering areas such as:

• Manufacturing operations
• Raw material control
• Food-contact and non-food-contact sanitation
• Warehousing and distribution
• Corrective action
• Preventive controls
• Monitoring
• Verification
• Supplier management
• Training
• Records management
• Change control
• Product-specific activities

The exact scope depends on the business. The important point is that procedures should be connected to actual responsibilities. A company should not create an SOP simply because it sounds like something a compliant company should have. It should create or maintain the procedure because someone needs a reliable way to perform and manage an activity.

What brand owners should ask about their manufacturers

If you use a contract manufacturer, ask:

• What procedures apply to our products?
• How do you train employees on those procedures?
• How are procedures updated?
• How are changes communicated to us?
• How are monitoring records maintained?
• How are deviations handled?
• How are corrective actions documented?
• How is verification performed?
• What information should our company maintain?

You do not need to duplicate the manufacturer's entire SOP library. You need enough visibility to understand how the systems supporting your products operate and where your responsibilities begin and end.

What if you discover that your SOPs are not being used?

Start with one. Do not attempt to rewrite the entire compliance manual overnight. Choose an important procedure. Observe the actual process. Talk to the employees. Compare the process with the document. Review the records. Identify the differences. Then determine:

• Does the operation need to change?
• Does the procedure need to change?
• Does training need to change?
• Does the record need to change?
• Does management need to clarify responsibility?

That turns a vague compliance concern into a manageable improvement project.

The best procedure may be the one employees actually want to use

That does not mean making the procedure casual. It means making it practical. Clear. Accurate. Accessible. Relevant. Specific enough to guide the activity. Flexible enough to reflect legitimate operational differences where appropriate. And connected to the records and responsibilities surrounding it. A procedure should not exist only to satisfy a checklist. It should help someone do their job correctly.

When FSVPServices.com helps turn procedures into working systems

FSVPServices.com supports food companies and brand owners with compliance documentation and implementation services designed around the actual operation—not simply the document library. Depending on the organization's needs, support may include:

• Brand owner compliance SOP templates
• cGMP compliance documentation and training
• cGMP implementation setup
• Food safety plan development and implementation
• Food safety plan reanalysis and updates
• Hazard analysis development and evaluation
• Preventive controls program development
• Preventive control monitoring and management
• PCQI oversight
• PCQI-managed compliance per product SKU
• Supplier compliance management
• Corrective action and incident response
• Food handler qualification and training compliance
• Records compliance management
• Training records and documentation compliance
• Remote PCQI services for monitoring procedures and record review
• Remote PCQI services for corrective action procedures
• Verification, validation, and effectiveness review
• Ongoing FSQA compliance management

Some companies need procedures developed from scratch. Others already have procedures but need them aligned with the actual operation. Some need employee training and implementation support. Others need recurring PCQI oversight and record review. The appropriate service depends on the company's products, processes, facilities, employees, manufacturers, and existing compliance system. The objective is simple: the procedure should not merely exist. It should work.

A procedure is only finished when the process works

Writing the SOP is the beginning. Then someone has to train the people. The people have to implement it. The records have to demonstrate implementation. The records need appropriate review. Problems need corrective action. The procedure needs to change when the operation changes. And the organization needs to verify that the system remains effective. That is how a document becomes part of a functioning food safety system. So if you open your compliance folder today and find dozens of beautifully written procedures, ask yourself one question: If I walked onto the production floor, would I see these procedures being used? If the answer is yes, your documentation is doing its job. If the answer is no, do not simply write another procedure. Find out why. Because the biggest compliance gap is sometimes not the procedure you forgot to write. It is the procedure everyone stopped using.