Start Here: The Story Behind Today

• What specifically prompted you to explore a new visitor management approach right now? Options: Community concern or alert, Board directive, Near-miss or incident, Routine security review, Grant or funding opportunity, Other
• Who in your district is most frustrated by the current sign-in and screening process? (select all that apply) Options: School principal, Front office staff, District safety director, IT department, Facilities/maintenance, Teachers, Board members, Parents/guardians
• How long has your building used the current visitor process (paper sign-in or existing system)? Options: Less than 6 months, 6–12 months, 1–3 years, 3–5 years, 5+ years
• Describe one recent moment or example that made you think ‘we need something better’—what happened and what was most concerning?
• What would you most like us to help you solve first? Options: Stop unauthorized entry, Faster check-in to reduce lines, Reliable emergency rosters, Contractor and volunteer vetting, SIS custody alert integration, Other
• On a scale of feelings: when you think about your lobby on a busy morning, which word fits best? Options: Calm, Tense, Overwhelmed, Reactive, Numb

If Your Lobby Could Speak, What Would It Admit?

• How confident are you that every person in the building during school hours is authorized to be there? Options: Completely confident, Mostly confident, Somewhat unsure, Not confident at all
• Which type of unverified entry keeps you up at night? Select all that apply. Options: Tailgating behind staff, Unsigned volunteers, Contractors without screening, Parents bypassing sign-in, Delivery personnel, Students with off-campus passes
• How often do you believe an unauthorized or unverified person passes through your building undetected? Options: Never (very unlikely), Rarely, Occasionally, A few times a month, Weekly or more
• When you try to answer 'who was in the building at 10:15 AM yesterday', which data sources do you rely on? (select all that apply) Options: Paper sign-in logs, Front office memory, Existing visitor software, Access control logs, Substitute/volunteer spreadsheets, No reliable source
• Tell me about a concrete situation where your current records fell short—how did that uncertainty affect decisions or feelings in the moment?
• If a district leader asked you to prove with data that your building was secure last week, what would you hand them? Options: Exported visitor logs, Paper sign-in sheets, Access control report, Nothing reliable, A verbal summary

A Day in the Life at the Front Desk

• If the front office had to process two buses, three volunteers, and a delivery in 15 minutes, what would break or get skipped?
• Walk me through your current visitor check-in step-by-step—from arrival to badge or entry—include who does what and any systems used.
• How long does a typical visitor check-in take when the office is busy? Options: Under 30 seconds, 30–60 seconds, 1–3 minutes, 3–5 minutes, Over 5 minutes
• What causes the biggest slowdowns or errors in check-in? (select all that apply) Options: Handwritten forms, Photo ID capture issues, Badge printer jams, SIS lookup delays, Insufficient staff, Network outages, Volunteer confusion
• Who currently prints badges and where are check-in points located across your campus? Options: Front desk printers, Dedicated kiosks in lobby, Portable station, No badge printing, Multiple ad hoc stations
• How often do staff intentionally bypass steps (like screening or photo capture) to keep lines moving? Options: Never, Rarely, Sometimes, Often, Always
• What emotions do front office staff express about managing visitors during peak times—stress, pride, resignation, something else?

When the Worst Happens: Drill vs Reality

• If you had to run an emergency attendance check right now, could you confidently identify everyone in the building? Options: Yes — immediately, Yes — with some effort, No — would take too long, No — not possible
• Have you run a drill that included visitor accounting? What was the single biggest gap exposed?
• Which reports or outputs would you need to produce in an emergency within 10 minutes? (select all that apply) Options: Current roster by name, Badge photos for everyone present, List of contractors/volunteers on site, SIS custody alerts linked to visitors, Door access events, Time-stamped entry/exit logs
• Have there been times when SIS custody or restriction information should have prevented access but didn’t? Tell me what happened. Options: Yes — multiple times, Once or twice, Never, Unsure
• How would parents, staff, or district leaders likely react if visitor records were incomplete during an incident?
• What tolerance does your leadership have for ‘acceptable risk’ when it comes to unknown people in your buildings? Options: Zero tolerance, Low tolerance, Moderate tolerance, High tolerance

