Use case
Manage contractor and temporary-crew entry with Access Control and Visitor Management. Define permitted doors, access schedules and expiry dates; use the visit record for host accountability and verify device synchronization when changing permissions.
One command surface
Module-by-module rollout
Audit-friendly operations
How it plays out
Each step ties to a real platform action — not a slideshow.
Onboard
A contractor is added with a role, the zones they need, and a validity window — no permanent card.
On site
They badge in by card, QR, or face; every entry is tied to their identity and sponsoring host.
Exception
An attempt outside their zone or window is denied and logged with full context.
Job closes
Access expires at its configured end time. For an early finish, revoke access and confirm device synchronization; retain the entry history for review.
Before and after
Temporary workers issued permanent cards that never come back
No single record of who is on site, for which job, under whose sponsorship
Manual onboarding that slows down the first day and the audit later
Access that should have ended weeks ago but is still live
Shared identity, policy, and site structure
Live events with module context attached
Governed operator actions with audit history
Phased expansion without replatforming
Most relevant modules
This use case starts with the module that solves the clearest operational pain, then expands on the same foundation.
Module stack
Shared foundation
Live operations layer
Access, visitors, parking, video, intercom, and audit events resolve into the same command surface.
Field references
Real customer references delivering capabilities now packaged as Duall Master — scope, hardware, and figures sourced from project documentation.
Access Control + Visitor Management + Time Attendance · 2026
A busy international container port never really closes — workers, drivers, and visitors move through its gates around the clock. At TIL’s Hải Phòng terminal, Duall Master keeps that flow secure and accountable: staff enter by face or card, visitors are managed at the gate, and the same recognized entry becomes the attendance record.
Access Control + Visitor Management + Time Attendance · 2024
A military medical university running access control, chip-ID visitor registration, and attendance for nearly 8,000 staff, students, and clinicians on one platform — face-recognition entry across the unit and citizen-ID check-in at patient reception.
Access Control + Visitor Management + Time Attendance · 2023
Children's Hospital 1, one of Ho Chi Minh City's largest paediatric hospitals, runs access control, visitor management, and staff attendance for roughly 10,000 people on one on-premise Duall Master platform — 84 doors and 14 lifts governed together and integrated with the hospital's management system.
For factories, offices and campuses with maintenance vendors or temporary crews, combine Visitor Management and Access Control to define who may enter, which doors they may use and when access ends.
Use a scheduled visit and approval flow for short appointments. Longer assignments need an identity record, access-group membership and a defined validity period. Agree host responsibilities, extensions and early revocation before issuing credentials.
Map gates, workshops, stores and restricted areas to each work group. Configure start dates, expiry dates and access schedules. Select card, QR or face credentials according to supported hardware and the site’s data policy.
Compatible devices apply synchronized access rules locally. An early revocation or schedule change still needs to reach the device: check connectivity and synchronization instead of assuming an offline device has received a server change.
Test valid entry, the wrong door, out-of-hours attempts and expired access on real devices. Confirm grant/deny history, report permissions and the guard’s exception procedure. Entry history is operational evidence, not proof that contracted work is complete.
This use case combines existing access and visitor modules; it is not a separate contractor-lifecycle system. Safety certificates, contracts and permit-to-work integrations require their own scope review.
Access expires at its configured end time. For an early finish, an operator must update or revoke access and confirm device synchronization. Connecting external job status requires a separate integration assessment.
Bring door and gate counts, crew sizes, shifts, existing device models, approval steps, retention requirements and acceptance scenarios. Personal worker records are not needed for an initial assessment.
Scenario operating model
Modules in play
Signal
Doors, visitors, cameras, intercoms, and parking generate live signals — not isolated alerts.
Context
Identity, policy, site, zone, and related module records attach to every signal.
Action
Operators approve, deny, review, or escalate inside one governed workspace.
Audit
Every decision keeps the who, what, when, and evidence — ready for review.
Buyer-facing model for phased adoption: start with the clearest pain, then add adjacent modules on the same foundation.
Deployment and trust
Typical adoption path
Next step
Review module priorities, deployment constraints, integrations, and rollout path for your environment.
