West Virginia's school safety mapping requirements took effect on September 1, 2026. The statute is direct: the requirements of §18-9F-10a "shall be effective on September 1, 2026."
If you have seen September 1, 2025 somewhere, that is wrong, and it appears on more than one vendor site. The code says 2026.
Most of the 55 county boards are not finished. There is no penalty clause and no stated completion deadline in the section, which means the useful thing to do now is work the sequence in the right order and document where you are. This guide is ordered by lead time, because the two slowest steps both have to happen before you buy anything, and that order does not change just because the date has passed.
First, who owns this
The duty falls on each county board of education. All 55 of them. It sits on top of the Crisis Response Plan already required under §18-9F-9 and the safety program under §18-9F-10, so if your board has those, this is an addition rather than a replacement.
In practice the work splits three ways. Your board handles the law enforcement approval. Whoever produces the data has to hit nine technical criteria and verify accuracy on site. Someone has to own dissemination and future updates, which outlast the initial project. Sort out who holds each before you start, because the handoffs are where this stalls.
Step 1: Open the law enforcement conversation today
Do this first, and note the timing the statute sets.
Subsection (c) requires local school systems to consult and receive approval from the primary law enforcement agency serving and supporting the district, and it puts that step before procurement. Not after production, and not as a courtesy notification once the maps exist. The statute names county, city, or municipal police departments and the Sheriff's Department as the agencies in scope.
Approval before procurement reorders the project for most boards. Your specification has to be blessed before you sign, which means a meeting, and in some counties, more than one, and their calendar is not yours. Starting here is the difference between finishing and explaining why you didn't.
While you have them, ask what their public safety answering point actually runs. You need that answer for step 2 anyway.
Step 2: Confirm formats against your PSAP, not against a brochure
The statutory test is not whether a format is industry standard. Subsection (a)(1) asks whether the data conforms to, integrates with, and is accessible within the software platforms used in your local public safety answering point and by the city, county, state, and federal public safety agencies that could provide emergency services at the school. It then adds the clause that decides most procurements: without requiring the purchase of additional software or the payment of fees to access the data.
So the question to ask is what your PSAP runs, whether the output opens in it, and whether anyone has to pay to look at it. Ask the PSAP directly. A vendor telling you their output is universally compatible is not the test the statute sets.
This belongs before procurement for the same reason step 1 does. It is the specification you hand a vendor. Running the check after delivery is too late to change anything.
Step 3: Get walk-throughs on the calendar
Subsection (a)(5) requires accuracy to be verified by the entity producing the data, through an on-site walk-through of the school buildings and grounds.
That gets misread in both directions. The verification duty sits with the producer, which means this is something you buy; your facilities lead does not have to walk it themselves. It is also not optional, and it cannot be desk-checked against existing floor plans. If a proposal is silent on walk-throughs, the work is either not scoped or not priced, and one of those becomes your problem later.
Either way, someone from the district escorts them through every building, inside and out. That is a scheduling problem months before it is a mapping problem.
While someone is walking through every building anyway, get more than one job out of it. Note where your camera coverage actually is, which is rarely where the as-built drawings say it is. Note which entry points are genuinely controlled. Both answers will matter to you in a budget conversation six months from now.
Step 4: Check the data against all nine criteria
Subsection (a) sets nine requirements, at a minimum. Check each one yourself instead of accepting a vendor's compliance claim, and keep the statute's own numbering so your record lines up with the code.
Number three catches people. A map that needs a paid license to open does not satisfy a requirement that it be viewable and printable from open-source viewers, and the only reliable way to know is to open the sample file on a machine with nothing installed.
Ask about number nine on the first call, before you shortlist anyone. Data residency is a yes or no question, the wrong answer disqualifies a vendor outright, and it covers the whole production process, from the first draft through to where the finished files sit at rest.
Step 5: Handle dissemination and future updates
Subsection (b) answers the question boards ask first, which is who gets copies.
The mapping data goes to the state board of education, the Division of Homeland Security and Emergency Management, and local first response agencies including police, fire, and emergency medical services, plus any other local entities your school's crisis response planning team determines should be consulted. It is provided at no cost beyond the initial cost of production, and it has to remain available to those entities permanently.
You cannot charge responders for access to it, so any vendor model that meters ongoing access to your own data collides with this. And "permanently," read alongside the requirement in (a)(8) that future updates stay compatible, means access has to outlive your contract term. Ask what happens to the files if you switch vendors in year four.
One more thing that is clear and worth telling your board early: the data is exempt from public disclosure. Any data obtained and maintained under this section is not subject to disclosure under §29B-1-1 et seq., West Virginia's Freedom of Information Act. Somebody will ask whether detailed building layouts become public records. They do not.
If you are already past the date
Two honest points, now that September 1 has arrived.
The section sets an effective date for the requirements rather than a stated completion deadline, and it contains no penalty or enforcement provision. That is not permission to ignore it. It does mean the useful thing to do is document where you are, what is scheduled, and when it completes, rather than going quiet.
If walk-throughs are the blocker, say so specifically. A board minute recording that walk-throughs are scheduled for October across eleven buildings is a defensible position. Nothing on file is not.
What this costs, and what the state will cover
Subsection (d) caps what the state may hand you. Subject to available funding, each county board may receive not greater than $4,500 per school for the purposes of the section. The section does not appropriate that money. Confirm the channel and the timing with the West Virginia Department of Education, because the section names a ceiling without naming a source.
Do not assume the Alyssa Alhadeff School Safety Fund covers this. That fund, created by HB 4798 and administered by the West Virginia Department of Homeland Security, is designated for mobile panic buttons and similar school safety equipment. Map production is a different line item.
And treat any dollar figure on a vendor site without a source as unverified. The statutory number is $4,500 per school; anything else needs a citation.
Higher education is already live
HB 4592, from the 2026 Regular Session, adds §18B-4-5c and requires each state institution of higher education to create standardized campus safety mapping data.
It was enrolled on March 14, 2026 and took effect 90 days later, on June 12, 2026. Almost nothing has been written about it. The campus requirement has been live since June while the K-12 requirement is only now starting. It carries the same nine criteria, the same requirement to consult and receive approval from the primary law enforcement agency before procurement, and the same FOIA exemption. Its dissemination clause is narrower, covering local first response agencies and any other local entities the institution determines should be consulted, and it says the data goes at no cost without the "beyond the initial cost of production" qualifier the K-12 section uses.
If you work at a West Virginia college or university, the exercise your K-12 colleagues are running now is already your obligation, and has been since June.
What the map will not do for you
Worth being clear about, because it affects what you budget next.
Standardized mapping shortens the gap between a responder arriving and reaching the right hallway. That is real, and it is the point of the statute.
It does not tell anyone what is happening right now, and it cannot lock a door.
West Virginia's own legislation makes that distinction explicit. HB 4798 is West Virginia's version of Alyssa's Law, which brings the state into a group of 13 that have now enacted some form of it. Passed March 10, 2026, approved by the Governor on April 1, and effective June 8, it adds §18-9F-9a and directs the state board, working with the Division of Homeland Security and Emergency Management, to promulgate a rule by December 31, 2026 permitting every public school in the state to implement a wearable panic alert system, contingent on available funding. Read the verb carefully: the enrolled version permits adoption. It does not require it, and it specifies what such a system must be capable of if a district adopts one, including transmitting 911 calls and mobile activations to the local PSAP and initiating a campus-wide lockdown notification. The section sunsets on December 31, 2029.
There is a second provision in HB 4798, and it matters more here than the panic buttons do. HB 4798 also requires each county board to ensure that all security data within a school facility is accessible by a local law enforcement agency, and to coordinate with that agency on access protocols. It names cameras, maps, and access control.
Your mapping project produces one of those three. The other two are live systems, and the access protocol has to cover them too. If you are choosing a mapping vendor this fall without knowing who owns that side, you are solving one third of the problem. Our guide to choosing a school panic button covers the alerting layer in more detail, and school safety issues and solutions covers the broader program.
Where Coram fits
Coram is not a mapping vendor. Producing your §18-9F-10a data is a separate purchase, and any page implying otherwise is selling you something.
Coram covers the live half. Once a building is mapped, someone still has to see what is happening, coordinate the response, and control the doors. Video Security, Access Control, Guest Management, and Emergency Management run on one unified physical security platform, on the cameras and infrastructure you already have, which is also the surface where the §18-9F-9a law enforcement access protocol has to be defined. One protocol covering one platform is a shorter conversation with your sheriff than four protocols covering four vendors.
On criterion 9, which disqualifies mapping vendors, the same question is worth asking of anything else you buy. Footage stays on a Coram appliance on site, with the cloud handling alerting, metadata, and viewing from infrastructure hosted in the United States. And how long footage is retained decides whether an incident is still reviewable weeks later, which matters for the after-action review as much as for the response itself.
.png)