What Would Make You Sleep Better at Night?

• What is the single change that would make you feel genuinely confident about who is in your schools?
• Which success signals matter most to you? Choose up to three. Options: Screening coverage (percent of visitors screened), Average check-in time, Roster accuracy during drills, Badge photo quality, SIS custody alert delivery, Contractor/volunteer pre-registration rate, Badge printing reliability
• For the top signal(s) you picked, what numeric target would feel acceptable (e.g., screening coverage 95%)? Be specific.
• How important are these integrations to achieving those targets? Options: SIS integration — critical, Access control — critical, Printer/printing reliability — important, Watchlist updates — critical, District dashboard/reporting — important
• Who would need to sign off on acceptance criteria for go-live (roles or names)?
• What timeline feels realistic to move from pilot approval to first-site go-live? Options: Immediate (2–4 weeks), Short (4–8 weeks), Medium (2–4 months), Long (4–6+ months), Unsure

Barriers to Change — What's Really Holding You Back?

• If you could wave a wand, why would this still not get done tomorrow?
• Which objections do you expect from stakeholders? Select all that apply. Options: Budget constraints, Staff workload and resistance, Union or labor concerns, IT/network capacity, Privacy or legal worries, SIS vendor limitations, Parent pushback, Procurement/contract complexity
• How has procurement, legal, or IT review delayed security projects before? Give a concrete example and timeline.
• What funding source would you use for this project? Options: District capital budget, One-time safety grant, ESSER or federal funds, Operating budget, No identified funding yet, Other
• Are there privacy or district policies that could limit taking photos, running watchlist checks, or sharing visitor data? Please describe.
• Which internal approvals or committees must be satisfied before a pilot can begin? Options: Superintendent, Board of Education, IT security committee, Legal counsel, Facilities director, Finance/Procurement

Ready to Move — Roles, Risks, and Next Steps

• If we agreed to a pilot today, who would be the visible champion and who is most likely to block or quietly stall it? Options: Superintendent, District safety director, School principal, Front office lead, IT director, Board member, Facilities manager, Other
• What pilot scope makes the most sense to prove value? Options: Single pilot school (your choice), Multiple schools by level (elementary/middle/high), All schools in one cluster, District-wide pilot
• Which sites should we include in readiness checks (network, printers, SIS mappings)? List site names or types.
• Which acceptance criteria would you require to call the pilot successful? (select all that apply) Options: Screening accuracy threshold met, Badge printing success rate, Roster exports validated in drill, SIS custody alerts delivered, Staff trained and confident, Emergency verification completed
• What is a realistic schedule for a 4–8 week pilot start date? Options: Start within 2 weeks, Start in 2–4 weeks, Start in 4–8 weeks, Start after approvals (timeline TBD)
• Who will own day-to-day implementation and troubleshooting at the site level? (roles/names) Options: School principal, Front office lead, District rollout coordinator, IT support, Facilities lead, Other
• What are the top three risks to a successful pilot we should proactively mitigate?

Walk Me Through Your Front Door

• How do visitors typically enter and sign in when they arrive at your school right now? Options: Paper sign‑in at front desk, Digital kiosk/self‑check, Pre‑registered online, Staff escorts only, Mixed / depends on time of day, Other
• Who usually manages the sign‑in process (role/title)? Options: Front office admin, Receptionist, School secretary, Principal / AP, Rotating staff/teachers, Vendor staff, Volunteer
• On a typical school day, approximately how many unique visitors arrive at a single building? Options: Fewer than 10, 10–25, 26–50, 51–100, More than 100
• Describe the physical layout of your lobby and where the sign‑in or screening interaction usually occurs (desk, vestibule, multiple points).
• What regular events or schedules meaningfully change how the lobby functions (drop‑off/pick‑up, volunteer shifts, evening events)?

