Business Access Control: Systems, Costs, and How to Choose

Profile image for Tiara Sutton
Tiara Sutton
Updated 17 min read
business access control at entrance
Used by more than 1 million, including the most trusted names in real estate
related-logo-png lincon-property-logo-png lennar-logo-png CA-ventures-logo bozzuto-logo-png

Key takeaways:

  • Choose controls by the risk, workflow, and safety needs of each opening instead of using the same credential everywhere.
  • Compare proposals by one-time, recurring, and lifecycle costs, not by a single cost-per-door figure.
  • Shared entrances and visitor workflows may suit a video intercom, while restricted areas can require complementary access controls.

 

business access control at entrance

 

Replacing physical keys is not just a hardware decision. A business needs to decide who can enter each opening, when they can enter, how visitors are handled, and what should happen if power or connectivity fails.

Business access control electronically verifies a credential, checks a person’s permissions, directs locking hardware, and records the event. The right system depends on the risk at each opening, daily workflows, building infrastructure, safety requirements, and the full cost of owning the system.

This guide explains the parts of a physical access control system for commercial properties, compares credential and deployment choices, and offers practical questions for evaluating a property, installer, or vendor.

This guide will answer:

More than 100K, 5-star ratings!

What business access control is and how it works

Business access control is a physical access control system, often called a PACS, that uses credentials, readers, controllers, locking hardware, and software to manage entry to doors, gates, turnstiles, and similar access points. It authenticates a presented credential, authorizes or denies the request based on rules, and can create an access record. The U.S. General Services Administration describes PACS as a connected system of identity data, hardware, software, and related operations, a useful planning model even though federal guidance is not a private-business mandate.

Physical access control governs entry to a place. Logical access control governs entry to digital accounts and systems. They may share identity data, but they are not the same thing. Authentication answers, who is presenting this credential? Authorization answers, may that identity enter this opening at this time?

  1. A person presents a card, fob, PIN, mobile credential, or other approved credential.
  2. A reader or keypad sends the request to a controller or software service.
  3. The system checks the credential against access rules, such as role, door, date, and schedule.
  4. The system directs the lock to respond if access is approved, subject to the opening design and safety requirements.
  5. The system records the event and may share it with connected tools when configured to do so.

Unlike unmanaged keys, electronic permissions can be issued to named people, limited to a schedule, set to expire for visitors or contractors, and revoked when work or tenancy ends. Access control is still only one layer of a broader security and operations plan. Doors, procedures, staffing, surveillance, and incident response also matter.

 

Watch how ButterflyMX works:

Core components and permission models

A complete access control design is more than a reader mounted beside a door. Each component has a job, and the design should show how those jobs work together.

  • A credential identifies or helps verify the person requesting entry. Common choices include cards, fobs, PINs, mobile credentials, and biometrics.
  • A reader or keypad captures the credential and communicates with the access controller.
  • A controller or panel makes, or relays, the access decision and communicates with locking hardware.
  • Locking hardware keeps the opening secured or releases it as designed. Its behavior must be selected for the door and applicable requirements.
  • Management software stores permissions, supports administration, and can maintain event records.
  • A door-position sensor can report whether a door is open or closed. A request-to-exit device, often called REX, supports authorized egress from the secure side.

Permissions are the rules behind the hardware. A business might give a retail manager access to the front entrance and stockroom during operating hours, give a delivery contractor a time-limited code for a service entry, and limit a finance room to a smaller group. Role-based, time-based, location-based, visitor, and contractor permissions can all be combined when the selected system supports them.

Keep three choices separate during planning: the credential type, the permission model, and the deployment model. A mobile credential can work with role-based permissions, for example, whether the system is managed on site, through a cloud service, or through a hybrid arrangement. Video intercoms, cameras, alarms, elevators, visitor tools, and fire systems can also be part of the wider plan, but compatibility, licensing, and event behavior must be confirmed for the specific equipment.

 

How to choose credentials for each workflow

There is no universal best credential. Compare options by enrollment and revocation, convenience, sharing or loss risk, fallback procedures, cost exposure, and privacy obligations. Many properties use different credentials for different users or openings.

Swipe to compare →

