Operational fit — integrations, retention, and usability

• Which of the following integrations do you need the new camera system to support? Options: Lockdown / building control integration, Mass notification / incident alert, Access control, Visitor management, Law enforcement evidence access portal, None required, Unsure — need seller to assess
• Do you have specific video retention or evidence-preservation requirements we should meet (state-mandated days, grant conditions, FERPA constraints)? Options: Yes — I will specify retention days and constraints next, No specific retention requirement, Unsure — need seller to review
• Please list any minimum camera or VMS requirements that would be non-starters for you (for example: resolution, low-light performance, simple UI for non-technical staff).

Budget

• Is there an allocated budget or identified funding source for this project, and which range best fits? Options: < $100,000, $100,000–$499,999, $500,000–$1,499,999, $1,500,000 or more (may require enterprise procurement), No allocated budget yet — funding planned, Unsure
• What is the primary funding source for this initiative? Options: Local capital budget, Safety bond or levy, Federal or state grant, Operating budget, Combination of above, Other (please specify)

Authority

• Who is the primary decision-maker for approving a surveillance solution, and which roles must also sign off (procurement, superintendent, board, law enforcement)?

Timeline and preferred installation windows

• What is your target 'live by' date or key deadline driving the timeline for this project? Options: Before the next school year, Within 3 months, 3–6 months, 6–12 months, No firm deadline / ongoing, Driven by grant or bond closing date (specify)
• Which installation windows work best for your campuses? Options: Summer break (preferred), Winter break, Spring break, Weekends and evenings only, Phased during term with careful scheduling, No restrictions / any time, Other (please specify)

Unpacking Your Campus Picture

• Tell me briefly about the campuses this project would cover, number of sites, building types, and approximate daily population.
• Describe your current camera inventory and which models remain in regular use across buildings and exterior areas.
• Walk me through the last time you needed footage for an investigation—who asked, how you located the clips, and what failed in that process.
• List the building types or zones you already consider highest priority for coverage (for example main entrances, bus loading, gyms, portable classrooms). Options: Main entrances, Bus loading/unloading, Hallways and common areas, Gyms and auditoriums, Parking lots, Portable classrooms, Other
• Who on your district or campus staff holds final sign-off for security scope, camera placement, and retention policies? Options: Safety director, Chief of campus police, Facilities director, IT director, Procurement officer, School board representative, Other
• How many separate VMS or recording systems are currently active across your sites? Options: One unified system, 2–3 systems, 4–6 systems, More than 6, Unsure

Where the Cameras Fail When It Matters

• Which single camera gap or site risk would make you pause or cancel this entire project? Options: Main entrance coverage missing, Bus loading area blind spot, Gym/athletic facility low-light failure, Network or PoE capacity constraints, Policy/legal restriction on sharing footage, Other
• Give a specific incident in the last two years where a blind spot changed the outcome, and describe what you wish you had captured.
• When lighting, weather, or mounting reduced image value, which locations were worst affected and how often does that happen? Options: Daily, Weekly, Monthly, Rarely, Not applicable
• What's the most common technical reason footage is unusable in investigations, compression or bitrate limits, improper angles, incorrect frame rate, or missing recordings? Options: Compression/bitrate, Camera angle/placement, Incorrect frame rate or settings, Recording not enabled, Storage corruption, Other
• If one immediate fix could remove the largest site risk, which fix would change your board or grant decision fastest? Options: Add cameras at entrances and bus zones, Upgrade low-light cameras in gyms and parking, Consolidate VMS for unified access, Increase retention to meet evidence rules, Network upgrades for HD streams, Other

How Incidents Flow Today

• When a serious incident occurs, where does footage discovery get delayed most, and who feels that pain first?
• Who currently handles evidence exports, audit logging, and chain-of-custody, and can that role grant law enforcement access quickly? Options: Campus police, District safety team, IT/Network team, Records/legal team, Third-party vendor, Other
• Outline any FERPA, district legal, or union steps that routinely slow down sharing footage, including approvals and typical timelines.
• How long does a typical request for recorded footage take from incident to delivery today? Options: Under 1 hour, 1–6 hours, 6–24 hours, 1–3 days, More than 3 days
• Is there any legal, union, or board-level restriction that would stop you from providing live feeds to first responders within 15 minutes? Options: Yes — legal/privacy, Yes — union/staff policy, Yes — board procurement, No, Unsure

The Other Options You're Considering

