InnerWeb
Skip to main content

Visitor health statement: a case from a packaging manufacturer

A corrugated packaging plant with its head office in Germany and a site in Poland had to prove to a BRC auditor that every visitor had signed a health statement on the day of the visit. The paper forms sat in a binder at reception, and the gate knew nothing about them. Below we describe how the statement became a condition of entry rather than a box to tick.

14 days
period covered by the statement under the BRC standard
Source: card
5
channels for signing the statement
Source: card
1
entry per person per day
Source: card

Starting point: a form in a binder

The plant makes corrugated board packaging that ends up in the food chain, so it works to the BRC Global Standard for Food Safety. 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.

Before the change the statement existed on paper. The receptionist printed a form, the visitor signed it, and the form went into a binder. The gate and security had no information on whether the visitor had signed, because these were two separate flows: paper at reception and a badge at the entrance.

In practice this caused three problems. First, on the day of an audit someone had to search by hand for the forms from a given day. Second, nothing stopped a visitor without a statement from entering the hall if they had a badge. Third, a plant with a head office abroad serves visitors in several languages, and the paper template existed in only one version.

What changed: the statement as a condition of entry

The change did not add another field to a form. It moved the decision to the gate. In InnerWeb the visitor health statement is a condition of entry: when the setting is on, a visitor without a statement for today does not get in, and the entry is not recorded in the register.

The requirement is off by default and is switched on with a plant setting in the administrator panel, without any change to the database. This allowed the plant to start visitor registration first and add the statement requirement only once reception and security knew the new flow.

The requirement applies to people from external companies and to visitors. Internal employees and accounts without an assigned company are exempt, because the document is meant for visitors, not for the core workforce.

The third verdict of the gate

When a visitor has a badge but no statement for today, the gate gives a third verdict next to admission and refusal: it asks for the statement. It records neither the entry nor a refusal event in the security log, so the log does not fill up with entries that are only a request to complete a step.

Five channels, one register

The statement can be signed through five channels: 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 channels write to the same register, so the auditor does not need to know which route the visitor took.

In this plant most of the change happened at reception. The oral statement field there 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. The receptionist does not have to hold up the queue when the visitor does not have a phone to hand.

  • Registration station at the gate
  • Reception
  • Security panel
  • Training on a phone or kiosk
  • Portal for external contractors

Evidence for the auditor: one entry per person per day

Each statement is recorded once per person per day. The day is counted in the Europe/Warsaw time zone, so a visit at 23:50 and a second one after midnight do not merge into one entry. Together with the statement, the channel and a SHA-256 hash of the displayed text are recorded, which is the proof of the wording version.

For the quality department this means that when the auditor asks about a specific day, the answer is the list of entries from that day, not a search through a binder. The system provides evidence for the audit and supports compliance with the requirement, but it does not replace the auditor's assessment or the plant's own procedure.

Effect and lessons for other plants

The effect is one of process, not of cost: the statement stopped being a separate flow running alongside the gate. If the statement is missing, the gate sees it and does not admit the visitor; if it is present, the entry has a date, a channel and a version of the text. We do not give savings in currency terms here, because this case contains no such measurements.

One limitation is worth remembering. The statement applies only to entry: 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. A plant introducing a similar requirement should write this into the security instructions, so that nobody holds back a person who is leaving.

  • Turn the requirement on after visitor registration is running, not at the same time.
  • Decide who is exempt: internal employees and accounts without a company.
  • Write into the instructions that leaving is always possible.
  • Check one day in the register before the audit.

Video

Frequently asked questions

Does the system open the gate after the statement is signed?

No. The system records the entry in the register after a scan of a QR badge or RFID card and gives a verdict, but it does not open the gate or barrier itself.

Do plant employees also sign the statement?

No. The requirement applies to visitors and people from external companies. Internal employees and accounts without an assigned company are exempt.

What if reception did not collect the statement?

An account and a badge are created without a statement entry, and the gate collects the statement later. The badge alone does not admit anyone.

Sources

Let's talk about visitor health statements

Book a conversation with the quality and security teams. We will show how the statement feeds the gate verdict and what the register looks like on the day of an audit.

Let's talk