When the SOP Says One Thing and the Production Floor Does Another

The SOP says one thing. The production floor does another. On paper, the process is clear. In reality, employees have developed a different way of doing the work. Maybe the procedure says a check happens every hour and the employee checks it every two hours. Maybe the SOP requires one form and the production team uses another. Maybe the procedure says a supervisor reviews the record, but in practice the review happens electronically. Maybe the SOP identifies one person as responsible, and that person changed roles months ago. Nobody necessarily intended to create a compliance problem. The operation simply evolved. The document did not. And now the company has two versions of reality: the process written in the SOP, and the process happening on the production floor. The question is not simply which one is right. The question is: Why are they different, and what needs to happen to bring them back into alignment?

The production floor usually tells you what is really happening

A procedure can look perfect in a compliance folder. It can have a clear title, a document number, an approval date, defined responsibilities, detailed instructions, forms, references, and revision history. But none of that tells you whether employees actually use it. The production floor does. That is why one of the most useful compliance exercises is also one of the simplest: go watch the process. Do not begin by asking employees whether they follow the SOP. Watch what they actually do. Then compare that activity with the written procedure. That is where the real gaps often become visible.

The mismatch does not automatically mean the employees are wrong

This is an important distinction. When the SOP and the production floor disagree, the immediate reaction can be: “Employees are not following the procedure.” Sometimes that is exactly the problem. But there are other possibilities.

• The process may have changed.
• The equipment may have changed.
• The staffing structure may have changed.
• The manufacturer may have changed the workflow.
• The original SOP may have been impractical.
• A more effective control may have been introduced.
• The employee may have been trained on a newer process that was never incorporated into the document.
• The procedure may simply have been written without enough understanding of how the operation actually works.

Before deciding who is wrong, find out why the difference exists.

The dangerous assumption is that the document is automatically the truth

A written procedure has authority because it is controlled documentation. But that does not make every sentence permanently correct. Food operations change. Processes change. People change. Equipment changes. Suppliers change. Products change. A procedure that was accurate when written can become inaccurate later. That is why document control is not only about preventing unauthorized edits. It is also about ensuring that controlled documents remain aligned with the operation.

The opposite problem is just as serious

Sometimes the production floor is doing something different because the documented process was never properly implemented. Employees may have:

• Never received adequate training
• Received incomplete training
• Learned the task informally
• Developed shortcuts
• Been given conflicting instructions
• Been provided an outdated form
• Never been shown where the SOP is located

In that situation, changing the SOP to match the production floor could make the system worse. The organization may need to correct the implementation instead. That is why the right answer cannot be determined simply by comparing two documents. You need to understand the actual process, the applicable requirements, the food safety rationale, and the reason for the difference.

Start with one question: “What actually happens?”

Take a single activity—for example, monitoring a preventive control. Do not begin with the SOP. Ask the employee: “Show me how you perform this activity.” Watch.

• What do they check?
• Where do they check it?
• When do they check it?
• What equipment do they use?
• What information do they record?
• What happens if the result is outside the established requirement?
• Who do they tell?
• Where does the record go?

Then compare what you observed with the SOP. This creates an objective picture.

Then ask: “What does the SOP say?”

Now review the written procedure. Does it describe the same activity? Does it identify the same employee? Does it specify the same frequency? Does it use the same equipment? Does it require the same record? Does it define the same response to a deviation? Does it identify the same reviewer? The differences become your starting point. Not your conclusion.

The three-way comparison

A particularly useful approach is to compare three things.

The SOP

What should happen?

The employee

What actually happens?

The record

What does the documentation show happened?

These three should generally tell a consistent story. If they do, the process is likely well aligned. If they do not, investigate why.

• SOP says one thing, employee does another — possible training, implementation, process-design, or document-control issue.
• Employee does one thing, record shows another — possible recordkeeping or implementation issue.
• SOP and record agree, employee does something different — possible training or execution issue.
• None of the three agree — the process likely needs a deeper review.

This simple framework can reveal significant gaps without starting with blame.

The frequency problem

One of the most common mismatches involves timing. The SOP says “monitor every hour.” The employee says “we check it at the beginning and end of the batch.” Now there is a significant question. Why? Maybe the production process changed. Maybe the original monitoring frequency was established under different operating conditions. Maybe the employee misunderstood the requirement. Maybe the actual process does not provide a practical opportunity to perform the check hourly. Maybe the written requirement is still appropriate and the employee is simply not following it. You cannot resolve that by guessing. The organization needs to evaluate the reason for the difference and determine the appropriate action.

The form problem

