Commercial Access Control: How to Scope Doors and Compare Quotes

Profile image for Aaron Rudenstine
Aaron Rudenstine
Updated 22 min read
commercial access control system
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:

  • Define who needs each opening, when they need access, and who may change their permissions before choosing equipment.
  • Have qualified professionals verify existing hardware, safe exit, and outage behavior before accepting promises about reuse or offline operation.
  • Compare prices only after proposals cover the same work, recurring fees, testing, training, and support responsibilities.

 

commercial access control system 

Commercial access control uses credentials and permissions to decide who may enter a particular door at a particular time, then records the event. For an existing office building, choosing a system starts with those access rules, not with a reader or an app.

If several tenants share an entrance, you also need to know what can stay. Existing locks, cards, and wiring may be useful, but an installer must assess their condition and compatibility before promising reuse. Without that assessment, two quotes can look like competing prices while covering different jobs.

This guide follows a hypothetical three-tenant office from access control system rules to proposal comparison. Use it to define a common scope for installers and identify the unanswered questions that could change the work or price.

This guide will answer:

More than 100K, 5-star ratings!

What is commercial access control and how does it work?

A commercial access control system manages physical entry to a building or area. It checks a credential and its permission for a particular opening and time, commands the lock, and records the event. This differs from logical access control, which manages access to IT systems.

The commercial requirement is not a minimum number of doors. It often involves managing different users, schedules, and administrator responsibilities. Axis describes these layered permissions for employees, contractors, and visitors. 

The access decision follows six steps:

  1. A person presents a credential, such as a card, fob, or supported mobile credential.
  2. The reader sends credential data to the controller or decision service.
  3. The system validates the credential, a step often called authentication.
  4. The system checks authorization: whether that credential may use this opening at this time.
  5. The controller commands the lock to release or remain secured.
  6. The system records the access event.

Credential validation and authorization answer different questions. Suppose an employee in our hypothetical office presents a recognized card at the shared entrance after their approved hours. The system can recognize the card and still deny entry. Recognizing the card also does not prove that its holder is the person it was issued to.

A keyed lock controls entry through possession of a key. A standalone smart lock may add electronic credentials and local rules without providing coordinated administration across the building. A video intercom supports visitor communication and entry, but should not be assumed to provide the entire access control function. A simpler setup can still be enough when its functions meet your needs.

For an early budget reference, WCC Tech publishes a 2026 Southern California estimate of $1,500–$4,500 per door installed, including reader, controller, lock hardware, cabling, and labor. It lists cloud licensing separately at approximately $150–$300 per door annually. This is one integrator’s estimate without a disclosed methodology, not a national average or a quote for your doors.

To judge whether a system or a per-door price fits your building, first define who needs each opening, when they need it, and who may change those permissions.

 

Turn building use into an opening-by-opening scope

Your first task is to describe the access you need, not choose hardware. That description gives an installer a clear outcome to assess and price.

 

Map shared entrances and restricted areas

Consider a hypothetical three-tenant office with a shared entrance, tenant-controlled areas, and a restricted service room. We will use these planning circumstances throughout the guide, without assuming any inspection findings.

Create an opening schedule: a location-by-location inventory of the doors and other access points under consideration. Here, schedule means an inventory, not permitted entry hours. Elwin Security recommends defining people, places, and times before selecting products.

For the shared entrance, record which tenant groups need entry and their approved hours. For each tenant area, record who should be admitted from the common space. List service-room permissions separately. An employee who may enter the building does not necessarily need access to that room.

 

Assign administrator boundaries and access rules

Next, decide who manages those permissions. One possible model gives the base-building team control of shared entrances and service areas, while each tenant administrator manages their employee roster within agreed limits. Approve that division with the relevant parties and confirm that the proposed platform supports it. It is an operating choice, not a legal assignment of responsibility.

Define who approves enrollment, changes schedules, sets expiration dates, revokes access, and reviews permissions. When an employee leaves, a clear revocation process matters more than remembering to collect their card. Permissions organized by user, location, and schedule provide a useful basis for these rules.

In our hypothetical building, each tenant could maintain its roster while shared-entry permissions follow building-approved schedules. Service-room access would need separate approval. Role-based groups let you apply a common rule to a group, such as a tenant’s employees, without granting that group every opening.

 

Define visitor and contractor routes

A visitor may need the shared entrance and a destination floor, but not the service room or another tenant’s office. Define that route before choosing how visitors will be admitted. For contractors, record permitted locations, entry hours, the approver, and an expiration date. Assign who may extend or revoke their temporary access.

