Skip to main content
An access control site survey may document this mobile credential and the electronic door lock it operates.

Access Control Site Survey: What to Expect

What Does an Access Control Site Survey Cover?

If you are preparing to replace, expand, or standardize a commercial access control system, the site survey is where assumptions become facts.

A good access control site survey does much more than count doors. It verifies the physical openings, existing hardware, controllers, cabling, network conditions, credential environment, integrations, operating constraints, and other details that determine what the project actually requires.

For an IT Director, Head of Security, Facilities leader, or project owner, that matters because an access control proposal is only as accurate as the information behind it.

What is a commercial access control site survey?

A commercial access control site survey is a structured assessment of the locations, doors, systems, infrastructure, and operating requirements that will affect an access control project.

The goal is to understand the environment well enough to design the right solution and build a realistic scope of work. Depending on the project, the survey may cover one opening, one building, or a representative set of sites in a much larger multisite rollout.

A useful survey should answer questions such as:

  • Which doors need controlled access?
  • What locking hardware is already installed?
  • Are the doors and frames in good working condition?
  • What readers, panels, controllers, power supplies, and batteries exist today?
  • Can any existing equipment reasonably be reused?
  • What cabling is available?
  • Where will network connectivity come from?
  • How are credentials managed today?
  • Does the organization need cloud, on-premises, or hybrid management?
  • What video, identity, HR, visitor, alarm, or other integrations are required?
  • What happens during an internet, WAN, or power outage?
  • Are there opening-specific egress, fire-rating, or life-safety requirements that need coordination?
  • How will installation affect normal business operations?

The survey is not the final design by itself. It gives the design team verified information to work from.

Why should an access control site survey happen before the final project scope?

Access control touches too many parts of a building to scope accurately from a spreadsheet alone.

Two doors that look identical on a floor plan may require different work. One may already have compatible electrified hardware and usable cabling. The other may have a mechanical issue, an unsupported reader, no pathway for new cable, a fire-rating consideration, or a different egress configuration.

The same problem appears at the system level. A company may describe its existing environment as “the same system at every office,” only to discover that different locations were installed at different times with different panel generations, credential technologies, power supplies, firmware, and door hardware.

That is why a preliminary conversation can establish direction, but a verified site assessment is often necessary before a complex retrofit scope becomes final.

What should you prepare before the access control site survey?

You do not need a perfect set of records before calling an integrator. If your documentation is incomplete, finding out what is missing is part of the process.

Still, anything you can gather in advance makes the survey more productive.

Useful information may include:

  • Building floor plans
  • Door schedules
  • Existing access control drawings
  • Panel and controller lists
  • Reader models
  • Locking hardware records
  • Current credential types
  • Network diagrams
  • IP addressing or segmentation standards
  • Existing video surveillance platform
  • Identity provider or directory platform
  • HR system used as an employee source of truth
  • Current access groups or permission structure
  • Known service problems
  • Planned renovations
  • Construction schedules
  • Sites expected to open or close
  • Existing support or maintenance records

For a multisite company, a location list is especially useful. Include the site type, approximate door count, operating hours, region, and whether each location appears to use the same or a different access control platform.

Do not delay the conversation because some of this is missing. A strong integrator should help identify what needs to be documented next.

What does the integrator look at first during an access control survey?

The best starting point is the business problem, not the reader on the wall.

Before walking doors, the project team should understand why the organization is considering a change.

Common drivers include:

  • An aging or unsupported access control platform
  • Inconsistent systems across multiple locations
  • Difficulty managing users remotely
  • Too many manual onboarding or offboarding steps
  • Shared door codes
  • A need for better audit history
  • Expansion into new facilities
  • An acquisition that introduced another security platform
  • Repeated hardware failures
  • Cybersecurity concerns
  • A need to connect access events with video
  • A desire to move away from local servers
  • A need for mobile credentials
  • Poor post-sale support from the existing provider

That conversation changes the survey.

If the main problem is multisite administration, the survey needs to document differences between locations. If the problem is cybersecurity, the architecture, reader communication, software lifecycle, remote-support path, and administrative controls deserve more attention. If the business is opening ten new locations, repeatability and construction coordination become critical.

A survey should be driven by what the company is trying to fix.

How are the physical doors evaluated?

A commercial access control system depends on the physical opening working correctly.

During a survey, the integrator may document:

  • Door and frame type
  • Door condition
  • Alignment
  • Latching
  • Closer operation
  • Existing strike, lock, electrified trim, maglock, or other locking hardware
  • Door position switch
  • Request-to-exit or other egress-release components
  • Panic or exit hardware where present
  • Power transfer hardware where applicable
  • Automatic operator where applicable
  • Fire rating where known
  • Existing keying or mechanical override requirements
  • Reader location
  • Accessibility considerations that affect the opening

This part of the survey matters because access control cannot fix a door that does not reliably close or latch.

A new reader on a badly aligned door can produce a new-looking system with the same old service call.

Life-safety and code note

Electronic access control must be designed around safe, code-compliant egress. Requirements can vary by opening, occupancy, lock type, fire rating, locally adopted code, and the Authority Having Jurisdiction.

The International Building Code’s means-of-egress requirements include specific provisions for electrically locked and access-controlled doors. A site assessment can identify conditions that require coordination, but it is not a code approval. Final hardware and release behavior should be coordinated with the applicable code requirements, the AHJ, and the relevant fire-alarm, door-hardware, electrical, and building teams.

What existing access control equipment is documented?

The survey should create a clear picture of the current system.

That may include:

  • Access control software
  • Server or cloud platform
  • Controllers
  • Interface boards
  • Readers
  • Credentials
  • Electric strikes
  • Electrified locks
  • Request-to-exit devices
  • Door-position switches
  • Power supplies
  • Backup batteries
  • Network switches or connections serving the security system
  • Cellular equipment where used
  • Gateways or hubs for wireless lock systems
  • Enclosures
  • Cabling

Photos are useful because model numbers and field conditions are easy to misremember later.

The purpose is not to build a museum inventory. It is to determine what the organization has, what condition it is in, what is still supportable, and what fits the target design.

Can the site survey determine what existing hardware can be reused?

It can provide the evidence needed to make that decision.

Existing equipment should not be kept simply because it still powers on. It also should not be discarded automatically because the organization is changing platforms.

A reuse decision should consider:

  • Compatibility. Can the component work with the proposed architecture?
  • Condition. Is it reliable enough to remain in service?
  • Supportability. Can replacement parts, firmware, documentation, and technical support still be obtained?
  • Security. Does it meet the organization’s current security requirements?
  • Operational fit. Will keeping it make the environment easier or harder to support?
  • Lifecycle. Does reuse make sense for the expected life of the new system?

Reader communication is one example. The Security Industry Association’s Open Supervised Device Protocol, or OSDP, supports supervised bidirectional communication and Secure Channel encryption when properly implemented. If a modernization project requires OSDP Secure Channel, an older reader that cannot support the target design may not be a good reuse candidate even if it still reads cards.

The same logic applies to controllers, locks, cabling, power supplies, and credentials.

What happens when the integrator surveys panels, controllers, and cabling?

Panels and cabling often determine how much of a retrofit can stay behind the walls.

The survey may document:

  • Panel manufacturer and model
  • Controller generation
  • Expansion boards
  • Enclosure condition
  • Power supply
  • Battery age or condition
  • Available capacity
  • Cable type
  • Cable condition where visible
  • Labeling
  • Grounding or installation concerns visible to qualified personnel
  • Network connection
  • Physical security of the enclosure
  • Available pathways for new cable

The team should also verify where panels are located and whether technicians can reasonably access them for future service.

A panel mounted above a ceiling in a difficult-to-access area may technically work but create a poor long-term service experience.

Safety note: Panels and electrical or life-safety-connected enclosures should only be opened by authorized and qualified personnel following site safety procedures.

What network and cybersecurity information is reviewed during the site survey?

For IP-connected access control, the physical survey and the IT conversation need to meet.

The integrator may need to understand:

  • Available network drops
  • VLAN or segmentation requirements
  • DHCP or static addressing standards
  • DNS requirements
  • Internet connectivity
  • Cellular feasibility where proposed
  • Firewall and outbound connectivity requirements
  • Cloud destinations
  • Time synchronization
  • Remote-support expectations
  • Administrator authentication
  • Logging requirements
  • Vendor-risk review process
  • API or integration requirements

