The School Safety Calendar: What Administrators Should Review Every Month, Semester, and Year

School safety has a calendar problem. Not because schools aren't doing enough. In many districts, quite a lot is happening. Emergency plans are updated. Drills are conducted. Threat assessment teams meet. Doors are checked. Staff complete training. Radios are tested. Reunification plans are developed. Law enforcement visits campuses. Safety committees meet. After-action reports are written.
The problem is that these activities can easily become individual events rather than parts of a deliberate cycle. The emergency operations plan gets reviewed because someone says it is time to review the plan. The behavioral threat assessment team roster gets updated when someone realizes a member left the district three months ago. The emergency contact list gets corrected after somebody calls a number that no longer works. That is not necessarily a failure of effort. It is often a failure of systems.
One of the simplest ways school and district leaders can strengthen preparedness is to stop treating school safety as a collection of tasks and begin managing it as a recurring calendar of readiness. The question becomes less "did we do our annual safety review?" and more "what should we be checking right now?"
DOWNLOAD THE CALENDAR HERE
School Safety Is Perishable
A school can have an excellent emergency plan in August and already have inaccurate information in it by October. Why? Because schools constantly change. Employees resign. New staff are hired. Students enroll and withdraw. Administrators transfer. Phone numbers change. Construction alters evacuation routes. A reunification site becomes unavailable. Someone assigned to an Incident Command System role leaves. Emergency equipment gets moved. A drill identifies a problem nobody anticipated.
Preparedness is therefore not something a district achieves once. It has to be maintained. The U.S. Department of Education's Guide for Developing High-Quality School Emergency Operations Plans describes emergency planning as a continuous process and recommends establishing a recurring process for reviewing and revising the EOP, noting that schools may find it useful to review portions of the plan each month or at natural breaks in the academic calendar rather than waiting to review everything at once. That is a useful model for the broader school safety program as well.
Think in Three Cycles
A practical school safety calendar doesn't need to include dozens of deadlines. I would organize it around three simple cycles: monthly, semester, and annual. Each serves a different purpose. Monthly checks catch things that change frequently or require continual follow-through. Semester reviews test whether systems are functioning and whether people remain prepared. Annual reviews allow leadership to step back and evaluate the entire program, reset priorities, and prepare for the next school year.
There should also be a fourth category: event-driven. Some things shouldn't wait until the calendar says it is time. A real incident, significant drill finding, personnel change, facility modification, new hazard, policy change, or other meaningful event should trigger an appropriate review. Together, these create a manageable preparedness rhythm.
Every Month: Check What Can Drift
Monthly reviews should be short. This is not the time to rewrite the emergency operations plan. The goal is to catch the small changes that can quietly create large problems. Review critical emergency contacts, making sure police, fire, EMS, emergency management, utilities, transportation, district leadership, facilities, and mental-health contacts are still accurate. Ask whether staffing changes have affected emergency responsibilities, connecting directly to the issue of leadership redundancy discussed elsewhere.
Behavioral threat assessment teams are operational teams, not just names required on a roster. Monthly, ask whether all required disciplines are still represented, whether active cases are being monitored according to their management plans, and whether follow-up actions are occurring. Look at open findings from drills, exercises, real incidents, safety audits, campus walkthroughs, and threat assessments, and ask what you said you were going to fix, who owns it, when it is due, and whether it has actually been completed. FEMA's Homeland Security Exercise and Evaluation Program treats improvement planning as an ongoing process in which corrective actions are continually monitored and implemented, not simply recorded in an after-action report and forgotten, a principle explored further in The After-Action Review. Finally, compare new hires and role changes against required safety onboarding, so new personnel enter the school's safety system, not simply its payroll system.
Every Semester: Test the System
The semester review should go deeper. Monthly checks ask, is our information current? Semester reviews ask, does our system still work? Choose specific sections of the EOP to review rather than the entire document at once, aligning with federal guidance encouraging schools to review plans on a recurring basis and noting that reviewing portions of the plan at different points in the year can be an effective approach.
Don't just ask whether required drills were conducted. Ask what they are telling us, looking across the semester for recurring problems, accountability issues, or protocols staff seem uncertain about, a diagnostic approach we describe further in How Do You Know Your School Safety Program Is Working. Each semester, verify that reunification sites, contacts, transportation plans, assigned roles, materials, technology, and student-release procedures are still current and realistic. Reconnect with public-safety partners, since police supervisors change, fire personnel rotate, and emergency managers change roles. The first time your principal meets the fire battalion chief shouldn't be in the parking lot during an emergency. And review training gaps by asking who needs training now that didn't need it six months ago, rather than simply who completed the training.
Every Year: Step Back and Evaluate the System
The annual review is different. This is where leadership looks across the entire school safety program, asking not "did we complete everything?" but "are we more prepared than we were a year ago?" Examine the overall EOP as a system: has the hazard environment changed, have facilities changed, and have lessons from incidents and exercises been incorporated? Federal guidance emphasizes that EOPs should evolve as schools learn lessons, obtain new information, and update priorities.
Confirm primary and backup ICS and leadership assignments, going a step further to ask whether those people are trained, understand their authority, and have practiced, the same discipline covered in our Incident Command System guide. Don't simply carry last year's behavioral threat assessment team roster forward; confirm membership, review multidisciplinary representation, and provide refresher training. Map the year's training, drill, and exercise calendar intentionally rather than letting drills simply happen as deadlines approach, since FEMA describes preparedness as a recurring cycle of planning, organizing and equipping, training, exercising, and evaluating and improving. Once each year, physically open the reunification kits rather than relying on the inventory sheet, and review MOUs and partnership agreements to confirm they are current and the people named in them still work there. Finally, bring the year's safety data together, including incidents, threat reports, drill findings, and corrective actions, to answer what your safety system is telling you.
Some Reviews Shouldn't Wait for the Calendar
A good calendar creates consistency. It shouldn't create rigidity. Certain events should trigger an immediate review: a real emergency occurs, a drill exposes a significant problem, a principal or other key emergency leader leaves, a threat assessment team experiences major turnover, construction significantly changes a facility, a new hazard is identified, a reunification site becomes unavailable, or a policy, law, or emergency protocol changes.
In those situations, don't wait until the semester review. Update what needs to be updated. This is another reason after-action processes matter: exercises and incidents should produce lessons, but lessons only improve preparedness when someone converts them into action.
Assign Owners, Not Just Dates
There is one more piece necessary to make a school safety calendar work. Every recurring activity needs an owner. Consider the difference between "emergency contacts reviewed monthly" and "the campus administrative assistant verifies the emergency contact list by the first Friday of each month and reports changes to the principal and district safety office." The second one is much more likely to happen.
For every calendar item, define what needs to be reviewed, when it happens, who owns it, how completion is documented, and what happens when a problem is identified. Without ownership, a calendar becomes another checklist. With ownership, it becomes a management system.
A Practical School Safety Calendar
A district's actual calendar should reflect state requirements, local policy, hazards, district size, and existing programs. A simple starting framework organizes monthly items around emergency contacts, personnel and role changes, BTA team status, open corrective actions, and new-staff onboarding. Semester items cover selected EOP sections, drill and exercise trends, reunification readiness, responder coordination, training gaps, and ICS and leadership readiness. Annual items cover a comprehensive EOP review, hazard and risk information, ICS and succession assignments, BTA team structure and training, the annual training and exercise program, reunification sites and resources, MOUs and partners, and safety data and trends. Event-driven items cover incidents, significant exercise findings, leadership turnover, facility changes, new hazards, policy or legal changes, partner changes, and unavailable resources or sites.
The point isn't that every district needs this exact calendar. The point is that someone should be able to show you the district's version.
Don't Let the Calendar Become Another Compliance Checklist
There is a risk here. Schools are already surrounded by calendars, deadlines, compliance requirements, inspections, certifications, and reports. The solution isn't another 47-item spreadsheet that someone updates because they are supposed to. The calendar should make the work easier, answering what needs attention this month, what can wait until semester break, what needs a deeper annual review, and what changed that requires acting now.
That creates a manageable rhythm. And perhaps more importantly, it shifts the conversation from "are we compliant?" to "are we maintaining readiness?" Those aren't always the same thing, a distinction we explore further in The Preparedness Gap.
The Calendar Creates Organizational Memory
There is another benefit that is easy to overlook. School safety programs frequently depend on individual people. A strong safety director knows when things need to be reviewed. An experienced principal remembers to call the fire department before an exercise. An experienced threat assessment coordinator knows when team training needs to be refreshed. Then that person leaves.
A documented safety calendar transfers that knowledge from the individual to the organization. It tells the next person what we review, when we review it, who participates, what we document, and what happens when we find a problem. That is how preparedness becomes institutional rather than personality-dependent.
Preparedness Is a Cycle, Not an Event
Schools don't become prepared because they updated the EOP in August. They don't become prepared because they conducted a drill in September or because the threat assessment team completed training. Those activities matter. But preparedness comes from continually maintaining the system those activities support: plan, train, practice, evaluate, correct, update, then do it again.
That cycle is reflected in federal emergency-management guidance and in the Department of Education's approach to maintaining school emergency operations plans. For school leaders, the practical challenge is turning that concept into normal organizational practice. A school safety calendar is one way to do it.
A Practical Next Step
Pull up your district calendar for the next 12 months. Then schedule just three categories: a monthly readiness check, a semester safety review, and an annual program review. Under each one, assign specific items and an owner. Then add a fourth process, an event-driven review: every time an incident, exercise, personnel change, facility change, or other significant event occurs, ask whether it changes anything in your plan, your people, your training, or your resources. If it does, don't wait for next August. Fix it now.
Put It Into Practice
School Safety Solutions works with schools and districts to move from individual safety activities toward an integrated preparedness system, including emergency planning, ICS, behavioral threat assessment and management, training and exercises, reunification, after-action review, and program evaluation, part of our broader school safety services. The goal isn't another checklist. It is a sustainable process for making sure plans stay current, people stay prepared, identified gaps get corrected, and the safety system continues to improve throughout the year. If you'd like help building your district's calendar, reach out to start the conversation.
School Safety Solutions helps K-12 leaders strengthen prevention, protection, and preparedness through practical assessment, training, tabletop exercises, Standard Response Protocol implementation, behavioral threat assessment support, and reunification planning. If your district wants a calm, working review of its active shooter protocol and broader emergency readiness, visit School Safety Solutions or call 512-387-6729 to talk through next steps.




Comments