• If you decided to keep your current supplier or build internally, what exact change would they need to show to keep your business?
• Which external vendors, integrators, or internal teams are you actively evaluating right now for camera, VMS, or analytics work? Options: Current incumbent, Local integrator, National integrator, Internal facilities/IT, Grant-funded alternative, Other
• What would have to be true about your existing system for you to decide to stay with it instead of changing vendors or partners?
• Has anyone on staff proposed solving coverage or retention gaps without an outside vendor, for example by reallocating internal IT or facilities resources? Options: Yes, internal plan in progress, Yes, suggested but no plan, No, not proposed, Unsure
• What single cost threshold, timeline, or compliance condition would immediately rule out the DIY option or keeping the incumbent? Options: Cost above available grant/budget, Timeline beyond next academic year, Inability to meet retention/compliance, Cannot integrate with lockdown systems, Other

Practical Roadblocks That Kill Timelines

• Which integration or infrastructure gap would prevent us from delivering on your schedule? Options: No API for access control, Network bandwidth too low, Power or PoE shortages, Procurement/contract limits, No physical site access windows, Other
• List the third-party systems that must connect to video for this project, for example access control, mass notification, or visitor management. Options: Access control, Mass notification/lockdown, Visitor management, Student information system, Law enforcement evidence portal, Other
• Name the team or person who owns APIs, network credentials, and VLAN changes, and indicate whether they have capacity for this work during the requested timeline. Options: IT director, Network engineer, Facilities manager, Third-party integrator, No owner identified, Unsure
• How ready is your network for persistent high-definition streams, including uplink capacity, switch PoE budget, and segmented VMS traffic? Options: Fully ready, Minor upgrades needed, Major upgrades needed, Not sure
• Are there existing vendor, lease, or procurement agreements that legally restrict installing new cameras or sending recordings to cloud storage? Options: Yes, restricts hardware/vendor, Yes, restricts cloud storage, No restrictions, Unsure — needs legal review

What Success Looks Like in a School Day

• If this system prevented a single serious safety incident next year, what would change operationally and politically for your district?
• Name the measurable signals that will tell you the system is delivering value, for example faster evidence retrieval, reduction in blind spots, or faster first responder access. Options: Time to locate footage, Number of blind spots reduced, Time to grant external access, Parent/community sentiment, Incident response time, Other
• How often would you want system health checks aligned to the academic calendar to prevent outages during the school year? Options: Quarterly, Biannually, Before each semester, Annually, On demand after incidents
• Identify the primary day-to-day users of the VMS and describe their typical technical experience level, for example non-technical safety staff or IT administrators. Options: Non-technical safety staff, Campus police with moderate IT skills, IT administrators, Third-party monitoring, Mixed users
• Assuming a short pilot shows coverage and retention meet your stated needs, what internal approvals would be required to proceed to contract signature and how long do those approvals typically take? Options: Procurement only (2–4 weeks), Procurement + board approval (4–12 weeks), Legal review required (2–6 weeks), Multiple committee approvals (timing varies), Unsure

Acceptance, Approvals, and Next Steps

• What single scheduling or approval constraint would force you to delay installation past the next academic term? Options: Board approval timing, Bond/grant timeline, Union/HR restrictions, Major network upgrades required, Construction/permits, Other
• Provide a short checklist of the documentation and evidence your procurement office and school board require to approve this purchase. Options: Scope of work and drawings, Total cost estimate and O&M, Compliance and retention plan, Integration/API statements, Pilot results or demo, Other
• How quickly could your district make a final decision once acceptance criteria and a pilot are satisfied, measured in days or weeks? Options: Immediately (days), 2–4 weeks, 4–8 weeks, More than 8 weeks, Unsure
• Identify the people who must be present or consulted at the final mutual-commit meeting to sign off on service levels, acceptance criteria, and ongoing support responsibilities. Options: Safety director, Chief of campus police, Facilities director, IT director, Procurement officer, Legal/records representative, Other
• Assuming a four-hour response SLA during school hours and quarterly health checks are included in the agreement, what remaining concerns would still keep you from proceeding?

• Solution Experience, Campus Scenarios

• Confirm the current state and its cost to your team
• You confirm the demonstrated scenarios remove the access delays and evidence gaps that currently prolong investigations.
• Deliver a camera-by-zone proposal for the validated scenarios, including recommended camera types for low-light and wide-area coverage and mounting considerations.
• Scenario A: Main entrance and bus loading lockdown flow
• You confirm the retention and access controls shown meet your state evidence obligations and FERPA constraints.
• Provide the top three priority campus scenarios or incident reports to use in the next proof session.
• Scenario B: Playground and portable classroom incident
• Share copies of any applicable state retention rules and evidence-preservation requirements for review.
• You agree on a deployment window approach that fits the academic calendar and provides verification checkpoints.
• Schedule a follow-up technical configuration workshop during the next school break window.
• Retention and access-control proof
• Deployment sequencing around the academic calendar
• Validate the future state