Many cloud-managed architectures can operate primarily through outbound encrypted connections, which may reduce the need for inbound firewall rules. That does not remove the need for cybersecurity review.

IT should still understand the vendor architecture, identity controls, device hardening, administrator roles, logging, remote support, update process, integrations, and connectivity requirements.

If cellular connectivity is proposed, the survey may also need carrier coverage and signal testing. A separate cellular path can reduce reliance on the local business LAN, but the access control platform, administrative accounts, vendor access, cellular equipment, and connected devices still need to be secured.

What should be reviewed about cloud access control during the survey?

Cloud-managed access control still has local field hardware.

Readers, controllers, locks, power supplies, sensors, and other components remain at the facility. The project team also needs to define what happens when internet or WAN connectivity is unavailable.

Questions may include:

  • Which users can still enter?
  • Which schedules continue locally?
  • Are events stored until connectivity returns?
  • How much local event storage exists?
  • What happens to a credential added during the outage?
  • What happens to a credential that was revoked while a controller was offline?
  • What happens after a controller restarts?
  • Is a secondary WAN or cellular path required at critical locations?

The answers depend on the selected platform and controller architecture. They should be documented rather than assumed.

What integrations should be discussed during an access control site survey?

The survey is the right time to identify integration requirements, even if the final configuration work happens later.

Common integrations include:

  • Video surveillance
  • Enterprise identity platform
  • Enterprise directory
  • Identity provider
  • HR platforms
  • Visitor management
  • Intercoms or door stations
  • Alarm systems
  • Elevators
  • Building systems
  • Parking or gate controls

The team should define the workflow, not simply write “integrate with video” on a scope sheet.

For example, if access control and video are supposed to work together, ask what the operator should be able to do. Should a denied-access event show the associated camera? Should an operator be able to search video from an access event? Should a door event appear in a central security interface?

Capabilities depend on the selected platforms, licensing, permissions, and camera-to-door configuration.

What credential information should be collected?

A credential strategy can affect every employee and contractor in the organization.

The survey or discovery process should identify:

  • Current card technology
  • Credential population
  • Mobile credential interest
  • PIN requirements where used
  • Multifactor requirements where supported and appropriately designed
  • Lost-card process
  • Contractor process
  • Visitor process
  • Temporary credentials
  • Credential printing or issuance workflow
  • Whether old and new credentials must coexist during migration

If the company wants mobile credentials, that does not automatically mean every card should disappear on day one.

A mixed credential strategy may make more sense during a phased deployment or for users who cannot use a mobile credential.

How are identity and HR workflows evaluated?

For IT-led projects, the access control survey should include the identity lifecycle.

The team should understand:

  • What system creates the employee record
  • When a new employee should receive physical access
  • Who approves access beyond a baseline role
  • How department or location changes are handled
  • What happens when an employee transfers
  • How quickly terminated users should lose access
  • How contractors are created and expired
  • What exceptions need manual approval
  • How failures are logged and reviewed

Automated offboarding only works when the source system, approval rules, timing, exception process, and integration are correctly designed.

The survey does not need to configure the identity system that day. It should identify the workflow the access control platform will need to support.

What does a multisite access control survey look like?

Surveying 75 locations one by one before making any design decisions is usually inefficient.

A better process is often to identify site archetypes.

For example:

  • Corporate office
  • Small branch office
  • Distribution center
  • Manufacturing site
  • Retail location
  • Mixed-use facility

The project team can survey representative sites in enough detail to understand common patterns and exceptions, then build a standard survey package for the remaining locations.

That package might define:

  • Required photos
  • Door naming
  • Hardware fields
  • Controller information
  • Network information
  • Site contacts
  • Local operating hours
  • Egress and fire-rating observations that require coordination
  • Exceptions from the enterprise standard

The goal is not to assume every site is identical. It is to collect information consistently enough that differences can be managed.

How should business operations affect the survey?

A technically correct design can still be a bad project if installation ignores the way the facility operates.

The site survey should identify:

  • Business hours
  • Shift changes
  • Public entrances
  • Shipping and receiving periods
  • High-traffic doors
  • Clean-room or restricted areas
  • Manufacturing shutdown windows
  • Construction phases
  • Tenant coordination
  • Areas where dust, noise, or drilling is restricted
  • Security coverage needed during cutover
  • Who can authorize temporary door conditions

This information helps the implementation team build a rollout plan around the business instead of forcing the business around the installation.

What should happen after the site survey?

The survey should produce more than a folder of photos.

The project team should be able to turn the findings into a verified design and scope.

Depending on the project, deliverables may include:

  • Door inventory
  • Existing-hardware inventory
  • Photos
  • Panel and controller inventory
  • Reuse recommendations
  • Replacement recommendations
  • Network requirements
  • Integration requirements
  • Credential strategy
  • Site exceptions
  • Life-safety or code-coordination items
  • Preliminary architecture
  • Phasing recommendations
  • Assumptions that still need verification
  • Project scope

For a multisite rollout, the survey may also produce a site taxonomy, deployment standard, pilot recommendation, and repeatable survey template for later locations.

This is where the site survey connects directly to the quote. The more accurately the environment is understood, the less the project needs to depend on broad assumptions.

What should you expect from a good access control site-survey experience?

You should come out of the process understanding your environment better than when you started.

A good integrator should be able to explain:

  • What they found
  • What is reusable
  • What should be replaced
  • What remains unknown
  • Which decisions belong to IT
  • Which decisions belong to Security or Facilities
  • Which openings require additional door-hardware or life-safety coordination
  • What the recommended architecture is trying to accomplish
  • How the project could be phased
  • What information is still needed before the final scope

You should not need to become an access control engineer before having that conversation.

The integrator’s job is to make the technical decisions understandable enough for your team to make informed choices.

What should make you question a site survey?

Be cautious if a complex retrofit survey:

  • Focuses only on readers and ignores the rest of the opening
  • Never looks at the existing panels
  • Does not involve IT for an IP-connected system
  • Assumes every existing component should be replaced without evaluation
  • Assumes every existing component should stay because it still works
  • Never asks about outage behavior
  • Ignores identity and credential workflows
  • Does not document site conditions
  • Treats life-safety requirements as a generic one-line checkbox
  • Produces no clear record of assumptions
  • Does not explain what happens after installation

A survey should reduce uncertainty.

If it creates a quote without creating a clearer understanding of the environment, it did not do enough.

Frequently asked questions about commercial access control site surveys

How long does an access control site survey take?

It depends on the number of openings, the complexity of the existing system, the quality of available documentation, the number of integrations, and whether the site represents a larger multisite rollout. A small office and a large manufacturing facility should not be expected to take the same amount of time.

Do we need drawings before an access control site survey?

No. Existing floor plans, door schedules, and security drawings are helpful, but incomplete documentation should not prevent the assessment from starting.

Does every door need to be surveyed?

For a final retrofit scope, each affected opening may need verification. In a large multisite program, representative sites and standardized survey templates can help establish the design before every remaining location is assessed.

Can a site survey tell us whether existing readers and controllers can stay?

It provides the field information needed to make that decision. Compatibility, condition, supportability, cybersecurity requirements, and lifecycle all need to be evaluated before reuse is recommended.

Is a site survey the same as a code inspection?

No. A site survey can identify conditions that require code or life-safety coordination, but final requirements depend on locally adopted codes and the Authority Having Jurisdiction.

Should IT attend an access control site survey?

IT does not necessarily need to walk every door, but IT should be involved early when the project includes network-connected controllers, cloud management, identity integrations, cybersecurity review, remote access, APIs, or vendor-risk requirements.

What happens after the survey?

The findings are used to refine the system design, document assumptions, identify reusable and replacement equipment, define integrations and network requirements, coordinate exceptions, and build the project-specific scope.

A better project starts with a better understanding of the site

A site survey should make the project clearer before installation begins.

That means understanding the doors, the existing system, the network, the people who administer access, the locations that need to work together, and the operating conditions the installation team will have to respect.

That is part of The Alen Advantage. The relationship starts with expertise before equipment is ordered, continues through expert installation, and stays in place when the system needs service, changes, or expansion later.

You do not need every answer before starting the conversation. Tell Alen Security what you are trying to fix, where the system is installed, and what you know about the current environment. We can help determine what should be assessed next.

Start a commercial access control project assessment with Alen Security.

An access control site survey may document this mobile credential and the electronic door lock it operates.

See Alen Security’s commercial access control services.

How to Standardize Multi-Site Access Control

How do you standardize multi-site access control?

