BRC version 9: what changes in the BRCGS Food Safety standard

BRC version 9 is Issue 9 of the BRCGS Global Standard for Food Safety, published on 1 August 2022 and applied to audits since 1 February 2023. It is not an overhaul: the structure of the standard and most of its requirements remain those of version 8. Version 9 mainly strengthens three areas - food safety culture, HACCP plan validation and equipment control - and clarifies expectations on supplier approval, food fraud and food defence, and incorporates the blended audit option. It applies to every site that is BRCGS Food Safety certified or seeking certification: food manufacturers and processors, co-packers, ingredient manufacturers, bottlers. The key point from the outset: it is not the number of requirements that changes most, it is the level of evidence expected for those that have changed.

In brief

• What "version 9" refers to : the 9th edition of the BRCGS Food Safety standard only. The other BRCGS schemes (Packaging Materials, Storage & Distribution, Agents & Brokers) follow their own numbering, with their own issues.

• Key dates : published on 1 August 2022, audits conducted against version 9 since 1 February 2023.

• The most visible changes : food safety culture plan, tighter HACCP validated before implementation, equipment and hygienic design, environmental monitoring with action limits, more tightly framed supplier approval, blended audit option.

• Who is directly affected : Quality teams, who own the documentation system, and Purchasing teams, who must produce supplier and raw material evidence.

• What to check : clause-by-clause interpretation is a matter for BRCGS and your certification body; a subsequent issue is in preparation at BRCGS.

• What Tracklab does : centralises supplier and product data, automates document collection, tracks expiry dates and uses AI to exploit document content. Not an ERP, not a certification body, not a regulatory monitoring tool.

Version 9 of the BRCGS standard: background and application date

An issue published in 2022, applied to audits since 2023

Version 9 (also called Issue 9 or BRCGS version 9) was published on 1 August 2022 by BRCGS. Audits conducted against this issue began on 1 February 2023 : from that date, certified sites were assessed against the requirements of version 9, no longer those of version 8. Both dates are documented by BRCGS in its publication announcement and repeated by training and certification bodies.

To put the standard's cycle in context:

This cycle of around four years explains the logic of the updates: BRCGS revises its standard issue by issue, incorporating developments in good practice, audit feedback and customer expectations. A site that is already certified therefore does not "retake" an audit solely to change version: it is audited against the issue in force on the date of its audit.

A subsequent issue is in preparation

In 2026, BRCGS communicated publicly on the development work for a subsequent issue (Issue 10), without announcing a publication date at this stage. In other words:

• BRC Food version 9 (the common name for the BRCGS Food Safety standard) remains the reference issue for audits;

• no date for switching to a later version is publicly known today;

• any timing information must be confirmed with BRCGS and your certification body, not inferred from an article, a forum or a third-party PDF.

Always check : the version applicable to your next audit, the date of your recertification cycle, and any position statements published by BRCGS, which clarify or modify the application of certain requirements between two issues. These documents are public and dated.

What changes between version 8 and version 9 of the BRCGS standard

Comparing the BRC version 9 standard with the previous issue makes it possible to target the requirements actually affected, rather than rereading the entire standard. BRCGS presents version 9 as an evolution of version 8 rather than a rewrite: the framework of the standard (senior management commitment, HACCP, quality system, site standards, product control, process control) is retained. The differences are concentrated on a few structuring themes.

Two readings are possible depending on your situation:

• if your documentation system is already mature, the transition is mainly an alignment exercise: rewording the procedures concerned, dating reviews, updating risk assessments;

• if your system relies on poorly documented intentions, the gap lies in producing written, dated evidence. It is rarely the most technical issue, but it is often the most time-consuming.

What changes in practice for Quality teams

Version 9 does not require everything to be rewritten, but it does require you to demonstrate what was sometimes only asserted. The points below correspond to the changes most frequently cited by training and certification bodies.

1. A documented and measured food safety culture plan

Clause 1.1.2 as published in version 9 requires senior management to define and maintain a plan for developing the food safety and quality culture. This plan must specify:

• the planned activities, with the people involved and the deadlines;

• product communication, training, employee feedback and expected behaviours;

• the indicators used to measure progress on safety, authenticity, legality and quality;

• a review of the effectiveness of the actions carried out, at least once a year.

The classic pitfall: producing a document once and then never updating it. The auditor will look for activities actually carried out, evidence of participation and an effective review - not a charter on the wall.

2. A validated HACCP plan, not just a constructed one

Validation means providing evidence, before implementation, that the selected control measures are capable of controlling the identified hazard. In practice, teams must be able to answer three questions: what data the validation is based on, who reviewed it, when it was redone after a change. A change of recipe, ingredient, supplier, packaging or line can render the previous validation obsolete.