• Solution Experience — Campus Scenarios
• Solution Experience Deck — Campus Scenarios
• Solution Brief — Campus Scenarios

• meeting
• slides
• document

• Install Outdoor High-Definition Perimeter Cameras
• Install Indoor Hallway and Common-Area Cameras
• Install Bus Loading Zone and Transportation Cameras
• Install Athletic Facility and Low-Light Gym Cameras
• Configure Video Management System and Zone Grouping
• Integrate Cameras with Lockdown and Mass Notification
• Configure FERPA-Compliant Access Controls and Audit Logs
• Provision Storage Architecture with Retention Lifecycle
• Onboard Existing Cameras and Devices to the Platform
• Deploy Video Analytics: Loitering and Occupancy Detection
• Deploy Video Analytics: Bus Arrival and Departure Verification
• Perform Firmware Management and Continuous Health Monitoring
• Provide Four-Hour Response SLA During School Hours

Install Outdoor High-Definition Perimeter Cameras

• How many exterior perimeter cameras do you require per building or lot (provide counts by building name or lot ID)?
• Which buildings or exterior zones must meet a minimum resolution for license-plate or face capture (e.g., main entrance, bus loop, north parking)? Options: Main entrance, Bus loop, Parking lot, Perimeter fence, Other
• Do you have existing camera mounting locations and conduits documented on a single-line diagram (SLD) for each exterior building? Options: Yes, SLDs attached, Partial documentation, No SLDs available
• Please list any required environmental or vandal-resistant ratings for outdoor cameras (e.g., IP rating, IK rating, heated enclosures).
• Describe the expected exterior lighting conditions for the listed zones (e.g., measured lux in parking lot at night, presence of sodium vapor lighting).
• Specify the verification evidence you will accept to confirm outdoor camera coverage meets acceptance (for example: coverage map signed by district safety director, 30-second night-vision clips showing license-plate legibility). Options: Signed coverage map, Sample daytime footage, Sample nighttime footage, All of the above

Install Indoor Hallway and Common-Area Cameras

• Which interior spaces require camera installations and how many cameras for each named space (hallway A, cafeteria, main office, portable cluster)?
• Do any indoor zones require specific mounting heights or tamper-resistant housings (for example: lower hallway vs. high-ceiling auditorium)? Options: Yes, tamper-resistant required, Yes, ceiling-mounted only, No special mounting
• Who will be responsible for unlocking interior spaces during installation windows and providing keys or access codes for the installation team?
• When are acceptable installation windows for interior work relative to the academic calendar (during school day, after-hours, summer break)? Options: During school hours, After school hours, Weekends, Summer break only, Mixed schedule
• Please list any interior privacy constraints tied to student privacy or choir/gym activities that will affect camera field-of-view.
• Identify any local policy or state mandate that defines minimum coverage for interior zones (for example a state requirement for main entrance and cafeteria retention).

Install Bus Loading Zone and Transportation Cameras

• Estimate the number of bus loading/unloading points and the expected daily bus movements for each named stop. Options: Less than 10 movements/day, 10-50 movements/day, More than 50 movements/day, Provide counts
• Which bus-stop zones must capture both boarding and curbside license plates versus general area monitoring? Options: Boarding/curbside plate capture, General area monitoring only, Both
• Are there preferred mounting locations for bus-zone cameras (light pole, canopy, building fascia) for each named stop? Options: Light pole, Canopy, Building fascia, Other
• Describe power availability at each bus zone (PoE from nearby switch, separate power drop, battery-backed feed). Options: PoE available, Power drop required, Battery/solar solution required, Unknown
• Please list any required integration with the transportation routing system or bus GPS feed to correlate arrival timestamps.
• Are video clips from bus zones required to be exported to law enforcement within a specified time window after an incident? If yes, specify the timeframe. Options: Yes - within 1 hour, Yes - within 24 hours, No specified timeframe

Install Athletic Facility and Low-Light Gym Cameras

• Which athletic facilities and gymnasiums require low-light optimized cameras and how many cameras per named facility?
• What minimum lux performance or low-light specification do you require for gym cameras to capture clear facial detail during evening events? Options: <1 lux, <0.1 lux, No specific lux requirement
• Describe any audio capture restrictions or policies for athletic facilities that will affect installation. Options: Audio permitted, Audio not permitted, Audio only with signage
• Identify mounting surfaces and ceiling heights for each gym to determine required camera enclosures and lens types.
• Do you require event-mode recording (higher frame rate during games) tied to facility scheduling systems? If yes, name the scheduling system. Options: Yes, tie to scheduling system, No event-mode recording, Manual trigger only
• Are there acoustical or reflective lighting conditions (scoreboard LEDs, court lights) that we should account for when specifying cameras? Options: Yes, detailed in attached lighting survey, No special conditions