Multi-site access control becomes hard to manage when each office uses a different platform, credential policy, and service process. One site inherits a landlord’s system. Another is added through an acquisition. A warehouse installs readers during a rushed repair. Soon, your team needs three calls to answer who can enter Site 27.

A workable standard sets one management model across locations: who grants access, which credentials are approved, how systems connect securely, what each site documents, and who supports a failed door. The hardware can vary when a building calls for it. The rules and ownership stay clear.

Start by inventorying your sites and defining the target model. Then pilot it at a few different buildings, record approved exceptions, and migrate in phases. This guide shows what to put in the standard and how to make it useful for IT, Security, Facilities, and local teams.

Employee uses a card reader at a commercial entrance in a multi-site access control system

Why do access control systems become fragmented across multiple locations?

Access control systems usually fragment as companies grow and local teams make decisions without a shared plan for the future. Common causes include:

  • Acquisitions
  • Regional purchasing
  • Landlord-provided systems
  • Different construction partners
  • Local IT ownership
  • Equipment installed before a corporate standard existed
  • Products reaching end of life at different times
  • Different industries or occupancy types across the portfolio
  • Emergency replacements that became permanent

None of these causes are unusual. The problem starts when a company keeps adding locations without deciding what the future environment should look like.

The U.S. General Services Administration (GSA) has faced the same enterprise challenge at a much larger scale. Its current Physical Access Control Systems directive describes an agency-wide approach to updating, procuring, and installing PACS while migrating disparate systems toward an enterprise environment.

A private company does not need federal requirements to use the same principle: define the enterprise model before each site solves the problem on its own.

What should a multi-site access control standard include?

The standard should answer everyday operating questions before it lists products.

A multi-site access control standard should define what every location needs to support, how teams should install and manage the system, and what happens when a site needs an exception. It should cover daily administration, equipment, security requirements, documentation, and ongoing support.

Think about the questions that land on your desk. Can you remove someone’s access across every location? Can a local manager issue a badge without getting access to the entire company? What keeps working if a site loses its internet connection? Your standard should give everyone clear answers.

Define what every location needs to support

Start with how your team needs the system to work each day. Once you agree on those expectations, you can choose equipment and configurations that support them.

  • Central visibility: Define what your team needs to see across locations, including access events, equipment status, and alerts. Someone supporting multiple sites should know where to look when a local manager reports a problem.
  • Remote administration: Specify which tasks authorized staff should be able to handle remotely, such as updating schedules or changing access permissions. That helps your team understand when it can resolve a request from its desk and when someone needs to visit.
  • Consistent credential policy: Set company-wide rules for issuing, replacing, and removing cards or mobile credentials. Employees and local managers should know what to do when someone joins, leaves, or loses a badge.
  • Defined offline operation: Spell out what must keep working when a location loses connectivity. Include how the system handles existing credentials, schedules, stored events, and updates that cannot reach the site during an outage.
  • Central user deactivation: Define how your team removes a person’s access across the locations they can enter. Include how it confirms the change and handles sites that are temporarily offline.
  • Role-based administration: Match administrative permissions to job responsibilities. A local manager may need to issue credentials for one office, while corporate security needs broader control across the portfolio.

Set consistent rules for events, doors, and support

Your team also needs to understand what the system reports and how to respond. An alert or service request should provide enough information to start working on the problem.

  • Standard event naming: Use consistent names for events and alerts wherever the platform allows. Your team should be able to recognize the same type of issue across sites without learning a different set of labels at each location.
  • Documented door hardware: Require a record of the reader, lock, controller connection, and related hardware at each opening. That gives the service team something useful to work from before it arrives.
  • A repeatable service process: Define how people report problems, who takes ownership, and when to escalate a request. Local managers should know whom to contact without calling around to find the right vendor.
  • Minimum reader security requirements: Set the minimum security capabilities and configuration requirements for readers. Different locations may need different physical devices, but every approved reader should meet the requirements that apply to its use.
  • Access event retention: Specify how long the company keeps access events and who can retrieve them. Your team should know whether the records it needs will still be available when someone requests a review.

These expectations can stay consistent even when one location uses wired readers and another uses wireless locks. The equipment can vary within the standard while supporting the same company requirements.

Define the approved equipment and system architecture

Once you know what the system needs to do, document the approved technical approach. This gives your installers, IT team, and service partners a shared starting point for each project.

  • Platform architecture: Define the approved system architecture and how sites connect to it. Document where management happens, what runs locally, and which responsibilities fall to the company or its service partners.
  • Approved controllers: Identify the controller families your organization supports and where each is appropriate. That helps teams make consistent choices during new installations, expansions, and replacements.
  • Reader technologies: Specify the approved reader technologies and communication methods. Include the capabilities needed for your credential policy and the conditions where teams may use different reader types.
  • Credential policy: Turn your company-wide credential rules into installation requirements. Teams should know which credentials the equipment must support before they order readers for a new site.
  • Door monitoring: Define which door conditions the system needs to monitor and how it should report them. Include expectations for events such as a door held open or forced open, where applicable.

Establish network, cybersecurity, and integration requirements

Access control needs coordination with the teams responsible for your network, identities, and connected systems. Document those requirements early so they become part of the project.

  • Network requirements: Specify the connectivity, addressing, and firewall requirements for the approved system. Give IT the information it needs to prepare a site and support it after installation.
  • Cybersecurity requirements: Set expectations for authentication, permissions, encryption, updates, logging, and remote support. Each location should follow the same approved security requirements wherever they apply.
  • Administrator roles: Document who can administer the system and what each role can change. Include responsibility for approving permissions and reviewing whether people still need them.
  • Identity integrations: Define how access control connects with your organization’s identity systems, where applicable. Make it clear which system supplies user information and how teams handle changes or failed updates.
  • Video integrations: Specify where access events should connect with video and what users need to see. Your team should understand which integrations it supports and how to find the relevant camera view.

Make installation and documentation repeatable

A standard needs to guide the work at the site, too. Clear installation and documentation requirements help your next project build on the last one.

  • Naming conventions: Set consistent names for sites, doors, readers, controllers, and events. Someone supporting the system remotely should be able to identify the location and equipment without asking what “Back Door 2” means.
  • Site documentation: Require current floor plans, equipment records, panel locations, photos, and as-built changes. Define where teams store those records and who updates them when work changes the installation.
  • Installation practices: Document expectations for mounting, cabling, labeling, power, and coordination with door hardware. Give installation partners a clear definition of the work your company expects.
  • Testing and acceptance: Define what teams must test before they hand over a site and who signs off. Include the functions the location needs to support, with a record of any unresolved issues.

Plan for maintenance and site exceptions

The standard should keep helping your team after the project closes. Equipment needs service, buildings change, and some sites will need an approved variation.

  • Service and preventive maintenance: Define service responsibilities, maintenance activities, and how teams record completed work. That gives your company a consistent process for supporting equipment throughout its life.
  • Exception handling: Set a process for documenting a requirement a site cannot meet, the reason, the approved alternative, and who authorized it. Include whether the exception is temporary and when someone should review it.

A technician should be able to arrive at the next location with a clear understanding of your company’s approach, even if they have never worked at that particular site.

How do you apply a multi-site access control standard to different buildings?

Group sites by how people use them. A company can set repeatable patterns for each site type without forcing every building to use the same door schedule.

Group sites by type

Corporate office: Typical needs include lobby access, employee entrances, executive areas, server rooms, conference spaces, parking, and visitor workflows.

Warehouse or distribution center: Typical needs include employee entrances, dock areas, exterior gates, cages, high-value storage, and 24-hour operations.

Retail location: Typical needs include back-of-house access, manager areas, stock rooms, finished interiors, and limited local IT infrastructure.

Manufacturing site: Typical needs include shift changes, production entrances, maintenance areas, exterior doors, overhead bays, contractor access, and closer coordination around shutdown windows.

Standardize the management model

For an IT Director or Head of Security, the largest benefit may come from consistent administration rather than identical readers. Define:

  • Who owns the platform?
  • Who can create users?
  • Who can change access groups?
  • Can regional managers administer only their region?
  • Can local managers issue temporary credentials?
  • Who approves access to restricted areas?
  • Who reviews stale accounts?
  • How are emergency changes handled?
  • How are audit logs retained?

Multi-site administration often requires delegation. One corporate administrator may not be the right person for every routine request. Giving every local manager broad access to the whole system creates a different risk.