If the route includes an elevator or vehicle gate, give it separate scope. Elevator and gate work differs from an ordinary door connection. Elevators require floor permissions, compatible interfaces, and coordination with the elevator contractor. Gates add vehicle approach, reader placement, weather exposure, cable distance, and staff overrides. Access control does not replace the elevator system or gate operator.

You can now describe the hypothetical shared entrance: approved employees of all three tenants use it during their assigned hours; the base-building team sets shared-entry rules; tenants maintain their rosters within those limits; visitors follow an approved route; and service-room access remains separate.

Mark the existing lock, reader, controller, and wiring as unverified. You have defined how access should work. The next step is finding out what physical work will deliver it.

 

Assess existing doors and exit requirements before promising reuse

You may be able to keep existing access control hardware, but a qualified installer must verify its condition, exact compatibility, and suitability for your requirements. Elwin’s retrofit guidance treats reuse as something to establish, not assume. A new reader cannot fix a worn latch or a door that does not close correctly.

 

Assess the complete controlled opening

A controlled opening is a connected assembly. The door, frame, and latch must work mechanically. Electrified locking hardware controls entry, the reader receives credential data, and the controller applies access rules. Electric strikes and magnetic locks are examples of locking devices, not interchangeable choices for every door.

A door position switch reports whether the door is open or closed. A request-to-exit device signals an exit request as part of the designed arrangement. Power and wiring support these functions, while software and configuration connect the equipment to users and schedules. The Security Industry Association’s component primer, authored by an HID employee, explains these basic roles.

Have the installer assess closing and latching, lock and exit hardware operation, reader and credential compatibility, controller capacity and support, and power load and backup. Cable checks should cover type, route, condition, and test results. Existing cable is not suitable simply because it is already in the wall.

For each relevant item, request a documented status: verified reuse, repair, replacement, or unresolved assessment. You commission these professional checks rather than perform electrical or compatibility tests yourself. In our hypothetical shared entrance, reuse remains unresolved until an actual assessment establishes otherwise.

 

Separate controlled entry from safe exit

A fail-safe lock releases on power loss. A fail-secure lock remains secured on the controlled side. Neither label alone tells you whether occupants can leave: a door can remain secured against entry while allowing people to exit.

NFPA’s 2021 staff explanation of egress door operation describes the principle that occupants must be able to operate doors from the exit side, generally without a key, tool, or special knowledge. This is conceptual commentary, not adopted code text or a compliance decision for your property.

Have a qualified professional assess the complete opening, exit path, required release methods, and applicable adopted code. The authority having jurisdiction, or AHJ, may also need to review or approve the arrangement. Do not choose fail-safe or fail-secure based only on a general security preference.

Equipment certification is a separate question. UL 294 addresses access control system units, including construction, performance, and operation. A listed component does not establish that an installation meets code. Whether listed equipment is required and the installation is acceptable needs project-specific professional and AHJ assessment.

These checks affect price as well as design. A proposal that assumes the shared-entry lock can stay is not equivalent to one that includes replacement until reuse is assessed and both cover the agreed work. Once those physical constraints are clear, you can evaluate how the system will be managed.

 

Choose management architecture around operating responsibilities

First decide whether you need standalone or centrally managed access. Central management becomes useful when shared entrances need coordinated schedules, prompt revocation, and clear administrator boundaries. A small door count does not settle the choice. If your requirements are limited, consider whether a basic access control system is enough.

 

Cloud management

Cloud management places management software with a provider and can support remote administration across properties. Review who maintains the service, who authorizes permission changes, where data is held, and what the subscription includes. Kastle’s architecture discussion describes these operating tradeoffs, though it is vendor guidance rather than an independent comparison.

For our office example, the key question is whether each approved administrator can manage the assigned people and areas without exceeding their limits. Cloud management alone does not establish where door decisions happen or what continues during an internet outage.

 

On-premise management

On-premise management runs software locally and gives your organization more direct responsibility for servers and data. That includes updates, backups, maintenance, and IT support. Name who will do that work rather than treating a local server as a one-time purchase.

Compare those duties with the cloud provider’s service obligations. Neither model is automatically cheaper or more secure. The choice depends on staffing, sites, data requirements, and service terms.

 

Hybrid configurations and connectivity