Configure Video Management System and Zone Grouping

• Which logical building and zone groupings do you want reflected in the VMS (by campus, by building, by floor, by classroom cluster)? Options: Campus, Building, Floor, Classroom cluster, Custom
• What is the maximum simultaneous live-view count needed for your safety operations center during an incident? Options: 4, 8, 16, 32+
• What playback performance acceptance criteria must the VMS meet (for example: 30 fps 1080p playback for a 24-hour window within 10 seconds of clip request)? Options: 30 fps 1080p within 10 seconds, Real-time playback only, Custom performance target
• Which named user groups require pre-configured camera layouts or bookmarks (for example: campus police, superintendent office, transportation dispatcher)?
• Do you require role-based dashboards that surface alerts by zone (for example: bus loop alerts to transportation dispatcher)? Options: Yes, No
• Identify any third-party integrations the VMS must support out of the box (for example: existing access control system API endpoint or mass notification connector).

Integrate Cameras with Lockdown and Mass Notification

• Which lockdown or mass notification endpoints must receive camera links or live feeds (provide endpoint type and owner contact)?
• How should live camera feeds be exposed during a lockdown (automatic pop-to-top for specific user role, tokenized URL, pinned layouts)? Options: Automatic pop-to-top, Tokenized URL, Pinned layout, Manual access only
• Who will authorize the connection between the VMS and the mass notification system and provide required API credentials?
• Provide the expected maximum concurrent requests from the mass notification system to the VMS during a campus-wide incident. Options: 1-5, 6-20, 21-50, 50+
• Are there existing incident-response playbooks we must align to when enabling camera access for responding law enforcement? Options: Yes, playbook attached, No playbook, Playbook under revision
• Specify any data retention or export constraints imposed when sharing footage with external law enforcement partners.

Configure FERPA-Compliant Access Controls and Audit Logs

• Which user roles require FERPA-restricted access and how should access be granted (time-limited, case-by-case, role-based)? Options: Role-based, Time-limited, Case-by-case, Other
• What audit log retention period do you need to meet district FERPA policy or state evidence rules (specify days)? Options: 90 days, 1 year, State-mandated period, Custom
• Who are the designated approvers for release of footage involving minors and what document will they sign to authorize release?
• Are there existing identity providers (for example SAML/LDAP) you want integrated for single sign-on to enforce access controls? Options: SAML, LDAP, Azure AD, None, Other
• Is forensic-level audit logging required for all access to recordings or only for releases to external parties? Options: All access, Releases to external parties only, Custom
• Identify any state-specific student privacy statutes that create additional access controls beyond FERPA.

Provision Storage Architecture with Retention Lifecycle

• State the retention period required by your district or state for standard camera footage in named zones (in days). Options: 30 days, 60 days, 90 days, 365 days, Custom
• Which storage architecture do you prefer for long-term retention (on-premises NVR/recorders, hybrid cloud archive, full cloud storage)? Options: On-premises NVR, Hybrid cloud, Full cloud, Undecided
• What is the minimum acceptable system behavior for retrieval of archived footage when requested by law enforcement (for example: retrieval within 12 hours)? Options: Within 1 hour, Within 12 hours, Within 24 hours, Within 72 hours
• Define the performance acceptance criteria for storage and lifecycle enforcement (for example: automated deletion of expired footage within 24 hours of retention expiry). Options: Auto-delete within 24 hours, Auto-archive then manual delete, Manual retention management
• Confirm expected average daily video ingest in GB per campus or building to size retention (provide estimates if known).
• Indicate any legal hold or evidence preservation workflows that must suspend normal lifecycle rules for specific incidents. Options: Yes - legal hold required, No legal hold, Legal hold on request

Onboard Existing Cameras and Devices to the Platform

• How many existing cameras and devices do you plan to onboard, listed by building and model where known? Options: Less than 50, 50-200, 200-500, 500+
• Identify existing camera firmware versions and whether firmware upgrades are permitted during onboarding windows. Options: Upgrades permitted, No upgrades during school term, Upgrades only during break
• Are there proprietary cameras that require on-site adapter hardware or configuration before onboarding? Options: Yes, adapters required, No, Unknown
• What percentage of existing cameras must be validated as operational at handoff for the onboarding to be considered complete (for example: 95% online and streaming)? Options: 90%, 95%, 99%
• Provide the inventory artifacts you can share for onboarding (network map, device list, IP addresses, default credentials).
• List any existing NVRs or VMS instances that must remain in parallel during migration and the expected coexistence duration.

