Video Surveillance
Technology and operations decisions where district leadership, IT, and stakeholders must align.
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, funding timing, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles, board and law-enforcement touchpoints, funding windows (bonds/grants), and success priorities.
Alignment Questions
Start with Who’s in the Room
- Who will be the primary point of contact for this campus video program?
- Which individuals or offices hold final approval authority for vendor selection or capital spend on this project?
- Are there standing committees, bond oversight groups, or regional authorities that must sign off before work can begin? Please list them.
- Who typically raises FERPA, student privacy, or parent-concern issues during technology decisions?
- How confident are you that this list captures everyone who needs to be involved?
Who Holds the Keys—And What Keeps Them Awake at Night?
- Which stakeholder could effectively kill this project if their concerns aren’t resolved, and what would that objection sound like?
- What are the top three objections you’ve heard from board members or finance about prior security projects?
- Have law enforcement partners asked for direct or expedited access to footage in the past? Which agencies and what access did they request?
- Which stakeholder voices privacy concerns most strongly, and what scenarios trigger those concerns (e.g., classroom recording, parent complaints)?
- How have prior vendor engagements influenced stakeholder trust—do decision-makers lean toward cautious, skeptical, or open with new vendors?
- What evidence or assurances would ease the biggest emotional objection you hear (e.g., live demo, reference from nearby district, FERPA attestation)?
Timing Is Everything—Are You on a Clock?
- If the next funding window slammed shut tomorrow, would this project survive?
- Which funding sources are realistically available to you for this program?
- When are the next budget decision points, board meetings, or grant deadlines that could approve funding?
- Have you applied for or used grants/bonds for surveillance or safety projects before? What was the outcome and timeline?
- Are there external deadlines or mandate-driven timelines (state coverage requirements, grant expirations, insurance conditions) that create non-negotiable dates?
- If funding slips to the next cycle, what operational or safety impacts would you expect in the interim?
What Would Make Everyone Say ‘Worth It’?
- One year after go‑live, what outcome would make the board, law enforcement partners, and families all agree the investment paid off?
- Which of these outcomes are absolute must-haves for project success (select all that apply)?
- What measurable KPIs would you use to prove success (examples: % of incidents with usable footage, average retrieval time, downtime minutes per month)? Please list the top three.
- Who will sign the official acceptance when those KPIs are met?
- How would you like us to report success after go‑live—format and cadence (e.g., quarterly dashboards, forensic case summaries, executive briefs)?
The Evidence Pipeline—How Does Footage Flow?
- In a critical incident at 2pm, what does 'rapid access' to evidence actually look like for you—who needs it and how fast?
- Which parties must be able to access live or recorded footage, and at what level of access?
- Do you prefer law enforcement to have direct access, a mediated/approved request workflow, or a secure evidence portal for exports?
- What chain-of-custody, export, or redaction requirements apply in your jurisdiction before footage leaves the district?
- Who will be responsible for long-term storage and custody—district, vendor-managed cloud, or a third-party evidence vendor?
How Do You Actually Say Yes — The Decision Playbook
- Think of the last technology purchase that passed—what process was followed from evaluation to sign-off, and where did it almost fail?
- Which procurement path will you most likely use for this work?
- Who signs the contract and who signs the budget approval—are they the same person/office?
- What proof points shorten approval time for your stakeholders (pilot results, nearby district references, security certifications, cost analysis)?
- Would an on-site incident-based walkthrough or a simulated law-enforcement evidence pull meaningfully speed approval?
- If stakeholders sign off today, how quickly could you finalize procurement and schedule a pilot or initial install?
Who Owns It After Go-Live — Escalation, Maintenance, and Trust
- After go‑live, who do you expect will be held accountable first if a camera/system fails during a critical incident?
- Who will own day-to-day system health checks, and who will be the escalation point for vendor issues?
- What response times are non-negotiable during school hours versus after hours?
- What cadence and format of SLA/health reporting will satisfy board or grant compliance (e.g., quarterly dashboards, incident logs)?
- How should firmware updates, maintenance windows, and training be scheduled to avoid disrupting instruction and parent events?
- What acceptance tests or verification steps post-install would make you comfortable signing final acceptance (select all that apply)?
-
Current State Mapping
Document existing cameras, blind spots, recording quality, integrations, retention gaps, and network/power constraints.
Current State
Start Where You Are — A Quick Snapshot
- Roughly how many physical cameras are currently installed across your district/campus (best estimate)?
- Who owns day-to-day responsibility for the cameras and VMS (operations, monitoring, maintenance)?
- How would you describe the general age/condition of the majority of your camera hardware?
- In one sentence, what frustrates you most about your current surveillance setup?
Blind Spots That Keep You Up at Night
- If an incident happened tomorrow, where would you most expect to discover you have no usable camera footage?
- How were those blind spots identified—through a formal audit, an actual incident, parent/community complaints, or staff observation?
- Pick one critical blind spot you selected and describe a recent example or near-miss where lack of coverage affected response or evidence collection.
- Have temporary or interim measures been used to cover gaps (e.g., portable cameras, staff posts, re-aims)? Which were attempted and why didn't they become permanent?
- Which zones do you consider untouchable vs. high-priority for immediate coverage (list 1–3 highest priorities)?
When Footage Fails: The Evidence Breakdown
- How often does recorded video end up being unusable when needed for investigations or law enforcement?
- Which technical problems show up most frequently when footage is unusable?
- Tell us about a specific incident where footage failed to meet needs—what critical detail was missing (quality, angle, continuous recording, metadata)?
- What minimum forensic specs would make footage acceptable for you (resolution, fps, retention days)?
- Do you currently perform any scheduled image-quality or forensic-validation tests (e.g., low-light tests, angle checks)? If so, how often?
Are Your Systems Talking — or Whispering?
- When an emergency (lockdown, active threat) occurs, can you instantly assemble and share the right camera feeds with responders?
- Which systems integrate with your camera/VMS today? Select all that apply.
- How are law-enforcement footage requests handled now (portal download, on-site export, handheld drive, emailed clips)?
- Has lack of integration ever delayed emergency response or evidence handoff? If yes, describe what caused the delay.
- Who currently has remote (off‑network) access to live and recorded video, and how is that access authenticated?
Power, Network, and Storage — The Invisible Limits
- Can your current network and power infrastructure support a full upgrade to modern HD cameras without surprise upgrades?
- Approximately what percentage of camera locations are connected to PoE-capable switches today?
- Do you have UPS or generator-backed power for camera closets and critical exterior cameras?
- Describe your current storage approach and average retention by site (local NVR, centralized VMS, cloud, hybrid).
- If upgrades are needed, which constraint is most likely to block progress: budget timing, installation during the academic calendar, contractor clearance, or network complexity?
- If known, estimate average daily video data produced by your fleet (or select 'Undetermined').
Who Sees What — Access, FERPA, and Forensics
- Could a substitute or temporary staff member accidentally expose student video or access restricted footage today?
- Which roles currently have routine access to live and recorded video? (Select all that apply.)
- Are FERPA and evidence-handling procedures documented and tied directly to camera access and sharing? If documented, how often are they reviewed?
- Are audit logs enabled for video access, and do you regularly review them for anomalies?
- How do you currently handle privacy vs. transparency (parent requests, redaction, selective sharing)? Describe your typical workflow.
What Would Make You Sleep Easier?
- If you could fix only three things about your surveillance today, what would you prioritize?
- Which of those priorities must be in place to move forward within your current funding cycle?
- What is your expected timeline for funding and decision (this fiscal year, next fiscal year, tied to bond/grant, or uncertain)?
- Who are the specific decision-makers and influencers who must sign off on scope, budget, and vendor choice (list titles or names)?
- What are the non-negotiable concerns that would make you pause on a replacement or upgrade (e.g., class disruption, data migration risk, vendor clearance)?
-
-
Outcome Discovery
Define measurable success signals (coverage of mandated zones, retention, access response time, low-light performance).
Discovery Questions
Quick Snapshot: Your Current Video Reality
- Tell us briefly: how would you describe your current camera system in one sentence?
- How many physical camera endpoints do you believe are currently deployed?
- Which of these best describes the system’s condition today?
- Which of these integrations are already in place at any campus (select all that apply)?
- How do staff currently retrieve footage when an incident happens?
Are You Comfortable Counting on ‘Maybe’ Footage?
- When an incident occurs, how often do you find the footage you need is unusable or missing?
- Share a recent example when video didn’t support an investigation—what failed and what was the outcome?
- What happens operationally and politically when camera evidence is missing (e.g., board questions, parent escalation, delayed arrests)?
- How does that recurring risk make you feel about your ability to keep students and staff safe?
- Who on your team currently owns follow-up when footage is lost or corrupted?
If a Regulator Stopped By Today: Mandates vs. Reality
- Which mandated coverage zones must your district meet today (select all that apply)?
- What are your legally required retention windows (days) for student-area footage?
- Are there standing legal-hold or evidence-preservation processes you must support (e.g., law enforcement holds)? If yes, please describe.
- How confident are you that your current system meets FERPA and local evidence access rules?
- Has your district ever failed an audit or investigation due to surveillance gaps? If so, what was flagged?
How Fast Do You Need Answers When Seconds Matter?
- If an administrator or police officer requests live access during an incident, what is your target maximum time-to-view?
- What’s an acceptable time to retrieve and deliver a recorded clip after an incident is reported?
- Who must be able to get immediate access (select all that apply)?
- How important is simultaneous multi-site viewing during a district-wide emergency?
- Describe any past situation where delayed access changed the outcome (briefly):
Seeing Clearly in the Dark and the Crowd
- If poor low-light footage meant an incident couldn’t be clarified, what would that cost you (operationally or reputationally)?
- Which environments give you the most trouble at night or in poor lighting (select all that apply)?
- What level of detail must be readable for forensic purposes in critical zones (choose one)?
- Do you have examples where analytics (loitering, crowding, bus arrival) would have changed the response? Please describe.
- Which of these imaging priorities matter most in order (select up to three)?
What Acceptance Looks Like — Tangible, Measurable Signals
- Imagine you had to sign acceptance tomorrow — what three measurable outcomes would guarantee sign-off?
- Choose the minimum acceptable coverage percentage for mandated zones (by zone group):
- Select the target system uptime and availability we must meet during school hours:
- Which of these SLAs matter most for your acceptance criteria (select all that apply)?
- What quantitative test would prove low-light forensic capability for critical zones (describe the test and pass/fail threshold)?
- For VMS usability, what task should a non-technical staffer complete within 5 minutes as part of acceptance?
Tradeoffs: What You’d Keep and What You’d Compromise
- If budget required sacrificing one capability, which would you be most willing to compromise on?
- Would you prefer a staged rollout (prioritize high-risk zones first) or a big-bang cutover? Why?
- How do you weigh on-prem storage vs cloud/hybrid in terms of compliance and cost for your district?
- What maintenance cadence would you find acceptable to minimize school-year disruption?
- Are there hard deadlines (bond/grant funding windows) that force a particular procurement or deployment timeline? If yes, please list.
Who Signs Off — The People, Politics, and Pressure
- Who are the decision-makers that must sign final acceptance (select all that apply)?
- Which external stakeholders need to be informed or have formal input (select all that apply)?
- What evidence will convince each stakeholder group that the system meets requirements (e.g., demo, field test clips, written report)?
- Do you have a public-facing acceptance or transparency requirement (e.g., share audit results with board/public)?
- Who will be responsible for operational sign-off and ongoing vendor escalation after deployment?
Small Tests That Prove Big Things: Pilot & Validation Ideas
- If we ran a focused pilot, which site or zone would you pick to prove outcomes quickly and why?
- Which measurable pilot goals would convince you the design will scale district-wide (select up to three)?
- How long of a pilot would you find persuasive before committing to wider deployment?
- What constraints must a pilot avoid (e.g., disrupting classes, harvest union concerns, privacy impact)?
- Would you want an independent third-party witness (e.g., law enforcement liaison) to certify pilot results?
Final Check: Risks You Might Not Be Asking About
- What network or power limitations have you learned to tolerate that could break this solution if unaddressed?
- Have you experienced privacy or FERPA incidents related to footage access previously? If yes, what happened?
- How critical is a documented chain-of-custody process for video evidence in your view?
- Which contingency would be most damaging if it occurred during school hours (select one)?
- What single unresolved risk would make you pause a project today?
-
Solution Experience
Walk through incident-led scenarios that show how the proposed system delivers required coverage, integrations, and forensic outcomes.
Experience Meetings
- Pre-Work Alignment: Current State & Consequence Capture
- Incident-led Tabletop: Scenario Walkthrough (Operational Flow)
- Proof-of-Capability: Technical Demonstration (Search, Retrieval, Access Controls)
- Field Validation Planning (Pilot & Acceptance Criteria)
- Executive Outcomes Review & Next Steps
- Lock down pilot dates that avoid critical academic events and confirm required site access and permissions.
- Test Scenario Setup & Success Criteria
- Provide objective proof that performance targets (retrieval time, ID quality, access controls) are achievable with the proposed configuration.
- Get non-technical staff to successfully complete key VMS tasks to validate usability and training scope.
- Confirm SLA and failure-mode expectations are documented for inclusion in Mutual Commit.
- Seller to deliver a short proof report showing measured retrieval times and image quality metrics from the demo.
- Customer to nominate 1-2 non-technical users to participate in the usability test and provide feedback.
- Seller to update the SLA and escalation section with agreed 4-hour school-hour response wording for review.
- Pilot Objectives & Scope
- Create a runnable pilot plan with explicit success criteria that proves the Solution Experience outcomes in the field.
- Introductions & Meeting Objective
- Assign pilot owners and agree reporting format to feed results into the Mutual Commit stage.
- Seller to produce a pilot test plan with pass/fail checklist and sample evidence templates.
- Customer to secure site access approvals and schedule pilot windows that align with academic calendar constraints.
- Both parties to confirm pilot participants and contact list for rapid escalation during tests.
- Executive Summary of Findings
- Obtain executive alignment on the validated outcomes and formal agreement on acceptance criteria for moving to Solution Scope.
- Confirm funding path and target timeline to reach Mutual Commit with named decision owner and date.
- Authorize the pilot or scope activities needed to close remaining gaps identified in the Solution Experience.
- Customer to confirm funding source and target procurement timeline and identify the signatory for Mutual Commit.
- Seller to deliver a one-page Outcome & Acceptance document summarizing validated metrics, pilot plan, and recommended Solution Scope entry points.
- Schedule the Solution Scope meeting with required technical and procurement stakeholders within the agreed timeline.
- Produce a verified one-sentence current-state statement that all participants agree describes the problem.
- Document concrete consequence metrics and examples for prioritized incidents.
- Agree the 3-5 incident scenarios and measurable success metrics that the Solution Experience will prove.
- Assign pre-work owners and deadline for artifacts needed for the live scenarios.
- Customer to provide floor plans, camera inventory with model and locations, and 3 representative incident video clips (if available).
- Customer to confirm decision-makers and law-enforcement or FERPA contacts to invite to the Solution Experience.
- Seller to draft one-sentence current-state and one-sentence future-state for review prior to the Solution Experience.
- Seller to prepare scenario scripts mapped to provided artifacts and success metrics.
- Recap Current-State, Consequence, Future-State
- Demonstrate, using customer context, that each scenario meets the future-state success metrics or surface why it does not.
- Validate integrations and chain-of-custody processes with law enforcement and FERPA stakeholders.
- Produce a prioritized backlog of technical gaps and configuration changes needed to prove full coverage for the scenarios.
- Seller to map scenario steps to specific camera locations and VMS workflows and deliver a scenario trace document.
- Customer IT to confirm API access and credentials or provide integration contacts for mass-notification and access-control vendors.
- Assign owners for each identified integration gap with target resolution dates.
- One-sentence Current State
- Test Cases & Acceptance Criteria
- Benefit & Risk Quantification
- Forensic Search & Retrieval Test
- Scenario 1 — Detection to Forensics
- Acceptance Criteria & Go/No-Go
- Consequence Quantification
- VMS Usability for Non-Technical Staff
- Logistics & Scheduling
- Scenario 2 — Response & Chain-of-Custody
- FERPA & Law-Enforcement Access Flow
- Scenario 3 — Low-light / Forensic Quality Case
- Roles, Reporting & Evidence Collection
- Commercial & Timeline Next Steps
- Select & Prioritize Incident Scenarios
- Validation Checkpoints
- Low-light Image Quality & Analytics Proof
- Define Future-State Outcomes & Success Metrics
- Open Items & Integration Gaps
- Pre-work & Data Checklist
- Failure-mode & SLA Discussion
-
Solution Scope
Define cameras by zone, VMS modules, integrations, storage architecture, retention, and maintenance cadence.
Scope Configuration
- Install Outdoor HD Dome Cameras (perimeters and bus zones)
- Install Indoor Low-Light Hallway and Cafeteria Cameras
- Configure Video Management System with Building/Zone Grouping
- Integrate Cameras with Lockdown and Mass Notification Systems
- Provision Storage with Automated Retention and Lifecycle Rules
- Deploy FERPA-Compliant Role-Based Access and Audit Logging
- Enable Forensic Search and Event-Based Clip Exporting
- Deploy Analytics: Occupancy, Loitering, and Bus Verification
- Install PoE Network Switches and UPS Backup for Cameras
- Configure Secure Remote Law Enforcement Access Portal
- Implement On-Premises or Cloud Recording Redundancy and Failover
- Perform Camera Aim, Focus, and Nighttime Low-Light Tuning
- Execute Firmware Upgrades and Patch Deployment During Breaks
- Provide Four-Hour On-Site Repair and Hardware Replacement SLA
Scope Questions
Install Outdoor HD Dome Cameras (perimeters and bus zones)
- Which outdoor zones require new HD dome cameras?
- Approximately how many outdoor cameras do you anticipate per zone?
- Are there existing mounts, poles, or conduit available at the proposed outdoor locations?
- What environmental and physical ratings are required for outdoor domes (impact, weather)?
- What network connectivity is available at the outdoor camera points?
- Are there any line-of-sight, glare or mounting-height constraints we should plan for?
Install Indoor Low-Light Hallway and Cafeteria Cameras
- Which interior areas need low-light optimized cameras?
- How many cameras are expected per building for hallways and cafeterias?
- What are typical ceiling heights and mounting surfaces in these areas?
- What low-light performance level do you require?
- Are privacy masks or restricted viewing zones required inside any areas (e.g., restrooms, staff-only spaces)?
- Any special mounting or tamper-protection requirements for indoor cameras (shrouds, tamper switches)?
Configure Video Management System with Building/Zone Grouping
- How many buildings and distinct zones (e.g., wings, bus loops) will need to be modeled in the VMS?
- Which VMS features are mandatory for your staff?
- How many concurrent VMS operator seats or simultaneous viewers are required?
- Do you require building/zone presets or custom layouts that match your campus maps?
- Should the VMS include automated health alerts and scheduled system health reporting?
- Are integrations with existing directory/SSO systems required for VMS logins (SAML/Active Directory)?
Integrate Cameras with Lockdown and Mass Notification Systems
- Which lockdown / mass notification systems must we integrate with?
- What actions should occur when a lockdown is triggered?
- What integration method is preferred or supported by your vendor (API, webhook, ONVIF event triggers)?
- Are there regulatory or district policies governing when integrations can auto-share or auto-disclose footage?
- Should integration include automated tagging of footage/incident IDs for later evidence retrieval?
- Who is the technical contact for the lockdown/mass-notification vendor to coordinate integration (name/role and preferred contact)?
Provision Storage with Automated Retention and Lifecycle Rules
- What are the required retention periods by policy or state law for different camera classes (e.g., entrances, buses, interior)?
- Which storage architecture do you prefer?
- Do you require automated lifecycle rules (e.g., tier from hot to cold, archival to evidence locker)?
- Are there bandwidth or network constraints that limit cloud replication or offsite backups?
- Is encrypted at-rest and in-transit storage required for legal/compliance reasons?
- Do you need automated evidence export and long-term archival to a separate evidence repository?
Deploy FERPA-Compliant Role-Based Access and Audit Logging
- How many distinct user roles should be defined (e.g., Admin, Safety Director, Principal, Campus Officer)?
- Do you require integration with district SSO or directory services for role assignment?
- What audit logging retention length is required for access and export logs?
- Should access to footage require two-person approval or signed requests for law-enforcement/third-party access?
- Do you require automated alerts for unusual access (e.g., mass exports, off-hours downloads)?
- Are there FERPA-specific redaction or sharing workflows we must support?
Enable Forensic Search and Event-Based Clip Exporting
- Which forensic search capabilities are required?
- Should exported clips be auto-watermarked, chain-of-custody tagged, and packaged with audit logs?
- What export formats are needed for evidence (MP4, AVI, vendor-proprietary)?
- Who will perform forensic searches day-to-day (e.g., campus staff, SRO, district safety team)?
- Do you require pre-configured export templates or incident bundles for law enforcement requests?
- Are there retention rules for exported clips separate from source recordings?
Deploy Analytics: Occupancy, Loitering, and Bus Verification
- Which analytics modules do you want enabled?
- For loitering detection, what minimum dwell time should trigger an alert?
- Do analytics need to run on-camera (edge) or centrally on servers/cloud?
- Do you require dashboards or automated incident creation from analytics events into the VMS/ticketing system?
- Are there privacy constraints (e.g., no facial recognition, anonymized occupancy) that limit certain analytics?
- Which thresholds or reporting cadence do you want for bus verification (e.g., daily summary, per-event alerts)?
Install PoE Network Switches and UPS Backup for Cameras
- How many PoE camera ports are required at each IDF/MDF or closet location?
- What PoE power budget per port is required (to support PTZ/IR/heaters)?
- What UPS runtime is required to keep cameras recording during a power outage?
- Do you require separate camera VLANs, QoS configuration, or PoE monitoring integrated into the NMS?
- Should we include surge protection and outdoor-rated switch placement for perimeter runs?
- Are there cabling constraints (existing CAT5 vs CAT6 vs fiber backbone) we need to account for?
Configure Secure Remote Law Enforcement Access Portal
- Which law enforcement agencies will need access and what is the expected frequency of requests?
- What remote access method is preferred for law enforcement?
- What authentication controls do you require for LE access (temporary accounts, 2FA, account expiration)?
- Do you require audit trails and automatic notifications to district admins when LE accesses footage?
- Will formal MOUs or evidence request forms be used before granting remote access?
- Any special evidence-handling requirements (download expiry, watermarking, non-rewritable archive)?
-
Mutual Commit
Finalize commercial terms, SLAs (including 4-hour school-hour response), funding milestones, and acceptance criteria.
Agreement Modules
- Non-Disclosure Agreement (NDA)
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Pricing & Payment Schedule
- Funding Milestone Agreement (Bonds/Grants)
- Acceptance Criteria & Test Plan
- Data Processing & FERPA Addendum (DPA)
- Evidence Access & Chain-of-Custody Annex
- Integration & Third-Party Interface Agreement
- Change Order Agreement
- Maintenance & Support Plan
- Installation Window & Academic Calendar Cutover Plan
- Warranty & Hardware RMA Terms
- Insurance, Indemnity & Liability Schedule
- Purchase Order / Procurement Authorization
- Final Sign-off & Closeout Certificate
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation aligned to the academic calendar.
-
Pre-Deployment Readiness
Confirm site access windows, network upgrades, power/backups, FERPA access controls, and law-enforcement evidence paths.
Readiness Questions
Start with the Map: Tell Me About Your Campus
- In one or two sentences, describe your campus footprint (number of buildings, portable classrooms, parking lots) and student population.
- Roughly how many cameras are currently deployed across your district or campus?
- Which of these areas do you believe have reliable camera coverage today? (select all that apply)
- How would you characterize the typical video quality you get when you need it for an investigation?
- Who currently owns day-to-day camera operations, exports, and account provisioning?
- Do you have up-to-date camera placement maps and retention policies that match state evidence laws?
Are We Comfortable Leaving Blind Spots?
- What would it cost the district — operationally, legally, and emotionally — if a critical blind spot went unnoticed until after an incident?
- Where do blind spots show up most often on your sites (specific buildings, matches, bus zones, portables)?
- How are blind spots usually discovered in your district—complaints, post-incident analysis, scheduled audits, or vendor reviews?
- How often do investigations fail or get delayed because footage was missing or unusable?
- Tell me about a recent example where video wasn't helpful—what specifically went wrong (coverage, angle, frame rate, retention, access)?
- Which camera types or legacy systems cause the most recurring issues for you?
When an Incident Happens — How Does It Really Play Out?
- If law enforcement needed video from an urgent incident, how confident are you that you could deliver usable footage within one hour?
- Describe your current process for evidence requests from police or investigators—who does what, and how long does each step take?
- On average, how long does it take to locate, export, and hand off footage for an investigation?
- Have you experienced any FERPA or legal complications when sharing footage? If yes, briefly describe what happened.
- Which roles should have immediate access during an active incident (select all that apply)?
- What does a 'good' evidence-handling workflow look like to you, from discovery to chain-of-custody?
What Would Success Actually Look Like for Students, Staff, and Parents?
- Instead of 'more cameras', what outcomes would make families, teachers, and officers genuinely feel safer and more supported?
- Which measurable signals would convince you the system is delivering on safety? (select up to four)
- What are your district or state retention requirements right now (days/months/forensic holds)?
- How should non-technical staff interact with the VMS during an emergency—what capabilities must be one-click or automated?
- Which integrations would change outcomes most meaningfully (select all that apply)?
- How often would you want evidence and health reports reviewed with our team post-install (and who should attend)?
What's Getting in the Way of Fixing This—Beyond Budget?
- What political, organizational, or procedural obstacles have caused past security projects to stall or underdeliver?
- Which internal stakeholders typically slow approvals or create scope changes (select all that apply)?
- Have you attempted similar upgrades and been stopped by procurement, contract terms, or vendor lock-in before?
- How does the academic calendar limit installation and cutover windows for you (specify blackout dates or preferred windows)?
- Which SLAs are non-negotiable during the school year (select all that apply)?
- Have past maintenance or firmware updates caused downtime that affected safety? Please describe briefly.
If Money and Time Were Flexible — What Would You Prioritize?
- If you could wave a wand and fix exactly three surveillance problems tomorrow, what would they be?
- Which of these would you prioritize first for investment?
- Would you prefer a phased rollout focused on high-risk buildings or a district-wide switchover? Why?
- Edge storage vs. centralized storage — which aligns better with your needs and why?
- How important is camera analytics (loitering, occupancy, bus verification) to your safety program versus pure recording quality?
- What level of training, documentation, and handoff do your staff need to feel confident using the system?
Who Holds the Keys — Decision and Funding Pathway
- If this project stalls, whose sign-off, timeline, or budget approval is most likely to be the bottleneck?
- Who are the decision-makers and approvers we should include in briefings and demos? (select all that apply)
- What procurement path does your district typically follow for security tech (select one)?
- What is your target timeline from decision to full deployment?
- What funding sources will you pursue for this work? (select all that apply)
- What criteria will the board or CFO use to evaluate proposals beyond price (e.g., lifecycle cost, local tech support, evidence chain, FERPA compliance)?
Operational Details We Can't Skip
- What must be confirmed before technicians arrive on site to avoid install delays (site access, keys, network closets, escorts)?
- Do your buildings have sufficient PoE switches, bandwidth, and VLAN separation to add or replace cameras?
- Which of these power and backup constraints exist today (select all that apply)?
- Do you have FERPA-specific access controls, account provisioning, and audit logging policies in place today?
- What are the preferred install windows around the academic calendar (e.g., summer only, weekends, evenings, break weeks)?
- Who is responsible for coordinating site-level logistics (site contact, after-hours access, fire alarm/coordinated shutdowns)?
- Are there any law-enforcement evidence-handling protocols or local policies we must follow for exports and custody?
Next Steps: What Would Make You Say Yes?
- What are the top three concerns that would prevent you from moving forward this quarter?
- Which proof points would help you feel confident selecting a vendor (select all that apply)?
- What would a low-risk pilot look like to you in scope, duration, and success criteria?
- Realistically, how soon could your team engage in a discovery walkthrough and technical audit?
- Who should we schedule next on our side to keep momentum (names/titles and best contact method)?
-
Deployment Enablement
Schedule installs and cutovers around the academic calendar, coordinate teams, and execute with Gantt-driven task owners.
-
Validation Checklist
Verify coverage, low-light imaging, VMS usability for non-technical staff, integration tests, retention policy, and audit logging.
Validation Questions
Opening: What Brought Us Here Today?
- What prompted you to review or replace the campus video system at this moment?
- Who on your team will be most impacted day-to-day by changes to the camera or VMS setup?
- Which of these outcomes is your highest priority right now?
- How confident do you feel in describing the existing system’s capabilities to your board or superintendent?
- What’s one short story or recent moment that makes you say 'we need this fixed'?
Are We Waiting for a Crisis to Force Change?
- If nothing changes in the next 12 months, what’s the most likely safety or compliance risk you’d face?
- How many incidents in the last year required video evidence but were delayed or unusable?
- When footage was needed, how long did it typically take for authorized staff to retrieve and share it?
- Describe a recent incident where video made a difference—or where it failed to. What felt most frustrating?
- Who outside the district (law enforcement, regional safety office, insurance, state) regularly asks for access to footage?
Where Are the Blind Spots That Keep You Awake?
- If you had to point to one location on campus you’d be embarrassed to show camera coverage of, where would it be and why?
- Please identify the types of spaces you believe are under-covered today.
- How were blind spots initially discovered—routine audit, incident, or anecdotal concerns?
- For the top two blind-spot areas you named, how long have those gaps existed?
- Are any of the under-covered areas constrained by power, mounting surfaces, or network bandwidth?
If Evidence Had to Stand in Court Tomorrow, Would It?
- When footage must support an investigation, how often has image quality been sufficient to identify faces or license plates?
- What resolution and low-light performance do you expect from new cameras in high-priority zones?
- How long must footage be retained to meet state evidence and FERPA requirements for your district?
- Have you previously had to place a legal hold on video for an investigation—how was that handled and what broke?
- Do you currently apply automated lifecycle rules (e.g., archiving, evidence hold) in your storage, or is it manual?
Who Really Needs Access — And Who Keeps Getting It?
- If you tightened access controls tomorrow, who would you absolutely want to retain immediate playback privileges?
- How are law enforcement requests for footage handled today—walk me through the typical steps and timeline.
- Have you audited who has accessed video in the last 12 months and found any inappropriate access?
- Which access control features matter most to you: role-based permissions, time-limited links, multi-factor authentication, or detailed audit trails?
- How comfortable are non-technical staff today with pulling clips and sharing them with investigators or parents?
What Would Truly Make Your School Safer — Not Just Appear Safer?
- If success is measured in concrete ways, what 2–3 metrics would prove the system is delivering value?
- What maximum time-to-live (from incident to footage in investigators’ hands) would you accept as success?
- How important is automated analytics (loitering, perimeter breach, bus arrival verification) versus pure high-fidelity recording?
- Which stakeholders will judge project success—what do the board, superintendent, and union reps each care about?
- How would you prioritize ongoing health checks and firmware updates relative to minimizing classroom disruption?
Money, Timing, and the Politics: What's the Real Constraint?
- If funding were guaranteed today, how quickly would you expect an initial phase to be scoped and priced?
- Which funding sources will you pursue—bond, state grant, federal grant, operating budget, or a combination?
- What are the non-financial blockers that tend to slow projects here—procurement rules, union agreements, competing projects, or political debate?
- How tied is the project timeline to a specific funding window or grant milestone?
- If costs exceed estimates by 10–15%, how tolerant is leadership of scope adjustments versus phased funding?
How Do You Want the System to Fit Day-to-Day?
- Who will perform routine tasks—clip export, bookmarking, evidence handoff—and how much time can they realistically spend per week?
- Describe the most common daily scenario where staff need to use video (e.g., student behavior, parent complaint, parking dispute). What steps do they take now?
- How important is mobile access for principals and officers versus desktop-only access?
- Would you prefer a VMS that is highly simplified for non-technical users with a separate admin console, or a single console with role-based views?
- What kind of training and documentation do non-technical users need to feel confident (quick reference cards, in-person training, video tutorials)?
What Happens During the School Year If Something Breaks?
- How critical is a guaranteed 4-hour response during school hours for your operations?
- What has been your past experience with vendor response times and temporary fixes versus permanent repairs?
- Which maintenance model do you prefer: time-and-materials, annual all-inclusive contract, or per-incident SLA?
- For quick triage, what diagnostic access should vendor technicians have to your network and equipment?
- How do you want emergency fixes scheduled during the school day to avoid disrupting instruction?
What Could Stop Deployment at the Last Minute?
- Thinking through install day, what single constraint would derail a scheduled install (examples: network not ready, access denied, missing approvals)?
- Do you have preferred install windows tied to the academic calendar (summer, spring break, weekends)? If so, which windows are off-limits or preferred?
- What internal teams need to be coordinated for deployment (IT, Facilities, Transportation, Principals)?
- Are there buildings with special access or background-check requirements for technicians?
- What would success look like on day one after cutover? Be specific about what must be working.
Let’s Be Specific: Validation Items and Acceptance Criteria
- Which validation items are non-negotiable on acceptance: coverage verification, low-light proof, VMS usability test for non-technical staff, integrations, retention policy, audit logs?
- For coverage verification, what acceptance method do you prefer: incident-based walkthroughs, filmed proof-of-coverage, or independent third-party validation?
- How will you test VMS usability for non-technical staff: scripted tasks during acceptance, follow-up user survey, or a pilot with a small group?
- What retention and evidence-hold behaviors must be demonstrable during validation (auto-hold, export with checksum, legal hold override)?
- Who will sign technical acceptance and who will sign commercial acceptance? Please name roles and responsibilities.
- If a validation item fails, what is your preferred remediation path: immediate fix and re-test, deferred backlog with partial payment hold, or project pause until fixed?
Closing: Next Steps and Commitments
- Based on this conversation, which next step feels most useful: site survey, pilot install, budget worksheet, or stakeholder briefing?
- Who else should be included in the upcoming discovery meetings to accelerate decisions?
- What concerns would you want us to address in the proposal to make it easier for your board to approve?
- Realistically, when could you assemble final decision-makers to review a proposal?
-
-
Success
Confirm outcomes, schedule quarterly health reviews, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Outcomes Confirmation & Acceptance Review
- Quarterly Health Review Kickoff
- Issue Triage & Shared Channel Setup
- Post-Acceptance Usability & Non-Technical Staff Training
- Funding, Renewal & Enhancement Roadmap Planning
Issues & Enhancements
- Schedule and assign trainers and dates for initial and refresher trainings tied to the academic calendar.
- Create and share the Quarterly Health Report template with data fields and dashboard links.
- Schedule recurring quarterly review meetings in district and vendor calendars for the next 12 months.
- Assign responsible owners for pre-work and verification for the first review.
- Channel Platform & Permissions
- Provision a secure shared channel with clear permissions and FERPA-safe sharing rules.
- Agree triage workflow, severity definitions, and SLA targets including the 4-hour school-hour response.
- Define enhancement intake process and how items are prioritized into the roadmap.
- Provision the agreed shared channel and invite named district and vendor participants.
- Publish a triage runbook including severity matrix, escalation steps, and contact roster.
- Create an enhancement intake form and route it into the vendor product backlog for prioritization.
- Audience & Training Objectives
- Confirm non-technical users can complete critical VMS tasks under observation.
- Agree on role-based access and FERPA-compliant audit procedures.
- Introductions & Objectives
- Deliver finalized training deck, quick reference guides, and recorded session links to district staff.
- Schedule hands-on training sessions and assign district trainers for ongoing onboarding.
- Document role mappings and update access control lists in the VMS to match agreed permissions.
- Review Funding Windows & Deadlines
- Align on the next renewal date and preferred licensing/maintenance option.
- Map top enhancement priorities to likely funding sources and calendar milestones.
- Assign owners and deadlines for budget briefs and board/grant submissions.
- Produce a one-page budget brief showing renewal costs, maintenance options, and enhancement priorities for the district board.
- Estimate costs and timelines for the top three enhancement requests and attach to the funding brief.
- Document funding milestone dates and owners and add them to the shared project calendar.
- Validate each acceptance criterion with evidence and obtain formal customer sign-off.
- Establish a remediation plan with owners and deadlines for any remaining gaps.
- Set the date and owner for the first Quarterly Health Review and record baseline metrics.
- Publish signed acceptance document and baseline metric report to shared project folder.
- Open remediation tickets for any outstanding items with owners, due dates, and verification steps.
- Create calendar invite for the first Quarterly Health Review and attach baseline evidence.
- Purpose & Cadence
- Agree on quarterly cadence, KPI set, and target thresholds for system health.
- Approve the health report template and delivery mechanism for district leadership.
- Assign owners for data collection, report generation, and follow-up actions.
- Review Acceptance Criteria & Success Signals
- Scenario-Based Hands-On Exercises
- Severity Definitions & SLA Matrix
- Baseline Metric Recap
- Renewal Options & Timeline
- Evidence Walkthrough
- Triage Workflow & Escalation Paths
- Enhancement Request Prioritization
- Access Controls & FERPA Verification
- KPI Definitions & Targets
- Enhancement Intake & Prioritization
- Cost Estimates & Funding Alignment
- Training Materials & Train-the-Trainer Plan
- Health Report Template & Frequency
- Usability Verification
- Roles, Owners & escalation
- Audit, Evidence & FERPA Handling in Channel
- Compliance & Forensics Path
- Decision Calendar & Owners
- Scheduling & Academic Calendar Alignment
- Open Items, Remediation Plan & Timelines
- Onboarding & Runbook Distribution
- First Review Agenda & Pre-work
- Formal Sign-off & Next Steps