At the gatehouse: the guest is there, the permit is not
Morning at the gatehouse of a production plant. A representative of an external company arrives to inspect part of an installation and prepare a quotation. He will not carry out any work, so nobody has issued a work permit for him. He scans the code on his phone and the gate shows a refusal stating that a required permit is missing.
At that point the guard has three bad options: issue a work permit for work that will not happen, write the guest into a paper logbook outside the system, or send him away. The first clutters the permit register and weakens its value as evidence. The second creates a gap in the record of who is on site. The third wastes time for both sides.
What a planned visit is and what it removes at the gate
A planned visit is the equivalent of a work permit for one day, without a time window, for a person who arrives without work to carry out: for an interview, a quotation or measurements. The system treats it as a valid document allowing entry on the given day.
What a visit does not do matters just as much. At the gate it removes only the requirement for a work permit. Training, qualifications and an active account still decide whether entry is allowed. A guest who has not completed the introductory training will not get past the gate, and he will see the training on the kiosk or on his phone before entering.
- The visit covers one day and has no start or end time.
- Every visit has a host: an active internal employee of the plant.
- The gate verdict still checks training, qualifications and an active account.
- A refusal and an exit do not trigger a phone call to the host.
Handling time for 10 guests a week without work to carry out
Who can plan a visit
Visits are planned by the administrator, manager and occupational health and safety roles from the panel for external companies and guests. On the day of arrival, the guard can also plan a visit directly from the refusal card at the gate, but only for that day. This means the gatehouse does not have to call the administrator to move the matter to another day.
The external company coordinator cannot plan visits. This is deliberate: if he could, he would remove the permit requirement from himself, and the whole control would lose its meaning. The inviting side and the deciding side remain with the plant.
Step-by-step scenario
We describe the concept of the process in a production-type plant, not a specific implementation.
Version with advance notice
The purchasing manager knows that a supplier will come for a quotation next week. In the panel for external companies and guests, he plans the visit for the given day and selects himself as the host. The system can plan visits on any day from today, up to 377 days ahead and up to 34 days at once. A day on which the person already has a visit is skipped, so there are no duplicates.
Version with a refusal at the gate
The guest was not announced in advance. The guard opens the refusal card, selects a host from the list and plans the visit for today. The host list contains employees who have already invited someone, usually the inviters appear at the top, and the logged-in employee is always on the list (up to 89 entries). The next scan of the guest passes without a refusal.
What happens after entry
When the guest first enters on the day of the visit, the dispatcher automatically calls the host, once, with no retries. The call states who has arrived, from which company, through which entry point and for what purpose. If the host has no phone number in his profile, he receives a single email asking him to complete it.
Effect for the plant: figures from an illustrative calculation
Let us assume a plant where 10 people a week come for quotations and interviews that do not require a work permit. When handled by issuing fictitious permits, we assume 15 minutes per person on the side of the administrator and the guard, and with a planned visit 3 minutes. This is an illustrative calculation based on our own assumptions, not a measurement at a specific plant.
In this setup, handling time falls from 150 to 30 minutes a week. However, the more important gain is order in the data: the permit register contains only work that actually took place, and the visit register answers the question of which guests were on site and whom they came to see.
Conclusions for the gatehouse
First, a refusal at the gate should be the start of a procedure, not its end. Second, a visit is not a back door: training and qualifications work exactly as before. Third, the host is accountable by name, because that is who the system calls.
If you want to see this flow on an example from your own plant, we will show it in a demonstration using data close to your environment.
Checklist
Video
Frequently asked questions
Can a planned visit let a guest in without training?
No. A visit removes only the requirement for a work permit at the gate. Training, qualifications and an active account are still checked.
Can the guard plan the visit alone?
Yes, on the day of arrival, from the refusal card at the gate and only for that day. Visits for later days are planned by the administrator, manager or occupational health and safety.
Who answers the call from the dispatcher?
The host assigned to the visit. The call is made once, without retries, and a refusal or the guest's exit does not trigger it.
Can a guest have several visits in one week?
Yes, you can plan up to 34 days at once and up to 377 days ahead. A day on which the person already has a visit is skipped.
See a planned visit in a demonstration
We will show the flow from a gate refusal to the call to the host, using an example close to your plant.
Let's talk