Are We Comfortable Trusting a Handwritten Note?

• Why does your team still rely on handwritten logs in places where they do—what made that the default?
• How often do you see sign‑in entries that are incomplete, illegible, or lack ID—enough that it concerns you? Options: Daily, Weekly, Monthly, Rarely, Never
• When a paper entry looks questionable, what steps are taken to verify identity or follow up?
• How confident are staff that paper logs accurately represent who was in the building during the school day? Options: Very confident, Somewhat confident, Not confident, Unsure
• How long has the handwritten or hybrid sign‑in process been in place at your school/district? Options: Under 1 year, 1–3 years, 4–7 years, More than 7 years

Who’s Quietly Walking Through Unchecked?

• How often do staff witness tailgating—people entering right behind someone else without being screened? Options: Daily, Several times a week, Weekly, Occasionally, Never
• Which doors or entry points are most vulnerable to tailgating or unscreened entry? Options: Main office door, Side/utility doors, Gym / event entrances, Bus drop‑off area, Loading/maintenance entrance, Multiple locations
• Tell us about a tailgating incident you remember—what happened, who responded, and what the outcome was?
• What policies or physical controls exist to prevent tailgating (staff training, door alarms, vestibules), and how reliably are they used?
• If a stranger gained unscreened access, what immediate actions would staff take and who would be notified? Options: Front office attempts contact, Call admin/SRO, Lockdown procedure, Call 911, Wait and document, Other

Contractors and Volunteers: Trusted or Unknown?

• What process do you use today to bring contractors, maintenance crews, and volunteers onto campus? Options: Pre‑registration with ID upload, On‑site sign‑in only, HR / facilities schedule, Vendor badge program, No formal process, Other
• Are contractor and volunteer background checks, certificates, or qualifications centralized in one place or scattered across staff? Options: Centralized district database, Each school maintains records, Contractor provides credentials on request, No records kept
• Have you experienced safety or accountability issues involving contractors or volunteers? Please describe one specific example and its impact.
• Who is responsible for approving contractor/volunteer access, and what criteria do they use? Options: Facilities director, School admin (principal/AP), HR, Vendor manager, No single owner
• How are contractors/volunteers supervised while on campus and how is their time/location tracked? Options: Escorted by staff, Badge with limited access, Time logs only, Not tracked, Other

When an Emergency Happens, Can You Account for Everyone?

• If an emergency required a roster of every person inside the building right now, how would you produce that list? Options: Manual paper review, Classroom rosters + sign‑in sheets, Digital attendance + sign‑ins, We could not produce a reliable list, Other
• How long would it take your team to produce a reliable present‑in‑building roster during an unplanned event? Options: Under 5 minutes, 5–15 minutes, 15–30 minutes, 30–60 minutes, Longer than 60 minutes, Not possible
• Have you ever been unable to account for someone during a drill or real event? What happened and how was it resolved?
• What emergency verification tools or outputs would make you feel confident (real‑time roster, photo IDs, SIS custody flags, exportable logs)? Options: Real‑time roster, Photo badge verification, SIS custody alerts, Exportable entry/exit logs, Automated checklists, Other
• Who exactly would be responsible for using and validating those emergency rosters during a response? Options: Principal, AP / Incident Commander, Front office staff, School Resource Officer (SRO), Facilities, District safety team

What Data Are We Ignoring That Could Save Minutes—Or Lives?

• Which screening and reference data sources do you currently consult—or wish you could consult—when approving a visitor? Options: National sex offender registry, State registry, Local watchlist / custom list, SIS student/guardian records, Contractor vendor lists, Background check provider, None / unsure
• How often are those sources checked or updated in practice? Options: Real‑time/continuous, Daily, Weekly, Monthly, Ad‑hoc, Never
• Who owns watchlists, data maintenance, and decisions to add or remove names at the district level? Options: District safety director, School admin, IT/data team, Legal/compliance, No single owner
• Are there privacy, union, or legal constraints that make centralizing visitor data difficult? Please explain.
• What routine reports or dashboards do leaders currently ask for about visitors and building occupancy? Options: Daily visitor counts, Badge photo capture rates, Check‑in time averages, Custody alerts, Incident logs, None

