InnerWeb
Skip to main content

Visitor health statement at entry: recommendations for the quality department

A BRC auditor asks about a specific day and a specific visitor, and the quality department must show the statement, not promise that it exists somewhere. Before the audit the head of quality can settle six things that turn the health statement register into evidence rather than an archive. Below are the recommendations with their rationale.

14 days
period of infection covered by the statement under the standard
Source: card
6
recommendations for the quality department
Source: card
2
language versions of the text: Polish and English
Source: card

Who it is for and why

These recommendations are addressed to the head of the quality department or the person responsible for the BRC standard in a plant producing food or packaging for contact with food. The standard requires every visitor entering a clean production zone to sign a daily statement that they have had no infection in the last 14 days and will report wounds, skin problems or stomach complaints.

The recommendations do not promise compliance with the standard. The system supports compliance and provides evidence for the audit, but the assessment belongs to the auditor, and the plant's procedure is written by the quality department.

Recommendations 1 and 2: settle who must sign

Recommendation 1: write into the procedure who signs the statement. In the system the statement is required from people from external companies and from visitors; internal employees and accounts without an assigned company are exempt, because the document applies to visitors. If the plant requires something from its own employees, it does so with a different document.

Recommendation 2: settle which entries are covered. The requirement applies to entry, not to presence: a person who is already on site may always leave, so that they do not stay on the evacuation list for the nightly automatic check-out. The auditor should hear this rule from you before asking why a person leaving was not held back.

Channels for signing the statement (illustrative split)

Channels for signing the statement (illustrative split)Pie chart of five channels: gate and reception one each, the security panel, training and the contractor portalGate and reception: 2 channels (40%)Security panel: 1 channels (20%)Training on a phone or kiosk: 1 channels (20%)Contractor portal: 1 channels (20%)5channelsGate and reception2 channels (40%)Security panel1 channels (20%)Training on a phone or kiosk1 channels (20%)Contractor portal1 channels (20%)
Source: Feature card: five channels for signing the statement, all writing the same register

Recommendations 3 and 4: the wording version and language

Recommendation 3: settle the text and its version. Each statement is recorded once per person per day (the day counted in the Europe/Warsaw time zone), together with the channel and a SHA-256 hash of the displayed text, which is the proof of the wording version. When you change the wording, the hash changes, so the register shows which version applied on a given day.

Recommendation 4: decide on languages. The text of the statement is a plant setting; a Polish and an English version can be entered, and an empty text is replaced by a generic default text without the plant name. For a plant with foreign visitors it is worth filling in both versions rather than relying on the default.

Recommendations 5 and 6: channels and a test before the audit

Recommendation 5: describe the channels. The statement can be signed at the registration station at the gate, at reception, in the security panel, during training on a phone or kiosk, and in the portal for external contractors. All of them write the same register, so the procedure can name a default and a backup channel without changing the evidence.

Recommendation 6: run a test before the audit. Pick one day from a week earlier, draw three visitors from the visit list and check whether each has a statement entry from that day. If one is missing, establish whether it is a process gap (the visitor entered without the requirement) or an exemption resulting from the role.

  • Pick a day and three visitors from the visit list
  • Find the statement entry from that day
  • Check the channel and the text hash
  • No entry: establish a process gap or an exemption

Pitfalls we see most often

The first pitfall is assuming that a statement collected at reception is enough. At reception the oral statement field is optional: if it is not ticked, an account and a badge are created without a statement entry, and the gate collects the statement later, because a label alone admits nobody. If the auditor asks for an entry, a badge is not enough.

The second pitfall is mixing up the gate requirement with a ban on leaving. The requirement is switched on in the panel and is off by default; until it is switched on, the gate does not stop a visitor without a statement. The quality department should know the date of switching on, because entries from before that date may come from other channels.

Video

Frequently asked questions

Can the quality department see which text was used?

The record contains a SHA-256 hash of the displayed text as proof of the wording version, so it is possible to establish which version applied on a given day.

How many statements can a visitor have on one day?

One. Each statement is recorded once per person per day, and the day is counted in the Europe/Warsaw time zone.

Is the requirement on from the start?

No. It is off by default and is switched on with a plant setting in the administrator panel.

Sources

Prepare the register for the audit

Book a conversation with the quality department. We will show the statement register for one day and rehearse the test with three visitors.

Let's talk