Map administrative rights to job responsibilities. This follows the identity-governance principle of giving people the access they need and reviewing it over time. NIST SP 800-53 includes controls for least privilege and periodic review of user privileges.

Set one credential policy

A multi-site company should decide what an employee credential means across the organization. Answer these questions:

  • Will one employee credential work at every location they are authorized to enter?
  • Are mobile credentials supported?
  • Do some workers still need physical cards?
  • How does the company handle contractors?
  • What happens when someone loses a phone?
  • What happens when someone loses a card?
  • How quickly should terminated employees lose physical access?
  • Which credential technologies are approved?

Credential choices affect readers, enrollment, identity integration, support, and the employee experience. Set the policy once instead of letting each location invent its own answer.

Define reader and controller requirements

Set requirements for the equipment without locking the company into one opening type. The standard can specify:

  • Approved controller families
  • Approved reader families
  • OSDP support where required
  • OSDP Secure Channel expectations
  • Mobile credential compatibility
  • Environmental ratings for exterior readers
  • Firmware support requirements
  • Backup power requirements
  • Enclosure standards

SIA’s OSDP standard gives organizations a vendor-supported path for supervised reader communication. SIA’s 2026 implementation checklist recommends verified devices and Secure Channel where OSDP is deployed.

These requirements can become part of the enterprise standard without requiring the same physical reader at every location.

Decide when existing hardware can stay

Standardization does not always require immediate replacement. A company with 80 sites may keep compatible existing controllers until a site is renovated, as long as it sets a clear rule. For example:

  • New sites: deploy the target standard.
  • Renovated sites: migrate to the target standard.
  • Existing sites with an unsupported platform: prioritize migration.
  • Existing sites with supported hardware: retain it until a planned upgrade.
  • High-risk doors: accelerate reader or credential changes.

A clear transition rule lets the company avoid a giant one-time replacement project as the only path to consistency.

How do you document and support multi-site access control?

Six months after installation, a door stops unlocking. Your team needs to know which reader serves it, where the panel sits, and what hardware was installed. If those answers live in someone’s inbox, a routine service call turns into hours of detective work. Clear site records and a repeatable support process make the next call easier.

Your access control standard should give every location a consistent way to name equipment, maintain records, follow cybersecurity requirements, and prepare for outages. That gives your team somewhere to start when something goes wrong.

Standardize naming and site records

“Back door” may make sense to the supervisor on site. It tells an IT director supporting 30 locations very little. Give each opening and device a unique name that matches the floor plan, platform, and service record.

  • Site code: Each location should use a unique identifier, by using them consistently in the access control platform, service tickets, and site records you’ll improve standardization. A quick check with you team is can they tell which location a record belongs to at a glance. If not your site code needs some additional work.
  • Building: Identify the building when a site has more than one. The main office and the warehouse may share an address, but a technician still needs to know where to go.
  • Floor: Include the floor or level so someone can find the opening without searching the building. Use consistent labels for basements, mezzanines, and other areas that might otherwise get different names.
  • Door name: Provide each controlled opening a clear, unique name that matches the floor plan and system records. “Site 27, Warehouse, Employee Entrance” gives your team more to work with than “Door 4.”
  • Door function: Record what the opening serves, such as an employee entrance, server room, loading area, or restricted storage room. That context helps your team understand how people use the door.
  • Reader name: Identify each reader and the door it serves. If a door has readers on both sides, make it clear which one controls entry and which one controls exit.
  • Controller name: Give each controller a unique name and record the doors it manages. When a controller goes offline, your team needs to know which openings may be affected.
  • Camera association: Note which camera, if any, covers the opening. That helps someone reviewing an access event find the relevant view without clicking through cameras across the entire site.
  • Alarm input name: Label each monitored input by its location and purpose. Someone receiving an alert should be able to understand what triggered it without first looking up what “Input 7” means.

Document what your team will need during a service call

Clear names help your team find the right equipment. Site records explain what’s there, how it connects, and what has changed. Keep those records somewhere the people responsible for support can actually find them, and make updating them part of the work whenever equipment changes.

When creating the document don’t miss out on these key areas:

  • Floor plans: Mark controlled doors and relevant equipment locations on a current plan. A technician should be able to use it to find the opening and understand where it sits within the building.
  • Panel locations: Record exactly where each panel is installed, including the room or closet. “Second-floor IT closet, north wall” saves someone from opening every utility room in the building.
  • Controller models: Record the manufacturer and model of each controller. That gives your team the equipment details it needs when checking compatibility, planning upgrades, or arranging a replacement.
  • Reader models: Identify the reader installed at each opening. Readers can look similar while supporting different credentials or communication methods, so appearance alone won’t tell your team what it needs to know.
  • Lock types: Record the type of locking hardware at each controlled door. A technician preparing to service an electric strike needs different information than someone working on an electrified panic device or magnetic lock.
  • Cabling: Document cable types, labels, and known routes between equipment. Your team should have a starting point for tracing a connection without having to rediscover how the installation was wired.
  • Egress devices: Identify the devices involved in allowing people to exit, including their locations and connections where documented. These details help the service team understand the opening before making changes.
  • Power supplies: Record which power supply serves each controller or locking device and where it is located. When equipment loses power, that connection helps narrow the troubleshooting process.
  • Battery dates: Record battery installation and replacement dates. That gives the team a maintenance history it can use instead of guessing how long a battery has been in service.
  • Network details: Document the network information your authorized IT and service teams need to support the system, such as device addresses, switch ports, and VLAN assignments. Keep sensitive information in the appropriate restricted records.
  • Photos: Include clear photos of panels, equipment labels, wiring, and door hardware. A useful photo can help a remote technician understand the installation before anyone makes a trip to the site.
  • As-built changes: Update the records to show what was actually installed and what changed afterward. If a controller moved or a door received different hardware, the documentation needs to reflect that.

These records become especially useful when you need to troubleshoot a door, plan an upgrade, or schedule maintenance across several locations. Alen’s current national AEC engagement includes documenting controllers, reader modules, readers, cabling types, and egress devices during site service. The case study explains how those records support future troubleshooting, upgrades, and maintenance.

Put cybersecurity requirements in the standard

Cybersecurity should not depend on which region installed the system. The enterprise standard should address:

  • Administrator authentication
  • Multi-factor authentication
  • Role design
  • Network connectivity
  • Inbound and outbound firewall requirements
  • Encryption
  • Reader communication
  • Remote support
  • API access
  • Logging
  • Software and firmware updates
  • Vulnerability notifications
  • Vendor account governance
  • Backup and recovery

NIST’s Zero Trust Architecture warns against trusting a system solely because it sits on an internal network. A controller on the corporate LAN still needs proper identity, configuration, updates, and monitoring.

A cloud platform is not secure just because it is cloud-managed. Define the organization’s security review criteria for every architecture.

Define how each site behaves during an outage

The company needs to know how each location operates when connectivity fails. Require the selected platform to answer:

  • Do authorized credentials continue working?
  • How long can the system store events locally?
  • Does it maintain schedules?
  • What happens to a newly terminated credential during an outage?
  • Can administrators still make local changes?
  • What happens after power loss and restart?
  • Do certain facilities need redundant internet or cellular connectivity?

Different sites may need different levels of resilience. A corporate office may tolerate a short delay in new credential updates. A 24-hour distribution center may need a different plan. Set those tiers before an outage happens.

Coordinate access control with life safety

An access control standard should never replace local code review. The 2024 International Building Code has different provisions for electrically locked egress doors depending on the locking arrangement and occupancy. UL’s access and egress control guidance explains why teams must coordinate electric locking with egress behavior, power loss, panic hardware, and life-safety systems where applicable.

A corporate standard can set a repeatable review process:

  • Require a door and hardware review.
  • Identify fire-rated openings.
  • Confirm panic hardware conditions.
  • Coordinate fire-alarm release where required.
  • Document the approved locking arrangement.
  • Require final local review where applicable.

Local requirements, occupancy, door use, fire rating, lock type, and the Authority Having Jurisdiction determine the final compliant configuration. A corporate standard should require a repeatable review, not assume that one locking detail works everywhere.

How do you pilot a multi-site access control standard?

Pilot the standard before applying it across the portfolio. A small test gives the organization a chance to find problems before they repeat at every site.

Test at pilot sites

Do not publish a 70-page corporate standard and roll it out to 100 locations without testing it first. Use pilot sites to check:

  • Does the naming convention work?
  • Can the service team troubleshoot the system?
  • Can local managers do the tasks assigned to them?
  • Are identity groups mapped correctly?
  • Is the credential process understandable?
  • Does the hardware fit real door conditions?
  • Are teams capturing documentation correctly?
  • Does offline behavior match expectations?
  • Are alerts useful or too noisy?