Imagine a Morning Without Lobby Chaos

• If a new approach reduced your lobby congestion and screening gaps, what single outcome would matter most to you? Options: Faster check‑ins, Accurate rosters for emergencies, Fewer unscreened entries, Higher staff confidence, Better reporting for leadership
• Which measurable signals would prove the new process is working (pick top three)? Options: Screening coverage (%), Average check‑in time, Badge photo capture rate, Roster accuracy during drills, Tailgating incident reduction, Integration with SIS/alerts
• Who are the stakeholders that must be visibly reassured before a change—whose buy‑in matters most? Options: Superintendent, Board member(s), Principal, Front office staff, Teachers / Union reps, Parents / PTA, Facilities, IT
• What concerns or objections do you expect from staff or parents about moving away from paper sign‑in toward a screened system?
• If we could pilot a solution, what would success look like after 30 days (specific metrics, behaviors, or qualitative changes)?

Who Needs to Be In the Room to Move Forward?

• Who are the decision‑makers and influencers required to approve a visitor management change (names/roles)?
• Are there procurement, budget, or vendor policies we should plan around (e.g., bidding thresholds, district purchasing windows)? Options: Yes—formal bidding required, Yes—purchase order limits, Budget cycle timing constraints, No special constraints, Unsure
• How soon could you realistically run a small pilot at one site if the pilot required a kiosk, screening integrations, and 2 weeks of training? Options: Immediately, Within 1 month, 1–3 months, 3–6 months, Longer / uncertain
• What would be non‑negotiable acceptance criteria for a pilot to be considered successful (specific thresholds or outcomes)?
• Are there upcoming events, holidays, or building projects that would make certain windows unsuitable for deployment? Options: Upcoming large event, School break/holiday, Construction on campus, State testing window, No conflicts, Unsure

Starting Light: Which Sites and People Are We Talking About?

• Which site(s) are we preparing for in this rollout? Options: Elementary School A, Middle School B, High School C, District Office / Admin Center, Multiple sites across district, Other (please name)
• Who is the primary onsite contact for each site (name, role, best phone/email)?
• Who is the district-level sponsor or final decision-maker for deployment? Options: Safety Director, Superintendent, Director of Operations/Facilities, IT Director, Business/Finance, Other (please specify)
• What is your desired target go‑live window for these sites? Options: Next 2 weeks, 2–6 weeks, 6–12 weeks, Next school semester, Next school year, TBD
• Are there any fixed blackout dates (state testing, graduations, major events, holidays) we must avoid?

If We Can't Get Into Your Building, Who's Left Scrambling?

• What has reliably stopped or slowed deployments in the past when it came to physical site access? Options: Vendor access denied at reception, Union/contractor rules, Keycard-only doors that block entry, Custodial/maintenance schedules, No issues in the past, Other (describe)
• Describe the typical daily access points for visitors at each site (main entrance, staff entrance, gym, auditorium).
• Are there auto-lock or scheduled door behaviors that would block kiosk installation or servicing windows? Options: Yes – centrally scheduled, Yes – site-managed, No scheduled locks, Unsure
• Do installers require background checks, district escorting, or special badges to be onsite? Options: Background checks required, Escort required, Special vendor badges required, No special requirements, Varies by site
• Who approves vendor access and how much advance notice is typically required?

The Network: Lifeline or Roadblock?