Another common mismatch involves records. The SOP says “record the result on Form PC-01.” The employee uses a production log. Why? Maybe Form PC-01 was replaced months ago. Maybe the production log captures the same information more effectively. Maybe employees were instructed verbally to use the production log. Maybe nobody updated the SOP after the form changed. Now the question is not “Why didn't the employee use the form?” It is: “Which record is the controlled record, and does the procedure accurately identify it?” That is a document-control issue worth resolving.

The responsibility problem

Suppose an SOP says the production supervisor reviews the monitoring records. But the company reorganized six months ago. Now the quality coordinator performs the review. Everyone knows this. The records show the quality coordinator's review. The SOP still identifies the old role. That may seem minor. But it creates ambiguity. Who is actually responsible? Is the current role appropriately assigned? Was the change evaluated? Was the SOP updated? Was the new person trained? This is exactly the kind of issue that becomes obvious when documentation is compared with actual operations.

The “shortcut” problem

Sometimes employees develop shortcuts because the official procedure is unnecessarily difficult. Imagine a procedure requires an employee to record information on a paper form, transfer it to a spreadsheet, have a supervisor sign the paper form, scan the form, and upload it to a shared folder. The production employee eventually creates a simpler workflow. They record the information directly in a digital log. From the employee's perspective, they improved efficiency. From management's perspective, they bypassed the official process. This is where the organization needs to ask: Did the shortcut remove an important control, or did it simply expose an inefficient documentation process? If the latter, the solution may be to redesign the procedure.

Compliance should not reward inefficient paperwork

A common misconception is that a more complicated procedure is automatically more compliant. It is not. The purpose of a food safety procedure is to establish and support effective control. If unnecessary complexity makes the procedure difficult to follow, the complexity itself can become a weakness. A practical procedure should give employees enough information to perform the activity correctly while supporting the necessary monitoring, corrective action, verification, and recordkeeping requirements. The goal is not more steps. The goal is reliable control.

But “this is how we've always done it” is not enough either

The opposite mistake is to assume that the production floor is automatically correct because employees have been doing it that way for years. Experience is valuable. But established practice still needs to be evaluated. Ask:

• What is the food safety rationale?
• What hazard or requirement does the activity address?
• Does the current process adequately control the identified risk?
• What evidence supports the approach?
• Are the monitoring and verification activities appropriate?

If the current process is sound, document it. If it is not, correct it. The goal is not to preserve tradition. It is to maintain effective control.

The food safety plan can expose these mismatches too

The SOP is not the only document that can diverge from reality. The same issue can occur with:

• Food safety plans
• Hazard analyses
• Preventive control procedures
• Monitoring procedures
• Verification procedures
• Sanitation procedures
• Training materials
• Supplier procedures
• Corrective action procedures
• Product specifications

A food safety plan may describe one process while production has evolved. That matters because the food safety plan should remain connected to the hazards and controls associated with the actual operation. FDA's preventive controls framework includes requirements for hazard analysis, risk-based preventive controls, monitoring, corrective actions, verification, recordkeeping, and food safety plan reanalysis under specified circumstances. The practical lesson is straightforward: the documents need to keep pace with the operation.

A process change should trigger a compliance question

Suppose production changes a piece of equipment. The equipment performs the same basic function. The team assumes nothing important has changed. But the question should still be: Does this change affect any existing food safety or compliance documentation? That may include:

• Hazard analysis
• Food safety plan
• Preventive control procedures
• Monitoring procedures
• Verification procedures
• SOPs
• Training
• Records

Not every change requires every document to be rewritten. The point is that the change should be evaluated, rather than automatically ignored.

What happens when the manufacturer changes the process?

This is especially important for brand owners using contract manufacturers. The manufacturer may improve its production process. It may change equipment. It may change an ingredient supplier. It may change monitoring technology. It may reorganize responsibilities. The brand owner may not be directly involved in every operational decision. But the relationship should have a way to communicate significant changes and determine whether they affect the brand's products or documentation. That is part of having a managed manufacturer relationship.

Training is often the missing link

Sometimes the SOP is correct. The production process is correct. The problem is that employees were never adequately trained on the current procedure. This creates a simple but important chain:

Procedure updated → employees informed → training completed → activity performed → records maintained → implementation verified

If the SOP changes but the employee continues using the old method, the system is incomplete. That is why document control and training management should work together.

A new employee should not have to learn the unofficial process

Imagine a new production employee starts. They receive the official SOP. Then an experienced employee tells them: “Don't worry about that. We actually do it this way.” That sentence is a major warning sign. The organization now has two systems: the official system and the tribal system. The longer that continues, the more difficult it becomes to know which process is actually controlled. The goal should be for the official procedure to be close enough to the real workflow that employees can rely on it.

The production floor can improve your SOPs

This is the positive side of the problem. The production floor is not only where compliance gaps are discovered. It is also where better procedures can be developed. Employees know where the process is awkward. They know which steps are easily misunderstood. They know which information is difficult to record. They know where equipment creates problems. They know which deviations occur repeatedly. That knowledge can make the compliance system better. A strong procedure-development process listens to the people who actually perform the work.