Hybrid access control combines hosted and local functions, but the label needs an explanation. Ask the provider to document what runs where, which component makes access decisions, and which tasks need a connection to the hosted service.

Keep management location separate from how devices connect. Wired and IP connections can overlap: IP describes network communication, not the absence of wires or controllers. Neither determines credential choice, reader protocol, or lock behavior. Wireless data also does not remove the need for power.

Record your administrators, available IT support, data-storage and control requirements, number of sites, and expected service costs. These needs narrow the management choice. You still need to establish what users will present at the reader and what happens when normal service fails.

 

Watch how ButterflyMX works:

 

Choose credentials that users and administrators can manage

Choose credentials by considering both the people who use them and the people who manage them. Elwin’s credential and retrofit guidance connects that choice to users, compatible equipment, and the upgrade path.

Cards and fobs need a process for issuance, returns, loss, replacement, and deactivation. Familiar key card entry still depends on current permissions. The system cannot act on an employee’s departure unless its access record is updated, and a card can be shared with someone else.

Mobile credentials require supported phones or platforms, compatible equipment, onboarding, and a lost-phone process. Provide another entry method for people without suitable phones. PIN access requires rules for issuing, changing, and expiring codes. Shared PINs weaken individual accountability, although that does not mean every keypad lacks per-user logging.

Restricted spaces may warrant evaluating biometrics or multifactor access. Biometrics add enrollment, consent, retention, and privacy responsibilities, with legal requirements varying by jurisdiction. Choose them to meet a defined need, not because one credential category is assumed to be universally better.

Our hypothetical office might want to retain employee cards while adding mobile entry. Treat this as a requirement to verify. The exact readers, controllers, software, and credential technology must support the combination. A product listing both cards and mobile entry does not prove it works with your existing cards.

The reader-to-controller connection is another compatibility question, separate from the credential. Wiegand is a legacy interface; SIA describes OSDP as supporting two-way communication, device-status supervision, and AES-128 Secure Channel encryption. Ask the installer to confirm exact support, whether Secure Channel is enabled, and what an upgrade would require. Support alone does not prove encryption is active or justify replacing every legacy reader.

A successful entry tests only part of this setup. Your access rules also depend on expiration, revocation, schedule limits, and an approved fallback when a credential or connection fails.

 

Define outage behavior and commissioning requirements

Commercial access control may work without internet, but behavior varies by product and configuration. A door may continue making local decisions while remote administration or visitor functions are unavailable. An offline claim does not tell you which permissions remain available or whether the latest changes have arrived.

 

Specify each failure separately

Require written answers for each relevant failure. Use these scenarios as a planning framework, not a certification checklist:

  • Power loss: Identify which components have backup power, how long it is stated to last, and how the complete opening responds.
  • Local network failure: Identify what can still make access decisions, which permissions it uses, and which devices lose communication.
  • Internet loss: State which local access functions continue and which remote administration or visitor functions pause.
  • Hosted-service disruption: Explain what becomes unavailable if the provider’s service fails while the building still has power and internet.
  • Credential or reader failure: Define the approved fallback and who may authorize it.

For each scenario, document event storage and recovery. Event buffering means storing events locally for later transfer. Cached permissions are access rules retained locally. Confirm whether the proposed system has these functions and what their limits are.

Suppose a tenant administrator revokes an employee’s credential while the hypothetical shared-entry controller is disconnected. Another card working offline would not prove that the revocation reached that controller. The proposal needs to explain when permission changes arrive, which rules remain available locally, and how records are brought up to date after recovery.

Backup power needs the same detail. A battery serving one component does not establish that the reader, controller, lock, and required network equipment will all remain available. Nor does backup duration establish safe exit. Kastle discusses backup power and lock behavior; your installer must document the response of the complete proposed setup.

 

Commission the required outcomes

Commissioning is the installer-led process of demonstrating that the configured system meets agreed requirements. Include approved, denied, expired, revoked, and wrong-schedule credentials. Test held-open behavior where configured, along with safely planned outage and recovery scenarios.

Witness the relevant demonstrations and receive records of the results. Do not improvise power-loss tests in an occupied building. Compare results with the written requirements, then record any unresolved items and who must address them.

Include these demonstrations in every proposal. A promised capability without a defined configuration, test, or support owner leaves work unresolved, just like an unverified lock-reuse assumption.

 

Budget installation, ongoing service, and implementation time

A useful budget follows the assessed openings and required outcomes. A per-door figure gives you a starting point, but it cannot show whether two installers are pricing the same project.

 