• If the network isn't ready, installs stall — what's the most likely network surprise we haven't planned for? Options: Firewall blocks outbound screening API, No PoE available at kiosk locations, Kiosk needs isolated VLAN we don't have, Weak Wi‑Fi signal in lobby, Printer not reachable on network, Other (describe)
• What is the network connection type and topology at kiosk locations (wired Ethernet, Wi‑Fi, VLAN/Subnet details)?
• Do you require static IPs for kiosks or will DHCP with reserved leases work? Options: Static IP required, DHCP with reservation is fine, Either is acceptable, Unsure
• Are there existing firewall, proxy, or content-filter appliances that will need whitelisting of our domains/IPs? Options: Yes – will provide rules to whitelist, Yes – IT must approve changes, No known appliances, Unsure
• Do you have a documented IT contact, and can you share maintenance windows for network changes? Options: Yes – contact provided, Yes – will provide soon, No formal contact, Other
• What internet bandwidth/latency constraints should we plan for during peak arrival times?

Printers, Badges, and the Little Things That Break Big Plans

• Printing badges is where a smooth lobby turns into a traffic jam—what's the most fragile part of your current badge setup? Options: Printer availability/age, Badge stock/size mismatch, Poor photo quality, Printer drivers or network blocks, No printer in lobby, Other (explain)
• Which badge printer make(s)/model(s) are currently approved or already onsite? Options: Zebra ZD series, Primera, Brother QL series, Dymo, No approved printers onsite, Other (specify)
• Which badge style do you prefer for daily visitors? Options: Full‑color photo badge, Black & white photo badge, Laminated card, Sticker/temporary pass, No preference
• How are visitor photos currently captured or accepted (kiosk camera, receptionist camera, parent-uploaded, none)? Options: Kiosk camera, Receptionist takes photo, Parent/guardian provides photo, No photos captured today, Other
• Where will badge printers be located relative to kiosks (attached to kiosk, networked in office, shared MFP)? Options: Attached directly to kiosk (USB), Networked printer in reception office, Shared multi‑function printer, Mobile/temporary setup, Undecided
• Who will be responsible for badge supplies (stock, ribbon) and first‑line printer troubleshooting?

SIS and Data: Who Needs to Know What—and How Fast?

• Many SIS integrations fail in UAT — what's the single data mismatch that keeps you up at night? Options: Custody flags missing, Roster sync delays, Field name mismatches, No API access, PII/security concerns, Other (explain)
• Which Student Information System(s) do you use across the district? Options: PowerSchool, Infinite Campus, Skyward, Aeries, Other (name), We do not use an SIS
• Preferred integration method for SIS mappings and roster synchronization? Options: Real‑time API/REST, Daily SFTP/CSV export, Manual CSV upload, Middleware / district data hub, Unsure
• Which SIS fields are critical for real‑time custody or restriction alerts (select all that apply)? Options: Student ID, Student full name, Current roster & homeroom, Custody/restriction flags, Authorized pick‑ups, Dismissal location, Other (specify)
• How often do rosters change and what sync cadence would be acceptable (real‑time, hourly, daily)? Options: Real‑time (preferred), Hourly, Daily, Weekly, On‑demand only
• Who in your SIS/IT team will own mapping validation and provide sample data for testing?

Watchlists, Compliance, and Who Gets a Second Look

• Tolerating false positives or missing a real threat—what keeps your leadership awake about watchlists? Options: False positives disrupting visitors, Coverage gaps in registries, Legal liability for misflagging, No custom lists for contractors/volunteers, Data privacy concerns, Other (explain)
• Which external registries and internal lists must the system check? Options: National sex offender registry, State sex offender registry, Local police watchlist, District custom exclusion list, Contractor/volunteer blacklist, No external checks required
• Do legal or HR constraints limit how matches are displayed, who sees them, or what actions can be taken? Options: Yes – strict display/handling rules, Yes – some constraints, No constraints, Unsure – need legal input
• What escalation path should fire on a watchlist match (front office hold, notify law enforcement, alert principal, other)? Options: Front office hold + call police, Principal notified only, Security team alerted, Custom escalation – describe below, Other
• Who must sign off on final watchlist configuration: legal, safety director, superintendent, or someone else? Options: Legal counsel, Safety Director, Superintendent, Director of Operations, IT Director, Other (name)
• Describe any past incidents where watchlist configuration materially affected outcome (what happened and what did you learn)?