Deploy Video Analytics: Loitering and Occupancy Detection

• Which named zones require loitering detection and what time thresholds define loitering for each (for example: >5 minutes in playground after hours)?
• Describe the occupancy detection outputs you need (headcount per room, percent occupancy, alert when over threshold) and the reporting cadence. Options: Headcount, Percent occupancy, Threshold alerts, Scheduled reports
• What false-positive tolerance do you accept for analytics in high-traffic school areas (for example: under 10% false alarms per day)? Options: <5%, <10%, <20%, No specific tolerance
• Are analytics rules required to change during school events or after-hours, and how should rule sets be scheduled around the academic calendar? Options: Scheduled by calendar, Manual switching, Event-triggered
• Describe any privacy-preserving requirements for analytics (for example: count-only, no face analytics) in classroom or locker-room adjacent zones. Options: Count-only, No face analytics, Full analytics permitted with controls
• Specify the integration endpoints or reporting receivers for analytics alerts (for example: campus safety dashboard, mass notification endpoint).

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Order Form (Product and Subscription)
• Service Level Agreement (SLA)
• Deployment Acceptance Test Plan
• Warranty & Workmanship Guarantee
• Change Order Agreement
• Payment Schedule & Funding Confirmation
• Public Procurement & Student Privacy Addendum (conditional)
• Escrow, Credentials & Integration Handover

• Go-live health check
• First measurement review
• Acceptance gate and incumbent wind-down
• Quarterly health check aligned to academic calendar

• Update the shared issue channel with owners and target dates for high-priority backlog items and close low-priority items.
• Schedule the acceptance gate meeting and circulate its checklist drawn from the Solution Scope.
• Restate acceptance criteria from the Solution Scope
• Produce a documented acceptance decision against each numeric criterion recorded in the Solution Scope with a named signatory for the buyer.
• Confirm the incumbent system is decommissioned or retained read-only and that data archiving or migration is complete with a closure date.
• Agree remediation tasks and retest dates for any unmet criteria so there is a clear path to full acceptance.
• Publish the acceptance decision document with the named signatory and store it next to the Solution Scope records.
• Execute and report the incumbent decommission or archive steps and provide confirmation of read-only access where applicable.
• Track and close remediation items with evidence for each conditional criterion and set re-test appointments.
• Quarterly KPI dashboard review
• Validate that uptime and incident footage SLA performance meet the Solution Scope targets or document required operational changes.
• Keep the enhancement and issue backlog short and schedule maintenance during school breaks to avoid instructional disruption.
• Confirm the shared channel owner and cadence for tracking open issues and enhancements between reviews.
• Publish the quarterly health report with KPI trends, open issues, and scheduled maintenance windows.
• Schedule firmware and major configuration updates for the next academic break and document rollback steps.
• Reconfirm Solution Scope acceptance criteria and owners
• Confirm the deployment items mapped in the Solution Scope are present and operational or documented as open issues.
• Agree a prioritized remediation plan with deadlines for any showstoppers preventing normal operations.
• Confirm named owners for user onboarding and incident retrieval readiness.
• Publish the go-live remediation log with item descriptions, priority, and resolution target dates.
• Schedule immediate fixes for any cameras offline or mis-positioned and verify recording continuity after fixes are applied.
• Confirm user account list and reset any access problems preventing live or recorded viewing.
• Present first-period metric set against Solution Scope targets
• Establish whether coverage, retrieval time, and retention are trending toward the Solution Scope targets and quantify any shortfalls.
• Identify root cause for each shortfall and agree corrective tasks with resolution dates to reach the acceptance gate.
• Confirm timeline and checklist items required for the acceptance gate meeting.
• Deliver the metric export and evidence pack used in the meeting for asynchronous review.
• Execute prioritized remediation tasks such as camera repositioning, network QoS adjustments, or VMS config changes and report completion dates.
• Present outcome data versus each criterion
• Incident and ticket summary
• Deployment validation checklist
• Root-cause analysis for any metric gaps
• Document pass or fail per criterion and capture the formal acceptance decision
• User access and onboarding verification
• Enhancements and open issues backlog
• Access and security review
• Early operational signals
• Agree corrective actions and timeline to acceptance gate
• Maintenance window and firmware planning
• Incumbent system wind-down or retention plan
• Open issues, blockers, and immediate remediation plan
• Agree remediation closure plan for any conditional passes
• Agree next quarter checkpoints