Visitor management for parking and controlled sites

Not necessarily. A journey can use a preregistered plate or a code sent before arrival.

Yes. The right can apply only to the lanes, zones and times needed for the visit.

Authorized staff can correct it or assist the driver through the lane procedure.

They can be configured with a defined end time so they do not remain active.

Not necessarily. A QR code displayed on a sign may open a registration or payment form on the visitor’s phone. A QR access credential is presented to a compatible lane scanner and checked against the configured permissions. Specify which role each code serves, who approves the visit and how approval reaches the entrance. A submitted form or payment confirmation alone does not establish that the barrier has received a valid access permission.

A visitor access permission defines where and when the visitor may enter; it does not by itself assign a numbered space or establish that a space is available. If your site requires reservations, allocations or capacity limits, include those rules and any supporting software interface in the project scope. Define what the visitor should do when the permitted parking area is full.

A repeated visit still needs an owner, purpose and defined access period. If a contractor returns on scheduled dates, agree whether staff renew a temporary right or use an approved recurring category. A permanent employee or resident permit follows a different policy. Avoid leaving an occasional visitor on an unrestricted list simply because they have visited before.

Define an arrival point where an unexpected driver can wait and request help. The responsible host or authorized operator checks the destination and site policy before creating or approving a temporary right. After-hours coverage, vehicle changes and access to restricted areas should be settled in the procedure rather than improvised at a blocked lane.

The host or authorized administrator should cancel or expire the visit’s access through the supported process, then check the associated plate or code status. Confirm how the change reaches each relevant entrance controller, how staff verify it has taken effect and what procedure applies if a controller is disconnected. A changed central record alone does not prove that every entrance has received the cancellation. Decide who informs the visitor and the receiving team so outdated arrival instructions do not cause confusion. If the visitor already entered, follow the site’s departure and assistance procedure rather than assuming cancellation alone resolves the vehicle’s presence.

First decide whether the site needs to identify individual arrivals or only authorize a defined group. A shared code can make it harder to distinguish who used it or to cancel one person’s access. Prefer separately assigned rights when individual control is required, and confirm the supported credential options. Do not assume a code is single-use or resistant to forwarding unless that behaviour is included and tested.

Provide the correct site address, entrance, permitted arrival period, credential instructions and a reachable assistance contact. Explain where a driver should wait if the plate or code is not accepted, and how to report a vehicle change before travelling. Keep these instructions aligned with the actual lane configuration and host responsibilities; a general building address may not identify the visitor entrance.

Lexoh uses a hybrid cloud and offline architecture. Its mesh network lets devices communicate locally when the internet connection is unavailable. For visitor access, commissioning includes the configured access rules, expiry and the handling of changes during an interruption. Local device communication and remote cloud administration have different connectivity requirements; equipment still requires power.