People, Roles, and the Moment of Truth

• If the system's alerts landed on an empty inbox, who would that break—and how quickly would they notice? Options: Front office staff, Principal/site leader, Safety Director, IT/Network team, District operations, Other (explain)
• For each site, who will be the primary owner, secondary owner, and their backups (name, role, contact)?
• Who has authority to approve emergency verification or release in a custody alert scenario? Options: Principal, Safety Director, District Administrator, Law enforcement, Other (specify)
• What is your preferred method for urgent alerts during school hours (select all that apply)? Options: SMS / text, Phone call, Email, Push notification (app), Intercom / PA announcement, Other
• How long should we wait for a response before escalating a missed alert to the next person? Options: Immediate (0–2 minutes), Short (2–5 minutes), Moderate (5–15 minutes), Long (>15 minutes)
• What training cadence and formats do your staff prefer for new systems (onsite, virtual, train‑the‑trainer, docs)? Options: Onsite live training, Virtual live training, Pre‑recorded videos, One‑page quick guides, Train‑the‑trainer, Other

If Go‑Live Were Tomorrow — What's the Biggest Risk?

• Assuming go‑live tomorrow, what single failure would cause you to halt the launch? Options: Major network outage, SIS synchronization failure, Printer / badge printing failure, Front office staff not trained, Watchlist false positive cascade, Other (explain)
• List your top three acceptance criteria that must pass on day one (e.g., badge print with photo, roster export, SIS custody alert).
• Do you require a pilot site first, a phased rollout, or a full district rollout? Options: Pilot (single site), Phased rollout (group of sites), Full district (big bang), Undecided
• What rollback or contingency plan should be available if a critical functionality fails during launch?
• Who is empowered to call a pause on go‑live and what communication channel should they use? Options: Safety Director, Principal, IT Director, Vendor Project Manager, Other (name)

Sequencing, Timing, and Support: How We Roll This Out

• Most schedules slip — where do deployments usually get held up in your timelines? Options: IT approvals/network changes, Facilities scheduling, Contractor/vendor vetting, Legal/commercial signoff delays, Training availability, Other (explain)
• What install window do you prefer to minimize disruption (after‑hours, weekend, during school day)? Options: After‑hours (weeknights), Weekend, During school day (limited hours), Hybrid – combination
• What level of onsite vendor support do you expect during go‑live week? Options: Full onsite presence, Partial onsite (critical days), Remote support only, On‑demand support as needed
• Who will be our primary escalation contact for technical issues (name, role, preferred contact)?
• Are there district policies about vendor background checks, insurance, or contractor badges we must satisfy before arrival? Options: Yes – strict requirements, Yes – some requirements, No formal policies, Unsure – will confirm

Commitment & Next Steps — Making Deployment Inevitable

• Everything sounds good—what's the one administrative obstacle that would still block this project from moving forward? Options: Legal/contract delay, Budget/PO approval, Union/HR restriction, Network or IT approvals pending, No major obstacle, Other (describe)
• What documents or approvals do you need to provide before we schedule installs (PO, signed SOW, network diagram, sample SIS export)?
• Who will own the final go/no‑go signoff and what measurable criteria will they use?
• When would you like us to follow up with a deployment readiness checklist and proposed install dates? Options: Within 48 hours, This week, Next week, After bill of materials delivered, Other
• Is there anything else about your sites, operations, or stakeholders we should know now to avoid surprises later?

Tell Me About Your Day at the Front Desk

