SQF from Scratch: 2.1 Management Commitment, 2.1.1 Food Safety Policy

* * * * *

This article series is a deep dive into each individual SQF element. Not just what the code says but what’s actually being asked, how it makes our products safer, and how that element looks in practice both inside and outside the audit. Personnel new to SQF seeking implementation and those reviewing existing systems should both benefit from a methodical study of each element, and how we can truly embrace the code and share it with internal and external customers.

Remember, the goal is not “Audit ready 365”, it’s to know that our facility embraces globally recognized best practices to maintain food safety. Because of this, as we dive into each element, we must always remember the quality management system golden rule: Never make systems to “pass audits”. Make systems that work for your company that help it make safer/higher quality products more efficiently.

2.1 Management Commitment

Management commitment is the pre-requisite to company culture. Whether talking about safety culture, lean culture, continuous improvement culture, anti-discriminatory culture, ethical business culture, or food safety culture, company direction and leadership begins with those holding the purse strings at the top.

The fact that this is our FIRST element is not a mistake, it’s an acknowledgement that this process will have no legs if it is not supported by those in control of the business. SQF has taken the same approach that successful safety, lean, and corporate responsibility initiatives have, wherein you begin with missions and core values that provide a compass for company priorities, especially when you get stuck back in the day-to-day.

The code:

2.1 Management Commitment

2.1.1 Food Safety Policy (Mandatory)

2.1.1.1 Senior site management shall prepare and implement a policy statement that outlines as a minimum the:
i. The site's commitment to supply safe food;
ii. Methods used to comply with its customer and regulatory requirements and continually improve its food safety management system; and
iii. The site's commitment to establish and review food safety objectives.

2.1.1.2 The policy statement shall be:
i. Signed by senior site management;
ii. Made available in language understood by all staff;
iii. Displayed in a prominent position; and
iv. Effectively communicated to all staff

What’s the point? How is this making our product safer?

Food safety procedure is what we tend to think of when we consider GFSI certification, a.k.a. all the stuff we should/need to get done. But each element of the code begins with “policy”; we’re asked to define our values as a company, from which our actions and priorities will follow.

SQF doesn’t begin the code with with any specific rule or task, but by asking us as an organization to establish food safety as part of our company’s core values. Not just a series of forms or tasks to be completed, but a wholistic view that when we strategize and determine the direction our business will take, food safety is going to be just as much a part of that discussion as finance.

Accepting and committing to food safety as a senior management value empowers departments, teams, and individuals to also treat food safety as a priority in their work. It shows all levels of the organization that GFSI certification isn’t just a pile of requirements, but a representation of what leadership is going to look for when they identify high performers and reliable employees.

What am I being asked to do?

You need a sort of company values/mission statement style document, you need the top representatives at your company site to review and sign it, and it needs to be posted and visible to your workforce.

Ideally, take some time to work with management to make something unique to your company. Maybe it’s formed on customer issues in the past, or ties into your existing mission statement. At the end of the day, there are some specifics that you, the SQF practitioner, are going to want to stick in there. Our standard approach is going to be taking the code line by line and making sure that language is represented or even mirrored in our documentation.


Posted Image

Whenever SQF asks for a policy, you have two objectives. First, that the people who are leaders supporting the policy know and embrace it. Second, that you have included language clear enough that you can defend your policy to an auditor who may just be using the code to “tick the box”. Below is an example policy that simply parrots the actual code. This will work very well in an audit but is not tailored specific to any particular company. Ideally your policy will reference your specific products and challenges.

I. Policy
a. [Company Name] is committed to manufacturing foods that are safe and compliant with both our customer and regulatory requirements. We will do this by:
i. Ensuring that adequate resources are available to support the continuous improvement of our food safety management system.
ii. Establishing and reviewing food safety objectives with senior site management.
iii. Ensuring we remain informed in new regulatory updates, customer requirements, or new technologies that support the mission of safe food.

To make this available, stick it into your SOP’s and maybe regular training. But it’s common (therefore expected by auditors) that it’s incorporated into signage. A simple way to do this is to build a sign in Microsoft PowerPoint (which will create a vector image that will scale indefinitely with size and still print well), then use a local print shop to print a laminated sign (or order a fancier sign if you prefer).

Posted Image

Get that somewhere visible for all staff and you’re good to go!

How will this be audited?

Auditors are going to look at the document, how it’s made available to your staff, and whether anyone on your production floor knows what it is and where to find it. If they talk to several new temps who say, “no idea, I was just put out on the line”, that’s going to be a potential issue. For the most part, effective implementation and evidence of management commitment is going to be more covered by 2.1.2 Management Responsibility.

Typically points of contention will be when auditors disagree with the language in your policy, that’s fine as long as you can defend it! Make sure your policy obviously covers all the components identified in the code, and don’t worry about an auditor who wants to go after semantics. It isn’t law if an auditor claims “you didn’t say continuously improve” when your statement says, “our system is going to be flexible and achieve the highest quality possible to support our customers”. OF COURSE that means you’re going to review and improve it! Back it up with evidence that you actually do and feel free to let the auditor grouse about how they would have written something different.

It’s not their company, their liability, its yours. And the opinion of a single audit should not change the way your entire facility communicates its food safety values from the top the other 364 days of the year. Modifying your mission statement based on auditor preference violates our golden rule.

Author Biography:

Posted Image

Austin Bouck is a food safety consultant and manufacturing supervisor in Oregon, USA. You can find more food safety resources and discussion on his website, Fur, Farm, and Fork, as well as contact information for consulting services.