Interpret installed cost per door

WCC Tech’s 2026 Southern California guide estimates $1,500–$4,500 per door installed for reader, controller, lock hardware, cabling, and labor, plus approximately $150–$300 per door annually for cloud licensing. This is one integrator’s estimate without a disclosed methodology, not a national average or a quote for our hypothetical office.

The condition of each opening affects how useful that range is. Keeping verified compatible equipment requires different work from converting a mechanical lock. Door repair, cable routes through finished walls, and exterior-rated equipment can also change the scope. Active Alarm identifies door construction, cable routes, and exterior exposure as cost drivers.

Do not assume an installed per-door estimate includes every integration, permit, or handover task. Total project cost includes the whole scope, including work shared across openings.

 

Separate upfront, recurring, and lifecycle costs

Upfront costs include hardware, labor, configuration, and testing. Recurring costs may include software licensing, support, and server or service obligations. Lifecycle costs cover credential changes, maintenance, upgrades, and eventual replacement.

Choose one planning period, such as five years, and have each bidder show the same cost categories over that period. Record billing units, subscription length, renewal terms, and assumptions. This lets you compare total cost of ownership without assuming cloud or on-premise management wins on price.

WCC Tech highlights omissions that can make low quotes misleading, including lock conversions, integrations, license periods, credentials, old-system removal, permits, and training. Verify these items rather than treating them as universal charges. An omitted item is not a saving until you establish that your required outcome does not need it.

 

Set an installation schedule with explicit assumptions

As a planning illustration, WCC Tech’s same 2026 Southern California guide estimates 1–2 weeks for a five-door project. No methodology is disclosed. That figure is neither a guaranteed schedule nor a defined amount of onsite labor.

Have your installer state the assumptions for survey work, equipment procurement, trade coordination, configuration, commissioning, and tenant disruption. Ask what must be finished before each stage begins and which dependencies could change the installation timeline.

A phased upgrade may retain compatible equipment and spread disruption when the assessed upgrade path allows it. Document how credentials and administration will work between phases. You can then give every bidder the same opening inventory, reuse findings, operating requirements, and cost period.

 

Compare proposals against the same opening schedule

Before comparing totals, give every bidder the same openings, permission outcomes, integrations, outage expectations, and planning period. Elwin’s proposal checklist connects these requirements to hardware, subscriptions, commissioning, handover, and support.

Copy this aid for each opening and bidder. Its cells tell you what to record; they are not findings about actual proposals. It is a procurement tool, not an engineering specification or compliance checklist.

Swipe to compare →

Scope item Required outcome Included or excluded Unresolved assumption Fee term Responsible party
Opening condition and hardware Identify the opening, repairs, and compatible reader, controller, and lock. State assessed reuse, repair, replacement, and removal. Flag unverified door, lock, reader, or controller reuse. List one-time work, allowances, and priced alternatives. Name the assessing installer and door or hardware trade.
Power, wiring, and exit coordination Document suitable infrastructure, opening behavior, and professional review. State cable, power, backup, coordination, and permits where applicable. Flag untested cable, unspecified backup, and unresolved release requirements. Separate base work from conditional work. Name the installer and specialists; identify AHJ review where applicable.
Permissions, credentials, and integrations Deliver agreed users, schedules, administrator limits, credentials, and visitor routes. State configuration, credential quantities, and directory, visitor, alarm, gate, or elevator interfaces. Flag unconfirmed credential compatibility, interfaces, or specialist work. Separate setup, credential, integration, and recurring charges. Name handoff, implementation, and support owners.
Outage behavior and acceptance testing Document access, revocation, event storage, and recovery for relevant failures. State commissioning scenarios and safely planned outage demonstrations. Flag undocumented local permissions, update timing, or backup duration. Identify included and separately priced testing or configuration. Name the commissioning installer and the party accepting results.
Software, licensing, and support term Compare equivalent service over the same planning period. State licenses, coverage, updates, and server obligations. Flag unmatched periods and unclear renewal or support terms. Record billing unit, term, recurring fees, and lifecycle assumptions. Name the provider and owner-side administrator or IT contact.
Handover, training, and warranty Provide usable records, trained administrators, and a clear service path. State configuration records, diagrams, training, warranty, and support handoff. Flag missing records, training scope, or troubleshooting ownership. Identify included handover and warranty and support periods. Name the delivering installer, administrator, and support contact.