• Walk me through a typical morning at your main school entrance—what does the front desk team see and do from 7:30–9:00am?
• Roughly how many visitors does this building (or your busiest building) receive on an average school day? Options: 0–10, 11–25, 26–50, 51–100, 101+
• Which types of visitors are most common (select all that apply)? Options: Parents/guardians, Contractors/maintenance, Volunteers, Deliveries, District staff, Community members, Other
• How is visitor sign-in currently handled at this location? Options: Paper sign-in log, Spreadsheet/CSV, Basic digital sign-in (no screening), Existing VMS with limited features, No formal process
• Who usually manages the sign-in process during peak times (select one)? Options: Front office receptionist, School secretary, Campus monitor/paraeducator, Principal or AP, Rotating staff, Other

Are We Comfortable With 'Good Enough'?

• If today nothing changed, how confident would you be that the person signed-in really should be in the building? Options: Completely confident, Somewhat confident, Unsure, Not confident
• How often do you experience events that make you question that confidence (near-miss, unknown person, tailgating, identity uncertainty)? Options: Daily, Weekly, Monthly, Rarely, Never
• Tell me about the last time you felt genuinely worried about someone getting in or being unaccounted for—what happened and how did it make you feel?
• When concerns surface, what typically prevents you from changing the process faster? Options: Budget constraints, District approval timelines, IT capacity, Staff resistance, Vendor procurement, Other
• If we solved for reliable identity verification at drop-off, what would that free your staff to focus on instead?

What's Slipping Through the Cracks?

• How often do people enter without signing in—through side doors, tailgating, or contractor access—and which entry points are most vulnerable? Options: Multiple times a day, Daily, Weekly, Monthly, Rarely
• Describe your current process (if any) for vetting contractors, substitutes, and volunteers—what documentation or checks are required?
• Which data sources do you currently rely on — state sex offender registry, county lists, internal watchlists, SIS flags, or others? (select all that apply) Options: State registry, County/local registries, District-maintained watchlist, SIS custody/restrictions, Third-party background checks, None/Unknown
• When someone’s presence is unclear during a fire drill or emergency, what is the typical impact on staff and students?
• What reports or artifacts do you wish you had after an incident to help explain what happened? Options: Time-stamped roster of everyone on site, Badge photo log, Entry/exit timeline, Access control event correlation, Screening match history, Other

If You Could See Everything at Once

• Right now—what single outcome would make you call the program a success after 6 months (be specific: time saved, risk reduced, coverage percent, etc.)?
• Which of the following success signals matter most to you? Pick up to three. Options: % Visitors screened against registries, Average check-in time per visitor, Badge photo capture rate, Accuracy of SIS custody alerts, Time to generate emergency roster, Reduction in tailgating incidents
• What is an acceptable average check-in time during peaks (e.g., arrival, dismissal, big events)? Options: <15 seconds, 15–30 seconds, 31–60 seconds, 61–120 seconds, >120 seconds
• Describe what a perfect visitor badge would include for your campus (photo quality, role, expiration, color coding, special flags).
• Imagine a lockdown or custody alert is triggered—what information or alerting behavior would make you feel you handled it correctly?

What Would It Take to Trust a New System?

• What worries you most about replacing your current process with an electronic visitor screening system? Options: Staff adoption/resistance, False positives/false negatives, Privacy concerns, Integration complexity (SIS/Access), Ongoing cost, Vendor reliability
• Who needs to be convinced internally for this to move forward, and what is each person's primary concern or criterion for approval?
• Which of these proof points would move you toward a purchase decision fastest? Options: Successful pilot at a peer school, IT/Network validation, Reference from similar district, Clear ROI/cost avoidance model, Board/superintendent endorsement
• What procurement or policy constraints do we need to work within (e.g., state contract, RFP timeline, sole-source approvals)?
• If I asked you to name three absolute non-negotiables for a vendor, what would they be?

Let’s Map Roles and Decisions — Who Really Signs Off?

