For a system integrator engaged in access control system design, this is a familiar starting point. The quantity is clear, and the customer may already be expecting a price.
“We need access control for 25 doors. Please send your quotation.”
But what do we actually know about those doors?
We know how many there are. We may know very little about the people using them, the areas they protect, or the practical challenges of installing and managing the system.
From my installation experience in ICT and ELV solutions, those details are often where the real scope of access control system design becomes clear.
What happens at each door?
Imagine an enquiry covering an office building and a separate store within the same compound.
The main entrance handles staff arriving in the morning. Internal doors separate departments. A server room needs access restricted to authorized personnel. Visitors arrive at reception, while deliveries may use another entrance.
Every opening contributes one door to the total. Each serves a different purpose.
Before selecting equipment, ask who needs access, at what times, and under whose authority. Establish which doors form the perimeter and which control movement inside the premises.
A door name on a floor plan helps identify a location. Understanding what happens there helps define the requirement.
Can the proposed access control system design be installed practically?
An existing building deserves particular attention.
Cable routes that look simple on a drawing may pass through occupied offices, finished ceilings, or areas where work is only permitted outside business hours.
At this stage, the integrator should understand the door construction, existing locking arrangement, available power, and access to the network.
A suitable wireless handle may reduce cabling work at some doors. It still needs assessment for physical compatibility, communication coverage, and ongoing battery maintenance.
For a separate building, distance is only one consideration. Available connectivity, power, and the required management model also influence the approach.
Finding these conditions during the survey gives everyone a better chance to agree the scope before installation begins.
How will visitors get in?
Staff access and visitor arrival are different workflows.
An employee may already have an assigned credential. A visitor needs to contact someone, explain their purpose, and receive permission to enter.
Who answers that call? What happens when reception is unattended? Does the visitor entrance lead directly into a restricted area?
These questions help establish whether door entry belongs in the proposal and how it should support the customer’s routine.
Otherwise, the building may have controlled staff access while visitor admission still depends on someone walking over to open the door.
What does the customer need to know after an event?
An access record can show that a credential was used. The customer may also want visual context when reviewing an incident.
Ask what the security team expects to investigate and how they expect to retrieve the information.
Do they need a straightforward record of access activity? Do they want to review associated video? Is there an existing surveillance system that must be considered?
Clarifying the expected outcome helps determine the platform and integration scope before either becomes an assumption in the quotation.
Who takes ownership after handover?
This question deserves a place in the first discussion.
Who adds a new employee? When is a lost credential removed? Who changes permissions when someone moves departments? Who handles an access request outside working hours?
The answer may be reception, HR, facilities, security, or an administrator responsible for several sites.
That person needs suitable permissions, training, and a management workflow they can use confidently. Where remote administration is required, include it in the original design and software selection.
A successful handover should demonstrate these everyday tasks alongside the operation of the doors.
What might change next?
Ask whether the customer expects to add another floor, building, or branch.
The intention is to understand likely growth and record the assumptions behind today’s proposal.
A planned extension may influence the system architecture now. An uncertain future requirement may simply need a clearly explained expansion path.
Either way, the customer should understand what the proposed system is intended to accommodate.
Where the Paxton range fits in Access Control System Design
Paxton offers several approaches for different access-control scenarios:
| Requirement to explore | Relevant Paxton approach |
|---|---|
| Centrally managed, networked access control | Net2 |
| Suitable doors where reducing cabling is valuable | PaxLock wireless access-controlled handles |
| Phone-based access control without an on-site data network | Solo, with its required power and internet connectivity |
| Recognizing and admitting visitors | Entry |
| Access control and video management within one platform | Paxton10 |
These are starting points for selection. They are not a suggestion to put every system into one project.
Net2 and Paxton10 are different platform choices. Compatible PaxLock and Entry products can support either, while Solo uses a different architecture.
The site survey and operating requirements should determine the appropriate combination.
Give Your Access Control System Design a Clear Foundation
Before preparing the bill of materials, create a door schedule that records:
- Door location, purpose, and permitted users.
- Required access hours and visitor arrangements.
- Door construction, locking requirements, and installation constraints.
- Available power, cabling, and connectivity.
- Event reporting, video, and administration requirements.
- Anticipated expansion and any assumptions still awaiting confirmation.
This makes the proposal easier to explain. It also helps the customer understand why two doors in the same building may need different treatment.
At CST, our role is to support integrators through that pre-sales discussion and help translate the requirement into an appropriate Paxton solution.
The door count remains useful. It becomes much more useful once we understand how the building actually works.
When an access-control enquiry reaches you, what do you ask before you start selecting hardware?
Share your floor plan or door schedule with CST.
About CST Pulse
CST Pulse is the technology insight platform of Core Solutions & Technologies, covering practical ICT and ELV topics for system integrators and technology partners across Middle East & Africa.
Bring your next project to the table.
Talk to CST about this technology or application.