Credential Administration User experience Risk and continuity Cost or privacy consideration
Cards or fobs Issue an individual credential and revoke or replace it when access changes. Users carry and present a dedicated credential. Plan for lost, unreturned, or damaged credentials and prompt revocation. Kisi lists an undated vendor estimate of $5 to $50 per card or fob. Treat it as illustrative, not a market benchmark.
PINs Create, expire, and revoke codes. Individual codes provide more accountability than shared codes. No physical token or phone is required. Set rules for sharing, observation, forgotten codes, and expiration. Consider keypad hardware and the operational work of managing unique or temporary codes.
Mobile credentials Enroll and revoke digital identities through the supported platform and device workflow. Users rely on a compatible phone and enrollment process. Plan for lost or replaced devices, low batteries, unavailable phones, and a fallback method. A vendor-sponsored 2024 global HID survey, based on fieldwork from November 2023 through January 2024, reported that 39% of surveyed organizations actively used mobile identities.
Biometrics Enrollment and deletion need a documented data-governance process. A biometric characteristic replaces or supplements a carried or remembered credential. Provide a fallback for failed reads and address disputed or compromised biometric data. Illinois BIPA illustrates possible notice, written-release, retention, destruction, sale, and data-protection duties. Laws differ by jurisdiction.

Mobile credentials may be worth considering where people already use phones for daily property tasks, but adoption data should not be mistaken for a requirement. The HID report was vendor-sponsored, global in scope, and included organizations of different sizes.

Biometric access control requires special care because biometric data cannot be handled like an ordinary replacement card. The Illinois Biometric Information Privacy Act is one example of a law that addresses notice, written release, retention and destruction policies, restrictions on selling biometric data, and data protection. It is not a nationwide rule. Obtain jurisdiction-specific legal guidance before collecting or using biometric information.

For shared entrances and visitor workflows, ButterflyMX materials describe options such as mobile access, Visitor Passes, and PIN-based visitor access. Those options can be useful where the workflow fits, but they do not eliminate the need to assess restricted rooms or high-risk openings separately.

 

Cloud, on-premise, hybrid, and standalone deployment

Deployment describes where administration and system services reside. It is different from how readers are wired or connected. An IP-connected reader does not, by itself, make a system cloud-managed, and a cloud-managed system may still depend on local controllers and local door hardware.

Swipe to compare →

Approach Typical advantage Primary responsibility Questions to resolve
Standalone Can suit a limited opening with simple local needs. Local credential and device administration. How are schedules, audits, backups, and credential changes handled?
On-premise Management and data services can remain under local control. Internal ownership of servers, backups, updates, recovery, and maintenance. Who supports the system after launch and tests recovery?
Cloud-managed Can simplify remote administration and multi-site management. Shared responsibility across the customer, vendor, and local operations team. Which functions depend on internet or hosted-service availability?
Hybrid Can combine local decision-making with remote management functions. Responsibilities must be clearly divided. What continues locally during an outage, and what requires remote service?

A commercial access control overview from Avigilon describes common architecture choices, while the practical decision is operational: document which access decisions happen locally and which administrative actions require the LAN, internet connection, or hosted service. Cloud availability and door behavior during a local failure are separate questions.

Ask for a clear outage description before signing. It should state how doors behave during a power loss, what happens when the local network fails, what administrators can do during an internet outage, and how service is restored after a hosted-service disruption.

 

Match access controls to each opening and property

Choose access controls opening by opening. A shared front entrance, employee suite door, stockroom, server room, loading door, and amenity space can have different users, assets, visitor patterns, and failure consequences. Using the strongest possible method everywhere can add cost and friction without improving the most important workflows.

 

Use an opening-risk checklist

  • Who needs access: residents, employees, tenants, visitors, contractors, delivery staff, or a limited group?
  • When is access needed: all day, business hours, scheduled shifts, or one-time visits?
  • How is entry approved: self-service credential, live visitor verification, receptionist approval, or another workflow?
  • What needs to be recorded: basic entry events, visitor activity, door status, or exceptions?
  • What must happen during a failure: continued local access, manual procedures, controlled release, or a safety response?
  • Which connected systems matter: cameras, alarms, elevators, visitor management, or other property systems?

A visitor-entry video intercom is not automatically a full multi-door PACS. At a shared entrance, live video communication and remote release may be the central need. Employee doors, schedules, restricted zones, extensive auditing, or higher-risk rooms may need broader permission controls, monitoring, or complementary hardware.

This approach works across offices, retail sites, warehouses, multi-tenant buildings, and multi-location businesses. Start with the workflow rather than assuming every property type requires the same equipment. As a planning aid, match controls to the highest-risk asset or activity behind each opening, but do not treat this exercise as a code classification or a security guarantee.

