The first employee arrives at the office with their phone in hand and their key fob at home. Could the phone open the door instead of someone making another trip?
Yes, a compatible commercial door access system can let authorized staff use a phone. But it is not a feature you can assume from the card reader beside the door. The reader, access software, phone and assigned permissions must support the same method. Keep an approved backup until that arrangement has been tested with the people who will use it.
Start with the action you want: tap the phone at the door, press a nearby app button, or let a designated person unlock it from elsewhere. Those are different requirements, even when a proposal calls all of them mobile access.
Choose how the phone should open the door
With a nearby app method, the phone can communicate with a compatible reader using Bluetooth, the short-range wireless connection familiar from headsets. The user may press a button in the app or bring the phone close to the reader. Required permissions, app behaviour and supported devices vary.
A wallet pass is different. It stores an authorized door credential, the digital permission used to identify the user, in a supported phone wallet. The person presents the phone to a compatible reader using near-field communication, or NFC, the short-range technology used for contactless taps. A wallet pass is issued by the access administrator; it is not a photo of a card or an ordinary file copied from a fob.
Remote unlock sends a command through the access system rather than relying only on the phone being beside the reader. Current manufacturer guidance for nearby and remote phone unlocking documents this distinction and a separate remote-unlock setting. That is one supported implementation, not a promise about every system.
Ask for a demonstration of the action your staff will actually perform at the door.Check every reader, not just the front entrance
A reader that accepts a card may support a nearby phone app but not a wallet pass. A newer front-door reader may offer methods that an older side-door reader does not. The documented reader and unlock-method compatibility table shows why model-level checks matter.
Make a door list before approving equipment. Include the entrance staff use before opening, any stockroom they need, and the route through a shared building. If the landlord controls the lobby reader, phone access at your suite does not automatically get an employee through the lobby.
Have the installer record which readers can stay, which need replacement and which software versions are required. If the proposal includes changes to the lock or door itself, use our separate guide to adding access control to existing commercial doors. A different credential does not fix a door that fails to close and latch.
Check the phones your team actually carries
Do not approve a rollout after one successful demonstration on the installer's phone. Check the phone models, operating-system versions, account requirements and app permissions for the staff who need entry. A watch may have different support from a phone. A company-managed account can also behave differently from a personal account.
The current wallet-credential setup and lifecycle requirements include reader, software, user-device, account and regional restrictions. They also describe licence renewal and different actions for suspending a pass or moving it to another device. Check the current documentation for the exact proposed setup, rather than treating phone ownership as the only requirement.
- Confirm whether staff need an app, a wallet pass, or both during enrolment and daily use.
- Agree who issues invitations, helps with a replacement phone and handles access outside normal office hours.
- Document any licence and renewal dependencies, including what happens if a credential expires.
- Keep a workable option for staff who cannot or do not agree to use a personal phone for entry.
Explain the app permissions and access records before asking employees to enrol. Collect only the information needed to establish compatibility and authorized access. Staff should not send personal account passwords or wallet screenshots to request a door assessment.
Plan separately for no signal and no battery
A basement entrance with poor cellular reception is not the same problem as a phone that will not turn on. Some wallet credentials work locally once added to a compatible device. That does not mean every phone app or remote-unlock command works without a connection.
The wallet-entry user guide and battery limitations documents offline use for its supported pass. It also distinguishes limited reserve operation on supported phones from devices that need the screen on. These are product-specific conditions, not a general promise that a dead phone will open a door.
The reader, door controller and lock have their own power and connection needs. The controller is the equipment that decides whether to release the lock. A phone working without cellular service says nothing about how those building components behave during an outage. Our business door outage guide covers that separate planning problem.
Agree on backup entry before taking cards away. It might be an individually assigned card or a staffed verification process. Do not make propping open a secured door the unofficial solution. Entry testing must never interfere with required emergency exit arrangements.
Treat a lost phone as a lost door credential
Decide who staff contact when a phone disappears and who can disable its door access. A screen lock is useful, but some wallet modes intentionally allow entry without unlocking the phone. Have the administrator confirm the configured behaviour rather than assuming a passcode is required for every tap.
Removing a pass from a wallet, unbinding a device and suspending a credential are not necessarily the same action. In the documented wallet system, unbinding permits transfer to another device for the same user; suspension disables the pass. Use the supported administrative action for the actual incident and confirm the affected equipment received it.
If someone is leaving the business, review their cards and other entry methods too. The employee door-access removal checklist covers that wider task. A phone replacement should not quietly grant more doors, longer hours or remote unlocking.
Pilot entry and denial before changing the whole office
Use an authorized test group and keep the existing fallback available. Record the tested phone, door, entry method, software versions and result. Include more than the easiest successful tap.
- Normal arrival: test each approved entrance with the screen and app in the states staff normally use.
- Denied access: confirm the test user cannot enter an unassigned room or outside their agreed hours.
- Lost-device response: perform a controlled suspension of a test credential and verify denial at the affected readers.
- Phone unavailable: demonstrate the agreed fallback and confirm who will help the first person arriving.
Schedule any connection-loss testing with the installer so it does not interrupt occupied premises or compromise safe exit. Mark untested cases as unverified. One successful phone tap is not evidence for every reader, device or outage scenario.
Bring the door list to a commercial access-control assessment
For a Windsor or Essex County business, start with NeuroDesk's commercial door access and business technology planning. Bring the reader models, the doors staff need, any landlord-controlled entrance and a list of phone types. Do not include access codes, invitation links or employee credentials in the enquiry.
We can scope the equipment and access requirements around those entrances. The sensible result may be phones for some staff and cards for others, not a compulsory phone-only change. Choose the arrangement your team can use, your administrator can manage and your fallback can support.