You Inherited an FSMS That May Be Broken: How to Understand It and What to Do About It

A Short Story Every FSMS Practitioner Should Hear

A new FSMS practitioner recently inherited a system that had passed its last audit but was quietly drifting. The previous practitioner didn’t pass it off well, and leadership waited too long to bring in a replacement. When the new practitioner finally stepped in, they made the most common mistake I see:

They rewrote the system before they understood it.

New forms. New procedures. New calendars. New flowcharts. They wanted to “make it theirs.” They wanted their brand on the system.
But the consequence?

The new special of the day at the company was a steaming plate of CB driven corrective actions.

Why?

Because the new practitioner did not identify periodic items that were past due and correct them.

The system’s routine cycles slipped, and the CB noticed. Not because the practitioner didn’t care — but because they tried to fix the system before they understood it. This pattern is common — and preventable.

How to Understand the FSMS You Just Inherited

Taking over an FSMS is deceptively difficult. The key is knowing the right order of operations so you diagnose the system without accidentally dismantling it.

Here is the correct, streamlined sequence.

1. Assess the Current State Before You Touch Anything

This is the first and most critical step. You evaluate:

• what is past due
• what corrective actions are open or overdue
• what periodic requirements have slipped
• whether HACCP is actually being executed

This is the diagnostic phase. You are not fixing. You are not rewriting. You are not “making it yours.” You are learning what you inherited. If you skip this step, the FSMS will drift — and the CB will be happy to point it out.

2. Review Procedures After You Understand Execution

Once you know how the system actually runs, then you evaluate the documented system. You ask:

• What procedures exist?
• Are they followed?
• Do they match operations?
• Do they align with HACCP and regulatory requirements?

A procedure not followed is fiction. Daily execution tells you what the system is. Documentation tells you what the system claims to be. Your job is to reconcile the two — not rewrite blindly.

3. Improve the System Only After Continuity Is Restored

Most FSMS failures happen because practitioners rewrite before they understand. Rewriting comes after:

• past due items are corrected
• corrective actions are closed
• HACCP execution is verified
• periodic requirements are restored
• continuity is stable

Only then do you improve the system. Only then do you put your stamp on it. And if the system is too broken to diagnose alone?

Bring in a consultant

There is no shame in needing help. There is only risk in pretending you don’t. A good consultant helps you:

• understand what you inherited
• restore continuity
• avoid breaking the system while trying to fix it

If the FSMS is drifting, a consultant can prevent months of pain – and prevent a stack of CB driven corrective actions from becoming a full-blown crisis.

The Punch Line

When you inherit an FSMS, putting your brand on it is not the right first step. Assessing it is.

The system may not have been passed off well. Leadership may have waited too long to replace the last practitioner. But none of that changes the first rule:

You don’t fix a broken FSMS by rewriting it. You fix it by understanding it, running it, and restoring continuity before you change anything.