Map your entrances, users, visitor workflows, integrations, and higher-risk areas before comparing systems. That door list becomes the foundation for a useful scope of work.

 

Plan installation, outages, and safe egress

Before final pricing, conduct a site survey. The installer should assess the door and frame, latch and existing hardware, available power, wiring path, network connection, fire-system interfaces, accessibility needs, and retrofit constraints. A promising product fit does not confirm that a particular opening can accept every lock or reader configuration.

Failure condition What to confirm in writing
Building or controller power loss Lock behavior, backup power, egress release, manual procedure, and recovery testing.
Local network loss Which access decisions remain local, whether readers continue operating, and what administrators can still change.
Internet loss Which remote-management or hosted functions pause and how the site continues operating.
Hosted-service disruption Local door behavior, escalation process, restoration procedure, and event-record handling.

Fail-safe and fail-secure describe different lock behavior when power is lost. Neither label is universally better. The correct design depends on the opening, the building use, the egress path, the fire and life-safety design, and local requirements.

Electrified-door egress must be reviewed with qualified installers and the Authority Having Jurisdiction, or AHJ. As one limited example, 2021 IBC language reproduced for an Illinois adoption includes conditions for covered sensor-release locks involving egress-side sensors, power-loss release, a direct power-cutting exit device, fire-alarm or sprinkler release, emergency lighting, and listed equipment. Code edition, local amendments, occupancy conditions, and AHJ interpretation can differ.

 

Questions to review with the installer and AHJ

  • What is the required egress behavior for this specific door?
  • How does the lock release during power loss and fire-alarm activation?
  • Are the exit device, release components, power supplies, and interfaces appropriate and listed for the intended use?
  • How are accessibility requirements and existing door hardware addressed?
  • What acceptance tests and documentation are required before turnover?

This checklist is a planning tool, not code or engineering advice. Confirm the final design and approvals locally before installation.

 

Build a realistic lifecycle budget

A useful budget separates installation costs from recurring operating costs and future replacement costs. A per-door number without scope details can hide the work that determines whether a proposal is complete.

Cost category Common items to include
One-time Readers, controllers, locks, power, wiring, door work, labor, integrations, enrollment, commissioning, training, permits, and repairs.
Recurring Software, hosting, support, connectivity, and any service or licensing fees.
Lifecycle Maintenance, replacement credentials, batteries where applicable, updates, component replacement, backups, testing, and future upgrades.

Door and frame conditions, lock type, credential method, available power and network infrastructure, integrations, local labor, software scope, and the number of doors or sites can all change the total. PACS should be budgeted as an IT and operations system, not just a one-time hardware purchase.

For limited numeric context, Kisi publishes undated vendor estimates of $2,000 to $4,000 per door for a typical system and $0 to $50 per door per month for software. The source does not provide a published methodology, so these figures are illustrative estimates rather than market averages or ButterflyMX pricing.

Compare proposals line by line. Ask whether the quote includes power, wiring, exit hardware, permits, door repair, commissioning, credentials, training, taxes, support, and recurring software. Bring your door list, workflow requirements, integrations, and outage expectations to an access consultation so vendors can define the scope rather than fill gaps after installation starts.

 

Manage access, privacy, and system security

Access control needs ongoing ownership after installation. Assign named people to approve new access, review permissions, manage visitor and contractor expiration, review important events, coordinate updates, maintain recovery procedures, and handle vendor escalation.

 

Use a documented offboarding process

  1. Identify the person and every credential or account connected to their access.
  2. Disable access promptly according to the organization process.
  3. Recover physical credentials where appropriate or revoke them in the system.
  4. Preserve audit records that the organization needs to retain.
  5. Test the revoked credential where practical and document completion.

Reader-to-controller communication also affects long-term security and interoperability. The Security Industry Association describes OSDP as an open reader-to-panel protocol that can support supervised, bidirectional communication, multi-drop wiring, and AES-128 Secure Channel. Those benefits depend on compatible equipment and correct configuration. Ask whether Secure Channel is enabled, how credentials work across readers, what event and identity data can be exported, how long records are retained, and what a future migration would require.

Data governance matters most when systems collect sensitive information. If biometrics are considered, establish who can enroll people, what notice and consent process applies, how long data is retained, how it is destroyed, who can access it, and which laws apply to the property. Legal requirements vary, so a local review is essential.

 

