InnerWeb
Skip to main content

Health declaration evidence for a BRC audit

An auditor does not ask whether the plant has a guest declaration procedure. They ask whether a specific person submitted a declaration on a specific day and what exactly they were shown. This guide explains which data the register records, how to read it during an audit and what to do so that the evidence is consistent from the gate to the archive.

5
channels writing to the same register
Source: InnerWeb feature documentation
256 bit
length of the SHA-256 hash of the text
14 days
period in the BRC declaration
Source: InnerWeb feature documentation

The obligation and the auditor's questions

The BRC standard for food safety requires every guest entering a clean production zone to make a daily declaration that they have not had an infection in the last 14 days and will report wounds, skin problems or stomach complaints. The key word is daily: a declaration from yesterday does not cover today's visit.

In practice the auditor asks four questions. Did this person submit a declaration on the day of the visit? Through which channel? What text was shown to them? And could a visit without a declaration have ended in entry? The evidence must answer all four, because an answer to only three leaves a gap.

What the register records

Each health declaration is recorded once per person per day. A unique key in the database guarantees that two entries for the same person and day cannot be created, and the day is counted in the Europe/Warsaw time zone, so the day boundary matches the local time of the plant.

Together with the entry the register records the channel and the SHA-256 hash of the text shown. The hash is evidence of the wording version: if the plant changes the text of the declaration, entries from earlier days keep the hash of the old version, and new entries carry the hash of the new one. The auditor can therefore establish what text the guest saw on the day of the visit.

A declaration can be submitted through five channels: the registration desk at the gate, reception, the security panel, training on a phone or kiosk, and the LivePermit portal. All of them write to the same register, so the auditor does not need to review five sources.

Evidence data recorded with the declaration

Evidence data recorded with the declarationBar chart: one entry per person and day, five submission channels, two language versions of the text012345countEntries per person and day: 1 count1 countEntries per person and daySubmission channels: 5 count5 countSubmission channelsLanguage versions of the text: 2 count2 countLanguage versions of thetext
Source: InnerWeb feature documentation: health declaration register

Text versions: Polish and English

The text of the declaration is a plant setting. A Polish and an English version can be provided, and an empty text is replaced by a general default text without the plant's name. For guests from abroad the English version is often a condition for the declaration to be understood.

When the text is changed, it is worth recording the date of the change in the quality documentation. The hash in the register allows the version to be reconstructed, but the document describing the change explains why the wording was changed, and that shortens the conversation with the auditor.

How to prepare the evidence step by step

Preparing the evidence takes several steps, which are worth doing before the audit rather than during it:

  • select a sample of days and people the auditor may ask about,
  • for each person read from the register the date, the channel and the hash of the text,
  • compare the hash with the version of the text in force on that day,
  • check that the guest's entry was recorded after the declaration was submitted,
  • prepare an extract in a form the auditor can review without access to the system.

What the register does not prove

The register proves that a declaration was submitted and what text was shown, but it does not prove the health status of the guest. It is the person's statement, not a medical examination. The auditor assesses the process, not the truth of every sentence.

When the requirement is switched on, a guest without today's declaration does not enter and the entry is not recorded. The gate then responds with the third verdict, a request for a declaration, with no entry record and no denial event. As a result the entry register contains no guests without a declaration, provided the requirement was switched on on the day of the visit.

Note the scope: the requirement covers people from external companies and guests. Internal employees and accounts without an assigned company are exempt, so they should not appear in the guest declaration register. It is worth preparing this answer in case the auditor asks.

At reception the oral declaration field is optional. Without a tick, an account and a badge are created with no declaration entry, and the gate collects the declaration later. An auditor who sees a badge without an entry should therefore look for the entry only after the person has passed the gate.

Checklist

Video

Frequently asked questions

Does the SHA-256 hash reveal the content of the declaration?

No. The hash is a fingerprint of the text, from which the text cannot be reconstructed, but it allows checking whether a given version is identical to the recorded one. The plant keeps the text of the version in its settings and documentation.

Does a declaration from one day apply to the next day?

No. The declaration is daily and is recorded once per person per day, so on the next day the guest submits it again.

What if a guest submitted the declaration through a channel that was not planned for?

All channels write to the same register, so the entry is the same regardless of the channel through which it was submitted. Only the channel field differs.

Sources

Let's prepare the evidence for your audit

Book a talk with InnerWeb and we will show the declaration register, the text hash and an audit extract on the example of a food plant.

Let's talk