Access Control Systems
Technology and operations decisions where district leadership, IT, and stakeholders must align.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome Discovery
Align on safety objectives, current access controls, stakeholders, constraints, and measurable success signals.
Discovery Questions
Starting Together: a quick snapshot of your situation
- Tell me briefly which buildings and door types you expect to include in this project
- When did the need for improved electronic access most recently become urgent for your district
- Who on your team will own day-to-day decisions for this initiative
- Describe the timeline you are targeting for a pilot and for district expansion
- Estimate the ballpark budget or funding window available for the pilot phase
Where a single failure would be most damaging
- If one unsecured door or a failed lockdown happened tomorrow, which outcome would be most career or district-defining for you
- Which specific sites or door groups keep you up at night and why
- Describe recent incidents or near-misses involving propped doors, lost keys, or credential confusion
- When those incidents happen, who notices first and what immediate steps are taken
- Name the single site-level risk that would make you stop the project immediately if unresolved
How daily routines must continue without friction
- Challenge: Which current access pain are you tolerating because fixing it feels like it will slow daily routines too much
- Tell me how students, staff, and visitors currently enter during peak arrival and dismissal windows
- On a typical school day, estimate how many credentials need to be issued, revoked, or reissued each month
- Describe any routines that cannot be slowed, for example teacher classroom turnover or lunch period flows
- If a new credential process added 30 seconds to a teacher's daily entry, what would that mean for operations and staff buy-in
Lockdown and emergency response — what success looks like
- Challenge: If your lockdown system does not activate in under a set time, what consequence would force an immediate change of plan
- Which party should be authorized to initiate building lockdowns in an emergency
- Describe how lockdown signals must interact with your existing PA, bell, and video systems
- Estimate an acceptable maximum time from lockdown command to doors secured at a typical campus
- Which measurable outcome from a pilot would convince you to expand (choose up to two)
Wiring, integrations, and data readiness — practical gates we must clear
- Challenge: If campus wiring or power cannot support the new readers, would you pause the project or fund upgrades immediately
- Which back-office systems must integrate with access control for you to consider the solution viable
- Who owns API or integration decisions and credentials in your district
- Describe the current state of door wiring and power at the sites you want to pilot, including known damages or missing runs
- If a required integration needs custom work, how quickly can your team or vendor authorize and fund that development
- Which data sources for credentialing are clean and accessible today (student/staff lists, HR records, contractor rosters)
Who needs to sign off and who will run this every day
- Challenge: If the board, union, or parent group objects to the rollout approach, what outcome would cause you to halt the project
- Which stakeholders must approve the pilot and final rollout
- Who will handle credential issuance and day-to-day administration after rollout
- Describe training capacity available for staff who will manage credentials and visitors
- How many full time equivalent staff can you assign to support a pilot and the first 90 days of rollout
Competitive landscape and the alternatives you are weighing
- Challenge: If your incumbent vendor could match pilot results at the same cost, what would make you still choose a new partner
- Which solution options are you actively evaluating today
- Describe any internal proposals to solve access without an outside vendor
- What would have to be true about your current approach for you to decide to keep it instead of moving forward
- Who on your team is advocating to solve this internally and why
Pilot success criteria, decisive checkpoints, and next steps
- Challenge: If the pilot demonstrates the agreed metrics, what single decision would allow you to sign and schedule rollout that same week
- Which pilot metrics will be make-or-break for you (select up to three)
- List the acceptance tests you want run at each pilot site before you call it validated
- Assuming the pilot needs one remediation cycle, how long from pilot end to a go/no-go decision will your team take
- Which conditions would immediately kill the deal for you
- Finally, who should be in the room for a pilot review to make the go/no-go call
-
Solution Experience
Translate district objectives into a shared view of how electronic access, credential workflows, and lockdown integration will operate in real school scenarios.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost to your team
- You confirm the documented current state and the concrete cost in risk, staff time, and community exposure.
- Deliver a scenario-specific pilot design that maps per-door hardware, credential types, lockdown triggers, and integration endpoints for the agreed pilot sites.
- Translate objectives into school scenarios
- You validate that the demonstrated credential and lockdown workflows map to your stated school scenarios and remove the key operational gaps.
- Provide an integration dependency checklist template (video endpoints, wiring condition checklist, network requirements) to support site readiness assessment.
- Walk through the credential lifecycle in your scenarios
- Identify pilot site access windows and named site owners for installation and testing.
- You agree on pilot acceptance criteria and the evidence needed to decide on district rollout.
- Confirm pilot acceptance criteria including target lockdown timing, credential issuance SLA, and acceptance test window.
- Prove the lockdown and integration sequence
- Confirm constraints and acceptance criteria
- Validate the shown workflows
- Solution Experience Session
- Solution Experience Deck
- Solution Brief — Access & Lockdown Experience
- meeting
- slides
- document
-
Solution Scope
Define per-site hardware, software modules, integration points, responsibilities, pilot scope, timelines, and acceptance criteria.
Scope Configuration
- Install Exterior Door Card Readers
- Install Electronic Classroom Door Locks
- Deploy Pilot Building Access Control Installation
- Provision and Onboard Staff and Student Credentials
- Deploy Mobile Credentialing and Issuance
- Integrate Access Control with Video Surveillance
- Integrate Access Control with Visitor Management
- Install Centralized Lockdown Controller and Alarms
- Replace Mechanical Master Key Systems
- Upgrade Door Low-Voltage Wiring and Power
- Install Battery Backup for Critical Locks
- Provide Ongoing Maintenance and Remote Monitoring
- Train Staff on Credential Use and Lockdown Procedures
Scope Questions
Install Exterior Door Card Readers
- Which campus buildings and specific exterior door IDs should be included in the exterior reader scope?
- How many exterior door openings require electrified readers (count by building)?
- Do you require readers that support legacy prox badges, new key fobs, and mobile credentials simultaneously at the same door?
- Identify any exterior doors that must remain fail-safe versus fail-secure during a power loss and provide door IDs.
- Are there exterior doors currently propped open or fitted with classroom security devices that will need sensor or forced-entry monitoring tied to readers?
Install Electronic Classroom Door Locks
- Which classrooms and door IDs are candidates for electronic classroom locks (breakdown by building and grade level)?
- How do classroom doors currently latch and what type of door hardware is installed (for example surface-mounted closer with latch, mortise lock, or classroom function lever)?
- Do you require a teacher-controlled interior push-button or classroom-side override and, if so, which rooms must keep teacher override enabled?
- Specify any special lockdown behaviors required for specific classrooms such as delayed egress, immediate manual lock, or a timed auto-lock on bell schedule.
- Are there educational or ADA accessibility constraints (for example assisted-living classroom access, accessible egress routes) that affect electronic lock selection?
Deploy Pilot Building Access Control Installation
- Which building(s) do you propose for the pilot and why (include student population, number of exterior and classroom doors, and typical after-hours use)?
- How many total doors and which door IDs should the pilot include (exterior, classroom, staff-only)?
- What is the target timeframe to complete pilot installation and initial testing (start and finish in weeks)?
- Which measurable acceptance criteria will validate successful pilot performance for lockdown timing, credential issuance, and system integrations (for example lockdown <= 7 seconds, credential issuance within 24 hours, 95% event log parity with video)?
- Who on your staff will be the pilot owner and primary contact for daily test results and sign-off (name, role, and contact method)?
Provision and Onboard Staff and Student Credentials
- How many active staff badges and student badges must be provisioned in the initial rollout and in each subsequent semester?
- Which student information system (SIS) or roster feed will you sync for automated credential creation and what field will be used as the unique ID (for example student ID number)?
- Will credentials require photo ID capture at issuance kiosks, and if so where will kiosks be located by building?
- Who is responsible for revoking lost or stolen credentials and what maximum window do you require for an issued revocation to take effect across the system?
- For student badge lifecycle, which expiration policy should apply (for example semester, school year, or manual deactivation)?
Deploy Mobile Credentialing and Issuance
- Which mobile platforms must be supported for mobile credentials by your staff and families (choose all that apply)?
- Do you require mobile credential issuance via self-service (user requests) or centralized issuance by district IT/administration?
- Are mobile devices subject to Mobile Device Management (MDM) policies or restrictions that will affect credential provisioning?
- Specify offline access needs for mobile credentials when a door controller loses network connectivity (for example allow cached access for X hours).
- Which authentication factor do you want for mobile credentials at doors (for example phone-only Bluetooth tap, phone + PIN, or proximity emulation)?
Integrate Access Control with Video Surveillance
- Which video management system (VMS) integration endpoints are available at each pilot site (for example RTSP, event metadata API, alarm input)?
- List the cameras by door ID that must be linked to access events for review and forensic retrieval.
- Do you require automatic video clip capture on forced-entry or lockdown events and what clip length is acceptable for each event (in seconds)?
- How long must linked video be retained for access-related events to meet district policy or local regulations?
- Which time synchronization method will be used to align access logs and camera timestamps (for example NTP server or district time service)?
Integrate Access Control with Visitor Management
- Which visitor management workflow do you use today for sign-in and badge printing (for example kiosk check-in, front office staff, or pre-registration)?
- Do you require the access control system to issue temporary visitor credentials that expire automatically and which door IDs should accept those visitor credentials?
- Which visitor data fields must be passed from the visitor system to access control for audit (for example visitor name, host staff ID, reason, and photo)?
- Are there background check or badge-clearing rules that should block issuance of a visitor credential automatically?
- Who will operate visitor badge printers and what locations will house those printers by building?
Install Centralized Lockdown Controller and Alarms
- Which physical location will host the centralized lockdown controller and alarm interface (for example main communications room by building and rack elevation)?
- How should the lockdown controller communicate lockdown state to door controllers and to the public address or alarm system (for example relay contact, IP API call, or hardwired alarm input)?
- Which ancillary systems must be notified during a lockdown event (for example PA system, fire alarm panel, video system, or site alarm monitoring)?
- How will you verify that lockdown timing and alarm integration meet district policy in live tests (for example measured lock actuation <= X seconds and verified alarm notifications to the monitoring center)?
- Do you require separate lockdown zones per building or a district-wide master lockdown command?
Replace Mechanical Master Key Systems
- How many mechanical master key systems or master key groups currently exist and where are their keyed areas (list by building and area)?
- Do you prefer cylinder replacement, full core rekey, or master-keyed electrified cylinders for transition away from mechanical master keys?
- Which high-security areas should retain restricted mechanical keying during rollout versus immediate conversion to credential-only access?
- What is your desired cutover plan for mechanical-to-electronic transition (for example phased by building, weekend bulk cutover, or classroom-by-classroom)?
- Who will manage legacy mechanical key custody and disposal after conversion and where will documentation of new key control policies be stored?
Upgrade Door Low-Voltage Wiring and Power
- Which buildings have verified low-voltage wiring for door devices and which require wiring upgrades (list by building and closet ID)?
- Estimate the average cable run length from the nearest low-voltage closet to door controllers and indicate any runs exceeding 150 feet that may need repeaters or new conduits.
- Do door locations have Power over Ethernet (PoE) available at the reader or will dedicated low-voltage power be required?
- Are there any known asbestos, hazardous materials, or permitting constraints that could delay wiring work at specific sites?
- Will you provide single-line electrical diagrams (SLD single-line diagram) and network closet rack elevations for each affected building prior to installation?
Install Battery Backup for Critical Locks
- Which locks are considered critical and require battery backup (list door IDs and reason for critical designation)?
- What minimum battery runtime do you require for critical locks to maintain operation during power outages (choose one)?
- Where will battery backup units be mounted and what environmental constraints (temperature, access) exist at those locations?
- Do you want remote battery health monitoring and alerts forwarded to a network operations center or district maintenance inbox?
- Who will be responsible for periodic battery replacement and how often should replacements be scheduled?
Provide Ongoing Maintenance and Remote Monitoring
- Which response time SLA do you need for on-site maintenance after a critical alarm or failure (for example next business day, 4 hours, or immediate dispatch)?
- Do you require 24x7 remote monitoring of access events and alarms with escalation to your emergency contacts?
- Specify the inventory of critical spare parts you expect to be maintained on-site or in a regional depot (for example spare readers, door controllers, power supplies).
- Which routine maintenance activities should be included in a fixed-fee contract versus billed as out-of-scope time-and-materials (for example firmware updates, badge reprints, wiring repairs)?
- Which of the following items do you expect to be explicitly out of scope for a fixed-fee installation (select all that apply)?
-
Pilot Evaluation
Execute a pilot installation against agreed acceptance criteria to validate lockdown timing, credential issuance, and system integrations before full commitment.
- decision_readiness
- success_criteria
- stakeholders
- gaps
- current_state
- desired_state
- current_state
- desired_state
- success_criteria
- decision_readiness
- gaps
- stakeholders
- stakeholders
- decision_readiness
- current_state
- success_criteria
- gaps
- desired_state
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Mutual Commit
Finalize commercial and contractual terms, schedule, district responsibilities, and sign-off criteria to move into rollout.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Purchase Order & Order Confirmation
- Support & Maintenance Agreement (SLA)
- Data Processing Addendum (DPA)
- Public Procurement & Security Rider
- Site Acceptance & Sign-Off Certificate
- Change Order Agreement
- Payment Schedule & Invoicing Agreement
-
Deployment
Operationalize rollout with readiness checks, execution, and outcome validation.
-
Pre-Deployment Readiness
Confirm site access windows, wiring condition findings, integration endpoints, named owners, and phased rollout sequencing the installation team needs.
Pre-Deployment Questions
Environment and site access
- List each site included in this rollout (site name and building code). This lets the field team map work and preload parts per location.
- For each site, will installation require after‑hours or weekend access (to avoid disruption)?
- Are there site-specific access restrictions the installers must follow (escort requirements, check‑in desk, ID/clearance rules)? If yes, briefly list the restriction per site so we can plan compliance.
Wiring condition and integration endpoints
- Have pre-survey wiring assessments (power, data, conduit) been completed for all listed sites?
- For any sites with incomplete or failed wiring checks, list the site and a short description of the issue (e.g., missing 4‑conductor, damaged conduit). This informs materials and contingency planning.
- Are integration endpoints (video VMS API availability, visitor management integration endpoints, and any access control middleware) confirmed as reachable for the integration team?
People and ownership
- Who is the district owner responsible for site access approvals and day‑of installation decisions? Provide name and role so the crew has a single approver.
- Who is the technical owner for integrations and testing (name and role)? Will they be available during pilot and the first week of each site rollout?
Timing, sequencing, and constraints
- Confirm the phased rollout order by site (site name → phase number). This establishes installation sequencing and staging.
- Are there blackout dates or recurring restrictions (testing days, assemblies, exams, seasonal closures) when installations are prohibited? If yes, indicate patterns or list dates so we avoid them in the schedule.
-
Installation & Rollout
Coordinate field crews, manage per-site installations, remediate wiring or integration issues, and track milestone completion for each phase.
-
Go-Live Validation
Per-site acceptance checklist verifying reader operation, credentialing, lockdown function, visitor workflows, and integrated video before declaring the site live.
Checklist items
- Verify each installed reader accepts and enforces configured credential types
- Validate on-site credential issuance and revocation workflows
- Confirm lockdown activation and controlled release operate to agreed timing and zones
- Test door hardware emergency egress and fail-safe/fail-secure behavior
- Verify integrated video captures and correlates with access and lockdown events
- Validate visitor management end-to-end on-site
- Perform network/power interruption and recovery test for access and video systems
- Confirm lockout/tagout (LOTO) and electrical safety documentation completed for site work
- Deliver as-built site documentation and configuration exports
- Obtain written per-site operational acceptance sign-off
-
-
Success
Review outcomes against success signals, run recurring operational check-ins, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-Live Health Check
- First Measurement Review (weeks 4-10)
- Quarterly Operational Review
- Annual Success Review
Issues & Enhancements
- Update operational runbooks and incident response steps based on lessons learned.
- Schedule field remediation visits and integration fixes with target completion dates.
- Publish an updated rollout readiness checklist tied to remediation status.
- Operational incidents and safety events
- Ensure the percent of doors meeting lockdown timing targets and reader uptime remain within thresholds recorded in Pilot Evaluation.
- Prioritize and schedule the top operational defects and enhancement requests for the next quarter.
- Confirm maintenance windows and communications to school site teams.
- Update the defect backlog with severity, owner, and scheduled remediation quarter.
- Publish the quarterly KPI dashboard to the shared operational channel.
- Notify school site contacts of upcoming maintenance windows and expected impacts.
- Yearly outcomes versus targets
- Validate whether year-to-date security incident counts and credential issuance time meet targets recorded in Pilot Evaluation.
- Confirm the operational meeting cadence and shared channel are sustaining issue resolution at acceptable timelines.
- Agree a prioritized action list for the next 12 months with owners and target dates.
- Publish the annual outcomes report with metric comparisons to Pilot Evaluation targets.
- Create a prioritized enhancement roadmap for the next 12 months with owners and tentative schedules.
- Reconfirm success criteria and owners
- Confirm the deployed components at live sites match the Solution Scope and Pilot Evaluation records.
- Identify and assign owners for all critical open issues needing remediation.
- Establish the timeline for fixes to be completed before the First Measurement meeting.
- Publish a deployment validation report listing installed hardware, observed wiring issues, and integration endpoint statuses.
- Open tickets for each critical defect with target resolution dates.
- Create a shared operational channel for ongoing issue triage and enhancement requests.
- Present outcome data
- Determine whether average lockdown response time and credential issuance turnaround time meet targets recorded in Pilot Evaluation.
- Document root causes for any gaps and assign remediation actions with dates.
- Confirm the incumbent access control has been decommissioned or formally retained read-only.
- Deliver a root-cause analysis report for each off-target metric.
- KPI trend review
- Operational cadence effectiveness
- Deployment and integration validation
- Diagnose gaps and root causes
- Enhancement and defect backlog
- Early adoption and onboarding signals
- Enhancement request review and prioritization
- Incumbent system wind-down confirmation
- Lessons learned and adjustments
- Maintenance and firmware schedule
- Critical issues triage
- Agree corrective actions and timelines
- Confirm readiness timeline for next rollout phase
- Short sync and action alignment
- Close year action list
- Immediate remediation plan