Automatic visitor passage requires separate states for the request, approval, person at the entrance, temporary permission and physical passage. A request or invitation records the visitor, host, time and purpose. Approval can then create a limited permission for specified entrances, areas, times and uses. On arrival, the visitor still presents the project-approved QR code, document, card or face credential. Only a valid identity and valid permission should produce one release, followed by the passage evidence actually available from the door or gate.
Do not collapse five different states
- A submitted request is not approval.
- Approval is not proof of the person at the entrance.
- Identity verification is not current door permission.
- A release command is not physical passage.
- Physical passage needs evidence available from the installed entrance equipment.
Recommended workflow
- Visitor request or employee invitation.
- Approval by the host or designated role.
- Create a visit record with doors, areas, times and uses.
- Issue the credential confirmed for the project.
- Match arrival identity with the approved visit.
- Recheck time, entrance, uses and status.
- Issue one release and retain identity, permission and passage outcomes.
- Expire after time, use, checkout or revocation.
Adapt to the site
- Staffed reception: use a visitor terminal for only the documented capture and comparison functions.
- Existing QR access: verify format, permission delivery and reuse controls.
- Industrial route restriction: open only approved zones and periods.
- Walk-in visitor: complete the required registration and approval instead of bypassing authorisation.
- Recurring contractor: use a bounded service permission, not an indefinitely extended visit.
Choose credentials and devices from proven capabilities
The current solution can use project-specific QR codes, cards, face or identity documents and lists identity-comparison terminals, face terminals, gates and controllers. This does not mean every terminal supports every method. Messaging, printing, OCR, document reading and person-document comparison require explicit product and scope confirmation.
Equipment and software
- Request, invitation, approval and visitor-record software.
- Visitor registration or identity-comparison terminal.
- Face or QR terminal as confirmed for the project.
- Access controller, lock or standard swing gate.
- Temporary credential, permission, passage and expiry management.
- A staffed exception process.
Confirm before implementation
- Invitation and approval roles.
- Required data and notice, consent, access, retention and deletion.
- Credential types and proven device capabilities.
- Allowed doors, zones, times, directions and uses.
- Final release authority and available feedback.
- Cancellation, expiry, checkout, watch-list and offline procedures.
Frequently asked questions
Does approval grant access through every door?
No. Temporary access must remain limited by entrance, area, time, direction and uses.
Can a visitor QR code be forwarded?
Validity, uses, status and any approved identity check should control reuse; the exact mechanism is system-specific.
Does identity verification prove the visitor entered?
No. Permission, release and physical passage evidence remain separate.
How does access expire after departure?
The project may use checkout, credential return, exhausted uses, revocation or the end of the validity period.