Prepare a visit before arrival, then verify it against the site access rules. HJ coordinates supported host approval, QR issue, expiry and check-in/out with the registration and access owners. A QR is a credential, not proof of identity or automatic permission for every door, floor or vehicle.
Conceptual QR Visitor Pre-Registration product and system illustration for Digital Visitor. Final device form, model, interfaces and quantities are confirmed from the assessed scope and approved product data. Conceptual identity and permission path for QR Visitor Pre-Registration, derived from this page's scope, interfaces and acceptance record.
Conceptual planning path — not an as-built drawing or project photograph.
Prepare a visit before arrival, then verify it against the site access rules. HJ coordinates supported host approval, QR issue, expiry and check-in/out with the registration and access owners. A QR is a credential, not proof of identity or automatic permission for every door, floor or vehicle.
It sits in Visitor Management under Digital Visitor. The final deliverable is shaped by the intended outcome, the installed or proposed environment and the interfaces that must be owned, supplied, integrated and tested.
Host approval rules, visitor fields, QR validity/use limits, check-in stations, access destinations, supported platforms and retention policy.
From the initial brief to the handover record: what to prepare, check and confirm with HJ.
Prepare a visit before arrival, then verify it against the site access rules. HJ coordinates supported host approval, QR issue, expiry and check-in/out with the registration and access owners. A QR is a credential, not proof of identity or automatic permission for every door, floor or vehicle.
Host approval rules, visitor fields, QR validity/use limits, check-in stations, access destinations, supported platforms and retention policy.
Confirm the issuer, scanner and registration/access systems support the intended time/place permissions. Staff identity checks and emergency/local access safeguards remain separately owned.
Test permitted, expired, revoked and repeated credentials according to the supported design, plus the agreed offline/manual exception path. Avoid exposing visitor data in public sample codes.
Retain credential/permission policy, supported version/interface list, test records and reception/guard guidance.
HJ coordinates assessment, engineering, installation, integration, testing and lifecycle support only for the scope recorded in the quotation. ISD handles catalogue, model, datasheet, supply and availability enquiries. Customer, consultant, builder and appointed-specialist responsibilities remain explicit.
Identity, image, credential and movement data require an authorised controller, lawful access, proportionate collection, retention rules and recorded administrator responsibility.
This focused topic remains connected to its complete system owner. Final models, quantities, interfaces and included work are confirmed in the assessed quotation.
See related systems, how HJ installs them, and support for equipment you already have.
Use the answers as a planning boundary; site conditions and written scope remain decisive.
No. The site validates identity and host permission; the supported credential rules limit where, when and how the QR can be used.
Confirm the issuer, scanner and registration/access systems support the intended time/place permissions. Staff identity checks and emergency/local access safeguards remain separately owned.
Test permitted, expired, revoked and repeated credentials according to the supported design, plus the agreed offline/manual exception path. Avoid exposing visitor data in public sample codes. Retain credential/permission policy, supported version/interface list, test records and reception/guard guidance.
Tell us where it will be used, what it needs to do and what equipment you already have. HJ will recommend the right system, explain who is responsible for what, and agree the next step with you.