InnerWeb
Skip to main content

Enabling the health declaration: implementation checklist

The health declaration requirement is disabled by default, and enabling it changes the gate verdict for every guest. The implementation coordinator should therefore go through a short checklist before switching the setting on. Below are eleven points with a comment on what each one protects.

5
channels for submitting a declaration
Source: InnerWeb feature documentation
11
points on the checklist
Source: this checklist

Before you enable it: setting and scope

The health declaration requirement is enabled with a plant setting in the administrator panel, without changes to the database. This makes the rollout easier, but it also means that once enabled the setting applies at once at all gates of the plant.

The requirement covers people from external companies and guests. Internal employees and accounts without an assigned company are exempt, because the document concerns guests. The coordinator should check that employee accounts have no external company assigned by mistake, as they would then be covered by the requirement.

Text and channels

The text of the declaration is a plant setting. The standard BRC requires a 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, so the text must express this clearly.

A Polish and an English version can be provided. An empty text will be replaced by a general default text without the plant's name, which works, but it is usually better to use the plant's own wording agreed with the quality department.

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. Before enabling the requirement, decide which of them the plant will actually run, and train the people who operate them.

Checklist points by area

Checklist points by areaDonut chart: two points on setting and scope, three on text and channels, four on gate reception and exit, two on evidence and trial runSetting and scope: 2 points (18.2%)Text and channels: 3 points (27.3%)Gate, reception and exit: 4 points (36.4%)Evidence and trial run: 2 points (18.2%)11pointsSetting and scope2 points (18.2%)Text and channels3 points (27.3%)Gate, reception and exit4 points (36.4%)Evidence and trial run2 points (18.2%)
Source: Breakdown of the checklist points on this page

Gate, reception and exit

Once the requirement is enabled, a guest with a badge but without today's declaration does not enter and the entry is not recorded. The gate gives the third verdict: it asks for the declaration. Guards must know that this is not an ordinary denial and direct the guest to the place where the declaration can be submitted.

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, because the label alone does not admit anyone. Reception does not need to stop the guest, but it should warn them that the declaration will be submitted at the gate.

The declaration applies to entry only. A person who is already on site can always leave, so they do not stay on the evacuation list for the nightly automatic sign-out. It is worth confirming this with a test at the exit gate.

Evidence and a trial run

Each declaration is recorded once per person per day, together with the channel and the SHA-256 hash of the text shown. Before enabling, it is worth making a trial declaration with a test guest and checking that the entry appears in the register with the expected channel.

The trial run is best done at one gate and on one shift before the requirement covers the whole plant. This way the first misunderstandings of security and guests come out on a small trial.

Commentary on the checklist points

The most common implementation mistake is switching on the setting without training security. The result is predictable: a queue at the gate in the first week and guests asking why they cannot enter. Two short briefings with security and reception solve most of these problems.

The second mistake is assuming the requirement will cover employees. It covers guests and people from external companies, while internal employees are exempt. If the plant wants the same for its own staff, that requires a separate procedure, not this setting.

Checklist

Video

Frequently asked questions

Does enabling the requirement need changes to the database?

No. It is enabled with a plant setting in the administrator panel, which is a configuration change, not a code change or a data change in the database.

Can the requirement be enabled for only one gate?

The setting is plant-wide. A trial at one gate is organised, for example by directing guests to that gate during the trial period, not by a separate setting.

What about guests who do not speak Polish?

The text can be provided in Polish and English. For other languages the plant should agree with the quality department how the declaration will be collected.

Let's go through the list together with your coordinator

Book a talk with InnerWeb and we will help you plan the enabling of the health declaration at your plant gate step by step.

Let's talk