Revise the standard before scaling it.

Document every exception

Every multi-site standard will encounter a building that cannot meet every requirement. A historic door may not accept the preferred hardware. A landlord may control the lobby system. A remote site may lack reliable broadband. A warehouse gate may need specialized equipment.

Exceptions are not a failure. Undocumented exceptions are.

For every exception, record:

  • The requirement the site cannot meet
  • Why it cannot meet it
  • The approved alternative
  • The security impact
  • The support impact
  • Who approved it
  • Whether it is temporary or permanent

This keeps exceptions from quietly becoming a second standard.

How does Alen approach multi-site access control standardization?

When working with a national architecture, engineering, and construction firm with roughly 140 offices they used Alen Security as their single point of contact for a phased Brivo roll-out. We made a 2026 case study about this client’s experiences, which included completing 50 locations.

Alen coordinates deployment with each office’s construction and renovation schedule, uses repeatable configurations, and maintains site records for future support. The client has one point of contact as the program expands. That is how a standard becomes a practical service model across locations.

Frequently asked questions about multi-site access control

Does every location need the same access control system?

A company should aim for a consistent management and security model, but every opening does not need identical hardware. Site type, door condition, occupancy, environment, and business use can call for approved variations.

Can we standardize access control gradually?

Yes. Many organizations apply the target standard to new construction, renovations, end-of-life replacements, and priority sites first, then migrate the rest over time.

Can acquired companies keep their existing access control system temporarily?

Yes, if the organization documents the risk, administration, support, and migration plan. It should define whether the existing system is a temporary exception or a permanent environment.

Should IT own enterprise access control?

Ownership varies by company. IT should usually be involved in identity, cybersecurity, networking, vendor risk, and integrations. Security or Facilities may own daily physical access operations. The standard should make those responsibilities explicit.

What should be documented at each location?

At a minimum, document door names, panel locations, controllers, readers, locks, egress components, power supplies, cabling, network requirements, credential behavior, integrations, photos, and as-built changes.

Ready to turn local systems into one operating model?

You do not need every site to look the same. You need every site to fit a plan.

For Alen, Trusted… Everywhere means that the standard stays dependable across the locations where your business operates, without pretending every building is identical.

Alen Security can review your current portfolio, identify common patterns and exceptions, and help define a multi-site access control standard that your IT, Security, Facilities, and service teams can support.

Talk with Alen Security about multi-site access control standardization.

How to Secure a Commercial Lobby in 2027

A secure commercial lobby does not need to feel like an airport checkpoint

lobby hero

A busy IT director can easily underestimate the lobby. It may look like a reception desk, a waiting area, and a set of elevators. From a security standpoint, it is the point where employees, vendors, visitors, contractors, deliveries, and unknown individuals first meet the organization.

A secure commercial lobby does not need to feel like an airport checkpoint. It does need to answer a few basic questions consistently: Who is entering? Why are they here? Who approved the visit? Where does the organization allow them to go? What happens when something does not look right?

Heading into 2027, the strongest lobby-security programs use access control as the foundation and connect it with visitor management, video surveillance, intercoms, alarms, and clear operating procedures. The goal is simple: make legitimate access easy, make unauthorized access difficult, and give the organization a reliable record of what happened.

What is the best way to secure a commercial lobby?

The best way to secure a commercial lobby is to control the entry process electronically, verify visitors before granting access, connect access events with video, and limit movement beyond the lobby to approved areas. The system should also provide a practical response when a credential is missing, a visitor arrives unexpectedly, or an employee holds a door open for someone else.

That sounds straightforward. In practice, many lobbies fail because they rely on one isolated measure. A receptionist may ask visitors to sign a paper book, while an unlocked inner door allows anyone to reach the elevators. A camera may record the entrance, but nobody can quickly connect the video to a specific person or access event. A card reader may protect one door, but former employees still have active credentials because the access process does not connect to HR and IT.

Commercial lobby security is not one device. It is a controlled sequence:

A person approaches the building.

The organization determines whether it expects the person or has authorized them.

The person receives the right level of access.

The system records the event.

The visitor remains in the appropriate area until staff escorts them or approves their movement.

The organization can investigate or respond if the process breaks down.

CISA’s Interagency Security Committee describes facility access control as a process that includes employees and visitors from entry through the broader access-control lifecycle. NIST likewise treats physical access as a security control that organizations should authorize, monitor, and review—not simply assume because a door has a lock. CISA facility access control guidance and NIST physical-access controls provide useful frameworks even for organizations that are not federal agencies.

Why does the lobby deserve special attention?

The lobby deserves special attention because it is usually the least controlled space inside a commercial building and the place where the most people interact with the organization. Employees know the building. Visitors do not. Reception teams may be handling phones, deliveries, employee questions, and scheduled appointments at the same time. That combination creates gaps.

The lobby also creates a natural opportunity for social engineering. Someone may claim to be visiting an employee, delivering equipment, repairing a copier, or returning a badge. If the process depends on a busy employee recognizing every face, the organization is asking people to compensate for a weak system with attention alone.

The risk goes beyond theft. An unauthorized person may reach sensitive offices, observe employee routines, photograph screens, access network closets, follow an employee through a secure door, or create a situation that staff do not know how to handle. OSHA’s workplace-violence guidance recognizes that workplace-violence incidents can involve clients and visitors and recommends evaluating access control, visitor procedures, escorts, identification, lighting, and surveillance as part of a site-specific prevention program.

This does not mean every lobby needs guards, metal detectors, or a complicated screening process. It means organizations should design the lobby around the actual risk, the building’s layout, the hours of operation, and the people who use it.

What should a commercial lobby access-control system include?

A commercial lobby access-control system should usually include a controlled exterior entry, a protected interior boundary, credential readers, visitor procedures, video coverage, a way to communicate with people at the entrance, and an administrative process for issuing and removing access. The exact hardware depends on the building, but the operating logic should be clear.

1. A clearly defined entry point

Start by deciding where people should enter. If every exterior door is open during business hours, the lobby may not be functioning as a security boundary at all. A primary entrance gives the organization a consistent place to apply the visitor process and allows cameras, intercoms, signage, and staff attention to work together.

Secondary doors still matter. They may need scheduled unlocking, badge access, automatic relocking, door-position monitoring, or alarm notifications. Emergency exits must remain available for life safety, but that does not mean the organization should ignore them from a security perspective.

The point is not to force every person through one narrow path regardless of the building. The point is to know which doors are public, which are employee-only, which are emergency-only, and who is responsible for reviewing exceptions.

2. An inner security boundary

Many commercial lobbies have a front door but no meaningful boundary after reception. Once a visitor enters, they can walk toward elevators, stairwells, conference rooms, or employee work areas. Access control should create a second decision point where appropriate.

That may be a secured elevator lobby, a turnstile, a card-controlled interior door, or a reception-controlled release. The right design depends on the building and the visitor experience, but the principle is consistent: a person should not gain access to the rest of the facility simply because they reached the reception area.

3. Credentials that match the person’s role

Employees, contractors, vendors, and visitors do not need identical access. A modern system should support different credential types and schedules, including cards, mobile credentials, temporary credentials, PINs, or other approved methods.

The organization should base access on the person’s role, location, and time—not on convenience alone. An employee who needs access to a warehouse may not need access to executive offices. A cleaning contractor may need a limited schedule. A visitor may need access only to one conference room and only while someone accompanies them.

This is where standardization matters. If every location creates access differently, the IT director eventually inherits a maze of exceptions. Consistent access levels and naming conventions make the system easier to audit, support, and expand.

4. Visitor management tied to access control

Visitor management should answer more than “Did someone sign in?” It should establish who the visitor is, who they are meeting, whether the organization expected the visit, what access they received, and whether they left.

The process may include pre-registration, host notification, identification verification, a temporary badge, escort requirements, expiration times, and a visitor log. The important part is that the visitor’s authorization does not last forever and does not quietly become employee access.

Paper logs are easy to overlook, difficult to search, and vulnerable to incomplete entries. An electronic visitor process can create a clearer record and reduce how much judgment reception staff must exercise. It can also help the organization produce an occupancy picture during an emergency.

5. Video that supports the access event