3. Equipment documented from the design stage

On equipment, version 9 tightens three requirements that are inexpensive to meet upstream and costly to remedy downstream: having specifications, documenting commissioning, and demonstrating hygienic design choices (ease of access for cleaning, no harbourage points, suitable materials). Hygienic design guidelines published by recognised technical bodies provide a useful basis for objectifying these choices.

4. Environmental monitoring with action limits

The environmental monitoring programme must be based on a documented sampling procedure, defined action limits and trend analysis of results. The difficulty lies in distinguishing limits related to product safety from those that reflect drift in the production environment: this requires establishing and then adjusting limits, site by site.

5. Root causes, not just corrections

Root cause analysis is strengthened: correcting a non-conformity is not enough; you must explain why it occurred, verify that the action prevents recurrence and keep evidence of this verification. This applies to audit non-conformities as well as to customer complaints, incidents and internal audit findings.

Quality checklist to assess where you stand:

• The food safety culture plan exists, is dated, and includes activities, indicators and evidence of an annual review.

• Each HACCP validation states its data, its author and its date; changes trigger a review.

• Each critical piece of equipment has a specification and a commissioning record.

• The environmental monitoring procedure sets action limits and how exceedances are handled.

• Closed non-conformities include a root cause, an action and a verification of effectiveness.

• Procedures use consistent vocabulary on safety, authenticity, legality and quality.

What changes for Purchasing and supplier monitoring

This is where version 9 most changes the operational workload of Purchasing teams. Supplier approval remains risk-based, but the supporting evidence expected is more tightly defined.

1. A raw material risk assessment, by material or by group

Every raw material - including primary packaging - must be subject to a risk assessment covering safety, authenticity, legality and quality. This assessment must be updated when there is a change in material, process or supplier, when a new risk emerges, following a recall or withdrawal involving the material concerned, and at a frequency defined in the standard.

2. Better-documented supplier approval

Approval must cover the safety and quality of the material, as well as the supplier's traceability processes. The available means remain recognised certification (notably BRCGS, or another GFSI-recognised scheme), supplier audit or, within a limited framework, a questionnaire. Version 9 frames the latter: the questionnaire is reserved for suppliers assessed as low risk, it must be reissued at the planned frequency, and any significant change at the supplier must be reported in the interim. Where approval is based on a questionnaire, the supplier's traceability must be verified at approval and then periodically.

3. An approved list that can be used day to day

The list (or database) of approved suppliers must be up to date and accessible to the relevant staff, starting with those who receive goods. It is a simple point to address but regularly penalised: a correct list stored in a file that nobody can consult at the loading dock does not fulfil its purpose.

4. Performance monitoring, not just initial approval

Approval is a starting point. The standard expects ongoing supplier monitoring, based on defined performance criteria (delivery conformity, responsiveness to non-conformities, documentation quality, incidents). This monitoring requires data: dates, non-conformities, actions, statuses.

5. Raw materials traced through to acceptance

The list of raw materials must be linked to their acceptance criteria: goods-in checks, visual inspections, certificates of analysis per batch, certificates of conformity or analyses. Each expected check must be defined and its record available.

The common breaking point for Purchasing - and this is where version 9 and version 8 converge: supplier data (certifications, certificates, analyses, approvals) lives in mailboxes, shared folders and spreadsheets. The result: expired certificates discovered in the middle of audit preparation. A raw material risk assessment dating from the BRC version 8 standard is a warning sign: it must be reviewed, redated and linked to the material concerned.

A platform such as Tracklab serves exactly this purpose: centralising supplier and product data, automating document collection, tracking expiry dates and using AI to extract critical information from documents (certificate number and expiry date, scope covered, analysis results). The aim is not to replace the purchasing or approval decision, but to make it demonstrable at any time. Our BRCGS Food Safety certification offering details this foundation, and our BRC certification support walks through it step by step.

New documentation requirements to anticipate

Here are the families of documents that version 9 makes particularly visible during audits. The exact list of expected records must be read in the issue of the standard in force.

Purchasing and Regulatory checklist:

• Each raw material has a dated risk assessment assigned to an owner.

• Each approved supplier can be linked to evidence of approval that is valid as of today.

• Questionnaires are used only for suppliers documented as low risk, and carry a reissue date.

• The approved list can be consulted by goods-in staff.

• Certificates and approvals with expiry dates are tracked with alerts, not rediscovered during audit preparation.

• Supplier performance criteria are written down, not implicit.

How to obtain the BRC version 9 standard in French

1. Use the official BRCGS source

