Health, Education & Government
›
K-12 Education
›
Campus Safety & Security
School Safety Planning
Technology and operations decisions where district leadership, IT, and stakeholders must align.
Example organizations in this space:
Raptor Technologies
Navigate360
Kroll
SAFE4SCHOOLS
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify, diagnose, and collect on-the-ground data to shape scope and outcomes.
-
District Safety Discovery
Align district leadership on safety objectives, constraints, stakeholders, and measurable success signals.
Discovery Questions
Starting Point: Your District's Safety Snapshot
- Tell me briefly how your district currently organizes and maintains emergency plans across schools and sites.
- Which description fits where your emergency plans are primarily stored today?
- How many physical sites and campuses does your district operate, and which of the following school types are included?
- Tell me about the most recent district-level drill or exercise you ran and what the immediate outcome was.
- Who on your staff currently owns plan updates and who is the escalation contact during an actual incident?
Where the Current System Breaks Down
- If an incident happened at one of your schools tomorrow, which single failure in your current setup would worry you most?
- Describe the kinds of confusion staff or substitutes most commonly report when a drill or event starts.
- What parts of your current plans or tools most often require manual workarounds during a response?
- How long does it usually take someone unfamiliar with a building to find the right response procedure, on average?
- Which specific school sites, functions, or roles create recurring exceptions that the central plan does not cover?
The Risks That Keep You Up at Night
- Could any single site condition or unresolved legal or access issue stop a safety program from moving forward for your district?
- Share a recent example where preparation or lack of preparation materially changed how an event was managed in your district.
- When you look at state requirements for plans and drills, which documentation or reporting obligation worries you most if left incomplete?
- Name the person or role who would be responsible for resolving the single biggest blocker you just identified, and how quickly they could act.
- Do any past incidents or near misses change how you view the timeline or scope for improving district preparedness?
The Other Paths You Are Considering
- Who else or what options are you actively evaluating to meet your district safety planning, training, or platform needs?
- Name any incumbent vendor or an internal approach you think could meet your goals without bringing in an external partner.
- What would have to be true about the current vendor or internal option for you to decide to keep them rather than change partners?
- Do internal stakeholders favor a do-it-yourself approach, and who is advocating for that path?
- Estimate the earliest realistic date your district could approve and start a pilot if cost, scope, and acceptance criteria matched your needs.
What Success Actually Looks Like in Practice
- Explain the single measurable change you would accept as proof the program is working within the first 12 months.
- Where would those improvements need to appear first, for you to declare the pilot a success?
- Rate the relative importance of the following success metrics for your district.
- List any quantitative targets you currently have, for example drill completion percentage, plan retrieval time, or training hours per staff member.
- In your view, which outcome would make the board or superintendent sign off quickly after a successful pilot?
Operational Readiness and Constraints
- If we needed to integrate with your student information system, security badge system, or rostering feed, are those APIs or export endpoints available today?
- Describe the district staff bandwidth available to support configuration, training, and data handoff during a typical deployment window.
- When it comes to site access, background checks, or insurance requirements for consultants, how long does approval usually take?
- Estimate whether your district has consolidated contact lists, floor plans, and response role assignments in a way that can be shared during onboarding.
- Could any of these readiness gaps stop deployment on the timeline you want, and which one would be the blocker?
People, Influence, and Decision Paths
- Share who the core decision makers are for safety strategy, budget approval, and vendor selection on your side.
- Where do school leaders and the school board sit in the approval sequence for changes to safety plans and vendor agreements?
- Are there council, union, or community approvals that typically extend timelines for safety program changes?
- Explain the factors that would make your superintendent or board sign a pilot after seeing pilot results.
- Rate how decisive your district tends to be once a pilot meets its stated acceptance criteria.
Early Indicators, Commitment Signals, and Next Steps
- Could a focused pilot that reduces plan retrieval time and improves drill completion convince your district to move to a full rollout?
- List the minimal acceptance criteria you would require for a pilot to be considered successful.
- Are there budget cycles, board meeting dates, or legislative deadlines we should align a pilot and contract decision with?
- In the event a pilot proves the expected gains, who has final authority to sign the district up for an expanded engagement?
- Identify the single next action that would accelerate this conversation on your side, for example an on-site survey, a cost outline, or a short demo.
-
Assessment Workshops
Conduct site surveys, stakeholder interviews, and tabletop scenarios to gather evidence and verify training and planning needs.
Working Meetings
- Assessment Workshops Kickoff and Scope Decision
- Site Survey, Elementary School (On-site)
- Site Survey, Middle School (On-site)
- Site Survey, High School (On-site)
- Stakeholder Interviews, District Leadership and First Responders
- Tabletop Exercise, Scenario Validation and Training Needs Decision
- Assessment Consolidation and Scope Recommendation Decision
- Document any requested modifications and circulate an updated scope for final confirmation.
- High school site survey completed with a ranked risk list and event-specific concerns noted.
- List of required plan updates and training needs for event and after-hours scenarios.
- Decision on whether a functional exercise at the high school is recommended following the assessment.
- Upload the high school site survey report, annotated photos, and event risk notes.
- Collect copies of event schedules and guest access policies for planning purposes.
- Identify staff or volunteer roles that require immediate briefing or quick training.
- Review high-level findings from site surveys
- Validated roles and notification chains documented in a roles and responsibilities matrix.
- List of mandatory compliance items and reporting requirements confirmed for planning scope.
- Agreed constraints and training cadence that will shape recommended deliverables.
- Finalize and upload the roles and responsibilities matrix derived from interviews.
- Request incident logs, recent drill documentation, and any policy documents needed for the final assessment.
- Document first responder contact list and mutual aid agreements referenced during the interview.
- Scenario briefing and scope
- Validated list of capability gaps and failure modes tied to observable actions in the tabletop.
- Prioritized training and exercise plan with measurable objectives and recommended sequencing.
- Decision on whether a functional exercise is required for one or more scenarios.
- Publish the tabletop exercise report with gap list, evidence, and recommended training modules.
- Produce a prioritized training schedule with measurable objectives and success criteria for each module.
- If required, draft the scope and logistics for any recommended functional exercise.
- Executive summary of consolidated findings
- Client decision to accept the recommended scope of work or provide a documented list of required changes.
- Signed set of measurable acceptance criteria and draft timeline for the Solution Experience stage.
- Clear next steps documented for transition to contracting and deployment planning if scope is accepted.
- Publish the consolidated assessment report and recommended scope with acceptance criteria to the shared workspace.
- Draft the statement of work and timeline for the Solution Experience stage based on the accepted scope.
- Confirm assessment objectives and success signals
- Approved list of sites, scenarios, and per-site focus areas to be assessed.
- Finalized stakeholder interview roster and interview guide for field teams.
- Agreed logistics, data needs, and delivery timeline for assessment artifacts.
- Distribute the finalized site schedule and stakeholder interview guide.
- Collect and upload site floor plans, existing emergency plans, and recent drill records for each site.
- Confirm point of contact and site access procedures for each scheduled survey.
- Confirm scope and safety protocols for the visit
- Completed site survey checklist with photographic notes for the elementary site.
- Ranked list of high, medium, and low risks per the observed conditions.
- Initial list of site-specific training and planning needs to be validated later.
- Upload the elementary site survey report, annotated photos, and raw checklist data to the shared workspace.
- Collect electronic copies of the site floor plan and any existing emergency plan documents observed during the visit.
- Schedule a short follow-up interview with the site leader to validate observations if any items were ambiguous.
- Review survey plan and documentation needs
- Middle school site survey checklist completed with annotated observations.
- Documented communications and technical gaps that affect incident response.
- Preliminary list of training modules and exercise needs informed by the middle school patterns.
- Upload the middle school site survey report, photos, and communication capability notes.
- Request building access diagrams and recent maintenance or construction records that affect exits or egress.
- Prepare targeted interview questions for school staff based on observed gaps.
- Confirm high school survey focus areas
- Campus flow and common areas walkthrough
- Present recommended scope of deliverables
- Play the scenario with timed injects
- Confirm roles, notification chains, and mutual aid expectations
- Large venue and perimeter inspection
- Exterior and perimeter walkthrough
- Finalize site list and per-site focus
- Surface regulatory, board, and state requirements
- Internal building review and shelter spaces
- Approve stakeholder interview roster and interview guide
- Identify capability gaps and failure modes
-
-
Solution Experience
Walk through how integrated planning, training, exercises, and the digital plan platform deliver district safety outcomes using the buyer's scenarios.
Solution Experience
- Solution Experience: District Safety Scenarios
- Confirm the current state and its cost
- You confirm the current state statement and its operational cost is accurate.
- Deliver a 1-page annotated scenario replay summarizing timing, decision points changed, and evidence captured within 3 business days.
- Run your prioritized scenario end-to-end
- You confirm the demonstrated scenario eliminates the key failures you described, including response delays and role confusion.
- Provide the final list of priority scenarios, pilot site roster, and on-site point of contact for drills.
- Walkthrough school-by-school roles and access during the scenario
- Draft a school-by-school module with roles, checklists, and measurable acceptance criteria for the pilot and share before pilot kickoff.
- You agree on the acceptance criteria, pilot metrics, and the evidence needed to recommend approval.
- Confirm pilot dates and any required site access or permissions for functional exercises.
- Show drill automation and compliance evidence
- Validate the future state explicitly
- Agree remaining evidence and next milestones
- Solution Experience: District Safety Scenarios
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define deliverables, school-by-school modules, roles, timelines, and measurable acceptance criteria for plans, drills, and platform features.
Scope Configuration
- Deliver FEMA-compliant Emergency Operations Plan
- Create School-Specific Annexes and Checklists
- Develop Standard Response Protocols
- Migrate Existing Plans into Digital Platform
- Deploy Mobile Plan Access for Staff
- Configure Real-Time Plan Activation and Alerts
- Configure Automated Drill Documentation and Compliance Reporting
- Facilitate District Leadership Tabletop Exercise
- Facilitate School-Level Functional Exercise
- Deliver Role-Based Staff Emergency Response Training
- Deliver Student Age-Appropriate Safety Trainings
- Provide Incident Playbooks for Key Scenarios
- Integrate Multi-Agency Incident Communication Templates
Scope Questions
Deliver FEMA-compliant Emergency Operations Plan
- Do you have an existing district emergency operations plan (EOP) or state template that we must align to?
- Identify the specific state model EOP or statute citation the plan must satisfy (enter name or citation)
- List the number of instructional sites, administrative buildings, and alternative sites to include in the district EOP
- Specify the acceptance criteria that will confirm the EOP meets FEMA and state requirements (for example: 100% checklist compliance, signed legal review, superintendent sign-off)
- Select which functional annexes must be included in the district EOP
- Name the district role who will own EOP maintenance and annual reviews (title or department)
Create School-Specific Annexes and Checklists
- Provide the count of schools that require unique school-level annexes versus those using a templated annex
- Describe which school artifacts should be captured per annex (for example: floor plans, key personnel roster, student reunification roster, utility shutoff locations)
- Indicate whether site floor plans and single-line diagrams (SLD) are available for each school and in what format
- State the threshold for annex completeness that you will accept (for example: all emergency contacts listed, 1:1 mapping of exits on floor plan, reunification site designated)
- Identify any school-specific constraints we must design around (for example: shared campus with district offices, leased facility limitations, co-located early childhood center)
- Who is the on-site point person (title) at each school who can validate the annex details during site work?
Develop Standard Response Protocols
- Identify which standard response protocols you require standardized across the district (examples: lockdown, hold-in-place, evacuation, shelter, reunification)
- Explain any local law enforcement or school resource officer (SRO) procedures that must be reflected in the protocols
- Indicate whether your district uses standard alert language or codes that the protocols must incorporate (for example: code words, PA scripts)
- Provide the target time-to-action expectations for staff during each protocol (for example: lockdown initiated within 60 seconds of threat recognition)
- Identify which operational artifacts should accompany each protocol (for example: PA scripts, classroom checklist, custodial shutdown checklist, bus evacuation checklist)
- Who will approve the finalized district protocols for publication to staff (title)
Migrate Existing Plans into Digital Platform
- How many total plan documents and attachments (PDFs, images, CAD files) are expected to be migrated into the platform?
- List the current storage locations for your plans (for example: shared network drive, state portal, legacy plan binder scans)
- Indicate the minimum migration success criteria you will accept (for example: percentage of schools with searchable plans and floor plans annotated)
- Describe any PHI/PII or student roster data embedded in plans that will require redaction or special handling during migration
- Specify whether single sign-on (SAML/SSO) or district directory integration will be required for plan access after migration
- Who in your IT team will provide access and approve data extracts for migration (name or title)
Deploy Mobile Plan Access for Staff
- Confirm which staff groups need mobile access to plans (examples: teachers, administrators, bus drivers, nurses)
- Describe device ownership model for staff mobile access (for example: district-issued tablets, BYOD bring-your-own-device, mixture)
- Indicate required offline access behavior for mobile plans (for example: full offline plan, critical checklists only, none)
- State any mobile security controls required (for example: PIN, device encryption, remote wipe capability)
- Identify whether staff training on mobile plan use should be included in deployment
- Who will maintain the mobile user roster and permissions after go-live (title or department)?
Configure Real-Time Plan Activation and Alerts
- Specify which trigger sources should be able to activate a plan (for example: authorized user, emergency call, integration from safety system)
- Indicate the notification channels required for an activation (for example: SMS, mobile push, email, PA integration)
- Provide the list of authorized activators by title who should be allowed to initiate a real-time plan
- Outline the expected activation workflow for staff during a real-time event (for example: alert -> role checklist -> confirmation)
- Indicate any external agency integrations required at activation (for example: county dispatch, regional alerting system)
- Describe the acceptable delay threshold for alert delivery to staff devices during an activation (for example: under 30 seconds)
Configure Automated Drill Documentation and Compliance Reporting
- Identify which state reporting elements must be captured for drills (for example: drill type, date/time, participant counts, outcome rating)
- Estimate the annual number of drills per school that should be automatically logged by the platform
- Describe the evidence artifacts you will accept as proof of drill completion (for example: timestamped device check-ins, photos, after-action report)
- Specify the compliance report format required for state submission (for example: CSV export, PDF summary, direct API push to state portal)
- State the acceptance evidence that will validate drill documentation meets state reporting requirements (for example: automated export accepted by state portal)
- Who will be responsible for reviewing and approving auto-generated drill reports in the district?
Facilitate District Leadership Tabletop Exercise
- Select the leadership roles that should participate in the district-level tabletop (for example: superintendent, safety director, director of operations)
- Describe the scenario focus for the tabletop exercise (for example: active threat, pandemic response, severe weather multi-site impact)
- Provide the desired learning objectives for the tabletop (for example: clarify decision authority, test notification chains, validate mutual aid agreements)
- State any external agency observers or facilitators who must attend (for example: county emergency manager, local law enforcement)
- Indicate the preferred duration and timing for the tabletop (for example: half-day, full-day, remote over two sessions)
- Who will be the district sponsor authorizing the tabletop outcomes and follow-up actions (title)?
Facilitate School-Level Functional Exercise
- Choose the exercise type for school-level drills (for example: full evacuation, shelter-in-place with student accountability, active assailant functional drill)
- Provide the number of schools and grade bands to include in the functional exercises during the engagement period
- Describe any necessary school-day constraints for exercises (for example: no live student movement, limited classroom disruption, after-hours drill)
- List required artifacts to be produced after each functional exercise (for example: after-action report, improvement plan with owners and timelines)
- Identify which school staff roles must participate in the functional exercise (for example: principal, custodian, front office staff, nurse)
- Who will approve school-level exercise logistics and parental notification plans prior to the exercise?
Deliver Role-Based Staff Emergency Response Training
- Identify the staff roles requiring role-specific training (examples: administrators, teachers, custodians, bus drivers, nurses)
- Describe the delivery method desired for role-based training (for example: in-person workshop, virtual instructor-led, micro-learning modules in platform)
- Specify the target competencies for each role training (for example: lockdown checklist mastery for teachers, reunification logistics for office staff)
- State any certification or attendance evidence you require after training (for example: signed roster, quiz pass threshold, issued certificate)
- Provide the preferred training schedule window (for example: within 30 days of plan publication, summer in-service week)
- Who will be the district lead coordinating staff scheduling and training approvals?
-
Mutual Commit
Finalize commercial and legal terms, confirm responsibilities, and lock acceptance criteria, milestones, and payment terms.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Order Form / Subscription Agreement
- Milestone Acceptance & Payment Schedule
- Service Level Agreement (SLA)
- Data Processing Addendum (DPA) — Student & Staff Data
- Public Sector Procurement & Security Rider
- Change Order Agreement
- Confidentiality Agreement (NDA)
- Transition & Offboarding Addendum
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm owners, drill schedules, site access, and operational prerequisites the deployment team must have before work begins.
Pre-Deployment Questions
Environment and site access
- List each district location/site included in this deployment and, for each, confirm whether on‑site access and a local point of contact are available (format: Site name — Access: Yes/No — POC name & role). This lets us create site‑specific readiness tasks.
- Does the district device policy allow installation of the platform app on district‑owned and/or personal devices? (This determines the mobile roll‑out approach.)
Data and integration readiness
- Which district systems will require integration as part of this deployment? Select all that apply (we'll map owners and test needs next).
- Are integration owners and a test/staging environment available for the integrations you selected? (So we can schedule connector work and QA.)
People and ownership
- Who is the district's primary deployment owner (name, role, email) — the single person our team will coordinate schedules, approvals, and escalations with?
- For these four workstreams—site access approvals, drill scheduling, IT/SSO approvals, and final acceptance—provide the named owner (name and role) for each so we can assign tasks without delay.
Timing and constraints
- List any district‑wide or site‑specific blackout windows or compliance constraints that block drills or system changes (e.g., testing calendars, graduations). Include dates and affected sites so we can plan around them.
- Target deployment start date or window (enter a specific date or month/quarter, or write 'Flexible — vendor to propose' / 'Dependent on approvals'). This becomes the baseline for sequencing and milestone dates.
-
Configuration Details
Capture exact configuration values the deployment team will use—integration credentials, mobile access settings, drill automation parameters, and platform options.
Configuration Details
ENVIRONMENTS & ENDPOINTS
- Target deployment environment identifier (enter a single short name the build will use — Default: production)
- Platform base URL for this environment (enter exact URL the deployment will configure; format: https://...) — Default example: https://<subdomain>.platform.example.com
IDENTITY & ACCESS
- SSO authentication method for this environment (choose one)
- SSO identifier — enter the issuer URL or entity ID exactly as in your IdP (format: https://... or urn:... ). Enter identifier only; do NOT paste client secrets.
CREDENTIAL HANDOFF & OWNERSHIP
- Credential delivery method for integration secrets (choose one) — the platform will not accept secrets in the form. Pick how the seller should retrieve secrets at kickoff
- Credential owner (name and role) — person responsible for providing integration secrets via the chosen delivery method (e.g., "Jane Doe, IT Director")
MOBILE ACCESS & DRILL AUTOMATION
- Mobile access model to enable for staff (choose one)
- Drill automation mode to configure for this district (choose one)
-
Deployment
Execute plan development, staff training, functional exercises, and platform rollout with clear owners, sequencing, and checkpoints.
-
-
Success
Validate outcomes against success criteria, operationalize plan maintenance, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Acceptance Gate Review (around day 90)
- Quarterly Success Review
Issues & Enhancements
- Close any identified fallback processes by removing legacy access or documenting official procedures and training refreshes.
- Restate acceptance criteria and targets
- Produce a documented acceptance decision for each numeric criterion recorded in Solution Scope, including pass or fail results.
- Confirm the incumbent system is decommissioned or retained read only and that data archiving or migration is complete.
- Agree a bound remediation plan and date for re-verification of any failed criteria.
- Publish the acceptance record and the evidence files used to validate each criterion.
- Execute the incumbent archive or decommission tasks and produce a handover log confirming access and retention terms.
- Create remediation tickets for any failed criteria with completion dates and re-verification steps.
- Review quarterly metric trends
- Ensure drill completion rate within the scheduled window and percentage of schools with current emergency operations plans on the platform remain at or move toward the targets recorded in Solution Scope.
- Agree a prioritized backlog for enhancement requests and a burn-down plan for open operational issues.
- Confirm the plan maintenance schedule for the next quarter and the verification checkpoints to measure compliance.
- Publish the quarterly metrics report with the backlog status and planned remediation dates.
- Schedule the next quarter's drill calendar and the associated plan review windows.
- Re-confirm success criteria and owners
- Confirm the deployment components and integrations are functioning end to end.
- Document top early issues and immediate remediation tasks with target dates.
- Agree the data collection plan and timeline for the first measurement meeting.
- Publish the deployment validation checklist and current issue log for async tracking.
- Enable diagnostic logging or access needed to investigate the top two technical blockers.
- Collect baseline data sources for the metrics to be reviewed at first measurement.
- Present first measurement data
- Determine whether percentage of schools with current emergency operations plans on the platform and drill completion rate within the scheduled window are trending toward targets recorded in Solution Scope.
- Document 3 specific corrective actions with completion dates that will close the largest gaps.
- Confirm the evidence package and signatory process required for the acceptance gate meeting.
- Publish the metric dashboard extract used for this review and the data sources for each metric.
- Create a remediation task list with target resolution dates for each corrective action agreed in the meeting.
- Schedule the acceptance gate meeting and circulate the evidence expectations documented from Solution Scope.
- Deployment and data migration validation
- Open issues and enhancement request burn-down
- Trend analysis and root-cause diagnosis
- Present outcome data against each criterion
- Agree corrective actions and timelines
- Document pass or fail per criterion and formal acceptance decision
- Operationalize plan maintenance cadence
- Early adoption signals and usage patterns
- Confirm readiness timeline to acceptance gate
- Blockers and open issues triage
- Incumbent system decommissioning and data archive confirmation
- Short check for fallback behaviors
- Agree remediation items and resolution timeline
- Agree immediate remediation actions