Return to our hypothetical shared entrance. Suppose one proposal assumes the existing lock can stay, while another includes replacement. The first depends on an unresolved reuse assumption. The second includes work that may or may not be needed. You cannot treat the lower total as an equivalent offer until an installer assesses the lock and both bidders price the agreed outcome.

If reuse is verified, have both bidders identify the work needed to retain it. If replacement is required, have both include the specified replacement work. If assessment remains open, obtain a clearly identified allowance or priced alternative rather than letting the assumption disappear inside a total.

Handle blanks and exclusions the same way. An empty training line does not mean training is free. An excluded elevator interface does not mean someone else has agreed to provide it. Get written clarification, align the work, and then compare totals and recurring obligations.

For integrations, record what information moves or what action occurs, who implements the connection, and who troubleshoots it. The SIA primer describes connections with other building and security functions, but a general integration category is not proof of a supported interface. Assign gate, elevator, intercom, and alarm work explicitly when included.

Require configuration records, relevant diagrams, commissioning results, administrator training, warranty terms, and a primary support contact at handover. Your comparison is ready when you can describe one opening, its users and schedules, the checks still outstanding, and whether each proposal covers the same work. Those requirements also give you a fair basis for evaluating a product.

 

Evaluate ButterflyMX against the defined requirements

ButterflyMX warrants evaluation when your scope calls for shared commercial entrances, remote permission management, and supported credential or visitor workflows. Its manufacturer documentation lists smartphone, fob, key-card, and PIN entry, along with commercial visitor features such as company-directory search, video calling, QR-code virtual keys, and access PINs.

Confirm which components and services deliver your needed workflow. Do not assume the controller alone provides every intercom or visitor function. Documented connections for doors, gates, and elevators also do not replace the gate operator or elevator system. Confirm interfaces, specialist coordination, and support ownership, including any complementary system needed for restricted interior spaces.

The manufacturer page inspected November 10, 2026 describes offline operation with a backup battery. Before relying on that capability, obtain configuration-specific confirmation of powered components, local permissions, revocation update timing, event storage, and recovery. The statement does not establish universal retrofit compatibility or detailed outage behavior for your building.

If these capabilities match your scope, explore ButterflyMX access controller and reader details and confirm the proposed commercial configuration. Repair, retaining a suitable existing setup, a simpler system, or a phased upgrade remain valid outcomes.

 

Frequently asked questions

 

Can I add access control to just one door?

Yes, a single opening can be a reasonable scope. An installer still needs to assess the door, locking and exit hardware, power, wiring, and administration needs. Door count alone does not determine whether standalone or centrally managed access is appropriate.

 

Can I upgrade an existing keycard system in phases?

Possibly, if the assessed equipment and upgrade path support it. Have the installer document what can remain, how credentials and controllers will work together, and who will manage access between phases. Each phase should preserve required functions and clear administration.

 

Can cards and mobile credentials work together?

They can when the selected readers, controllers, and software support the combination. Confirm the exact existing card technology and proposed mobile configuration, including fallback and revocation. A product listing both methods does not establish compatibility with every legacy card.

 

Is a standalone smart lock enough for a small office?

It may be enough when its functions meet the needs of your opening and users. Compare requirements for coordinated schedules, tenant administrator limits, remote revocation, and visitor access rather than assuming a larger platform is necessary. Have the complete opening assessed before deciding.

 

Who is responsible for fixing the system after installation?

Your proposal and service terms should establish that responsibility. Identify a primary support contact and define the roles of the installer, software provider, door or lock trade, and integration specialists. Warranty coverage and response obligations depend on the agreement, not a universal division of duties.

 

Start with one opening: define its users, schedules, administrator, and visitor route. Then have qualified professionals assess the physical opening and document required exit and outage behavior. Give every bidder that same scope, including unresolved assumptions, before comparing prices.

The right result is the work needed to meet those requirements. It may be repair, verified reuse, a simpler system, a phased upgrade, or replacement, not automatically the largest platform or the lowest headline quote.

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.

Aaron is the CEO of ButterflyMX. He specializes in building high-performing teams to launch and grow new technology products. He was a cofounder of Citymaps, which was acquired by TripAdvisor in 2016, and is an investor in Reddit, Button, Omaze, Henry The Dentist, Parallel Wireless, Clear Ballot, Pinata, and FilmRise. He is an angel investor, board member, advisor, author, and a results oriented technology executive with extensive experience at startups, growth-stage, and publicly traded companies. Aaron holds an MBA from Harvard.