How to compare vendors and proposals

A strong vendor comparison begins with the same requirements for every bidder. Ask each vendor to map hardware, credentials, permissions, hosting, integrations, and outage behavior to every opening and workflow. A low initial price can be difficult to compare if those assumptions are missing.

  • Request a written scope, exclusions, recurring fees, support model, warranty terms, update policy, commissioning steps, and acceptance tests.
  • Ask how the proposal addresses door condition, power, wiring, exit hardware, egress, listings, permits, and local approval.
  • Confirm credential compatibility, reader protocol, Secure Channel configuration where applicable, replacement-hardware options, data export, contract terms, and migration costs.
  • Require applicable demonstrations or tests for revoked credentials, schedules, visitor expiration, power loss, network loss, internet loss, alarm release, and recovery.
  • Identify who owns administration, access reviews, software maintenance, backups, incident handling, and vendor escalation after launch.

For a deeper look at door-by-door commercial planning, protocols, outage testing, and commissioning, review a technical guide to commercial access control systems. A checklist supports better buying decisions, but it does not replace a site survey, cybersecurity review, legal review, or local code review.

 

Where ButterflyMX can fit in the access plan

ButterflyMX can be a natural fit for shared entrances and visitor workflows that benefit from video communication, remote mobile release, Visitor Passes, PIN access, access-event records, and, where configured for the property, elevator access. Residents can receive visitor calls and grant access through their smartphones, while property teams can remotely manage residents, visitors, credentials, and access.

For commercial and office properties, ButterflyMX access for commercial properties can support a modern alternative to legacy telephone-entry hardware without relying on traditional POTS telephone lines. The right fit still depends on the opening and property configuration. Employee-only doors, restricted rooms, specialized industrial areas, and other higher-risk openings may require broader PACS functions or complementary controls.

Start with requirements, not product labels: list the openings, users, visitor workflows, integrations, outage expectations, and local safety requirements. That process makes it easier to see where a shared-entry solution fits and where another control should be added.

 

Frequently asked questions

 

Can access control be added to existing doors and locks?

It can often be added, but feasibility depends on the door, frame, latch, existing locking hardware, power, wiring, network access, egress hardware, and integration needs. A site survey should happen before final pricing or compatibility claims.

 

Does a multi-location business need a different system at every site?

Not necessarily. One management approach may span multiple sites, but each location still needs an opening-level assessment, local hardware plan, continuity plan, permissions, support process, and code review. Centralized administration does not remove local operating needs.

 

Can business access control integrate with cameras, alarms, intercoms, and elevators?

These are common integration categories that can support coordinated workflows. Confirm the exact hardware, software, licensing, event behavior, and vendor compatibility in writing because integrations are not universal or automatically plug-and-play.

 

How should access be revoked when an employee leaves?

Use a documented process that promptly disables access, recovers or revokes credentials, preserves necessary audit history, tests the revoked credential where practical, and records completion under a named owner.

 

What should a business ask an installer before signing a proposal?

Ask what the proposal includes for door work, power, wiring, egress, equipment listings, commissioning, outage tests, software fees, support, credential compatibility, Secure Channel configuration, data export, and migration. Local code, cybersecurity, and legal questions may also require specialists beyond the installer.

 

The best business access control plan begins with each opening, not a favorite credential or a single price estimate. Define the users, permissions, visitor workflow, failure behavior, and safety requirements first, then choose the hardware and management model that can support them over time.

For shared entrances, visitor access, and mobile entry workflows, ButterflyMX may be part of that plan. Explore whether it fits your property configuration while ensuring restricted and higher-risk openings receive the complementary controls they require.

ButterflyMX deliveries

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.

Content Writer
Tiara Sutton joined the ButterflyMX team as a Content Writer in 2022. After graduating from Agnes Scott College with a degree in Political Science, she started her journey registering underrepresented communities to vote, before becoming an ESL teacher, and eventually discovering her love for freelance writing.

With a knack for translating complex ideas into compelling stories, she brings years of experience in writing and teaching where she crafts insightful content for multifamily and commercial real estate industries.

She lives in Atlanta, GA, where she enjoys writing poetry, exploring new cities, and performing at open mics. She also enjoys reading and spending time outdoors, whether hiking through nature or finding peaceful moments in a local bookstore.