Starting point: reception, security and paper
The plant makes corrugated board packaging (a site in Poland, headquarters in Germany) and serves a steady flow of outside visitors: drivers delivering paper, machine service technicians, customer auditors and sales guests. Before the change, each of them stopped at reception or the security booth, filled in a slip of paper, and an employee copied the data into the register.
The site operates to the BRCGS standard, which requires anyone entering the production area to sign a health declaration. Paper declarations had to be collected, stored and found again during an audit. On top of that, the safety briefing was summarized verbally by security, so its content depended on who was standing at the gate that day.
- Guest data copied by hand from the slip into the register.
- Health declaration on paper, with no search by person and date.
- Safety briefing given verbally, with no proof that the guest had watched it.
- No language versions for people who do not speak Polish.
Assumption: the guest's phone as the only device
The plant adopted one firm assumption: the guest does not install an app. The phone camera scans the code and opens an address in the browser, and the token from the invitation or badge is passed to the screen as an entry parameter. For a driver visiting a customer for the first time and for only a few minutes, installing an app means abandoning registration or calling the dispatcher.
Browser-based registration has one more advantage for the IT department: there is no app version to approve, update and withdraw. Changing the wording of the declaration or the briefing is a data change on the installation, not the release of a new program version.
Time to find a person's account at the gate
One pass: invitation, declaration, video, label
The flow was designed so the guest never has to guess what comes next. The host is a plant employee who sends the invitation. The invitation contains a QR code, and after scanning it the guest sees their own data instead of an empty form.
The following steps run in the same browser session, without switching between tools:
- Confirmation of the guest's data and of the person they are visiting.
- Health declaration at entry, compliant with the BRCGS requirement, saved against the person and the visit date.
- Safety video briefing in the guest's language, and for groups with an assembly point assigned to that group.
- Print order for a QR label that stays with the guest for the duration of the visit.
- Notification to the host through the channel the plant chose for that role.
Health declaration without paper
The declaration is part of the flow, not a separate document. As a result, an auditor can see that the person signed it before entering on that day, without searching through a binder. The system provides audit evidence, while the assessment of compliance rests with the plant and its certification body.
Video briefing in language versions
The safety briefing is a film that the guest watches on their own phone or on a tablet at the gate. The film library lets you choose the language of the material independently of the interface language and turn on CC subtitles. Adding a new film is a data change on the installation, not a code change.
Availability of the training in a given language depends on the plant's materials: the system does not promise versions that the plant has not prepared.
Group guests and the assembly point
The hardest case for security is a group: a customer delegation or a service crew that arrives in one car and must enter together. The plant set up the briefing for groups too, and assigned the assembly point to the group rather than to a single person. As a result, during an evacuation security knows where to look for the whole crew.
Setting up groups required only that the host enter one visit with several people. The rule is simple: the fewer fields to fill in at the gate, the fewer errors in the register.
Result: time to find the account and proof in the register
The plant compared two ways of finding a person's account at the gate. The values in the calculation are working assumptions, to be replaced by measurement at your own gate: manually selecting the company and entering the login takes on average about 90 seconds per person, while scanning a badge with confirmation takes about 15 seconds.
A difference of 75 seconds per person across several dozen entries a day adds up to tens of minutes of security work, but repeatability matters more than time: every guest goes through the same steps and leaves the same trace in the register.
Conclusions for other plants with BRCGS or similar requirements
This case shows three things that can be repeated at another food or packaging plant. First, the health declaration and the safety briefing should be built into one registration flow, because separate documents drift apart over time. Second, a guest's phone is enough if the plant ensures HTTPS and access to the page from the guest network. Third, language versions of the material must be prepared before the gate opens, not after the first complaint from a driver.
Video
Frequently asked questions
Does the guest have to download an app?
No. The phone camera scans the code and opens an address in the browser, and the token from the invitation or badge is passed to the screen as an entry parameter.
Can the health declaration be stored in the system?
Yes, as part of the registration flow, against the person and the visit date. The system provides audit evidence, while the BRCGS compliance assessment is carried out by the plant and its certification body.
Is the briefing available in every language?
It depends on the plant's materials. The film library lets you choose the language of the material and turn on CC subtitles, but the system does not create versions that the plant has not prepared.
Want to shorten guest registration at your own gate?
Book a talk or a demo: we will walk through the guest flow on your materials and measure the time to find an account at your gate.
Let's talk