Video surveillance is most useful when it helps answer a specific question. Who entered? Did the person who received the badge use it? Did someone follow behind them? Did someone hold the door open? Did the visitor go where the organization allowed them to go?

Camera placement should cover the approach to the entrance, the person’s face at the point of entry, the reception area, the interior access point, and other areas where movement matters. Avoid placing cameras where glare, backlighting, decorative walls, or poor angles make identification difficult.

When a security or IT team reviews video and access events together, an investigation becomes much more practical. Instead of searching through hours of footage, a security or IT team can start with a credential event and examine the associated video.

6. Intercoms and communication tools

An intercom or video intercom can give staff a way to communicate with someone before releasing a door. This is especially useful for after-hours entry, delivery doors, remote sites, or locations without a full-time receptionist.

Communication should not become a substitute for verification. A person who sounds convincing on an intercom is still an unverified person. The best process combines communication with scheduled visits, host confirmation, credentialing, or a defined escalation path.

7. Door monitoring and exception alerts

Access control should report more than successful entries. Forced-open doors, doors held open too long, repeated denied attempts, offline devices, and access outside an approved schedule may all deserve attention.

The system should not create so many alerts that staff ignore them. Define which events require immediate response, which staff can review later, and who receives each notification. A small number of meaningful alerts is more useful than a flood of noise.

How should visitor access work in a commercial lobby?

Visitor access should begin before the person reaches the lobby whenever possible. The host or employee should submit the visit, the visitor should receive clear arrival instructions, reception should be able to confirm the appointment, and the visitor should receive limited access that expires when the visit ends.

A practical visitor workflow looks like this:

Before arrival

The employee schedules the visit with the visitor’s name, company, expected arrival time, host, destination, and any escort requirement. If the visit involves a sensitive area, the host identifies that restriction in advance.

For recurring contractors, do not let familiarity replace control. Their access may be recurring, but it should still have a defined purpose, location, and expiration date.

At arrival

The visitor checks in at the designated point. Reception or the visitor-management system confirms the visit, captures the required information, and notifies the host. If the employee did not schedule the visit, the visitor waits while the organization confirms who they are and why they are there.

This is where the system should make the right behavior easy. If reception has to search multiple spreadsheets, call several people, and manually create a badge, shortcuts become more likely.

During the visit

Visitors should wear a badge that makes their status visible without exposing unnecessary personal information. They should remain in approved areas, and staff should escort them when policy or risk requires it.

The goal is not to make visitors feel unwelcome. It is to make the boundaries understandable. A visitor who knows where they may go is easier to manage than a visitor who receives vague instructions and must follow signs through the building.

At departure

The visitor checks out, returns the badge if applicable, and loses access at the end of the appointment or at a defined expiration time. The system should record the departure or flag an open visit for follow-up.

Organizations frequently miss that last step. An organization may have a strong check-in process and still lack a reliable understanding of who remains in the building. Check-out is part of access control, not administrative cleanup.

How does cloud-managed access control help IT directors?

Cloud-managed access control gives IT directors a central place to manage users, doors, schedules, events, and permissions across locations. It can reduce the need to visit each building for routine changes and provide visibility when an employee, contractor, or visitor needs access adjusted quickly.

For an organization with one building, the benefit may be easier administration. For an organization with multiple sites, the difference is larger. A centrally managed system can apply consistent policies, standardize access groups, review activity, and support new locations without creating a separate security island at every site.

Cloud management does not mean organizations should expose every control directly to the public internet. The underlying system still needs strong identity management, secure communications, appropriate permissions, device maintenance, and a clear plan for network outages. NIST’s security controls emphasize both physical access restrictions and the need to manage access authorization over time.

The network design also matters. A security system should not require unnecessary open ports or firewall holes simply to make remote administration convenient. IT directors should ask how the platform communicates, what outbound connections it needs, how the platform protects administrative access, and how the security integrator will coordinate with the organization’s network team.

The best solution is the one that gives the IT team useful visibility without adding an unmanageable technology stack. One system, consistent rules, and a partner who can support the deployment are often more valuable than a collection of impressive features that operate separately.

visitor check in

What role does video surveillance play in lobby security?

Video surveillance helps deter misconduct, verify identity, investigate incidents, and provide context around access events. It should support the access-control process rather than operate as a separate camera project.

In a lobby, the most important video questions are practical:

Can the camera produce a usable face image at the entry point?

Can staff see the person approaching before the system releases the door?

Can the organization determine whether a visitor entered alone or followed someone through?

Can the video show where a person went after entering?

Can authorized staff review video remotely when an incident occurs?

Video retention should reflect the organization’s risk, legal requirements, investigation needs, and available storage. More footage is not automatically better. If nobody can find the relevant event, the organization has stored data without gaining much operational value.

Privacy also belongs in the design conversation. Limit access to video, define retention practices, protect administrative accounts, and make sure signage and policies fit the organization’s obligations. Security should protect people without creating casual access to sensitive recordings.

How can a lobby be secure without making it inconvenient?

A lobby can be secure without being frustrating when the organization designs the process around predictable movement. Employees should be able to enter quickly with reliable credentials. Expected visitors should not have to repeat information from registration. Reception should have enough information to make decisions without calling five departments.

Convenience comes from preparation, not from removing controls.

Mobile credentials, pre-registration, automatic host notifications, temporary badges, scheduled access, and clear signage can reduce friction while still creating meaningful boundaries. The system should also have a plan for the exceptions that cause the most pressure: a forgotten badge, a delivery at the wrong door, an employee who needs after-hours access, a visitor who arrives early, or a system that temporarily loses connectivity.

Test those situations. A system that works only when everyone follows the normal process is not finished.

What should IT directors ask before upgrading lobby security?

Before selecting hardware or replacing a lobby system, ask questions that expose the operating model:

Which doors are public, employee-only, emergency-only, or restricted?

What should happen when an unscheduled visitor arrives?

How does the organization issue, change, and remove employee credentials?

Who approves contractor and vendor access?

How long should visitor credentials remain valid?

Can the system support multiple locations from one administrative view?

Can the system connect access events to relevant video?

What happens during a network or power interruption?

Which alerts require immediate action?

Who owns the system after installation?

Does the design require unnecessary inbound firewall access or exposed ports?

What will the process look like for a new location, a new employee, or a changed floor plan?

These questions force the project beyond a product comparison. Two systems may both offer card readers and mobile credentials, but they may differ significantly in administration, support, reporting, integration, and long-term cost.

What are the most common commercial lobby-security mistakes?

Protecting the front door but not the next door

An exterior reader does little if visitors can move freely from the lobby to employee areas. Review the entire path, not just the entrance.

Treating cameras as proof of security

A camera records what happened. It does not decide whom the organization authorizes to enter. Video is strongest when it works with access control and clear procedures.

Giving permanent access for temporary needs

Temporary work should receive temporary access. Expiration dates, schedules, and regular reviews prevent old permissions from becoming invisible risk.

Leaving HR and IT changes disconnected from access control

When an employee leaves or changes roles, access should change promptly. Manual hand-offs create delays and uncertainty. Define who triggers the change and how the organization verifies it.

Using different rules at every location

Local differences may be necessary, but every site should not invent its own access groups, naming conventions, or visitor process. Standardize the common pieces and document the exceptions.

Designing around equipment instead of behavior

The right reader cannot fix a process that nobody understands. Walk through the lobby at opening, closing, lunch, shift change, delivery time, and after hours. Watch what people actually do.

Ignoring the support relationship

Commercial security does not end when installers mount the equipment. Firmware, credentials, camera views, door hardware, user permissions, and operating procedures all need ongoing attention. Choose a partner who will stay involved after installation.

How should you plan a commercial lobby-security project?

Begin with a site assessment, not a shopping list. Document the entrances, interior doors, reception position, elevators, stairs, public areas, sensitive areas, visitor flow, delivery routes, employee schedules, and after-hours conditions.

Then define the decisions the system must make. Who may enter? At what time? Through which door? With what credential? Who approves exceptions? What event creates an alert? Who receives it? What happens next?

From there, create a standard design that the organization can repeat at additional locations. Use consistent access groups, door names, user roles, alert priorities, and reporting practices. Where a site requires something different, document why.

The technology should serve that design. A qualified security partner can help coordinate access control, video, intercoms, door hardware, networking requirements, visitor workflows, and service responsibilities so the IT director does not have to manage disconnected vendors.

Commission the system in stages. Test every reader, door contact, request-to-exit device, camera view, intercom, alert, credential type, schedule, and emergency procedure. Test denied access as carefully as successful access. Then train the people who will use the system every day.

