InnerWeb
Skip to main content

Health declaration at guest entry: how to document it without a queue

A food production plant certified to the BRC standard must know whether a guest entering production has no symptoms of an infectious disease, and must be able to show this to an auditor. A paper form at the gatehouse creates a queue and a pile of sheets. This guide shows how to move the health declaration to the registration station so that proof is created at every entry.

0
gate entries for a person without a declaration in the state required declaration
Source: karta
2 s
time for the label print card to close after printing
Source: karta

Why food plants collect health declarations

In food plants the hygiene of people entering production is part of the food safety system. The requirements of the BRC standard cover the health control of employees and visitors, and the auditor checks whether the plant can show that a person entering confirmed the absence of symptoms before entry. Having a procedure is not enough: a record is needed that can be found by surname and date.

A typical problem is the gap between procedure and practice. The procedure requires a form, but at high traffic the gatehouse skips it for known suppliers, and the paper declarations end up in a binder from which nothing can be pulled during an audit. The registration system solves this by enforcing a step before entry.

How the system enforces the declaration before entry

When the plant requires a health declaration, the scan returns the state required declaration. In this state the system does not record a gate entry and does not add the person to the group. The person therefore cannot pass the gate or appear on the list of people on site until the declaration is made.

For the reception there is an intermediate step. Before the code is printed, the reception marks that the person made the declaration verbally, and only then is the label printed. This solution is practical for guests who arrive without an invitation in advance: a human asks the question, but the confirmation stays in the system.

Steps of the declaration process and their closing time on the system side

Steps of the declaration process and their closing time on the system sideBar chart: 0 gate entries without a declaration, label card closing after 2 seconds, 2 default form languages.012wartoscGate entries without declaration: 0 wartosc0Gate entries withoutdeclarationLabel card closing (s): 2 wartosc2Label card closing (s)Default form languages: 2 wartosc2Default form languages
Source: Documentation of the guest registration station

How to avoid a queue at the gatehouse

A queue forms when the declaration is made only at the gate. The most effective way is to move it in time: the guest registers before the visit, and the declaration is part of that registration or of the step at collecting the identifier. At the gate the scan takes seconds, because the state is already known.

In a plant that serves guests in several languages, remember the language of the form. The list of languages in the reception form is a plant setting (by default Polish and English), so a plant with guests from abroad adds the versions it needs before it starts requiring the declaration.

  • Declaration as part of registration before the visit.
  • Verbal confirmation by the reception before printing the label, when the guest did not register earlier.
  • State required declaration at the scan, when the step is missing.
  • Language list of the form adjusted to the plant's guests.

Proof for the BRC auditor

The auditor will ask three things: whether the requirement is defined, whether it is enforced, and whether a record can be shown for a specific person and date. The first answer is the plant procedure and the setting of the requirement in the system. The second is the behaviour of the gate: without a declaration there is no entry record. The third is the history of the guest account with entry records and confirmation.

The system delivers proof for the audit, but it does not replace the plant's decision on hygiene rules. The plant decides which questions it asks guests, whom it sends home and how long it keeps the records. InnerWeb supports meeting the requirement, it does not guarantee compliance with certification.

Label in the state required declaration

Printing a label for a guest who requires a declaration makes sense only after confirmation. A label on a DYMO printer prints by itself when the DYMO Connect service responds, a LabelWriter printer is connected and the logo has been loaded. If the reception wants to check the data first, use the parameter auto=0, which forces a preview only.

It is worth rehearsing two scenarios with the reception: a guest with an invitation and a declaration made earlier, and a guest without an invitation. In the first case the state is green at once, in the second the reception performs the step of verbal confirmation. Record both scenarios in the station instruction.

Checklist

Video

Frequently asked questions

What happens when a guest has not made the declaration?

The scan returns the state required declaration. The system does not record a gate entry and does not add the person to the group.

Can the reception replace the form with a verbal confirmation?

Yes. Before the code is printed, the reception marks that the person made the declaration verbally. The plant's rules decide whether this is sufficient for a given group of guests.

Does the system guarantee compliance with a BRC audit?

No. The system delivers proof for the audit and supports meeting the requirement, but the hygiene rules are set by the plant.

Let us attach the declaration to the registration station

Book a call with the quality and security departments. We will show the state required declaration on the scenario of your entry to production.

Let's talk