Who these recommendations are for
The recommendations are addressed to the security chief preparing a QR gate pilot in a chemical plant, and to the health and safety specialist who co-decides on entry requirements. We assume the plant has already defined its induction training and permit rules, and that the gate only enforces them at the moment of the scan.
The recommendations describe a model, not a specific installation. Concrete thresholds and settings depend on the plant profile, and the values are set during implementation.
Four conditions that the system calculates itself
The gate verdict rests on four conditions checked at the code scan. The guard panel is used to operate the gate and verify people entering the site, and the result is unambiguous: approval, or refusal with a reason.
The four conditions are: a complete set of valid trainings, no missing qualifications for the work in progress, a permit or a planned visit for today, and an active account for the person. All of them are calculated from data that already exists in the system, so the gate does not create a new, parallel register of requirements.
- Trainings: the person has valid results for the required trainings.
- Qualifications: checked against the hazardous work in progress.
- Permit or planned visit: for the given day.
- Account: active, not blocked.
Sample distribution of refusals in the first days of the pilot
Recommendation 1: keep the four conditions as the default
During the pilot do not shorten the list of conditions. The reason is simple: the pilot should show what reality looks like with the full verdict. If you switch off qualifications or trainings, the guard will see approval for people who should not enter, and you will not learn how often the gate would really react.
A good practice is to record the number of refusals in the first two weeks and break them down by cause. Most often they show where the invitation process is incomplete, not that the gate is too strict.
Recommendation 2: a planned visit does not replace training
At the gate a planned visit serves as a one-day permit. It removes the requirement for a work permit, but trainings, qualifications and the account still feed into the verdict. The security team should know this rule, otherwise the first refusal for a guest with a correct visit will be taken as a system error.
It is worth preparing one sentence for the guard that explains the situation to the guest: the visit is registered, but the induction training is missing, and it can be completed at the registration desk.
Recommendation 3: add installation conditions only where law or standards require them
The installation level is used to add requirements that cannot be derived from the four basic conditions. An example is a health declaration required by food plants operating under quality standards: when the setting is on, a person from outside the plant who is not on site and has no declaration for the day receives a refusal with a reason. In chemicals, separate requirements for installation zones can play this role.
The rule: add only what has documentary justification, and record the owner of that decision. Every additional condition lengthens service at the gate and increases the number of questions to security.
Control questions before adding a condition
Does the requirement come from a regulation, a standard or the plant's instruction? Who has to approve the change? How will it be communicated to contractors in advance? If any answer is unclear, the condition should not go into the pilot.
Recommendation 4: decide what the guard may settle alone
Decide whether the guard may confirm a requirement verbally, as in the case of the health declaration, or only record the gap and refer the person to the supervisor. The fewer exceptions, the more consistent the entry log, so it is worth limiting exceptions to two or three clearly named situations.
Every refusal is saved as an event, so after a month of the pilot the team has data to review: how many refusals concerned trainings, how many qualifications, how many a missing permit.
Recommendation 5: measure the pilot result and decide on extension
The pilot should not end with the feeling that it works. Define three indicators: the share of scans ending with approval, the number of refusals by cause, and the time the gate takes per person. After two weeks compare them with the assumptions.
The sample calculation below assumes a pilot of one gate with 120 scans a day. If every tenth scan ends in refusal, the guard handles 12 refusals a day, and the causes of refusals will show which trainings or invitations need fixing before extending to more gates.
Pilot of one gate
| Parameter | Value |
|---|---|
| Scans a day | 120 scans |
| Refusal rate | 10 % |
| Refusal breakdown by cause | 6/4/1/1 refusals |
Result: 12 refusals a day, of which half are missing trainings
Note: Sample calculation; the cause breakdown is an assumption, not a measurement.
Checklist
Video
Frequently asked questions
Can I switch off one of the four conditions?
We do not recommend it during the pilot. The full verdict shows the real scale of gaps, and switching off a condition hides it.
Where are additional requirements added?
At installation level, through the facility settings, for example a health declaration requirement. The scope is set during implementation.
Are refusals recorded?
Yes. An entry attempt ended with a refusal is a separate event in the register, which gives data for review after the pilot.
Who should approve installation conditions?
The owner of the requirement, usually health and safety or the security chief, together with the person responsible for contact with external companies.
Plan a QR gate pilot
We will help you decide which conditions to keep as the default and which to add for your installation. Book a conversation with the InnerWeb team.
Let's talk