InnerWeb
Skip to main content

Vehicle pass for a guest: who is responsible, the inviter, the host or security

A guest arrives by car and nobody in the plant knows whether the person who invited him, the host on site or security at the gate is responsible for him. We propose a division of roles based on how the system records a visit: who plans it, who answers the phone, who scans and what each of them leaves in the register.

377 days
maximum planning horizon for a visit
Source: feature sheet
34 days
maximum number of days planned at once
Source: feature sheet

Three roles and three records

In a plant three roles usually overlap: the inviter, the host and security. The inviter is the person who wants to see the guest, plans the visit and knows its purpose. The host is an internal employee who is responsible for the guest on site. Security controls the entry and records it in the gate register. When these roles belong to one person, everything works, but in larger plants they blur, and a guest in a car becomes the first case in which nobody knows whom to call.

We recommend separating the roles at the level of rules, and leaving the system as the place of record: each role has one specific record that can be found afterwards. The inviter leaves the visit with a date, the host takes the phone call, and security scans and saves the gate entry.

Recommendation 1: plan the visit in advance

A visit can be planned from today for up to 377 days ahead, and no more than 34 days at once. In practice this means that the visit of a service technician, an auditor or a client should enter the system at the moment the date is agreed, not the day before arrival. Early planning gives the host time to complete a phone number and gives the dispatcher time to prepare the register.

A planned visit is the equivalent of a permit for one day, without a time of day. This means that for multi-day visits each day has to be planned separately within the permitted window of 34 days, and the limit of 377 days ahead sets the maximum horizon.

Visit planning limits

Visit planning limitsHorizontal bar chart: the planning horizon is 377 days from today, and no more than 34 days at one time.0100200300400daysHorizon from todayHorizon from today: 377 days377At one timeAt one time: 34 days34
Source: Feature sheet for planned visits

Recommendation 2: the host is always from the list of employees

Every visit has a host, an internal employee of the plant. The rule matters in practice: when something happens on site, security knows whom to call, without browsing invitations. The inviter and the host may be the same person, but in large plants it is worth separating them, especially when the inviter is an office employee and the guest works in the hall.

At the first entry of a guest on the day of the visit, the dispatcher calls the host once, without retries. A group of guests with one host results in one collective call after 30 seconds of silence within a 3-minute window. For the host this means one phone call instead of ten when the group arrives together.

Recommendation 3: complete the phone numbers

When the host has no phone number, the system sends him one e-mail asking him to complete the number, instead of staying silent. This safeguard does not replace order in the data: the plant should check once a quarter whether the hosts with the most visits have numbers.

A missing number surfaces only on the day of the visit, when the guest is standing at the gate. Then every minute of delay is visible to the drivers behind him. It is worth treating the number as part of the employee's profile, not as an extra field to fill in when it happens to be convenient.

Recommendation 4: a scenario for a machinery manufacturing plant

For a plant manufacturing agricultural machinery belonging to a global group, we describe a concept presented in a demo, not a deployment: guest registration at a kiosk with a QR code from the invitation, an isometric map of the hall, SOS and inactivity shown on the map. In such a setup the inviter sends an invitation with a QR code, the guest arriving by car registers at the kiosk at the entrance, and the host receives the phone call only at the first entry, not at every registration.

Such a division of roles simplifies the instruction for security: one sentence is enough to say who the host is and where the duty officer gets his number from. However, this solution needs to be agreed on the plant side, specifically who has the authority to plan visits, because that determines who stands in for the inviter during leave.

Recommendation 5: write the responsibilities down in one document

A one-page role card: who plans, who answers the phone, who scans, who escorts the guest out. It is worth adding what happens when the host is unavailable and who stands in for him. The system provides the register but does not decide who the deputy is.

A role card also makes it easier to prepare for an audit, because when asked who was responsible for a guest, the answer is written both in the rules and in the register.

Video

Frequently asked questions

Must the inviter and the host be different people?

No, but in larger plants it is worth separating them. The host must be an internal employee of the plant, while the inviter may represent the department that arranges the guest's visit.

Who receives the phone call when a group of guests belonging to one host arrives?

The host receives one collective call after 30 seconds of silence within a 3-minute window, instead of a separate call for each guest.

What should be done when the host has no phone number?

The system sends him one e-mail asking him to complete the number. The plant should, however, check periodically the numbers of the hosts with the most visits.

Let us agree the roles at your plant

In the demo we will show visit planning, the call to the host and the gate entry record. We will help you prepare a one-page role card.

Let's talk