Finally, set a review schedule. A lobby changes when the company moves teams, adds contractors, changes reception coverage, opens another location, or remodels the floor. The access-control design should change with it.

How should an IT director measure whether lobby security is working?

Measure the process, not just the equipment. A lobby-security review should show whether the team removes credentials on time, whether temporary visitors are expiring as intended, whether doors are generating repeated forced-open events, and whether staff can retrieve the right video and access record when something happens.

Useful measures include the number of active credentials by site, credentials with no recent owner review, overdue visitor check-outs, repeated denied-access events, door-held-open alarms, unresolved device outages, and how long it takes to disable access after an employee departure. These are not performance numbers for the sake of creating a dashboard. They point to places where the process is drifting.

Run a short access review at regular intervals. Pick a sample of employees, contractors, and visitors. Confirm that their permissions match their current role, location, and schedule. Walk the visitor path and ask a receptionist to demonstrate an expected visit, an unexpected arrival, and a lost badge. If the person responsible for the lobby cannot complete those tasks without a workaround, the system needs attention.

The review should also include the relationship with the security provider. Does the provider answer service requests clearly? Does the provider fix recurring issues at the source? Does the partner understand the organization’s standard design, or does the provider treat every change as a new project? A scalable system is valuable only when the operating support around it can scale too.

The 2027 standard for a secure commercial lobby

The standard has moved beyond “install a card reader at the front door.” A secure commercial lobby should establish identity, control movement, record access, support investigation, and remain manageable as the organization grows.

For a busy IT director, that means the system should be simple to administer, scalable across locations, and secure by design. It should not depend on a receptionist remembering every employee, a paper log nobody reviews, or a camera archive nobody can search. It should give the organization a consistent way to handle normal arrivals and unusual situations.

The strongest lobby-security programs also recognize that experience matters. Employees need a system that works. Visitors need a process that is clear. Reception teams need tools that help them make decisions. Security teams need usable records. IT needs visibility without unnecessary complexity. Leadership needs confidence that the system will still make sense six months from now.

That is what good commercial security delivers: controlled access that feels straightforward to the people who should use it, and meaningful barriers for the people who are not.

FAQ: Commercial Lobby Security

What is the most important security measure for a commercial lobby?

The most important measure is a controlled access process that verifies people before they move beyond the public lobby. In most commercial buildings, that means electronic access control at the appropriate doors, a defined visitor-management process, and a clear way to connect access events with video. A single lock or camera cannot replace a complete entry process.

How does access control secure a commercial lobby?

Access control secures a commercial lobby by deciding who can enter, which doors they can use, and when they can use them. Employees receive credentials according to their roles and schedules, while visitors and contractors receive limited, temporary access when appropriate. The system records successful entries, denied attempts, door alarms, and other events so the organization can respond and investigate.

Should commercial lobbies use visitor-management software?

Most commercial lobbies benefit from electronic visitor management, especially when they receive regular visitors, contractors, vendors, or guests across multiple locations. A visitor-management system can support pre-registration, host notification, temporary badges, access expiration, check-in, and check-out. It also creates a more usable record than a paper sign-in sheet.

How do you secure a lobby without making it unwelcoming?

Secure the lobby by making the normal visitor process clear and efficient rather than removing security controls. Pre-register expected visitors, provide simple arrival instructions, notify hosts automatically, issue temporary credentials when appropriate, and use clear signage. Employees should receive reliable credentials that allow quick entry, while visitors should understand where they may go and who is responsible for them.

What cameras does commercial lobby security need?

Commercial lobby security typically needs cameras covering the approach to the entrance, the person’s face at the entry point, the reception area, the interior security boundary, and important movement paths such as elevators or restricted corridors. Camera placement should prioritize usable identification and context, not simply the number of cameras installed. Video is most valuable when staff can review it alongside access-control events.

Is cloud-managed access control secure for a commercial building?

Cloud-managed access control can be secure when it uses strong administrative authentication, controlled permissions, secure communications, maintained devices, and a documented plan for outages. IT directors should also ask whether the system requires unnecessary inbound firewall access or exposed network ports. Cloud management should simplify administration and provide centralized visibility without weakening the organization’s network-security practices.

How should businesses handle former employees’ access?

Businesses should disable a former employee’s credentials as part of the offboarding process, not days later during a periodic review. The organization should clearly assign HR, IT, and security responsibilities, and the organization should verify that it has removed or changed physical credentials, mobile credentials, PINs, visitor permissions, and remote administrative access. Role changes should trigger an access review as well.

What should a commercial lobby-security assessment include?

A commercial lobby-security assessment should review exterior entrances, reception, interior doors, elevators, stairwells, visitor flow, delivery routes, employee access, after-hours conditions, cameras, intercoms, door hardware, alarms, network requirements, and operating procedures. It should also examine how the organization issues and removes credentials, how the organization approves and checks out visitors, and how the system will scale to additional locations.

How often should organizations review commercial lobby access permissions?

Organizations should review access permissions whenever an employee leaves, changes roles, or no longer needs a location, and organizations should also conduct scheduled reviews at regular intervals. The review should look for inactive credentials, temporary access that failed to expire, permissions outside a person’s role, repeated denied events, and doors or devices that are frequently offline. The schedule should match the organization’s risk and operating complexity.

visitor check in

If you’re ready to experience The Alen Advantage yourself, send us a message.

antimicrobial-door-handle-vs-traditional-door-handle

Bacteria Doesn’t Stand a Chance Against Antimicrobial Door Hardware

The Challenge:  More than ever before employers, employees and customers are thinking about their health and wellbeing in the workplace and will expect the highest standards of health and cleanliness in their business environments.


The Solution:  Use the best innovative technologies, such as our antimicrobial door and security hardware that fights bacteria 24/7 to make your work environment safe and secure.
You already know Alen for security and fire alarm solutions, among other core services, but did you know we also have expertise in Health-Based Safety and Security solutions? We are committed to helping companies feel safe and healthy, especially now with everyone being more health conscious, and more focused on cleaner offices.

Antimicrobial Door and Security Hardware has a unique Ionic Silver (AG+) coating with a formulation that inhibits bacteria and mold on doorknobs and other high-touch surfaces. This hardware solution is well-equipped for a wide variety of industries such as healthcare, government, retail, education, corporate and foodservice. Our antimicrobial hardware is available in many different styles, functions and finishes to suit any workplace environment.


The Result:  An environment that feels safe, healthy and adaptable to the ever-changing world so your employees and businesses can continue to thrive.

Frequently Asked Questions

What is antimicrobial door hardware?

Antimicrobial door hardware features a specialized coating designed to inhibit bacteria and mold on frequently touched surfaces such as doorknobs and door handles.

How does antimicrobial door hardware work?

The hardware uses an Ionic Silver (AG+) coating formulated to provide continuous protection against bacteria and mold on the treated surface.

Why is antimicrobial hardware useful in the workplace?

Door handles and other security hardware are touched frequently throughout the day. Antimicrobial hardware adds another layer of health-focused protection to help businesses maintain cleaner workplace environments.

What industries can use antimicrobial door hardware?

This hardware is suitable for many environments, including healthcare facilities, government buildings, retailers, schools, corporate offices, and food-service businesses.

Is antimicrobial door hardware available in different designs?

Yes. Antimicrobial hardware is available in different styles, functions, and finishes, allowing businesses to choose options that fit their security needs and workplace appearance.

avigilon-security-camera-in-corner-of-room

IP Video Surveillance System Helps Secure a Local NJ Food Bank

The Challenge:  Local Food Bank Offices and Warehouse Robbed Twice


The Solution: IP Video Surveillance System to protect both inside and out
Believe it or not, an important community benefactor, which has been helping its New Jersey community and surrounding areas for over 30 years with emergency food assistance, had been robbed several times. Each time the culprits gained entrance in different ways. Once it was through a bathroom wall, another time was through the basement, knowing there was no video surveillance system. While there, these thugs helped themselves to the contents of the safe and even food supplies for those in need. That’s when the the organization called on Alen Security. They tasked us with a way to catch these criminals in the act or deter them in the first place.

After a careful review of their facility and consultation and tour with their Managing Director, we devised a Security plan to secure their new facility. It was decided that they would maintain their current Security Alarm System and add an IP Video Surveillance System to complement that alarm system.