• Who are the decision-makers and approvers for safety/technology purchases in your district—select all that apply. Options: Superintendent, School Board, District Safety Director, Procurement Director, IT Director, School Principal, Business/Finance Officer, Other
• Which stakeholder usually defines the acceptance criteria for go-live (performance, integrations, training)? Options: District Safety Director, IT Director, Principal, Procurement, Vendor/Integrator, Other
• How do you prefer decisions to be documented and approved—formal board memo, email sign-off, signed mutual commit, or another method? Options: Board memo, Email approval chain, Signed commercial/acceptance document, Procurement PO, Other
• What political or community sensitivities should we be aware of when we talk to parents, staff, or the board about implementing screening?
• Who will own the day-to-day relationship with the vendor after purchase (name or role) and who will own incident escalation?

Tiny Tests That Prove Big Things

• If we proposed a short pilot that uses your real morning workflows, what would make you say the pilot succeeded?
• Which scenario would you want to run first during a pilot (select up to two)? Options: Regular visitor arrival, Volunteer check-in, Contractor site entry, Student custody alert, Emergency roster/drill
• Are you willing to provide a small dataset (anonymized roster and sample visitor list) to seed testing and speed validation? Options: Yes—ready now, Yes—need approvals, Maybe—need more info, No
• How much staff time can you commit to pilot activities each week (for testing, feedback, and trainings)? Options: <2 hours, 2–4 hours, 5–8 hours, 9–16 hours, None available
• What would be an acceptable minimum duration for a pilot to prove value? Options: 1 week, 2–4 weeks, 1–3 months, 3+ months

Operational Readiness — What’s Already Ready (and What’s Not)?

• Which of these infrastructure items are already in place at the pilot site(s)? (select all that apply) Options: Reliable Wi‑Fi at lobby, Power outlets at kiosk locations, Network VLAN for kiosks, Badge printers, SIS integration endpoints, Access control connectivity, None of the above
• Describe any limitations in your network or printer environment that have blocked previous projects (bandwidth caps, guest VLAN rules, printer drivers, etc.).
• Is your SIS vendor open to integrations and do you have API/CSV export access for roster and custody data? Options: Yes—API access, Yes—CSV exports only, Pending/unknown, No
• Which buildings/sites are high priority for deployment and who is the site owner for each (name/role)?
• What logistical constraints should we plan for on install days (hours access, background checks for vendor techs, student schedules)?

How Will You Know We Delivered?

• Which acceptance tests will you require before signing off on go-live? (select all that apply) Options: Screening accuracy checks, Badge printing with photo, Roster export/alignment with SIS, SIS custody alert validation, Emergency drill roster generation, Integration stability over 72hrs
• Who will run or witness these acceptance tests (role or name) and what data will they record?
• What service levels do you expect for response time and resolution after go-live (hours to respond, days to fix)? Options: Same business day, 24 hours, 48–72 hours, Unsure/depends
• How would you like post-launch training and knowledge transfer delivered (on-site, virtual, train-the-trainer, recorded modules)? Options: On-site full-day, Virtual live sessions, Train-the-trainer, Recorded/self-serve, Combination
• What metrics and reporting cadence would help you feel confident long-term (daily incident logs, weekly dashboards, monthly executive summaries)? Options: Daily operational, Weekly summaries, Monthly executive, On-demand exports, Custom alerts

Next Steps — Small Commitments That Move the Needle

• If nothing changes in the next 12 months, what specific risks or operational pain do you expect to see increase?
• How soon are you looking to start a pilot or procurement process? Options: Immediately (next 2 weeks), In 1–2 months, In 3–6 months, Later this year, Undecided
• Which site(s) would you prioritize for a pilot (name the building or campus) and why?
• What approvals or documents do we need to move forward (PO, MOU, district IT sign-off, background checks)? Options: Purchase order, MOU/contract, IT/network sign-off, Board approval, Other
• What’s the best way for our team to keep this conversation moving—preferred point of contact, communication channel, and ideal time for a 30-minute follow-up?