Start here
Build a school campus security plan around the full operating day, a collaborative planning team, clear responsibilities, and coordinated physical-security layers. Arizona district and charter schools should use the current 2026 EOP requirements and verify the laws governing their personnel, funding, and emergency readiness. Private School Security Officers have a distinct role from statutory law-enforcement positions. Assign, fund, and verify improvements before translating the plan into daily tasks.
Key takeaways
- Use the August 2026 Arizona EOP requirements and the current ADE template rather than relying on an older plan.
- Review access, visitors, pickup, events, facilities, communications, and staff responsibilities together.
- Keep private School Security Officer assignments distinct from Arizona’s statutory School Safety Officer and School Resource Officer roles.
- Check district security-personnel training, school-specific credentials, and the correct 2026 or 2027 AED and employee-training effective dates.
- Preserve safe egress, accessibility, student privacy, and controlled access to sensitive campus details.
- Turn findings into assigned corrective actions, then verify completion and update the EOP and daily procedures.
A school entrance can work well during class and become difficult to manage at dismissal. A visitor procedure can be clear to the receptionist and unfamiliar to a substitute. A camera can record an event without anyone being responsible for reviewing an alert.
Those handoffs deserve attention before another piece of equipment is ordered. School campus security planning connects the property, daily routines, staff responsibilities, and emergency procedures. The result should be a plan people can carry out during an ordinary busy day, with a clear way to get help when conditions change.
This guide gives Arizona district, charter, and private-school leaders a framework for that work. The planning recommendations below are not a certification of compliance or a substitute for the school’s emergency operations plan, qualified assessments, or required approvals.
Start with the Arizona requirements that apply to your school
District and charter leaders should begin with their existing emergency operations plan, usually called the EOP. Under A.R.S. § 15-341(A)(31), district governing boards must develop a plan for each school with local law enforcement and emergency-response agencies. Section 15-183(E)(10) establishes the corresponding charter-school requirement. Both address communication with and assistance for students with disabilities.
Use the current edition. ADE and the Arizona Department of Emergency and Military Affairs issued new minimum requirements in August 2026, replacing previous versions. A binder developed under an earlier edition needs a deliberate comparison, not a new cover date.
The ADE EOP page provides the current requirements and template. Schools may incorporate the template into their own systems while preserving required content and sequence and maintaining backup access during outages. Have the school’s EOP lead check assigned-role training and documentation against the current requirements.
Private schools can use this planning framework, but should confirm their own applicable laws, building requirements, policies, and insurance conditions. District and charter provisions should not simply be labeled requirements for every private school.
Put the people who run the campus in the planning conversation
The front office knows which visitor questions recur. Transportation knows where pickup instructions become confusing. Facilities knows which repairs keep returning. Teachers and special-education staff understand supervision and assistance needs that a property-only inspection can miss.
Bring those perspectives together with school leadership, the nurse or health lead, IT, counseling and student-support personnel, and the security representative. Include local law enforcement, fire/EMS, and emergency management in the appropriate planning work. Designate a school leader who can approve decisions and a person who tracks implementation.
First agree on what the campus includes: regular instruction, before- and after-school care, athletics, performances, deliveries, construction, rentals, and shared-use areas. Review incident reports, near misses, maintenance records, and repeated exceptions. Ask what was observed, what happened next, and which condition still needs correction.
A physical-security review examines the environment, systems, procedures, and responsibilities. Behavioral threat assessment is a separate multidisciplinary process for evaluating concerning behavior and arranging appropriate intervention. Neither a guard nor a camera replaces that process or the school’s student-support services.
Review four physical layers, then check how they work together
The CISA K–12 School Security Guide organizes physical security across the grounds perimeter, school grounds, building perimeter, and building interior. It also connects personnel, policies, design, technology, and training. This is planning guidance, not a separate Arizona equipment mandate.
Use the layers to organize a confidential review. The questions below are starting points for administrators, not a campus vulnerability map.
| Layer | Planning question | Responsibility to settle |
|---|---|---|
| Grounds perimeter | Do boundaries and wayfinding make authorized arrival understandable? | Who owns inspections, repairs, and changes in use? |
| School grounds | How do parking, pedestrian movement, outdoor activities, and supervision fit together? | Who coordinates transportation, facilities, and activity staff? |
| Building perimeter | Does entry management work alongside emergency escape and accessible access? | Who approves access rules, hardware, and exceptions? |
| Building interior | Can staff recognize authorized access, communicate concerns, and follow approved procedures? | Who maintains instructions, credentials, and staff preparation? |
For each proposed improvement, name the task it performs and the person responsible after installation. If a system needs staff attention, identify who provides it during the relevant hours. If a procedure depends on a roster, determine who keeps that roster current.
Treat arrival, dismissal, and visitors as distinct operations
Arrival and pickup
Walk through the process with transportation and school staff. Look at pedestrian and vehicle interaction, supervision assignments, accessible routes, authorized pickup, late arrivals, and early releases. Changes should be understandable to families who are new to the school and to staff covering an unfamiliar duty.
Have administrators resolve custody and release questions through approved school procedures. A School Security Officer should know whom to contact when authorization is unclear, rather than independently interpreting family documents or making educational decisions.
Visitors, vendors, and deliveries
Write a process that reception can actually run. It should cover check-in, identity and purpose verification under school policy, host confirmation, visible authorization, escort expectations where appropriate, checkout, and exceptions. Include maintenance contractors and recurring vendors, not only parents attending meetings.
Test the awkward cases: an appointment the host forgot to communicate, a delivery during a busy period, or a visitor-management system outage. Decide who can approve an exception and how it is recorded. A printed badge does not resolve an uncertain authorization.
Explain visitor expectations to families in advance and apply them consistently. Clear directions and calm communication help staff uphold the procedure without turning every question into a confrontation.
Keep controlled entry compatible with safe escape and accessibility
“Lock every door” is not a complete school security plan. Entry control, evacuation, fire protection, accessible movement, and emergency responder access must work together.
Before changing door hardware, gate controls, or access arrangements, involve qualified facilities personnel and the fire or building authority having jurisdiction. Check applicable accessibility requirements and obtain required approvals. Do not improvise barricades or disable required exit functions to solve an entry-management problem.
Include the people who need assistance in planning. Consider communication, mobility, transportation, medical needs, supervision, and the effect of a disrupted routine. Keep individual support information appropriately confidential while making necessary instructions available to authorized staff.
Maintenance needs an owner and a reporting route. Staff should know how to report a malfunction and who decides on an approved temporary arrangement. Closing a work order should mean the problem was checked, not merely that a replacement part was ordered.
Define the School Security Officer’s duties before choosing staffing
A private School Security Officer can support access procedures, observation, communication, de-escalation, reporting, and emergency coordination within the approved assignment. Write those duties into post orders and identify the school administrator who can change them.
Keep the legal roles distinct. Arizona’s School Safety Program statute defines School Resource Officers through specified law-enforcement categories, including qualifying retired officers assigned by a law-enforcement agency. Its statutory School Safety Officer is a School Resource Officer working off duty. A private School Security Officer does not acquire those roles or police authority from a job title.
There is also a specific training requirement to check. A.R.S. § 15-249.08 requires district-employed security personnel, including personnel supplied through a contractor, to complete the ADE/AZPOST training within one month of starting, subject to the statute’s valid-certificate exception for completion less than two years earlier. Charter schools may choose to require the program. Verify the requirement for the individual assignment.
For a contracted service, verify agency and applicable guard-registration status through Arizona DPS. Separately confirm the school’s fingerprint/background-check and clearance-card requirements. Guard registration and a fingerprint clearance card are different credentials.
Any armed assignment needs separate review of school-ground firearms law, the school’s authorization process, agency requirements, and insurance. An armed registration or concealed-carry permit alone does not settle that question.
Headcount follows the work. List responsibilities that occur at the same time, relief needs, supervision, events, and absence coverage. Do not expect one person to remain at a fixed assignment while performing another duty elsewhere. Arrow’s school staffing FAQ explains why enrollment alone does not establish a suitable officer count.
Connect communications, emergency care, and after-hours use
An emergency plan should still be usable when a principal is absent, a substitute is teaching, or a program is operating outside ordinary hours. Confirm who holds the assigned responsibilities, how staff reach help, and how essential instructions remain available during a communications or power outage.
The 2026 Arizona EOP requirements address plain-language response protocols, disability/access/functional needs, off-campus emergencies, and school-sponsored activities beyond normal hours. Align security instructions with that plan. Do not create a second set of conflicting emergency terms for contract personnel.
Plan family communications and reunification before an incident. Staff need an approved source of information, and families need to understand how instructions will arrive. Keep sensitive locations and operational arrangements out of public-facing material.
Check the school-specific AED dates
Under A.R.S. § 15-120.07, beginning August 1, 2026, public schools serving any grades nine through twelve and sponsoring athletics must provide AEDs at each campus and school-sponsored athletic event, subject to the law’s access, location, and maintenance conditions. Its athletic-event definition covers on-campus practices, trainings, and competitions.
The same statute’s district/charter requirement for at least one appropriately CPR/First Aid-trained employee per campus during regular hours begins August 1, 2027. It also requires AED training when an AED is present. That employee-coverage provision is not yet effective as of this guide’s October 2026 publication.
Organize medical responsibilities with the school health lead and applicable oversight. Review supplies, equipment availability, training records, and coverage across activities. In Arizona, include local weather and utility-disruption scenarios in the hazard review. A security assignment should not silently replace nursing duties or qualified emergency care.
Set rules for cameras, visitor data, and reports
Before expanding a camera or visitor-management system, agree on its purpose, authorized users, retention, vendor access, incident preservation, and disclosure review. Ask what happens when equipment fails and how reported faults reach someone with authority to arrange a repair.
School video is not automatically public or automatically outside FERPA. The U.S. Department of Education’s video FAQ explains that the answer depends on matters including the relationship to a student, who maintains the record, and applicable exclusions. Have the school’s privacy lead review the actual use and records process.
Require reports that distinguish direct observations from statements made by others. Route urgent matters immediately under the school’s procedures rather than leaving them for a routine report. Limit student information to what is necessary and authorized. For reporting structure, see Arrow’s guide to security activity and incident reports.
Turn the assessment into an improvement plan
A useful assessment ends with decisions. Keep a restricted action log showing the issue, its consequences, an approved interim measure when needed, the responsible owner, a target date, and how completion will be verified. Separate routine maintenance from projects needing design, procurement, or governing-body approval.
Budget for continued operation: staffing, relief, training, software, credential administration, repairs, testing, and replacement. Before approving a purchase, ask how it will be staffed and maintained after the installation team leaves.
Do not confuse an operational walkthrough with a mandated outside assessment. Under A.R.S. § 15-154.02, district and charter recipients of approved School Safety Program funding must contract every five years with a provider from ADE’s list for the specified assessment. This is not a blanket requirement that every Arizona school hire a security company. Verify the current ADE provider list; this guide does not establish Arrow as an approved provider.
Use the following strategic checklist to organize implementation. For routine execution after the plan is set, use the separate K–12 Daily Physical-Security Coordination Checklist.
- Identify the applicable requirements, current EOP, and authorized planning lead.
- Review the campus across its full operating day and changing uses.
- Evaluate physical layers together with staff duties and procedures.
- Resolve visitor, pickup, and authorization exceptions in writing.
- Obtain qualified review of access changes, egress, and accessibility.
- Define personnel roles, required credentials, training, and supervision.
- Align communications and medical responsibilities with the EOP.
- Approve data access, incident reporting, and retention practices.
- Assign, fund, and verify corrective actions.
- Schedule review and update the plan when operations change.
Practice, review, and correct what the exercise reveals
The 2026 Arizona requirements call for annual EOP review, staff preparation, essential information for substitutes, and collaborative after-action review and improvement planning within one week of a drill or incident. Use the current document for the full drill and training requirements rather than treating this article’s checklist as that schedule.
Prepare staff for their actual roles and use age-appropriate, carefully planned exercises. The U.S. Department of Education’s emergency-planning resources emphasize collaborative planning, regular review, training, exercises, and recovery preparation.
After practice, ask concrete questions. Were responsibilities understood? Did essential messages reach the intended people? Could staff account for students and address assistance needs? Which instruction was unclear? Assign the resulting changes and confirm they were implemented.
Questions to settle before hiring school security
Does every Arizona school need an armed officer?
No universal armed-officer requirement is established by the provisions discussed here. Determine the school’s obligations and assess the assignment before choosing personnel or equipment. Any armed proposal requires its own legal, authorization, training, and insurance review.
Does private School Security Officer training replace the state program?
Do not assume equivalence. Arrow’s private School Security Officer pathway includes online and separately completed in-person components. Confirm the state requirement and the records for each assigned person. A course description is not proof that an officer has completed it.
What should a school ask a security provider?
Ask for the exact contracting entity, applicable credentials, school-specific preparation, post orders, supervision, relief coverage, reporting examples, data-handling terms, and coordination with administrators and responders. Ask how the provider will document and address service problems.
Where should the first discussion with Arrow start?
Start with the school’s operating needs, existing planning work, responsibilities needing coverage, and procurement requirements. Arrow’s School Security Officer services cover discussions for private, charter, and public schools. Confirm availability and the proposed scope directly. Share sensitive campus details only through an agreed, appropriate channel.