The standard is not a royalty-free document. It is downloaded via the BRCGS online store, and BRCGS states that reproducing or translating its publications requires written permission from the rights holder. Many teams search for the free French BRC version 9 standard : this is possible when the issue and language are available, but only through the official channel. The steps to follow:

1. create a "My Account" account on the BRCGS website - required even for a free document;

2. open the Food Safety standard product page in the BRCGS store;

3. choose the PDF format, then the desired language (French is available for several issues);

4. confirm the download and comply with the licence terms.

2. Understand the limits of the licence

BRCGS governs the use of the downloaded PDF: the licence covers one named user, with one electronic copy on one computer and the option of printing it. A document downloaded free of charge may not be passed on to third parties. In practice, a team of several people must therefore either have several accesses or organise consultation from the authorised computer.

Another often overlooked point: the English version remains the definitive reference for the audit. The French translation is a valuable working aid for operational teams, but in the event of differing interpretations, the reference text applies.

3. Beware of third-party PDFs circulating online

Copies of the standard and its guides circulate on unofficial websites. They present three risks: an obsolete issue presented as the current version, an unauthorised translation with discrepancies in meaning, and no traceability of updates. For a document that serves as the contractual basis for an audit, the source matters.

4. Obtain useful supplementary documents

Beyond the standard itself, three families of documents make preparation easier:

• the summary of key changes (Guide to Key Changes) published by BRCGS, which compares issue by issue;

• the position statements, published free of charge by BRCGS, which clarify the application of certain requirements (for example on unannounced audits);

• the documents from your certification body, which set out the audit protocol and grading expectations.

For schemes other than Food Safety - Packaging Materials, Storage & Distribution, Agents & Brokers - the logic is the same, but each scheme has its own issue: check the one that applies to you before ordering or downloading. If you are hesitating between several standards, our comparison which GFSI certification to choose and our article BRC vs IFS frame the decision.

Transition plan to version 9: the steps

A certified site does not have a formal "migration project": it is audited against the issue in force. The plan below therefore serves to close the gap between what version 9 requires and what your site demonstrates today.

1. Confirm the framework. Check with BRCGS and your certification body the issue applicable to your next audit, the date of your cycle and the position statements in force. This step avoids working on a false basis.

2. Read the relevant requirements, not the entire standard. Using the guide to key changes, list the version 9 requirements that affect your actual practices: culture, HACCP, equipment, environment, suppliers, food defence and food fraud, testing, internal audits.

3. Carry out a gap analysis, evidence by evidence. For each requirement identified, note what exists, what is missing and, above all, what cannot be demonstrated: a plan that has not been reviewed, an undated validation, a risk assessment not linked to a material.

4. Prioritise by risk and by effort. Separate what would block an audit (missing approvals, absent validations), what would weaken the grade (incomplete documents) and what falls under continuous improvement.

5. Address supplier and material data first. This is the largest body of work: certificates, analyses, specifications, risk assessments. Centralise, date and link each document to a supplier and a material.

6. Set up expiry date tracking. Supplier certificates, training, internal audits, equipment checks, annual review of the culture plan: each deadline must be dated and triggered by an alert, not by someone's memory.

7. Replay the auditor's journey. A mock audit, conducted under the same time constraints, quickly reveals whether documents can be found and whether answers are consistent with the records.

8. Maintain the evidence over time. After the audit, keep the same logic: each new piece of data feeds the same foundation. This is what distinguishes a certification obtained from a lasting certification - and it is the spirit of our article preparing for a BRC audit.

If your site is also subject to other private standards, the method carries over: our article on the changes in the IFS version 8 standard describes the same mechanics of issue, transition and documentation updates.

Next steps: what to decide now

Three decisions are enough to take version 9 beyond mere document monitoring.

1. Set the framework : applicable issue, date of the next audit, chosen audit option. To be confirmed in writing with your certification body.

2. Take stock of missing evidence : culture, HACCP, equipment, environment, raw material risk assessments and supplier approvals. A gap analysis lasting a few days provides more information than a month of rereading the standard.

3. Decide where the data lives : if your supplier certificates, analyses and risk assessments still live in mailboxes, the issue is not version 9, it is the traceability of your evidence. This is where a centralised foundation, with automated collection and expiry date tracking, genuinely changes the teams' workload - and the robustness of the file on audit day.

Useful sources

• BRCGS - Global Standard Food Safety (Issue 9)

• BRCGS - Position statements Food Safety Issue 9 (F926)

• BRCGS - Publishing & licensing: terms of use for publications

• Campden BRI - Guide to the key changes in Issue 9

• AFNOR Certification - BRCGS Food certification, food industry