BRCGS Issue 9

The audit arrives, on any day.

A three-month window. No notice. Clausework holds the evidence against the clauses it satisfies, runs the internal audits, and keeps the pack ready to issue.

The platform — 1 min 50

Evidence that cannot be produced cannot be assessed.

The position today

Three days on site. Most of it documentary.

The evidence exists

Cloud drives, local drives, paper. Nothing connects a document to the clause it satisfies.

Preparation runs on recall

One person holds the map. It works until they are on leave inside the window.

Internal audits are the recurring work

Required across the year, run on paper, and the findings never reach the record.

The mechanism

Proposed by AI. Confirmed by name. Dated.

One document answers every clause it satisfies. Nothing counts until a person accepts it.

evidence · confirmation
Internal audits

Run the audit where the work happens.

Pick the clauses. The audit is written.

Questions written for each clause, with what to look for and what a finding sounds like.

Conducted and signed, separately

Nobody audits their own work unnoticed. When the two names match, the record says so.

Every run adds to the record

Findings land against their clause. Readiness is a by-product, not a project.

Ask the evidence

Answers, with the source attached.

Ask in plain language. Answers are drawn only from evidence a person has confirmed. Where nothing is held, it says so.

ask · grounded in confirmed evidence
Six questions

How exposed are you today?

Book a demo

When the window opens, the question is not whether the evidence exists.

It is whether you can produce it that morning, in the room, without the one person who knows where it is.

Thirty minutes, screen shared. We walk your position, not a script.

Used only to arrange the demo.

Questions

Answered plainly.

Does this replace our food safety management system?

No. If a full system is properly implemented, the audit-readiness overlap is substantial and we are unlikely to be worth the change. Clausework is built for sites running on shared drives, spreadsheets and paper.

Can it tell us what grade we will receive?

No. The certification body determines the grade after audit. Clausework shows an internal readiness position built only from findings your team has recorded, and labels it as such.

Who confirms the clause mappings?

A named person at your site. The system proposes with a confidence score and its reasoning. Nothing counts towards coverage, enters the pack or is cited until someone accepts it, and the decision carries their name and the date.

What happens to our documents?

They remain yours. Held in the UK or EU, encrypted, never used to train models, with a documented export path that survives the end of the contract.

Our audits happen on the floor. Does it work there?

Phone or tablet, offline capable, syncing when a signal returns. Paper entry afterwards remains an option.

We hold more than one BRCGS standard.

Evidence is held against topics as well as clause numbers, so one procedure can satisfy requirements under more than one certificate without being prepared twice. Food Safety is supported today.

What does it cost?

Priced per site, by size and number of users. We would rather quote against your position than publish a figure that is wrong for you.

What about Issue 10?

In development, with a transition period before audits begin against it. Requirements largely move rather than disappear — what expires is the mapping. Re-confirming mappings inside a system is a review task rather than a rebuild.