Key takeaways:
- Choose how access permissions will be issued, limited and ended before deciding what residents carry.
- Identify the actual credential format because legacy 125 kHz proximity fobs have documented cloning risks that should not be assigned to every fob.
- Compare proposals that clearly separate equipment, installation and recurring charges and explain revocation, backup entry and door safety.

A keyless building entry system unlocks a door after it accepts an authorized PIN, card, fob, phone or other credential. For a managed property, opening the door is only part of the job. You also need to control who can enter, which areas they can use and when their access ends.
If you manage an existing apartment building, an upgrade does not have to mean replacing everything or requiring everyone to use a phone. You may be able to keep suitable equipment, improve credential security or add mobile access. Start with how residents and visitors will enter, including when their usual method fails. Then use those needs to decide what your building should keep or change.
This guide will answer:
- What is a keyless building entry system and how does it work?
- Choose credentials around resident needs and permission changes
- Manage access from move-in through move-out
- Give visitors and deliveries a separate access workflow
- Plan for phone failure, internet outages and power loss
- Assess existing equipment, safe exit and emergency entry
- Compare keyless entry costs by scope, not just per door
- Turn requirements into a retain, upgrade or replace decision
Watch how ButterflyMX works:
What is a keyless building entry system and how does it work?
A keyless building entry system releases a door when it accepts an authorized credential instead of requiring a metal key. A credential is what someone presents to request entry, such as a PIN or fob. Keyless entry describes that opening method. Managed electronic access control adds the ability to manage people, door permissions, schedules and access records. A standalone smart lock does not automatically provide coordinated management across a building.
Follow one entry attempt to see how these parts work together. The sequence described in Kastle’s apartment access control guide separates presenting a credential from deciding whether to unlock the door:
- A person presents a credential, such as a fob, phone or PIN.
- A reader captures the credential or input.
- A controller or connected software checks whether it has permission for that door at that time.
- If access is approved, the electronic locking hardware releases.
- The system may record the event for later review.
An electric strike or magnetic lock secures or releases the door. It is locking hardware, not a credential. Likewise, using a phone does not mean every access decision happens in the cloud. Depending on the system, that decision may happen locally or through connected software.
These separate roles matter when you choose a system. Before deciding whether residents should carry fobs or phones, establish who needs access, at which doors and during which hours. The credential must work with those permissions, not replace the need to define them.
Choose credentials around resident needs and permission changes
The right credential mix depends on your users, their doors and how often their permissions change. A resident may need the main entrance and selected amenities, while a staff member needs service areas. Both could use the same type of credential without receiving the same access.
You can also support different credential types for different users. Compare that mix against the work it creates: enrolling residents, replacing lost credentials, ending access and helping someone enter when their usual method is unavailable.
Compare PINs, fobs, mobile access and biometrics
The table below compares operating needs, not security scores. It draws on Kastle’s credential guidance, DOOR’s discussion of credential handling and backup entry, and the independent legacy-fob reporting discussed below.
An individual PIN can be assigned to one resident where supported. A shared building code loses that connection: a record of its use does not identify which person entered it. Even an individually assigned credential record shows which credential was used, not conclusive proof of who presented it.
Swipe to compare →
The useful comparison is not simply physical versus digital. A familiar fob may fit your building if its format and management meet your needs. Mobile access may offer another convenient choice, but it still needs enrollment support and a way in without a working phone.
Identify the credential format before judging security
Key fob entry is not one security category. In reporting dated May 10, 2024, independent security publication IPVM documented the cloning exposure of legacy 125 kHz proximity credentials to inexpensive tools. That finding gives you a specific reason to identify your existing format. It does not show that every physical credential has the same weakness.
Kastle distinguishes legacy unencrypted proximity credentials from encrypted cards and fobs. However, a 13.56 MHz label alone does not establish encryption or secure settings. Ask the provider to name the credential format, compatible readers and enabled reader settings.
Apply the same standard to phones and biometrics. Neither label proves that an entire system is more secure. You still need to evaluate how the credential works, how permissions are managed and what happens when access should end.
Match the credential mix to actual users
Ask residents about practical needs rather than assuming an age group prefers one method. Have the provider demonstrate enrollment and everyday entry, including any app requirements. For biometrics, also require an explanation of information handling and a non-biometric alternative.
Make the reason for each choice clear. Exposed legacy credentials may call for a format upgrade. Difficult phone enrollment may call for a physical credential option. Once you have a proposed mix, test it against the same three events: move-in, credential loss and move-out.
Manage access from move-in through move-out
Consider this hypothetical example: an installer confirms that your existing door hardware is suitable, and the proposed readers and management system support encrypted fobs and optional mobile credentials. You could retain that hardware while changing how residents receive and use access.
The next test is whether staff can manage both credential types throughout a resident’s stay. The steps below apply Kastle’s recommended operating practices. They illustrate what to specify, not results from an actual customer project.
1. Assign permissions at move-in
In this example, a designated administrator enrolls the resident and assigns the approved doors, floors and amenities. Choosing a fob or phone does not determine those areas. The permissions attached to the credential do.
Specify who sets up access and who helps the resident complete enrollment. Then check that the resident can use the intended entrances and amenities. A credential marked active in software is not a substitute for confirming that entry works.
2. Handle a lost credential after hours
Suppose the resident reports a missing fob at night. An authorized contact needs to handle the report, arrange deactivation and provide an approved replacement or backup entry method. Kastle recommends making lost-credential reporting and deactivation available at any hour.
Restoring entry and ending authorization are separate tasks. Letting the resident inside does not disable the missing fob. Issuing a replacement does not, by itself, prove that the old fob has stopped working. Assign responsibility for both tasks, including confirmation that the change reached the relevant doors.
If a door is disconnected, a remote change may remain pending. Your loss-response plan needs to cover that gap instead of assuming deactivation takes effect everywhere at once. The outage section below explains what to ask the provider.
3. End access when permission ends
At move-out, Kastle recommends deactivating resident access when the lease ends, whether or not the fob is returned. Collecting an object is not the same as ending its authorization. In this example, staff collect any issued fob, deactivate the resident’s permissions and confirm that the changes reached the relevant system.
A property management system, or PMS, integration may automate parts of issuing and ending access. Confirm which lease events trigger changes, which doors are covered, when updates take effect and who handles exceptions. An integration label does not guarantee that every access record stays in sync.
This same permission model applies to nonresidents, but their access should follow their purpose. A guest or service provider does not need permanent resident access simply because that is the credential you have chosen for residents.
Give visitors and deliveries a separate access workflow
A resident credential alone does not solve visitor entry. Verifying a visitor, remotely releasing a door and issuing temporary access are different tasks. An intercom can help a resident or staff member verify someone, while remote release opens the door after that decision. A temporary credential allows entry within the limits the system supports.
Kastle’s guidance on nonresident access emphasizes permissions tied to the visit. Define the process for each group:
- Guests: Identify whether a resident or staff member verifies and admits the person, and through which entrance.
- Couriers: Specify who authorizes a supported delivery credential, which door it opens and when it is valid.
- Vendors: Assign only the needed areas and times, with automatic expiry where supported.
Kastle recommends time-limited, area-specific vendor access. Assign responsibility for issuing and ending it rather than handing out a permanent shared resident code.
These controls define authorized entry; they do not guarantee that tailgating or package theft will be prevented. They also need separate failure plans. A guest waiting for remote release may be affected differently by an outage than a resident using a locally stored permission.
Plan for phone failure, internet outages and power loss
Ask for separate demonstrations of a dead phone, lost internet service and electrical power loss. Each affects a different part of the entry process. A general promise of backup access does not tell you which doors or functions will keep working.
A dead or missing phone
DOOR describes possible phone-loss fallbacks, including PIN entry, an authorized physical-key override and credentials on more than one device. These are product-dependent options, not features available at every door.
Require a demonstrated non-phone entry route and a clear after-hours support process. Do not assume every lock has a key override or that remote assistance will always be reachable. If support is part of the backup plan, establish who provides it and what happens when that person cannot be reached.
An internet outage
Some systems can keep admitting authorized users during an internet outage. Motorola describes systems that store permissions locally, allowing some entry to continue while remote management and updates pause. That does not mean every feature works without a connection.
Return to the resident who lost a fob. A backup method may get that resident inside while the missing fob’s remote deactivation remains pending at a disconnected door. Keeping entry working and keeping permissions current are different problems.
Ask the provider to demonstrate what a disconnected door accepts, how pending changes are applied and how an administrator confirms completion. Assign responsibility for handling a reported loss during that gap. Stored permissions alone do not guarantee immediate remote revocation.
A power outage
Stored permissions do not supply electrical power. Have the installer identify which readers, controllers, network components and locks receive backup power. Then ask for a demonstration of what continues working in the proposed setup.
Get the supported backup duration and its assumptions in writing. An offline-access claim is not a promise of indefinite entry, working remote services or power throughout the building.
Cloud and on-premise administration
Once failure behavior is clear, compare who will manage and maintain the system. Vendor descriptions in Kastle’s guide and Motorola’s guide associate cloud-based access control with remote administration and connected services. On-premise access control places local infrastructure and related IT responsibilities with the operator.
Where you manage access and where a door stores permissions are separate questions. Neither cloud nor on-premise is an automatic security winner. Neither label tells you how long a door will operate without power.
Turn these decisions into a resident-facing policy. Document non-smartphone entry, enrollment and lockout support, who pays recurring charges, what entry events are recorded, who may view them and how long records are kept. Resolve legal obligations through jurisdiction-specific review rather than treating a product feature as an answer about resident rights.
You now have a clearer picture of what the system must do. An installer must next establish whether your actual doors and equipment can deliver that behavior safely.
Assess existing equipment, safe exit and emergency entry
Establish what can be reused
A keyless entry retrofit may retain existing equipment, but reuse depends on its condition and compatibility. Have a qualified installer assess doors, frames, locking hardware, readers, controllers, wiring and power. The assessment should document which parts can work together and support your chosen credentials.
Retaining suitable locks or wiring changes the work a proposal needs to cover. It does not guarantee a plug-and-play upgrade. Each retained component must still support the required entry and failure behavior.
A credential change also needs a clear end point. Kastle describes dual-format reader transitions that accept legacy and replacement credentials during a changeover. Legacy acceptance must then be manually disabled. Require an agreed transition end and confirmation of the final settings so issuing new credentials does not leave unwanted legacy access enabled.
Separate lock power behavior from safe exit
Fail-safe locking hardware unlocks when power to that hardware is lost. Fail-secure hardware remains secured on power loss. These terms describe lock behavior, not whether occupants can safely exit through the complete door assembly.
The release method, other door hardware and local requirements must be assessed together. Do not choose a lock solely because one power-loss label sounds safer.
For example, the 2024 International Building Code sensor-release provision includes specified power-loss, alarm and independent manual-release conditions. It illustrates one release method under a model code, not a universal rule for every electric lock or apartment building. The locally adopted edition, occupancy and amendments determine what applies.
Have qualified professionals establish the approved arrangement with local building or fire officials. A controller listing or certification alone does not prove that the complete door installation complies.
Agree on emergency responder access
Responders also need an agreed way into the building. As a local example, Mobile Fire-Rescue in Mobile, Alabama describes key-box administration for commercial buildings, including updating responder keys after lock changes. That notice does not establish apartment requirements elsewhere.
Before approving installation scope, ask your installer and local building or fire official to establish:
- The approved occupant-release arrangement.
- The required response to alarm activation.
- The backup-power scope and expected door behavior.
- The responder-entry method and who keeps it current.
For the broader project sequence, explore how a keyless entry system is installed. Use that resource to discuss professional project scope, not as a substitute for a site assessment or as electrical-work instructions. The assessment establishes which equipment and work belong in the proposals you compare.
Compare keyless entry costs by scope, not just per door
Keyless entry installation cost per door depends on what the price includes. A project retaining suitable locks and wiring has a different scope from one needing new equipment throughout. An equipment-only price also answers a different budget question from a proposal covering hardware, labor and software.
Separate upfront work from ongoing charges
Start with the new and retained equipment, then identify installation, configuration and testing. Separate those upfront costs from recurring software or management services, replacement credentials and optional visitor-service charges. This follows the component-based approach in Kisi’s access control cost guide.
Ask what each charge covers and how it is billed. A monthly amount per door cannot be compared directly with an annual amount per unit without understanding the included services. Also establish whether residents pay any charges and what support is included.
Read published figures with their inclusions
Two undated vendor examples show why scope matters. Kisi’s one-door example totals $3,850, including first-year licensing. ButterflyMX’s installation guide gives $500–$2,500 per door for installation. The ButterflyMX figure is for installation, not an all-in equipment and subscription price.
These figures do not establish a typical apartment-building price and should not be averaged or ranked. Use current project quotes with matching inclusions to make a purchase decision.
For each itemized proposal, record:
- Equipment: Each new component and each retained component.
- Implementation: Installation, configuration, testing and onboarding work.
- Recurring services: Amount, billing unit, renewal terms and included functions.
- Credentials: Issuance and replacement charges.
- Visitors: Any separate visitor or delivery-service charges.
- Support: Who handles faults, enrollment and after-hours loss reports.
A blank item means unresolved scope, not zero cost. If one quote omits installation or testing, ask the provider to add that work before comparing totals. Even a fully itemized lower price does not resolve missing non-phone entry, unclear revocation or an unapproved exit arrangement.
Turn requirements into a retain, upgrade or replace decision
Your requirements should narrow the choice, not force replacement from the start. Retain compatible equipment when its credential format and management meet your needs. Upgrade exposed legacy credentials where warranted. Add supported mobile access when enrollment and non-phone entry work. Replace a system when a professional assessment shows it cannot meet the requirements.
These paths can overlap. A mobile access upgrade might keep suitable locks while changing readers or management software. What matters is which parts and processes meet your needs, not whether a proposal is labeled new or upgraded.
Confirm interoperability rather than assuming it
Interoperability means products can work together, but you need to establish which parts of the system that covers. The Connectivity Standards Alliance released Aliro 1.0 on February 26, 2026. Its initial scope addresses communication between user devices and readers or locks through NFC, Bluetooth LE, and Bluetooth LE plus ultra-wideband, or UWB.
The CSA Aliro FAQ distinguishes that device-to-reader scope from broader access management. Aliro does not by itself make administration, integrations and records portable between complete platforms.
Ask for evidence of support and certification for the actual products proposed. A standard’s release does not prove compatibility with your installed hardware or establish ButterflyMX support.
Evaluate a documented product against the requirements
As one manufacturer-documented example, the ButterflyMX access control system lists smartphone, fob, card and PIN credentials, visitor QR keys, Delivery PINs, remote management and PMS integrations. These features address credential choice, visitors, deliveries and administration. Use them as starting points for the demonstrations and confirmations above, not as proof of project fit.
ButterflyMX describes outage operation with a backup battery installed. Confirm which doors, equipment and functions that covers in your proposed setup rather than assuming every entry and remote feature continues. Its product page also documents a time-stamped photo audit trail stored for 365 days. That retention term does not establish who may view or use the records. The documentation reviewed does not specify fob encryption format or Aliro support, so neither should be assumed.
Before requesting proposals, put your requirements in a short statement covering:
- Users, doors, schedules and responsibility for issuing access.
- After-hours revocation, disconnected-door updates and confirmation of completed changes.
- Non-phone entry, enrollment help and lockout support.
- Guest, courier and vendor access.
- Recurring-charge responsibility, recorded data, authorized review and retention.
- Assessed retained equipment, approved exit arrangements and responder entry.
- Separate upfront and recurring costs.
A proposal is not ready for a decision while a material answer remains undefined. Use those gaps to guide the next discussion rather than choosing a credential or vendor first and trying to build the operating plan around it.
Frequently asked questions
Can a keypad be enough for a managed building?
Yes, if the supported setup meets your access needs. A keypad is an interface for entering a credential, not proof of complete access management. Check individual versus shared codes, door permissions, turnover, visitor access and backup entry before deciding.
Do mobile credentials need Wi-Fi every time someone enters?
Not necessarily. Presenting a phone credential and checking its permission are separate steps. Some systems store permissions locally during internet loss, but that does not establish offline support for every mobile implementation. Confirm how the proposed phone credential communicates with the reader, what enrollment needs and what works at a disconnected door.
Does Aliro make access management platforms interchangeable?
No. Aliro 1.0 initially addresses communication between user devices and readers or locks. It does not establish complete portability of administration, integrations or records. Ask for product-specific support and certification evidence rather than assuming compatibility from the standard’s release.
How long are entry records kept?
Retention depends on the selected system and building policy. ButterflyMX documents a 365-day time-stamped photo audit trail, but that period should not be applied to other systems. How long records are kept is also separate from who may view them or how they may be used.
The right keyless building entry system may keep suitable equipment, improve credential security, add mobile access or replace an unsuitable setup. Choose the approach that provides clear permissions, a workable lost-credential response, non-phone entry, assessed door arrangements and full costs.
Use those requirements to request comparable proposals. If ButterflyMX is on your shortlist, evaluate its access control system against the same requirements before deciding whether it fits your building.
Get your free quote!
Fill in the form below, and we'll email you right back.
Want a free quote?
Fill in the form below, and we'll email you right back.
Redirecting you in 5 seconds.