Key takeaways:
- Define each opening, its users, schedules, and administrator before choosing equipment or a platform.
- Have qualified professionals assess equipment reuse and exit requirements, and get configuration-specific answers about outages.
- Compare the same installed scope, separate recurring charges, and check ownership and subscription terms before choosing a proposal.

Commercial building access control uses credentials, readers, controllers, software, and controlled locking hardware to manage who can enter particular areas at particular times and record access events. To choose a commercial access control system, first define which doors need control, who uses them, and who manages their permissions.
For an existing office building, that work may point to a shared-entrance upgrade, a few additional controlled doors, or a broader replacement. An opening-by-opening plan helps you tell the difference. It also gives you a way to compare proposals: two per-door prices may cover very different work, even when the readers look similar.
This guide will answer:
- What does commercial building access control include?
- Define the openings, users and responsibilities first
- Confirm what can stay and how each door must release
- Choose credentials around daily administration
- Compare architecture and outage behavior separately
- Compare installed costs and recurring charges on the same scope
- Assess where ButterflyMX fits the defined requirements
- Verify operation and ownership before handover
Watch how ButterflyMX works:
What does commercial building access control include?
A physical access control system, or PACS, checks a credential against rules for a controlled opening. A credential is the card, fob, mobile credential, or PIN someone uses to request entry. A controlled opening might be a shared building entrance, tenant suite door, or service entrance.
The Security Industry Association resource on physical access control, published in March 2024 and written by an HID employee, explains the components and controller decisions behind this process:
- A user presents a credential to a reader.
- The system validates the credential. This is authentication.
- It checks whether the credential has permission for that opening at that time. This is authorization.
- The controller grants or denies the requested release.
- The system records the event.
Authentication and authorization answer different questions. A system may recognize a credential but deny its use at a service door or outside approved hours. Neither step, by itself, proves the identity of everyone who walks through an open door.
Understand the complete controlled opening
The SIA resource identifies six basic parts: a credential, reader, locking device, door position switch, request-to-exit device, and controller. The credential carries access information, the reader receives it, and the controller applies the rules. The locking device controls release at the opening.
A door position switch reports whether the door is open or closed. A request-to-exit device signals an exit request. These are separate functions: an exit request does not tell you whether the door has closed or establish the complete exit arrangement. Software, a permission database, communications, and power connect the parts into a working system.
Use this component list as a planning baseline, not an installation specification. A qualified installer must determine what each opening needs. Buying a reader alone leaves the lock, power, exit functions, and management process unresolved.
Separate entry tools from building-wide permissions
A key provides entry through its matching lock. An isolated smart-lock setup may meet a local door requirement. An intercom supports an entry conversation or visitor-entry workflow and may also include access-control features. Managed building permissions address a broader task: assigning, changing, and removing access across the openings you need to control.
That broader task does not mean every property needs a larger system. If your needs are limited, basic access control for a few doors may be enough. First identify where you need these functions and who will manage them.
Define the openings, users and responsibilities first
Identify who needs each opening and when
Start with shared entrances, tenant suites, and service areas rather than assuming every door needs replacement. For each opening, record the user groups, permitted hours, visitor destination, and person responsible for approving access. This creates your initial door schedule: an opening-by-opening record of operating requirements.
In a multi-tenant building, separate shared-building access from tenant permissions. A tenant may approve its own employees, while the landlord controls shared entrances and service areas. Record who can issue credentials, change schedules, and revoke access across those boundaries. Coram recommends documenting approvals, credential management, visitor limits, and review responsibilities. Confirm that a proposed platform supports the division of work you need.
Also list required connections to other systems. Visitor entry, elevator permissions, and a tenant employee directory are separate requirements. A general claim of integration support does not answer whether a system supports your particular workflow.
Build a scope-to-quote worksheet
A scope-to-quote worksheet connects each operating requirement to the work and price proposed to deliver it. For existing equipment, use three labels: retain, replace, or verify. Until an installer has checked condition and compatibility, verify may be the right label for most items.
Record upfront and recurring charges separately. Include exclusions and the person responsible for resolving each unknown. As answers arrive, update the worksheet rather than treating a blank cost or unconfirmed feature as included. This is a planning aid for you and your providers, not a technical survey or installation design.
Apply the worksheet to an illustrative building
The example below uses hypothetical schedules to show how the worksheet works. It is not a customer deployment, site survey, product design, or actual bid. Equipment compatibility and installation feasibility have not been established.
Swipe to compare →
The lobby row separates a known requirement from an unknown solution. Management wants public entry during stated hours and controlled entry afterward. That does not yet tell the installer whether the lock can stay, what release arrangement is needed, or how much the work will cost.
Visitor access needs the same care. Approval to visit one tenant does not grant access to every suite or service area. If the route includes an elevator, confirm floor permissions with both the access vendor and elevator provider. The entrance, elevator, and tenant suite may each require a separate permission decision.
Carry the lobby row through the rest of your assessment. Each answer should help define the work a proposal must include, starting with what equipment can stay.
Confirm what can stay and how each door must release
Verify reuse instead of assuming compatibility
Existing locks, readers, and wiring may be reusable, but working equipment is not necessarily compatible equipment. Coram says these items often carry over while access control panels usually change. That is vendor retrofit guidance, not a rule for your building or a guarantee from another platform.
Keeping equipment can reduce work, but it may also limit credential formats, reader communication, or platform choice. A lock that operates correctly does not establish that the reader and controller can communicate with the proposed system.
Ask the installer to survey the door and frame, lock operation, reader protocol, controller compatibility, cable pathways, power, and network. Request a written retain/replace/verify record explaining each decision and the work needed to support it. If a manufacturer must confirm compatibility, leave that item marked verify until the answer arrives.
Reader protocol is one part of that check. SIA describes OSDP, the Open Supervised Device Protocol, as supporting two-way communication and supervised connections. Its Secure Channel uses AES-128 encryption. By contrast, Coram describes legacy Wiegand communication as one-way and unencrypted.
Ask whether the reader and controller support the required protocol and configuration together. An OSDP label alone does not confirm that the devices will work together, that Secure Channel is configured, or that the installed system is secure.
Assess exit requirements before selecting locking hardware
Fail-safe means a lock unlocks when lock power is lost. Fail-secure means it remains secured when lock power is lost. These terms describe power-loss behavior, as explained in the basic access control guide. They do not, by themselves, tell you whether occupants can exit.
Have a qualified installer or code professional assess entry-side security and the means of exiting together. The authority having jurisdiction, the local official or body responsible for applying the relevant requirements, determines what applies to your project. Do not choose locking hardware based on its power-loss label alone.
The 2024 International Building Code treatment of sensor-release electrically locked egress doors is one example of a specific exit arrangement, not a universal specification for electronic access control. Your project professional must confirm the applicable text, adopted edition, local amendments, and release design before specifying equipment.
To see why release design affects scope, consider the Minnesota State Fire Marshal guidance for its covered sensor-release arrangement under the 2020 Minnesota State Fire Code. It addresses an occupant sensor, a separate manual release, fire-system connections, and power-loss release. Those functions involve more than a reader: they introduce release devices, wiring, coordination, and testing. This is a Minnesota example, not a design checklist for your building.
Equipment listing is a separate question. UL 294 sets requirements for access control system units. Listed equipment is not approval of the complete installed opening. The applicable code and local authority still determine what the installation must satisfy.
For the illustrative lobby, keeping the lock remains a possibility to verify. Even if it stays, the proposal must address any required power, cable work, door-state sensing, and release integration. Record that work separately so lock reuse is not mistaken for a complete installation scope.
Choose credentials around daily administration
Compare cards, mobile credentials and PINs
Choose credentials based on the people using them and the work required to manage them. BTI discusses credential costs and administrative tradeoffs, but its cost ordering is not a universal price rule. Compare the proposed formats and fees rather than assuming one method is always cheapest or best.
Key cards and fobs require a process for issuing physical credentials, replacing lost ones, and revoking old ones. Check the credential format as well as the reader, since cards and fobs do not all have the same capabilities.
Mobile credentials can reduce physical-badge handling, but they shift work to account and device administration. Users need supported devices and a clear replacement or recovery process. Plan a fallback for someone whose phone is unavailable. Mobile entry is not inherently the best or most secure choice for every user.
PIN codes avoid issuing a physical item, but people can share them. A shared PIN also makes it harder to associate an event with one credential holder. Decide whether that limitation fits the opening rather than using the same method everywhere.
Assign permissions and remove them reliably
Role-based access control applies permissions through groups, such as departments or job roles, rather than setting every permission separately for each person. Kastle describes this permission model, while Coram recommends a policy covering approvals, credential issuance, replacement, revocation, and periodic review.
In the illustrative building, a contractor group could be limited to the service entrance during the Tuesday and Thursday windows. Visitor permissions should end with the approved visit. These are rules to configure and test, not reasons to grant broad building access.
Offboarding also needs a named owner across tenant and landlord boundaries. When a tenant employee leaves, someone must remove both suite access and any shared-building permission. Disabling an email account does not establish that the badge has stopped working.
Biometric credentials add privacy obligations to that process. For covered collection, Illinois BIPA requires specified written notice and a written release, along with a public retention and destruction policy. Subject to statutory scope and exceptions, destruction is required when the purpose is satisfied or within three years of the last interaction, whichever comes first. This is an Illinois example, not nationwide legal guidance. Have qualified counsel assess your proposed use.
These daily tasks help define your management requirements. Once you know who changes permissions, how quickly changes must take effect, and what fallback users need, you can compare where and how the system should be managed.
Compare architecture and outage behavior separately
Compare standalone, on-premises, cloud and hybrid systems
Architecture describes how system management and local control are arranged. It is separate from credential type, reader protocol, and who provides support. Coram treats architecture and local operation as distinct buying questions. Compare each approach against your staffing, connectivity, and expansion needs.
Standalone access control generally uses local administration with limited central management. It may fit an isolated door requirement. If you expect to add openings, consider how staff would change permissions across all of them.
On-premises access control hosts management locally. Your property or service provider takes responsibility for the server and its upkeep. Establish who handles that work and which management functions become unavailable if the server fails.
Cloud-hosted access control uses hosted management and can support remote administration. It can still use controllers at the building. Confirm the local equipment, connectivity, and subscription requirements rather than assuming all access decisions happen online.
Hybrid access control divides functions between local and hosted systems. To make that label useful, have the provider explain where permissions are stored, where decisions happen, and who maintains each part.
Service ownership is another choice. Kastle describes a managed service covering design, installation, monitoring, and maintenance. A self-managed deployment assigns more ongoing work to the property or its providers. Neither arrangement follows automatically from a cloud or on-premises label. Get the actual responsibilities and charges in writing.
Verify four different failure scenarios
Architecture alone does not tell you what happens during an outage. Local enforcement, cached permissions, available power, and configuration determine which functions continue. Cached permissions are rules stored locally for use when a connection is unavailable. This distinction comes from vendor buying guidance, not independent resilience testing of your proposed system.
- Power loss: Confirm which devices remain powered, how the lock behaves, and the documented backup runtime for the proposed equipment.
- Local-network loss: Confirm which reader and controller connections are affected and whether local access decisions continue.
- Internet loss: Confirm whether credential entry continues and which remote management functions stop.
- Hosted-service loss: Confirm what continues locally and which administrative functions depend on the unavailable service.
For each scenario, get answers about existing credentials, revocation, schedule changes, event storage, and later synchronization. Continued entry is only part of the requirement. A system might admit existing users while limiting your ability to remove access during the disruption. The vendor must document what the proposed configuration does.
Return those answers to the lobby worksheet. Management requires credential entry during internet loss, but that is not yet a verified capability. The answer may change controller, power, or support requirements. Resolve it before comparing prices as though every proposal delivers the same result.
Compare installed costs and recurring charges on the same scope
Interpret published per-door figures
Commercial access control cost per door depends on the work included. As planning context, BTI publishes roughly $3,000–$5,000 per door for the first year as a US estimate on a page dated November 12, 2025. It does not disclose a pricing method. That figure is not a site-specific quote or an independent market average.
The examples below were recorded in the supplied research on November 11, 2026. They are separately attributed planning figures, not verified current quotes. Their scopes differ, so the rows are not comparable installed offers.
Swipe to compare →
BTI’s $20–$30 monthly cloud figure equals $240–$360 per door annually when multiplied by 12. That falls within its broader $200–$400 annual range, so the two presentations alone do not establish a contradiction.
Kisi publishes materially different licensing figures, while its installation-component figures match BTI’s. Matching numbers do not provide independent validation, and different license figures may cover different services or billing units. Confirm scope before interpreting either comparison.
The useful distinction is installed cost versus recurring cost. Do not average these rows or choose a cheapest provider from them. Instead, use your opening schedule to request quotes for the same work.
Carry the opening scope into each proposal
Give every provider the same requirements. For the illustrative lobby, the proposal should address door preparation, lock retention or replacement, reader and controller work, door-state and exit devices, cable pathways, power, network work, release integrations, permits, commissioning, and support. BTI identifies installation conditions and equipment choices as cost drivers. Those details explain why a reader price cannot define the installed cost.
Some equipment may serve several openings. Ask which controller, power, or network costs are shared so you do not automatically treat each as a separate per-door charge. Keep shared infrastructure visible alongside opening-specific work.
Suppose one proposal includes lock and cable work while another lists only a reader and subscription. Their totals answer different questions. Have the second provider price the missing work or identify another party responsible for supplying it. Unpriced work is unresolved, not free.
Include the retain/replace/verify record with each proposal. If one provider would keep the lobby lock and another would replace it, compare the reasons and resulting work before comparing totals. Keeping compatible equipment or upgrading a few openings in phases can be a valid result, not an incomplete version of full replacement.
Compare five years without double-counting
Coram recommends a five-year cost view. Use quoted amounts to compare upfront installed cost plus five years of non-overlapping recurring charges. State support, credential, and replacement assumptions separately, and identify whether they are already included elsewhere.
Check where the first year’s subscription sits. If it is included in a first-year total, add only the remaining four years of that same charge. If you start with installation alone, include all five years. Identify quoted contract increases and variable fees, and leave unknown amounts unresolved rather than adding an unsupported allowance.
Include ownership and termination terms in the comparison. Get written answers about what stops if the subscription ends, whether local entry continues, who owns the equipment and administrative accounts, whether data or permissions can be exported, and who supports retained hardware. A lower recurring fee does not answer those questions, nor does an architecture label.
Assess where ButterflyMX fits the defined requirements
Evaluate ButterflyMX against the same opening schedule you give every provider. Its access control specifications document smartphone, fob, key card, and PIN credentials; a UL 294-listed controller and readers; and controller inputs and outputs for door-state, exit, and locking functions. These are first-party specifications, not approval of a complete installation or proof of suitability for every opening.
Credential-based entry and remote administration may fit your operating needs. Get written confirmation of retained-device compatibility, landlord and tenant administration, required integrations, and coverage for specialized interior or high-security openings. A controller listing or commercial product overview does not establish universal compatibility or suitability at every scale.
ButterflyMX also describes offline access and backup-battery provision for power loss on its product page. Before marking the lobby requirement as satisfied, obtain configuration-specific answers about battery runtime, each credential method, revocation, event recovery, and the four separate failure scenarios. The general feature description does not answer all of those questions.
Keep video-intercom entry separate from building-wide permissions. ButterflyMX documents elevator access controls that temporarily unlock a key-fobbed elevator in a residential workflow. That example does not establish commercial tenant-floor mapping. Confirm commercial floor permissions and elevator-provider integration separately.
If your worksheet suggests a potential fit, review the specifications against your opening schedule and explore ButterflyMX for commercial properties. A limited upgrade, retention of working equipment, or another platform remains a valid outcome of that review.
Verify operation and ownership before handover
Access control commissioning, the process of checking the installed system against agreed requirements, should demonstrate more than a successful unlock. For the illustrative lobby, acceptance includes its public-hours schedule, controlled after-hours entry, and agreed internet-loss behavior. Apply the same approach to suite and service-opening permissions.
Have the installer demonstrate authorized, revoked, and wrong-schedule credentials; relevant door-state and held-open events; and the agreed outage scenarios. Coordinate safety-critical release tests with qualified personnel. Do not alter or disable safety systems yourself to test a claim.
Set realistic expectations for records. Coram cautions that credential logs are not proof of who entered. An access-granted event does not establish the identity or number of people who passed through. Logs, photos, and paired video do not by themselves eliminate tailgating or credential misuse.
At handover, obtain operating documentation, configured schedules and permissions, administrative ownership, and the final retain/replace record. Your support route should identify responsibility for the access system, network, door hardware, and integrations. Assign credential reviews, offboarding, and required inspections to named roles.
Inspection duties may continue after installation. For its covered arrangement under the 2020 Minnesota State Fire Code, Minnesota State Fire Marshal guidance calls for monthly sensor and manual-release checks and annual fire-system and power-loss checks. That is a Minnesota example, not a national maintenance schedule. Have your project professional identify the duties that apply locally and who will perform them.
Close the worksheet by assigning each remaining question. The installer handles condition, compatibility, and proposed work; the qualified code professional and relevant authority address applicable requirements; the vendor documents outage behavior and contract terms; and management owns access approvals and daily administration. Those answers turn your initial door schedule into a scope you can price, test, and operate.
Frequently asked questions
Can access control be added to just one door?
Yes. A limited upgrade can be appropriate when only one opening needs new control. Keep door condition, compatibility, power, and exit assessment in scope. Plan for expansion if you need it rather than assuming every door must join the project.
Does a video intercom replace building-wide access control?
Not automatically. An intercom handles an entry conversation or visitor-entry workflow and may include access features. Determine separately whether shared entrances, tenant suites, and service areas need managed permissions, schedules, and records. Some properties may need only a limited solution.
What happens if the access control subscription ends?
The answer depends on the product and contract. Get written terms covering continued local entry, administrative access, permission changes, data export, and support. Cloud and on-premises labels do not establish what happens at termination.
Can tenants administer their own employee access?
Confirm that the proposed platform supports the tenant administration you need. Define which suite permissions a tenant may manage and which shared-building permissions remain with the landlord. Assign responsibility for employee approvals, departures, and schedule conflicts.
What if a user cannot use a mobile credential?
Include a documented fallback using cards, fobs, or PINs supported by the proposed system. Assign issuance, replacement, and revocation responsibilities. Confirm how fallback methods behave during outages rather than assuming every credential works the same way.
The right commercial building access control scope starts with openings and responsibilities, not a platform label. Define who needs each door and when, obtain professional reuse and exit assessments, and get written operating answers before comparing installed costs and recurring charges.
Start with the lobby row and resolve its unknowns. That work may support a broader project, but it may also show that a limited upgrade is enough. If ButterflyMX appears to fit, explore ButterflyMX for commercial properties with your opening schedule and compatibility questions in hand.
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.