The IP Video Surveillance System included two 5MP Bullet cameras with IR to view the Front Entrances and Street. We also deployed 3MP Bullet cameras to patrol the Driveway, Side Warehouse Door, Rear Parking Lots and Loading Dock. Meanwhile, Alen Security installed 2MP Dome Cameras inside to protect the General Offices, Warehouse, Storage, Thrift Store, Food Distribution and Basement. The cameras would run to a 24 port; 9TB Video Appliance to record all of the activity. The new IP Video Surveillance System offers live viewing and playback with a feature-rich; user-friendly video management software application. Alen Security also installed a fiber network to keep the video off of their local network.

Remote access was also provided for viewing of the new cameras on their phones and tablets away from the office.


The Result: A happy customer with a way to deter any new break-ins and identify anyone foolish enough to attempt another robbery. 

Frequently Asked Questions

Why did the food bank need an IP video surveillance system?

The food bank’s offices and warehouse had been robbed multiple times through different entry points. A surveillance system was needed to deter future break-ins and help identify anyone attempting another robbery.

Did the food bank replace its existing security alarm?

No. The organization kept its existing security alarm system and added IP video surveillance to provide visual monitoring and recorded evidence alongside the alarm protection.

What areas of the food bank were covered by cameras?

Exterior cameras monitored the entrances, street, driveway, warehouse door, parking areas, and loading dock. Interior cameras covered the offices, warehouse, storage areas, thrift store, food-distribution area, and basement.

Could the food bank view its cameras remotely?

Yes. Authorized users could remotely view the cameras from their phones and tablets while away from the facility.

How was the surveillance footage recorded and managed?

The cameras connected to a 24-port, 9TB video appliance that recorded activity and supported live viewing and playback through video-management software. A separate fiber network kept the video traffic off the food bank’s local network.

thermal-camera-systems

Thermal Camera Systems

The Challenge:  People are concerned about inadvertently contracting COVID-19 as we all head back to work.

Here are a few important facts we know about the virus:

  • Elevated body temperature is an indicator of this and other illnesses
  • COVID-19 does have a lifespan on a variety of different surfaces
  • Hand and surface contact can be a means of transmission from person to person

As we all plan to return to work, we are helping many employers prepare their office environments to ensure their employees will feel safe and protected from inadvertently contracting coronavirus. Like the Food Distribution Company in Hamilton who wanted to put a process in place to perform a temperature check on incoming drivers. We recommended, and they installed, one of our Thermal Camera Systems to their continued satisfaction.

Using Thermal Camera Systems is just one component of our comprehensive approach to keeping your employees safe. Thermal Camera Systems give you instant confirmation if an employee or visitor has an elevated temperature before they enter the workplace. Our “contactless” thermal cameras process a body temperature scan for pass/fail with audible alert sounds in less than 3 seconds, and within an accuracy of +/- .9 degrees Fahrenheit.

The system also offers subscription-based remote management software to allow for email and text alerts. The technology is configurable to deny entry to any employee with an elevated temperature status, and can also be configured to allow/deny entry. Since this procedure of temperature checks will be new to most companies, HR professionals will need to put certain guidelines and policies in place. To assist them with the process, we have an HR Consultant available for guidance on policy and implementation procedures.

Features of our Thermal Camera Systems:

  • Tablet style display
  • Reads and displays temperature instantly with confirmation of pass/fail
  • Configurable temperature thresholds
  • Accurate within +/- .9 degrees
  • Optional face mask check
  • Commercial grade hardware
  • Ability to integrate with controlled access

The Result: Our Thermal Camera Systems are just one of the innovative health-based safety systems that help to comfort your employees and keep illness out of the office.

Frequently Asked Questions

What does a thermal camera system check?

The system performs a contactless body-temperature scan and provides a pass-or-fail result, helping employers identify employees or visitors with an elevated temperature before they enter the workplace.

How quickly does the thermal camera provide a result?

The thermal camera completes its scan in less than three seconds and can provide an audible alert when it detects an elevated temperature.

How accurate is the thermal camera system?

According to the article, the system measures body temperature within plus or minus 0.9 degrees Fahrenheit.

Can a thermal camera integrate with an access control system?

Yes. The technology can be configured to allow or deny entry based on the temperature result and can integrate with controlled-access systems.

Can employers receive remote alerts from the system?

Yes. Subscription-based remote-management software can send email and text alerts. The system also offers configurable temperature thresholds and an optional face-mask check.

 

contactless-access-control-from-phone

Wave Hello to “Contactless” Door Technology

The Challenge:  As companies transition back to the in-office environment, employees and customers should feel safe, healthy, and protected.


The Solution:  Alen Security’s Health-Based Safety & Security solutions offer best-in-class innovative technologies for the new, “clean” office, including “contactless” automatic door openers that can be activated with just a wave of the hand or arm.

When employees do return to work, their first stop will be the front door to the office. A new contactless door system will help to reassure them that they are about to enter a clean, safe and secure environment. The technology also works well for restrooms and certain doors that must be kept closed for compliance with the fire code.

Alen Security’s contactless doors are very easy to use with motion-activated microwave sensors that use the wave of a hand, phone-based Bluetooth technology® or with the option of integrating into a card access system. There is no need to ever touch a doorknob or keypad again.

Our electromechanical automatic door openers are relatively quick to install, so we can get you up and running within a short timeframe. We will then follow up with annual visits for recommended calibration and maintenance.

An investment in health-based safety and security is truly an investment in your employees, your customers and the peace of mind it provides. We can work together to ensure they feel confident entering the businesses they love without having to worry.


The Result:  An environment that feels safe, healthy and adaptable to the ever-changing world so your employees and business can continue to thrive.

Frequently Asked Questions

How does a contactless automatic door opener work?

The door opener can use a motion-activated microwave sensor that responds to the wave of a hand or arm, allowing someone to open the door without touching a handle or keypad.

What other methods can activate a contactless door?

In addition to wave sensors, the system can use phone-based Bluetooth technology or integrate with an existing card access system.

Where can contactless door technology be installed?

Contactless systems can be used at office entrances, restrooms, and certain doors that must remain closed to comply with fire-code requirements.

How long does it take to install an automatic door opener?

The article explains that electromechanical automatic door openers are relatively quick to install, allowing businesses to begin using them within a short timeframe.

Do contactless door openers require maintenance?

Yes. Annual visits are recommended to calibrate the equipment and perform maintenance so the automatic door system continues operating properly.

long-haul-trucks-parked

Security Case Study: Access Control for Vehicle Dealership with Corporate, Sales, Service and Retail Departments

The Challenge: A local vehicle dealership and supply company needed access control to secure their brand-new multi-department facility.


The Solution: Access Card Readers with Multi-Level Access Control protocols and a Video Intercom System.

A large vehicle dealership and supply company wanted to secure their multi-department facility. The need was to restrict the flow of traffic throughout their building.

Their building housed their corporate offices as well as sales, service and some retail space.  With all of this traffic and activity they needed to control “who went where”. This was a key to restricting the flow of traffic throughout their facility. Our solution was a Physical Access Control System.

We used a multi-pronged Access Control approach including access card readers, keypads, electric locks and a video intercom system. First, they needed to solve for the fact that they receive parts deliveries in the middle of the night. This necessitated a system to avoid having to staff 24/7.  To accomplish this, we installed access card readers with keypads and issued them codes. We further integrated their Access Control System with their security system to allow for after-hours deliveries.

Thirdly, we secured their inventory of trucks with electric gates and a video intercom, access cards and a keypad.

Finally, they did not want their retail clients walking into their corporate offices upstairs. So, we installed access card readers to prevent walk-in customers from gaining access to their corporate offices.


The Result: Consequently, they have a more secure facility with access to specific areas restricted to authorized personnel.

Frequently Asked Questions

Why did the vehicle dealership need an access control system?

The dealership’s new facility contained corporate offices, sales, service, and retail departments. Access control was needed to manage traffic and prevent people from entering areas where they were not authorized.

What access control equipment was installed?

The facility received a combination of access card readers, keypads, electric locks, electric gates, and a video intercom system.

How could the dealership accept deliveries after business hours?

Delivery personnel received access credentials and keypad codes. Integrating the access control and security systems allowed approved overnight deliveries without requiring the dealership to remain staffed around the clock.

How was the dealership’s truck inventory protected?

Electric gates, access cards, a keypad, and a video intercom were used to restrict access to the area containing the truck inventory.

How were customers prevented from entering the corporate offices?

Access card readers were installed between the public retail space and the upstairs corporate offices. Only authorized personnel could enter the restricted office area.