HB 3166: Requirements for School Safety Mapping Data - West Virginia

hb3166 s fin am _1 4-2 adopted.htm → hb3166 hfa pinson 3-20 _1 reformed adopted.htm · 7 edits

MODERATE

The bill was reformed to add flexibility in who can update school safety mapping data and to clarify that updates should be possible by data producers, public safety agencies, school safety personnel, or school administration. The original version required strict compliance with public safety software platforms and had specific funding and disclosure provisions that were removed in this reform.

Scope change

The bill's scope was narrowed by removing detailed requirements for data formats, storage locations, funding amounts, and disclosure exemptions that were present in the original version.

REQUIREMENT

Detailed requirements for data formats, open-source compatibility, true north orientation, accuracy verification methods, and specific labeling elements were removed.

Added language allowing data to be updatable by data producers, public safety agencies, school safety personnel, or school administration.

Added requirement for consultation and approval from primary law enforcement agencies before procurement.

FISCAL

The $4,500 per school funding provision was removed.

TIMELINE

The September 1, 2026 effective date was removed.

DEFINITION

The requirement that data be stored exclusively within the United States was removed.

ENFORCEMENT

The exemption from public disclosure under §29B-1-1 et seq. was removed.

Committee Substitute → hb3166 s fin am _1 4-2 adopted.htm · 6 edits

MODERATE

The bill was amended by the Finance Committee to add data security requirements, funding limits, and enforcement mechanisms to school safety mapping provisions. The amendment changes 'may create' to 'shall create' for mandatory compliance, adds a requirement that data be stored exclusively within the United States, establishes a $4,500 per school funding cap, and sets a September 1, 2026 effective date.

Scope change

The bill's scope expanded from optional county board discretion to mandatory compliance with new data security and procurement requirements.

REQUIREMENT

Changed language from 'may create' to 'shall create' making standardized school safety mapping data mandatory for all county boards of education.

Added requirement that all mapping data must be created, stored, and maintained exclusively within the United States for security purposes.

Added requirement for local school systems to obtain approval from primary law enforcement agencies before procuring mapping data.

FISCAL

Established a funding limit of no more than $4,500 per school for county boards to receive for mapping data purposes.

TIMELINE

Set the effective date for school safety mapping requirements to September 1, 2026.

ENFORCEMENT

Added exemption from public disclosure laws for data obtained and maintained under this section.

Enrolled Committee Substitute → Committee Substitute · 5 edits

MODERATE

The bill was converted from an enrolled committee substitute to an introduced version, reverting the language from 'shall create' to 'may create' and removing the mandatory requirement for local law enforcement approval. This changes the bill from a mandatory requirement to an optional capability for county boards, significantly reducing the scope of the legislation.

Scope change

The bill's scope was narrowed from a mandatory requirement for all county boards to create safety mapping data to an optional permission allowing them to do so if they choose.

REQUIREMENT

Changed from mandatory 'shall create' to optional 'may create' for standardized school safety mapping data

Removed the requirement for local school systems to consult and receive approval from primary law enforcement agencies before procurement

FISCAL

Removed the specific funding provision of up to $4500 per school for mapping data creation

TIMELINE

Removed the specific effective date of September 1, 2026

ENFORCEMENT

Removed the provision exempting mapping data from Freedom of Information Act disclosure requirements

Engrossed Committee Substitute → Enrolled Committee Substitute · 7 edits · Apr 29, 2025

MODERATE

The bill was converted from a committee substitute to an enrolled final version, adding several new substantive provisions. The most significant changes include a new requirement for data to be stored exclusively within the United States, a new provision requiring consultation with local law enforcement before procurement, a specific funding cap of $4500 per school, a new effective date of September 1, 2026, and an exemption from Freedom of Information Act disclosure. The language also shifted from 'may create' to 'shall create,' making the requirement mandatory rather than optional.

Scope change

The bill's scope expanded to include mandatory consultation with law enforcement agencies and new data security requirements regarding geographic storage location.

REQUIREMENT

New requirement that mapping data must be created, stored, and maintained exclusively within the United States for security purposes.

New provision requiring local school systems to consult with and receive approval from primary law enforcement agencies before procuring mapping data.

Language changed from 'may create' to 'shall create,' making the requirement for standardized mapping data mandatory rather than optional.

Updated coordinate system language from 'x and y coordinates' to 'fixed grid with consistent x and y coordinates' for greater clarity.

FISCAL

New funding provision allowing county boards to receive up to $4500 per school for mapping data purposes, subject to available funding.

TIMELINE

New effective date set for September 1, 2026.

ENFORCEMENT

New exemption from Freedom of Information Act disclosure for mapping data obtained under this section.

Introduced Version → Engrossed Committee Substitute · 5 edits · Apr 12, 2025

MODERATE

HB 3166 was amended to change a mandatory requirement into a permissive option for county school boards, and added new requirements for data verification and future updates. The bill now allows rather than requires schools to create standardized safety maps, while also expanding who must verify the data's accuracy and ensuring maps can be updated as needed. This change gives local districts more flexibility in implementing safety mapping while maintaining core safety standards.

Scope change

Changed from a mandatory requirement for all county boards to create standardized safety mapping data to a permissive option allowing county boards to create such data.

REQUIREMENT

Changed 'shall establish' to 'may create' making standardized school safety mapping data optional rather than mandatory for county boards of education.

Added requirement that data accuracy must be verified by multiple parties including relevant public safety agencies, school safety personnel, or school administration through on-site walk-throughs.

Added requirement that future updates or modifications to school mapping data must conform to and integrate with software platforms used by relevant public safety agencies.

Added new subsection (8) requiring maps to be updatable by the entity producing the data, relevant public safety agencies, school safety personnel, or school administration.

Consolidated and reorganized subsection (a) requirements, moving the future updates requirement from a separate subsection to the end of subsection (a) and adding the new updateability requirement.

Requirements for School Safety Mapping Data

What changed between versions

How they voted

Actions timeline

Sponsors