Who these recommendations are for and what the verdict means
The recommendations are addressed to the plant director and the managers responsible for safety, who at the design stage of the rules decide what the system should check at entry. They apply to plants where both own employees and external company staff enter the site, and some of them perform work of elevated risk.
In InnerWeb, the gate panel, after scanning a QR badge or an RFID card, shows a verdict on whether the person may be on the site. The verdict has four elements: valid trainings, qualifications for hazardous work, a permit in progress and an active account. Each of them can be treated as a necessary condition, but not every one of them should be such in every plant.
The function itself is only a tool. Whether the rules will be effective depends on the order of decisions: first the plant policy, then the configuration. The reverse order ends with rules that contractors bypass, because they do not understand why they exist.
Recommendations
The recommendations below are ordered from the most important. Each has a rationale that can be presented to the OHS department, security and the external companies.
1. Mandatory induction as an absolute condition
Treat the OHS induction training as a condition without which there is no entry. It is the only training that at the moment of the gate scan should decide on admission. Rationale: a person without the induction does not know the evacuation routes, assembly points or traffic rules for vehicles, and this information is needed from the first minute.
2. Additional trainings do not block the gate
Additional trainings beyond the mandatory induction are not treated as required at the gate check. Keep them as a requirement for specific permits and works. Rationale: the gate does not know the scope of today's work, so it should not refuse entry because of a training that concerns a completely different task.
3. Check qualifications in the permit, not only at the gate
When a work permit is created, the system automatically checks whether the assigned workers hold the required qualifications. This is the right place to control authorizations for hazardous work, because it is known there what work is to be performed. The gate repeats this check as an additional safeguard.
4. Active account as a technical condition
An inactive account usually means a person who has ended cooperation with the plant or the company. The condition is cheap and effective, provided the procedure for withdrawing access is run on an ongoing basis. Rationale: without it, the badges of people who have left keep working for months.
5. A permit in progress only where the work requires it
Not every entry requires a work permit. Set this element as a condition for zones and works where a permit is required, not for the whole plant. Rationale: too broad a rule stops suppliers, guests and drivers, who should not need a permit.
6. Set exceptions consciously and by name
When a selected company must be exempted from a requirement, for example for short deliveries, do it in the configuration as an exception with a justification, not by manually bypassing the gate. An exception in the system is visible in the audit, while bypassing the gate leaves no trace.
7. The scan record as evidence
The scan at the gate is itself a control act and records the entry. Make sure security scans everyone, including people known by sight. Rationale: exceptions based on recognizing faces end in holes in the data, and in case of an incident there is no proof of who was on the site.
Sample rollout plan for the rules: duration of stages
How to resolve disputed conditions
The most common dispute concerns trainings that someone would like to add to the gate because they consider them important. A good criterion is the question: does the lack of this training make it unsafe to be on the site, or only to perform a specific task? In the first case the condition belongs to the gate, in the second to the permit.
The second dispute concerns the hardness of the block. The plant may choose a full block or a supervised path, in which a person without training enters under supervision until the gap is closed. We recommend a hard block for high-risk zones and supervision in offices and in the yard. If the plant integrates with an access control system, the block can be moved to the physical passage, provided the vendor of that system allows it.
The third dispute concerns response time. The director has the right to expect that information about a gap reaches the right coordinator within an hour. The system aggregates notifications within a 55-minute window, so this expectation fits its behavior.
Risks of badly designed rules
Rules that are too hard cause queues at the gate and frustration among contractors. The side effect is bypassing the system: security lets people in without a scan to speed up traffic, and the whole control stops working. Rules that are too soft give a false sense of safety: the verdict is always green, because no condition is required.
The third class of risk is data. If a training result did not reach the system or was saved on the wrong account, the gate will refuse entry to a person who did pass the training. We recommend naming in the procedure the person who corrects such cases within one shift, and deciding what security does in the meantime.
The fourth class is lack of communication. Contractors should know the rules before their first arrival, ideally together with the invitation. A rule that they learn about at the gate looks like malice, while the same rule announced a week earlier looks like a standard.
The first 30 days: from rules to review
We propose a three-step introduction. First week: the rules switched on in observation mode, without a block, with a report of how many people do not meet the conditions. The next two weeks: a block for the mandatory induction and the active account, and during this time communication to external companies with a list of gaps. Fourth week: a review with security, OHS and coordinators, and a decision on extending the rules.
The review should answer three questions: how many times the gate refused entry, how many of these refusals were justified, and how many resulted from data errors. If the share of data errors is high, the data is fixed first, and only then are the rules tightened.
Checklist
Video
Frequently asked questions
Should every training be a condition for entry?
No. At the gate, what counts is the mandatory induction; additional trainings are not required at the gate check. Keep them for specific permits.
Where should qualifications for hazardous work be checked?
When the permit is created, the system automatically checks the qualifications of the assigned workers. The gate repeats the check as an additional safeguard.
Can a company be exempted from a requirement?
Yes, as an exception in the configuration, visible in the audit. The scan at the gate should not be bypassed.
How long should the rules be introduced?
We propose 30 days in three stages: observation, block, review. This gives time to fix the data before the rules are tightened.
Let's talk about conditional admission
We will show, using your plant as an example, how trainings and qualifications become a condition for entering the site. Book a short conversation or a demo.
Let's talk