Access Control Systems
Technology and operations decisions where district leadership, IT, and stakeholders must align.
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles, timelines, budget cycles, and what ‘secure enough’ looks like for the board, superintendent, facilities, and safety teams.
Alignment Questions
A Quick Snapshot: Your Daily Reality
- Walk me through a typical morning at your busiest school — what security tasks land on your desk before the first bell?
- How often in the past 12 months has a security incident (unauthorized entry, propped door, lost credential, alarm failure) required an urgent operational response?
- Who on your team is primarily responsible for day-to-day lock and credential issues?
- Which of these best describes your current entry controls across district buildings?
- Describe one recent moment where a door or credential problem created real stress or visible concern at your district.
If a Single Breach Could Define Your Career — What Would That Look Like?
- Imagine an incident that becomes a district-defining headline — what sequence of access failures would have to occur for that to happen?
- Who would the board, superintendent, and community expect to answer for that incident?
- When the board asks whether the district is 'secure enough,' what concrete evidence have they asked for in the past?
- How would you describe the emotional weight of being the point person for building security—what keeps you awake at night?
- If the district had to show 'secure enough' to an external auditor tomorrow, what single fix would you prioritize?
Where the Doors, Wiring, and Processes Actually Break
- Which types of door hardware are most common across your buildings (select all that apply)?
- How would you rate the state of building wiring and conduit for access control and cameras?
- How do you currently handle credential lifecycle (issuance, transfer, revocation) for staff, students, and visitors?
- Where do you see doors most often compromised (e.g., propped during events, wiring failures, badge sharing)? List locations and typical causes.
- What failure modes have you observed in emergencies (lockdown signal delay, badge readers offline, video not recording)? Please give specific examples and frequency.
- Do any buildings currently support remote lockdown from a single console or mobile command? If yes, which ones?
Why Pilots Typically Stall — Let’s Call Out the Real Reasons
- When you’ve run a security pilot before, what unexpected issue most often stopped it from scaling?
- Which of these has derailed pilots in your experience (select all that applied)?
- Who in your organization typically objects to piloting new access technology, and what are they afraid of?
- What pilot length has proven most revealing and feasible for your staff: a single month, quarter, or longer? Why?
- How do you measure pilot success today (e.g., lockdown time, credential churn, integration uptime)? List exact metrics you’ve used or would trust.
What a Truly Secure Day Would Feel Like
- If you could press a button and guarantee one outcome for every building, what would it be — and why does that outcome matter emotionally and operationally?
- How fast must a lockdown command complete (in seconds) for you to feel confident in an emergency?
- What acceptable credential turnover process would make parents and staff feel secure while still being practical for administrators?
- Picture after-hours community events — what visitor workflow would prevent propped doors while keeping the public experience welcoming?
- Which measurable signals would tell you a new solution is working (choose up to three)?
Budget Calendars, Procurement Realities, and Political Timelines
- When does your district finalize capital/technology budgets each year?
- Which funding sources could support an access control rollout (select all that apply)?
- What procurement path do you prefer for hardware and services (e.g., RFP, piggyback contract, sole-source, cooperative purchasing)?
- Have you aligned a procurement timeline to the next board meeting or budget vote? If yes, when is the decision window?
- What political sensitivities (e.g., parent groups, unions, board factions) must we navigate together to get approval?
Who Needs to Be on the Bus — And Who Might Slam the Door
- Which stakeholders must explicitly sign off for a pilot to proceed?
- Who in your organization is likely to champion a pilot and actively defend it to others?
- Which stakeholder’s concerns, if unanswered, would most likely derail the project?
- How do individual stakeholder priorities differ — what does each group value most (e.g., legal liability reduction, cost control, ease of use, integration)?
- What internal communications or demos have convinced skeptical stakeholders in the past?
What Would Make a Pilot an Unquestionable Win?
- If the pilot could only prove one thing to get district-wide approval, what should that single proof point be?
- Which buildings would you put in scope for a pilot to be both representative and achievable?
- What acceptance tests must pass before you’d sign off on a pilot (select all that apply)?
- Who will own day-to-day pilot operations and who will be the escalation contact for failures?
- What timeline feels realistic for site survey → install → validation in a pilot building?
Operational Realities: Maintaining Security After the Install
- Who will be responsible for ongoing maintenance and warranty interactions after deployment?
- How do you currently handle urgent hardware failures after hours (weekends/nights)?
- What Mean Time To Repair (MTTR) would you expect for critical failures to feel acceptable?
- Which training formats work best for your staff to adopt new access workflows (select all that apply)?
- What ongoing reporting or dashboard views would reassure leadership that systems are healthy?
Escalation, Warranty, and Risk — Who Owns What?
- If an integrated lockdown fails during an emergency, what escalation path do you expect to follow?
- What warranty expectations do you have for hardware and installation labor?
- Which risk-sharing arrangements would make procurement easier for your board (select all that apply)?
- Describe one past vendor relationship that felt proactive and trustworthy — what behaviors stood out?
- What documentation or proof (certificates, test runs, references) will make legal and procurement comfortable signing?
Deciding to Move Forward: Small Steps, Clear Signals
- Given everything we’ve discussed, what would an acceptable first milestone look like to you?
- How soon could you realistically begin a pilot once terms are agreed?
- What information would you need from us to confidently present this to the board?
- What would make you hesitate to sign a pilot agreement today?
- On a scale from 1–10, how confident do you feel about moving forward with a pilot after this conversation? Please explain the number you chose.
Final Notes — What We Promise to Deliver Together
- What single guarantee or commitment from a vendor would most reduce your personal risk in recommending this project?
- What would you like us to prepare and share in the next 72 hours to keep momentum (select up to three)?
- Who should be copied on next steps and scheduling for an on-site survey?
- Is there anything we haven’t asked that would be critical for us to know before designing a pilot for your district?
-
Current State Mapping
Document existing locks, wiring, credential practices, propped doors, and failure modes that drive risk exposure.
Current State
Setting the Scene: Which Sites Are We Mapping?
- Which buildings or campus areas should we include in this current-state mapping?
- Give a short summary of the three security concerns you notice most often across the selected sites.
- When was the last formal security audit, door inventory, or incident review completed at these sites?
- Who on your team will be our primary operational contact(s) for mapping (name and role)?
- Do you have digital site plans, door lists, or wiring diagrams we can reference?
If a Stranger Walked In Right Now — Where Would They Get In?
- How confident are you that exterior doors are consistently secured during arrival and dismissal?
- Which doors are most frequently found propped open or otherwise bypassed?
- Why are those doors typically propped (pick all that apply and then describe specifics)?
- Tell us about a recent time someone bypassed secured entry—what happened, who noticed, and what changed afterward?
- On a scale from 1–5 how urgent is fixing uncontrolled entry for your district right now?
Under the Hood: Power, Wiring and What Could Fail
- If wiring or a power issue prevented remote lockdown during an incident, how likely would that be to occur at any site?
- What describes your door controller and wiring situation most accurately?
- Which doors have local power backup or UPS on controller circuits today?
- Have you experienced recent failures tied to wiring (e.g., doors stuck unlocked, intermittent readers, controllers offline)? Describe the last occurrence.
- Are there known areas where running new wiring would be especially difficult or costly?
- Do you have preferred contractors, in-house electricians, or restrictions on who can perform wiring work?
Keys, Credentials and Who Actually Opens Doors
- How true is this statement: “We know exactly who has keys or credentials to every building”?
- Which credential types are currently in use across the district?
- Describe your issuance and deprovisioning workflow for staff, substitutes, and contractors. How long does it typically take to revoke access?
- Approximately how many active credential holders exist district-wide and per building (best estimate)?
- How often do you discover lost, shared, or duplicated credentials, and what usually triggers discovery?
- What are your visitor and vendor access workflows today (temporary badges, sign-in, escorts)?
Failure Modes That Keep You Up at Night
- Imagine a worst-case failure during school hours—what single access-control failure would be most consequential for your district?
- Which of these failure types have you experienced in the last 24 months?
- When failures occur, how quickly are they typically detected and who is notified?
- What is your current escalation path and repair SLA for critical door failures?
- Tell us about any false lockdowns or false unlocks—what caused them and what was the impact?
Day-to-Day: How Security Fits Into Your Routine
- Who currently owns daily access control operations (e.g., badge provisioning, door troubleshooting, visitor check-in)?
- How do staffing cycles (semester changes, substitute teachers, seasonal vendors) affect your access management workload?
- What tools do you use today to manage credentials and door state (spreadsheets, access control software, SIS integration, none)?
- How do after-hours community activities (sports, events) change how doors are used and monitored?
- What training or communications have you given staff and parents about access control expectations and why those rules exist?
What Small Changes Would Reduce Your Risk Tomorrow?
- If you could change just one operational habit that would meaningfully reduce uncontrolled entry, what would it be?
- Which of these near-term fixes would you prioritize for a pilot project?
- What measurable signal would convince you a pilot succeeded (e.g., lockdown speed, reduction in propped doors, credential revocation time)?
- What constraints—budget cycles, union rules, procurement timelines, or IT policies—must we design around for any immediate changes?
- Realistically, who needs to sign off to allow a pilot at one building, and what is the shortest timeline to get that approval?
-
-
Outcome Discovery
Define target security outcomes, pilot success criteria (lockdown speed, credential turnover, integration), and measurable signals of success.
Discovery Questions
Starting Point: What's Top of Mind Right Now?
- What's the single most important security outcome you want us to help you achieve this year?
- What recent event, audit finding, or mandate sparked attention on this project?
- Who typically initiates and champions security projects in your district (pick all that apply)?
- How would you describe staff and leadership sentiment toward changing door access from mechanical to electronic?
- Tell a short story — in a sentence or two — that best captures why this outcome matters to you (what keeps you up at night)?
If a Door Could Talk, What Would It Say?
- What’s the one thing about your current access control the district would be embarrassed to admit in a public forum?
- Which exterior or high-risk doors are habitually propped open today (select all that apply)?
- How often are master keys or mechanical keys issued, duplicated, or unaccounted for?
- When a door is propped or a lock fails, who currently gets notified and how long until someone responds?
- Describe a recent near-miss or security-related incident tied to access control and what followed.
When Seconds Matter, What Does Success Look Like?
- If an active threat alarm sounded right now, how confident are you that you could lock down the required doors within a minute?
- What target average lockdown time would you set for pilot buildings?
- Which doors or zones must lock automatically with zero human steps during a lockdown (select all that apply)?
- What maximum failure rate (doors not locking as expected) would you accept during drills or an event?
- If an electronic lock fails during an emergency, what fail-safe behavior or fallback is acceptable (e.g., local manual override, backup power, physical lockdown procedures)?
Who Needs to Say 'Yes' — and What Would They Require?
- If the superintendent asked you right now, 'Is our district secure?' — what answer would you dread giving?
- Which stakeholders must approve scope, budget, and timelines (select all that apply)?
- For each stakeholder above, what single piece of evidence or metric would win their support (briefly list by stakeholder)?
- Which procurement or budget cycle constraints shape decision timing for this project?
- How do parents and the broader community currently express their security expectations (channels and intensity)?
Pilots That Prove Value — What’s Non‑Negotiable?
- If a pilot had to be judged a clear success or failure in three metrics, which three would you choose?
- Of those three, which single metric is the non-negotiable 'show me' measure?
- What pilot scale and duration would feel convincing to your leadership (buildings × weeks)?
- Which operational scenarios must be exercised during the pilot (select all that apply)?
- What level of training and behavior change do you expect staff to demonstrate by pilot completion (describe acceptance criteria)?
Signals We Can Measure — Pick Your North Star
- Which single KPI would you show the board at the 90‑day review to prove the pilot worked?
- What are your current baseline values (or best estimates) for the KPIs you just identified?
- Which systems will be the source of truth for these metrics (select all that will feed dashboards/reports)?
- What reporting cadence and format will convince decision-makers (dashboard, executive summary, drill logs)?
- Who in your organization will own ongoing measurement and be responsible for sign‑off on pilot success?
Hidden Constraints That Break Good Plans
- What single technical or organizational constraint in your buildings could silently derail a pilot if left unaddressed?
- Which of these technical realities apply at the proposed pilot site(s)?
- Do you have an existing credential or directory system we must integrate with (select all that apply)?
- Are there union, school-hour, or vendor access rules that will limit when or how we can install or run drills?
- What are your expectations for warranty/SLA and ongoing maintenance responsibilities after pilot completion?
Next Step: Pilot Scope, Commitments & Quick Wins
- If we agreed to start a pilot this quarter, what must be written down and guaranteed before work begins?
- Which acceptance tests must pass before you approve expansion beyond the pilot (select all that apply)?
- Who will be the on-site project owner (role) and who will be the executive sponsor (role)?
- Please provide the preferred pilot start window and any immovable blackout dates we must avoid.
- How will this pilot be funded or procured (select the likely path)?
- Imagine success six months after pilot completion — what does that look and feel like for staff, students, and the board?
-
Solution Experience
Run outcome-driven scenarios (lockdown, after-hours community use, visitor workflows) using the district’s actual sites and constraints to validate fit.
Experience Meetings
- Experience Prep & Current State Confirmation
- On‑Site Scenario Run: Lockdown (Outcome Validation)
- On‑Site Scenario Run: After‑Hours Community Use & Visitor Workflows
- Failure Mode & Integration Stress Test (IT, Wiring, Video, Credentials)
- Validation & Go/No‑Go Decision Review
- IT to provide network diagram and commit to timeline for any firewall/VLAN changes required.
- Agree any immediate fixes to re‑test or items that require scope changes.
- Collect and timestamp logs, video, and manual notes from each lockdown run for the validation report.
- Vendor to adjust configuration or equipment for any high‑priority failure identified and schedule a short re‑test if feasible.
- Facilities to mark physical issues (broken strikes, propped doors) and assign remediation owners.
- IT to flag any network changes required to meet failover requirements discovered during tests.
- Recap Objectives & Success Signals for Community/Visitor Scenarios
- Validate that visitor and community workflows meet success metrics (throughput, temporary credential reliability, staff effort).
- Identify policy or configuration changes required to reduce operational friction.
- Confirm that emergency transitions from community events to lockdown are safe and meet timing targets.
- Document required visitor management rules, credential lifetimes, and front desk procedures.
- Create a training checklist and estimated staff time for event days based on observed throughput.
- Flag any hardware (readers, gates) or process gaps that prevented meeting target throughput for remediation in pilot scope.
- Integration Objectives & Acceptance Criteria
- Confirm all critical integrations function within the district's constraints or identify required IT changes.
- Surface wiring or hardware limitations that would block meeting acceptance criteria and quantify remediation effort.
- Validate that event logging and video correlation provide the investigation signals the district requires.
- Introductions & Objectives
- Vendor to produce an integration remediation plan with estimated labor, parts, and timeline for any failures discovered.
- Facilities to verify wiring punchlist and schedule corrective work for any identified door wiring issues.
- Agree a log/video export package to be included in the pilot acceptance deliverables.
- Review One‑Sentence Artifacts
- Reach a documented go/no‑go decision with explicit rationale tied to the consequence and measured outcomes.
- If go: finalize pilot scope, acceptance tests, timeline, and owners to hand off to Solution Scope and Deployment stages.
- If no‑go: agree targeted remediation work and a revalidation plan with dates and success gates.
- Produce and share the Scenario Validation Report (measurements, video, logs, gaps, and remediation estimates).
- Finalize pilot scope document and acceptance criteria and obtain district signoff or identify remaining preconditions.
- Schedule Pre‑Deployment Readiness and Deployment Enablement meetings and assign task owners.
- If remediation required, create a timeline with owners to address high‑priority items before pilot start.
- Capture a clear one‑sentence current state agreed by district stakeholders.
- Document the explicit consequence that makes the outcome urgent and quantify where possible.
- Agree a concise future state statement and success metrics for each scenario.
- Confirm all logistics, pre‑work deliverables, and participants for on‑site scenario runs.
- District to provide latest floorplans, door lists, wiring maps, and credential roster for pilot buildings.
- Vendor to prepare scenario scripts, measurement templates, and required demo equipment list.
- Schedule on‑site windows and confirm point people for facilities, safety, and IT.
- Define safety protocols and communication plan for simulated lockdowns and community events.
- Recap Current State, Consequence, Future State & Metrics
- Measure and document lockdown time versus success criteria and baseline.
- Identify and record failure modes that prevent achieving the future state.
- Obtain customer validation at checkpoints that the observed behavior ties directly to their stated consequence.
- Community Event Ingress/Egress Simulation
- Credential Import & Turnover Test
- One‑Sentence Current State
- Evidence Package Presentation
- Baseline Measurement (Current Process)
- Gap Analysis & Mitigation Plan
- Explicit Consequence Statement
- Network & Wiring Failure Simulations
- Visitor Check‑In & Temporary Credential Issuance
- Configured Solution Run — Normal Path
- Emergency Egress & Lockdown Overlap Test
- Decision Framework & Pilot Scope Proposal
- One‑Sentence Future State / Success Definition
- Failure Mode Tests
- Video Integration & Event Correlation
- Observer Validation Checkpoints
- Scenario Scope & Success Metrics
- Operational Friction Review
- Cyber & IT Constraints Review
-
Solution Scope
Define buildings in-scope, hardware & integration modules, pilot boundaries, responsibilities, and acceptance tests.
Scope Configuration
- Install electrified classroom lockdown locksets
- Install electrified exterior door locksets and strikes
- Install and wire access control panels and network
- Install and program card/fob readers at doors
- Bulk-provision staff and student credentials
- Integrate access events with video surveillance
- Install door position and REX sensors
- Install wireless lockdown buttons and command stations
- Install visitor-management kiosk and access integration
- Replace mechanical cylinders with electronic cylinders
- Install UPS backup for controllers and locks
- Commission and functionally test installed systems
- Train front office and facilities staff
- Configure scheduled after-hours and community access
- Quarterly preventive maintenance and firmware updates
Scope Questions
Install electrified classroom lockdown locksets
- How many classroom doors do you want electrified for lockdown initially (pilot)?
- Are classroom doors primarily wood, metal, hollow metal with vision panels, or mixed?
- Do any classroom doors require delayed egress or ADA-compliant egress hardware?
- Is there existing electrification or power at classroom doors (low-voltage or door power), or will new wiring be required?
- Are there union, code, or district-specific installation constraints we should know (installation hours, vendor restrictions, bonded contractors)?
Install electrified exterior door locksets and strikes
- Which exterior entry types are in scope for electrification (main entries, side exits, staff entrances, gym/community access)?
- How many exterior doors are in-scope for the pilot/phase?
- Do exterior doors currently have magnetic locks, mechanical strikes, or mechanical deadbolts?
- Are there weather, vandalism, or high-traffic concerns that influence hardware selection (e.g., tamper-proof strikes, stainless finishes)?
- Will exterior doors require additional features such as weather sealing, card-in/card-out, or integration with vestibule interlocks?
Install and wire access control panels and network
- Do you prefer centralized controllers (panel rooms) or distributed controllers at each building/closet?
- Are network closets and low-voltage pathways available at the proposed controller locations?
- Will access control panels be connected to the district network (PoE/managed switches) or on a segregated network/VLAN?
- How many controller locations and total door endpoints do you estimate for the pilot scope?
- Are there specific IT constraints or approval processes we should account for (firewall rules, port openings, maintenance windows)?
Install and program card/fob readers at doors
- Which reader form factors are required or preferred (mullion, keypad, touchless mobile, QR/visitor)?
- How many doors will require multi-factor or keypad access versus card-only?
- Do you need readers to support mobile credentials (smartphone) in the pilot?
- Will readers require vandal shields, weatherproofing, or elevated IK ratings for exterior placement?
- Is there an existing badge technology (Wiegand, OSDP, proprietary) we must support or migrate from?
Bulk-provision staff and student credentials
- Approximately how many staff and student credentials need bulk-provisioning for the pilot?
- Where are credential records currently stored (SIS, HR system, spreadsheet, none)?
- Do you require staged credential lifecycles (temporary badges, term-based expiration, visitor passes)?
- Are there privacy or district policies for credentialing (photo ID, PII restrictions) we must follow?
- Do you want the vendor to perform the bulk provisioning or provide tools/training for district IT to run imports?
Integrate access events with video surveillance
- Which VMS/NVR platforms are in use (vendor names) and versions?
- Do you need real-time event-triggered camera pop-up on access events (e.g., unlock, forced entry)?
- How many cameras will be integrated per door or per building in the pilot?
- Are camera streams on the same network/VLAN as access controllers or segregated?
- Do you require forensic linking (one-click playback from event) or only event logs exported to VMS?
Install door position and REX sensors
- Which doors need door position (magnetic) sensors versus only REX (request-to-exit) detection?
- Are there special door types (double doors, overhead doors, sliding doors) that require specific sensor types?
- Do you need alarms for propped doors or automated notifications when doors remain open?
- Is hardwired sensor wiring available to each door, or would wireless sensors be preferred?
- How should door-open or forced-entry events be routed (email, SMS, paging, VMS integration)?
Install wireless lockdown buttons and command stations
- Do you want portable wireless panic buttons, wall-mounted command stations, or both?
- How many button locations or staff kits are needed for the pilot?
- Should wireless buttons trigger full building lockdown, selected zone lockdown, or staged responses?
- Are wireless signals required to work offline (locally) if network is down, or is cloud/central control acceptable?
- Do you require training and drills for staff to validate button workflows during pilot?
Install visitor-management kiosk and access integration
- Do you want a self-service kiosk, staffed check-in, or both for visitor management?
- Should visitor badges be printed with access levels and expiry that integrate with access control?
- Which visitor workflows are required (pre-registration, watchlist screening, badge printing, escort assignment)?
- Do you need integration with background-check or volunteer databases as part of check-in?
- Where will kiosks be mounted/powered (front office desk, wall-mounted, mobile cart)?
Replace mechanical cylinders with electronic cylinders
- How many mechanical cylinders are targeted for replacement in the pilot?
- Are cylinders keyed to a master key system that will be retired, or do you plan to coexist with mechanical systems?
- Do you require retrofit-friendly electronic cylinders that avoid door trim changes, or full lockset replacement?
- Are there high-security areas that require audit trails and per-event logs from cylinders?
- Do you need cylinders to support emergency egress (fail-safe vs. fail-secure) per door/function?
Install UPS backup for controllers and locks
- Do you require UPS backup at every controller and critical door, or only at central controller locations?
- What target runtime do you need for battery backup during outages (e.g., 1 hour, 4 hours, 24 hours)?
- Do existing electrical rooms have capacity and space for UPS units, or will electrical upgrades be required?
- Should UPS systems provide graceful shutdown/alerts to IT and facilities teams during extended outages?
- Are there generator hookups or campus-level resiliency features we should coordinate with?
Commission and functionally test installed systems
- Which acceptance criteria are highest priority for commissioning (lockdown timing, credential provisioning, video integration, alarm response)?
- Do you require third-party or district-supplied testers to be present during commissioning?
- Should commissioning include simulated emergency drills (timed lockdowns, power failure scenarios)?
- What documentation and sign-off artifacts do you require (test logs, punch list, as-built drawings)?
- Do you have a formal acceptance sign-off process and who are the authorized signatories (title/role)?
-
Mutual Commit
Agree commercial terms, pilot objectives, warranty and maintenance responsibilities, and escalation paths for failures.
Agreement Modules
- Statement of Work (SOW)
- Master Services Agreement (MSA)
- Commercial Terms & Purchase Order
- Pilot Agreement & Acceptance Criteria
- Warranty & Maintenance Agreement
- Service Level Agreement (SLA)
- Roles, Responsibilities & RACI
- Escalation & Incident Response Plan
- Integration & Data Sharing Addendum
- Data Processing & Privacy Addendum (DPA)
- Change Order / Scope Modification Process
- Insurance, Indemnity & Liability Schedule
- Installation & Site Acceptance Test (SAT) Checklist
- Training & Knowledge Transfer Plan
- Renewal, Support & Licensing Options
- Termination & Exit Plan
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm wiring assessments, IT integrations, credential imports, site access windows, and roles for the pilot and phased rollout.
Readiness Questions
A Quick Snapshot — Who Are You in This Story?
- Which role are you representing in this conversation?
- How many school buildings and approximate total student population are we talking about?
- What triggered you to explore access control now?
- How urgent does the district consider this initiative?
- Who else will need to be part of decisions and why? (names/roles helpful)
Are You Quietly Accepting Risk — Or Ready to Fix It?
- If a single unlocked or propped exterior door led to a critical incident tomorrow, would your current systems let you contain it?
- How often do exterior doors get propped or forced open across your sites?
- Which failure modes have actually occurred in the last 24 months (pick all that apply)?
- When those failures happen, how does it feel for you and your team?
- How long have these security gaps been tolerated without a systemic fix?
- Tell us about one specific incident that made you realize current controls aren't enough.
Who Really Holds the Keys — And Who Isn’t Even Tracked?
- Are mechanical keys, electronic badges, and mobile credentials inventoried and controlled district-wide?
- What credential types are currently in use across sites?
- How are credentials issued and retired today (process and timelines)?
- How often do you perform credential audits or reconciliation?
- Who tends to resist tighter credential controls and why (staff groups, unions, community)?
- Give one concrete example of credential misuse or uncontrolled access you've discovered.
Does Your Wiring & IT Meet You Halfway — Or Will It Slow You Down?
- What if your building wiring or network can't support the access solution you need — have you validated that risk?
- Describe the typical age and condition of the electrical/network infrastructure in your buildings.
- Which door wiring types do you have (select all that apply)?
- Which systems must integrate with access control for your district to consider it successful?
- Have you experienced integration failures before (describe what went wrong)?
- Who owns on-prem IT vs vendor responsibilities for networks and controllers?
When Seconds Matter — What Will Prove Success?
- If you could measure one single thing to prove the solution works in an emergency, what would it be?
- Which pilot success criteria would convince your board to fund wider rollout?
- What target lockdown timing would you consider acceptable for the pilot (ex: all exterior doors locked within)?
- How will you measure day-to-day operational success (adoption of credentials, reduction in propped doors, staff satisfaction)?
- Who must sign off at pilot completion to expand the program (roles or committees)?
What Could Go Wrong — And Who Fixes It?
- If the access control system failed during a lockdown, do you have an on-the-ground recovery plan that will work in minutes?
- Which single points of failure worry you most (select up to three)?
- Who would be on-call to respond to an access control failure during school hours and after hours?
- Describe the escalation path you currently use for security system outages.
- What warranty and maintenance expectations would make you comfortable (response times, parts, software updates)?
- What percentage of the initial project budget are you willing to reserve for ongoing maintenance and lifecycle replacement?
Small Wins That Build Momentum — Where Should We Start?
- What small, visible improvement would reassure parents and the board within 90 days?
- Which sites make the most sense for a pilot (pick top 2)?
- What site access windows exist for installing hardware with minimal disruption (summer, weekends, early release)?
- Which staff groups should be trained first as part of the pilot?
- What training format works best for your teams?
- How do you expect to fund a pilot or initial phase?
- If the pilot succeeds, what timeline would feel reasonable to begin district expansion?
-
Deployment Enablement
Schedule and execute the pilot and phased installs with task owners, sequencing, training, and escalation plans.
-
Validation Checklist
Verify acceptance criteria (lockdown timing, credential provisioning, video integration), document results, and sign off before district expansion.
Validation Questions
Quick Intro: Who’s in the Room?
- Which role will be the primary point of contact for this access-control initiative?
- Who else needs to be at the table for decisions (names & roles)?
- What is your target decision timeline for a pilot and for district expansion?
- Which budget source will likely pay for the pilot and subsequent phases?
- Has the district completed any security assessments or audits in the past 12–24 months? If yes, please summarize findings or upload a reference.
- What outcome from this discovery conversation would make you feel this time was well spent?
Are We Comfortable With “Secure Enough”?
- When someone in your district says a building is 'secure enough', what specific risks are you choosing to tolerate?
- Which of these issues do you currently see as most urgent?
- How often are exterior doors found propped during school hours or events?
- Who in the district typically makes the call to lock down a building in an emergency, and how confident are you in that workflow?
- When you imagine the board, parents, and staff looking at your security plan, what would they say is missing?
- On a scale from 1–10, how much anxiety does the current state of building security create for you personally?
Walk the Buildings With Me: Where Are the Weak Spots?
- If an intruder tested every entry point, which specific doors or areas do you think they'd get through first?
- Describe the most common failure modes you’ve seen (e.g., wiring shorts, door hardware mismatch, reader power loss).
- Which buildings have aging wiring or electrical issues that could block a straight install?
- What credentialing practices are in use today (select all that apply)?
- How do you currently manage credential turnover for students, staff, and contractors?
- Where do you feel your video surveillance and access control are least integrated (systems or workflows)?
Moments That Broke Trust: Incidents & Near-Misses
- Tell me about a specific security incident or near-miss that changed how you think about school safety.
- When that incident happened, which systems or human steps failed first?
- What were the short- and long-term consequences of that event (public outcry, board action, disciplinary, policy changes)?
- How did parents, boards, or local officials respond—did they demand immediate fixes, or did the district opt for incremental changes?
- Since that event, what has changed operationally or procedurally—what stuck and what didn’t?
- How would a repeat of that incident affect your career or the district’s reputation?
What Would Change Everything? Your Target Outcomes
- If you could eliminate one outcome-related fear tomorrow (e.g., unauthorized entry during class), which would it be and why?
- Which measurable outcomes would most convince you a pilot succeeded?
- What target lockdown timing would you consider acceptable for full sign-off (provide number in seconds)?
- How much disruption to daily routines (student arrival, teachers entering classrooms) is acceptable during and after deployment?
- Beyond technical metrics, what stakeholder signals would indicate success (parent confidence, staff trust, board vote)?
- If the pilot delivers outcomes you like, how quickly would you want to scale across the district?
What’s Really Stopping Progress? Hidden Barriers
- What’s the single most common reason previous security projects stalled or failed in your district?
- How does your procurement process constrain the speed or flexibility of pilot procurement?
- What IT or networking constraints should we anticipate (VLANs, firewall rules, credential directory sync, guest Wi‑Fi policies)?
- How do staff and teachers typically react to changes in access procedures—what worries them most?
- Which internal approvals are likely to be hardest to get, and who are the decision blockers?
- If funding is phased, what minimum deliverable must a pilot show to unlock the next tranche of budget?
Pilot Rules of Engagement: How Will We Know It Worked?
- What single failure during a pilot would cause you to stop the project and not expand?
- Which acceptance criteria must be demonstrated before district expansion (select all that apply)?
- Who must sign technical acceptance and who must sign the executive go/no‑go? (name & role)
- How will we measure acceptance—automated logs, timed drills, staff surveys, or external audit?
- What are realistic dates for pilot start, acceptance test, and sign-off given your calendar?
- After pilot sign-off, what maintenance and warranty expectations should be documented (response SLA, spare parts, training refresh)?
-
-
Success
Review achieved outcomes, capture lessons, and keep a shared channel for ongoing issues and enhancement requests.
Success Reviews
- Outcomes Review & Formal Acceptance
- Lessons Learned & Continuous Improvement Workshop
- Operational Handover & Support Pathways
- Enhancement Requests & Roadmap Planning
- Quarterly Success Review (Recurring Governance Cadence)
Issues & Enhancements
- Publish the prioritized enhancement backlog and draft roadmap to the shared channel and project repository.
- Publish a Lessons Learned report in the shared project repository with RCA artifacts attached.
- Create prioritized improvement tickets (internal and district) and assign owners with target due dates.
- Update installation and IT integration playbooks to include fixes from the workshop.
- Handover Checklist Review
- Transfer operational ownership with clear support SLAs and escalation paths.
- Ensure district teams have access to monitoring, documentation, and training resources.
- Establish a persistent shared channel and governance for day-to-day issues and enhancements.
- Deliver an Operational Handover packet (accounts, manuals, spare-parts list, warranty certificates) to district ops.
- Integrate system alerts into the district's NOC or chosen monitoring channel and verify alert routing.
- Create and populate the shared communications channel and set initial moderation/response roles.
- Enhancement Intake Recap
- Produce a prioritized enhancement backlog tied directly to measurable district outcomes and budget windows.
- Agree on a roadmap timeline and owners for top-priority enhancements.
- Establish governance and cadence for ongoing enhancement reviews via the shared channel.
- Introductions & Objective
- Open formal change-request tickets for top 3 enhancements and assign technical owners.
- Schedule the next roadmap review aligned with the district's upcoming budget planning session.
- Metrics Dashboard Review
- Keep performance transparent and address trending issues before they escalate.
- Maintain a steady cadence of governance to support phased district expansion.
- Ensure continuous improvement items progress and owners remain accountable.
- Update the KPI dashboard with latest data and distribute to governance stakeholders.
- Close or escalate outstanding action items from prior meetings with updated ETA.
- Confirm next quarterly review date and adjust attendee list as needed.
- Confirm whether pilot met agreed acceptance criteria and obtain formal customer sign-off or a documented remediation plan.
- Ensure all measured outcomes are backed by evidence and customers validate results.
- Define clear next steps and owners for either expansion or corrective work.
- Produce and circulate final Acceptance Report with evidence attachments and customer sign-off block.
- If gaps exist, create a prioritized remediation punch list with owners, target dates, and verification tests.
- Schedule follow-up acceptance verification meeting (date/time) to confirm remediation closure.
- Workshop Context & Rules
- Document a clear set of lessons learned with evidence and root causes for major failures.
- Create a prioritized improvement backlog with owners and deadlines.
- Agree process changes and training actions required before wider rollout.
- Review Acceptance Criteria
- Support & Escalation Workflow
- What Worked Well
- Incident & Change Log Review
- Impact vs Effort Mapping
- Monitoring, Alerts & Maintenance Plan
- Adoption & Training Metrics
- Measured Outcomes & Evidence
- What Didn't Work / Incidents
- Align Requests to Outcomes & Budgets
- Root Cause Analysis
- Credential Lifecycle & Admin Processes
- Roadmap Draft & Timelines
- Maintenance & Warranty Items
- Gap Assessment & Risk Impact
- Proposed Process & Technical Improvements
- Expansion Opportunities & Risks
- Training Recap & Documentation Access
- Customer Validation & Sign-off
- Governance & Review Cadence
- Prioritization & Owner Assignment
- Next Steps & Expansion Recommendation
- Action Review & Next Steps
- Shared Channel Setup & Governance