BRCGS Manual: A Clear Guide to What Clause 3.1 Asks For

A BRCGS manual is the one place where a site’s procedures, working methods and practices are gathered together, and clause 3.1 of Issue 9 is what asks for it. This post explains what 3.1 requires, what does not belong in the manual, and why a copied manual fails at audit.

Two honest points first. The Standard itself is free: BRCGS lists a PDF of it on its site, so nobody needs to pay for the requirements. And no template can write your manual for you, because the manual describes what your site does. The toolkit mentioned at the end is independent of BRCGS.

What the BRCGS manual must do under clause 3.1

Clause 3.1 is short. Its statement of intent requires processes and procedures to be documented to support consistent application, training and due diligence in making safe product to the Standard. The sub-clauses then ask for three things.

1. 3.1.1: gather it together. Collect the site’s procedures, working methods and practices into one food safety and quality manual. It may be printed or electronic.
2. 3.1.2: use it. Implement the manual in full, and keep it, or the relevant parts, readily available to the staff who need it.
3. 3.1.3: make it usable. Procedures and work instructions must be legible, unambiguous, in suitable languages and detailed enough for the right staff to apply correctly. Add photographs, diagrams or other pictures where text alone will not do, for instance because of literacy or language issues. The pictures part is a “should”, not a “shall”.

Notice what is missing. Clause 3.1 does not prescribe a chapter list, a page count, a house format or a sign-off layout. It does not say the manual must be one document. The test is whether the site’s way of working is written down, implemented and reachable. Clause 3.1 is not one of the twelve fundamental clauses, though a weak manual tends to show up as findings elsewhere.

Why a copied BRCGS manual fails

Auditors check a manual against the factory. If the manual says a task is done one way and the operator does it another, that is a finding, whatever the manual says. Three things go wrong with copied manuals.

• They describe a different site. Another company’s metal detector test, line clearance or cleaning method does not match your equipment. The auditor asks the operator to show you the procedure, and the operator has never seen it.
• They promise more than you do. Copied wording that commits you to daily checks you run weekly turns a working practice into a non-conformity.
• They sit unused. Clause 3.1.2 asks for implementation, not just existence. A manual nobody reads fails the clause in spirit even if the document is perfect.

The fix is not to avoid templates. A good template gives you structure, clause references and prompts for what to describe. The content must still be yours, checked against what staff do. The same applies to our own toolkit: it gives you a starting point to edit, not a finished manual to file.

What goes in the BRCGS manual and what belongs elsewhere

The manual is not the whole system. Clauses 3.2 and 3.3 sit beside it for a reason.

A workable approach is a short manual that states how the system is organised and points to controlled procedures, work instructions and forms. The manual then stays stable while the procedures change.

Some topics belong in the manual’s index but have their own detailed home. Your HACCP plan is a required output of section 2 and is not rewritten inside the manual. Food safety culture has its own plan under clause 1.1.2. The manual simply says where each lives.

Document control and records: the neighbours of the BRCGS manual

An auditor who reads your manual may go on to clauses 3.2 and 3.3, so get them right at the same time.

Clause 3.2.1 asks for a document management procedure covering four things: a list of controlled documents with the latest version numbers; how documents are identified and authorised; a record of why changes were made; and how updated documents replace old ones. Electronic documents must also be held securely, for example through authorised access, amendment control or passwords, and backed up against loss.

Clause 3.3.1 asks that records stay legible, in good condition and retrievable. Alterations need authorisation and a recorded justification. Clause 3.3.2 asks you to define a retention period that considers legal and customer requirements and product shelf life, including any labelled consumer extension such as freezing. The floor is shelf life plus 12 months.

Watch for a controlled manual surrounded by uncontrolled copies: old printouts in the packing hall, a superseded work instruction on a noticeboard. Walk the floor and look for them before the auditor does.

Writing a BRCGS manual that works: a practical sequence

1. List what you actually do. Start from the clauses and the tasks on the floor, not from a blank page.
2. Decide the structure. Section numbers that follow the Standard’s nine sections make auditors’ lives easier, but nothing requires it.
3. Write at the level your operators read. Clause 3.1.3 expects suitable languages. If part of your workforce reads another language, translate the work instructions they use.
4. Add pictures where they help. Allergen changeover, line clearance and metal detector test pieces are good candidates.
5. Check each statement against practice. Take a section to the line and ask someone to follow it. Fix whichever is wrong, the document or the habit.
6. Control it. Register it, give it a version, set a review date, and remove old copies.
7. Train people to find their part. The manual is only available if people know where it is.

Update the manual when something changes: a new line, a new allergen, a changed supplier route, a revised position statement. Position statements bind as part of the Standard, and Part III 6.2 expects sites to turn them into action. Keep a register, and see our BRCGS audit checklist post for how an auditor reads across the whole system.

How the BRCGS manual shows up on audit day

An auditor may pick a task on the floor, ask the person doing it how it is done, then ask to see the written instruction and compare. The manual is tested through people, not through its contents page.

So prepare the people as well as the paper. Operators should know where their instruction lives and have used it. Supervisors should be able to explain why a step is there. Deputies for key managers should know the manual well enough to take an auditor to the right document without help. Those three habits cost little and remove most of the awkward moments.

Where the Standard and your manual meet

The BRCGS manual is also where you record the decisions you made about the Standard. Conditional parts depend on your site: section 8 applies if your 4.3.1 assessment finds production risk zones are needed, and section 9 if traded products are in scope. Your manual should say which apply, and why. An exclusion for traded products must also appear on the audit report and certificate, so the manual and the scope record should agree.

The free Standard is the place to check wording. Download it from BRCGS, but do not paste its clause text into your manual as if that were your procedure. A restated requirement tells the auditor nothing about what happens on your site.

If you want a structured start, the BRCGS Food Safety Toolkit includes a Food Safety and Quality Manual, a Document Control Procedure, a Master Document Register and a Records Control and Retention Procedure, within 123 templates (78 Word and 45 Excel) for $149. Edit every one to match your site.

Sample pages from the toolkit: Food safety and quality manual cover; HACCP food safety plan procedure; Product withdrawal and recall.

BRCGS manual FAQ

Is there a free BRCGS manual download?

The Standard is free from BRCGS, but it is the requirements, not a manual. A manual has to describe your own site. Anyone offering a free finished manual is offering a generic one, and a generic one will not survive an auditor asking an operator to show the procedure.

Does the BRCGS manual have to be one document?

Clause 3.1.1 asks you to gather procedures, working methods and practices into one manual, printed or electronic. How you build it is your decision, provided staff can reach the parts they need.

Can the BRCGS manual be electronic?

Yes. Clause 3.1.1 allows either form. Electronic documents must also meet the security and backup expectations in clauses 3.2.1 and 3.3.1.

How often must the BRCGS manual be reviewed?

Clause 3.1 gives no review interval. Review it when practices change, and align it with your document control procedure under 3.2. The HACCP plan has its own annual review under clause 2.12.3.