The “walk the process” exercise

Choose one important SOP. Then physically follow the process from beginning to end.

1. Read the SOP

Understand what the document says.

2. Observe the activity

Watch the employee perform it.

3. Ask questions

Find out why the employee performs each step.

4. Review the records

Compare the documentation with what you observed.

5. Identify differences

Separate minor administrative differences from differences that could affect food safety or compliance.

6. Determine the cause

Was it training? A process change? An impractical procedure? Poor document control? An unauthorized workaround? Unclear responsibility?

7. Correct the system

Update the process, document, training, records, or oversight as appropriate.

8. Verify

Confirm that the corrected process is actually being implemented.

That last step matters. Changing the SOP does not prove that the problem has been solved.

The goal is alignment, not blame

When the SOP and production floor disagree, it is tempting to find someone responsible. That may be necessary in some circumstances. But the first objective should be understanding. Ask:

• What happened?
• Why did it happen?
• What does the operation need?
• What does the food safety system require?
• What needs to change?
• How will we know the change worked?

That approach turns a potentially adversarial situation into a system-improvement exercise.

What if the SOP is correct and the employee is not following it?

Then the response should be structured. Determine whether:

• The employee was trained
• The procedure was available
• The employee understood the requirement
• The task was feasible
• Supervisory oversight was adequate
• The deviation was isolated or systemic

Then take appropriate corrective action. Do not assume one employee's mistake means the entire system failed. But do not assume it was only one employee either. If five employees make the same mistake, the procedure or training may need attention.

What if the production floor is correct and the SOP is wrong?

Then update the SOP. But do not simply rewrite it to match whatever employees are currently doing. First evaluate the process. Confirm that it provides appropriate control. Confirm that responsibilities are clear. Confirm that monitoring and verification remain appropriate. Then update the documentation and train affected personnel. The goal is a controlled change—not a cosmetic edit.

What if both sides are partially right?

That happens too. The SOP may describe the correct control but not the practical way employees perform it. The production floor may have developed a better workflow but omitted an important documentation step. This is where the system can be improved. Keep the essential control. Improve the workflow. Update the procedure. Train employees. Update the record. Verify implementation. Now the written system and operational system can become one system again.

Your documents should tell the same story as your production floor

This is the real objective. If someone reads your SOP, then walks into production, they should recognize the process. If someone reviews the records, they should see evidence of that process. If someone asks an employee to explain the task, the employee should describe the same basic process. That creates alignment between what you say you do, what you actually do, and what you can prove you did. That is a much stronger compliance position than simply having a large SOP library.

A quick test for your operation

Choose one critical procedure and ask:

• Does the current SOP match the equipment?
• Does it match the employees' responsibilities?
• Does it match the actual workflow?
• Does it match the current form or digital record?
• Does the training reflect the current procedure?
• Do the records demonstrate the activity?
• Does the corrective action process match what actually happens?
• Has the process changed since the SOP was written?
• Does the food safety documentation reflect the current process?

If you cannot answer some of these questions, you have a useful starting point.

When the document and the floor finally agree

Something important happens when the system is aligned. Employees stop thinking “that's the procedure, but this is how we really do it.” Instead, they can think: “This is how we do it.” The SOP becomes useful. The training becomes easier. The records become more meaningful. Supervision becomes clearer. Verification becomes more effective. Corrective actions become easier to evaluate. And management gains confidence that the compliance system reflects reality. That is the outcome worth pursuing.

When FSVPServices.com helps bring the two back together

FSVPServices.com supports food companies and brand owners with compliance documentation, implementation, review, and ongoing management services. 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
• Remote PCQI services for process change evaluation
• Remote PCQI services for verification procedures and record review
• Verification, validation, and effectiveness review
• Ongoing FSQA compliance management

Some companies need an SOP developed from scratch. Others have procedures that need to be brought into alignment with the current operation. Some need employee training. Others need a broader review of the food safety system. And some need ongoing PCQI or FSQA support to make sure the system continues to stay aligned as the business changes. The objective is not to make the production floor conform blindly to a document. It is to create a controlled process that is technically appropriate, operationally practical, properly documented, and actually implemented.

The production floor is telling you something

When the SOP says one thing and the production floor does another, do not ignore the difference. It is information. It may be telling you that the SOP is outdated. That training is incomplete. That responsibilities changed. That the process evolved. That the documentation is impractical. That employees created an unofficial workaround. That a control is not being implemented as intended. Whatever the cause, the mismatch deserves attention. Because the strongest compliance system is not the one with the most procedures. It is the one where the written procedure, trained employee, actual process, and supporting record all tell the same story.