Industry SecurityAction checklist

K-12 Daily Physical-Security Coordination Checklist

A K-12 daily physical-security checklist helps school leaders coordinate entrances, arrivals and dismissals, visitors, deliveries, credentials, communication equipment, visible facility conditions, incident reporting and unresolved issues. It must sit beneath the school's site-specific emergency operations plan, student-safety policies and district authority. In Arizona, a private security guard does not have the authority of a commissioned police or peace officer, and a private guard should not be described as a school resource officer. Federal guidance defines an SRO as a career law-enforcement officer with sworn authority. This checklist does not provide tactical response, student discipline, search, restraint or threat-assessment instructions. Call 911 for immediate danger.

20 checks5 sectionsSources checked July 19, 2026
Why it matters

Use a system view, not a single-control view

School security is a system involving leadership, staff, students, families, facilities, transportation, mental-health partners and public-safety agencies. A daily guard task list cannot replace that system or the school's required emergency planning.

Clear handoffs make the daily layer useful: administrators retain school decisions, trained teams address behavioral concerns, facilities correct building issues, and private guards observe, communicate and act only within post orders and private-citizen authority.

Before you begin

How to use this checklist

  1. Have the principal or designated administrator approve the school-specific version with district safety, facilities, transportation, accessibility and security leaders.
  2. Complete the shift briefing before arrival activity and update it for events, contractors, schedule changes and open facility issues.
  3. Use the checklist to confirm observable conditions and communications, not to publish campus maps, camera locations, door weaknesses or response tactics.
  4. Refer student discipline, behavioral threat assessment, search, reunification and emergency command decisions to the authorized school and public-safety processes.
  5. Document exceptions, assign owners and review lessons after drills, incidents, construction or major schedule changes.
Interactive checklist

Mark each task from current evidence

Use Not applicable only when the item genuinely does not apply, and follow the site’s approved escalation process for any urgent condition.

Section 1 of 5

Leadership, plans and daily briefing

Daily security tasks must align with the current school plan and an identified administrator.

01A designated school administrator is available for security, access, student and emergency decisions during the operating period. Priority review item

Evidence to look for: Confirm the primary and alternate contact and their decision authority without placing private numbers in a public result.

02Current post orders and daily tasks are aligned with the school's site-specific emergency operations plan. Priority review item

Evidence to look for: Resolve conflicting terminology, alarms, communication channels, evacuation or shelter roles and after-hours procedures with school leadership.

03Private-guard duties are clearly distinguished from the duties of sworn school resource officers and police. Priority review item

Evidence to look for: Arizona law states that security guards do not have commissioned police or peace-officer authority; job titles and procedures should reflect the actual role.

04The daily briefing covers schedule changes, events, contractors, transportation issues, closed areas and unresolved incidents relevant to security.

Evidence to look for: Share only need-to-know information and protect student, employee and family records.

Section 2 of 5

Arrival, dismissal and perimeter

High-volume transitions need coordinated traffic, access and communication rather than improvised enforcement.

05Student drop-off, bus, staff, visitor and service flows follow the school-approved arrival and dismissal plan. Priority review item

Evidence to look for: Observe conflicts, queue spillback and unauthorized vehicle movement while leaving traffic direction and enforcement to trained, assigned personnel.

06Primary and secondary entrances, gates and exterior doors are in their approved daily state without defeating emergency egress. Priority review item

Evidence to look for: Report propping, visible damage and access faults; do not publish weak points or attempt unqualified repairs.

07Fire lanes, responder access and accessible pedestrian routes are unobstructed. Priority review item

Evidence to look for: Check normal arrival and dismissal conditions, not only an empty campus.

08Exterior lighting, fencing, signs and visible boundary conditions with an obvious fault enter a tracked facilities process.

Evidence to look for: This is a safe visual observation, not a code or engineering inspection; keep specific vulnerabilities restricted.

Section 3 of 5

Visitors, deliveries and credentials

Consistent verification protects the school while preserving dignity, privacy and accessibility.

09Visitors enter through the designated process, present required identification and connect with an authorized school purpose or host. Priority review item

Evidence to look for: School policy must define screening, exceptions and record retention; staff should not create ad hoc rules based on appearance.

10Visitors receive and return the required badge and understand where they may go and whether escort is required.

Evidence to look for: Use the school-approved process and accessibility accommodations without displaying unnecessary personal information.

11Deliveries and contractors are expected, verified and directed to the approved service point. Priority review item

Evidence to look for: Confirm company, purpose and receiving contact; suspicious packages are not opened, moved or handled by untrained personnel.

12Lost, expired, shared or unreturned keys and credentials follow a documented school escalation process. Priority review item

Evidence to look for: Record identifiers only in the restricted access-control system, not the public checklist.

Section 4 of 5

Interior conditions and communication

Security observations should support, not replace, qualified facility and emergency-system work.

13Public corridors, common areas and assigned zones show no obvious obstruction, damage, unattended item or urgent hazard. Priority review item

Evidence to look for: Observe without entering private student or staff spaces outside authority and without moving a suspicious item.

14Exit routes and emergency doors remain usable and are not blocked by furniture, equipment or security measures. Priority review item

Evidence to look for: Qualified school and fire-safety personnel determine technical requirements.

15Security radios, phones and approved emergency-notification tools have a documented operational check. Priority review item

Evidence to look for: Use authorized test procedures that do not trigger an unintended emergency response.

16Staff know the plain-language method for requesting routine security help and reporting an emergency. Priority review item

Evidence to look for: Instructions should be accessible to substitutes and address people with disabilities and communication needs as the EOP requires.

Section 5 of 5

Reporting, privacy and improvement

Good records support school decisions without exposing protected student information or tactics.

17Concerning behavior and safety reports go to the school's designated reporting or behavioral-threat-assessment process. Priority review item

Evidence to look for: Report observable behavior and context, not stereotypes or protected characteristics; security does not independently conduct a clinical assessment.

18Security logs and incident reports use objective facts and protect student, family and employee information.

Evidence to look for: Use authorized systems, minimum necessary detail and restricted access; distinguish direct observations from statements.

19Drills and exercises include the security role and produce an after-action improvement record.

Evidence to look for: School leadership should plan age-appropriate, accessible exercises and coordinate with public-safety partners as applicable.

20End-of-day handoff lists unresolved access, facilities, incident and follow-up items with a responsible owner.

Evidence to look for: Keep tactical and personally identifying information in the restricted system.

Current result

Complete the checklist to see a summary

Results are informational and do not certify compliance or eliminate risk.

Common mistakes

What can weaken the review

  • Calling a private guard an SRO or assigning sworn law-enforcement functions to private security.
  • Publishing campus maps, door weaknesses, camera locations, response staging or lockdown tactics.
  • Using physical appearance, disability, race, religion or other protected traits as a substitute for observable behavior.
  • Letting a daily checklist replace the site-specific EOP, behavioral threat assessment or district policy.
  • Designing drills without age, disability, trauma and communication considerations.
Practical questions

Frequently asked questions

Is a private school security guard the same as a school resource officer?

No. Federal guidance defines an SRO as a career law-enforcement officer with sworn authority. Arizona law says a security guard does not have commissioned police or peace-officer authority and performs duties as a private citizen.

Can this checklist replace an Arizona school emergency operations plan?

No. The Arizona Department of Education says public districts and charter schools must maintain site-specific EOPs aligned with state minimum requirements. This checklist should support daily coordination beneath that approved plan.

Should a school publish its completed security checklist?

Publish only general educational content. Campus vulnerabilities, maps, camera locations, access details, student information and response tactics should remain in restricted systems shared with authorized partners.

Who decides whether a visitor may enter a school?

The school or district should define that authority in policy. Security can perform assigned verification and observation tasks, but unusual access and school-business decisions should go to the designated administrator.

What should security report about concerning behavior?

Report specific, observable behavior, statements and context through the school's designated process. Avoid profiling, diagnoses or independent threat conclusions, and call 911 for an immediate threat.

Sources and evidence baseline

These references support the general planning baseline. Site-specific decisions still require the responsible organization and appropriate qualified professionals.

  1. K-12 School Security Guide, Third EditionCybersecurity and Infrastructure Security Agency

    Systems-based vulnerability assessment and layered physical-security planning for K-12 schools.

  2. Emergency Operations PlanningArizona Department of Education

    Arizona site-specific EOP requirements, accessibility, training, drills and plan maintenance.

  3. School Resource Officers and School-Based Policing Fact SheetU.S. Department of Justice Office of Community Oriented Policing Services

    Federal definition and role of a sworn school resource officer.

  4. A.R.S. 32-2634: Authority; LimitationsArizona State Legislature

    Arizona private-security authority boundary and private-citizen status.

Source links checked: July 19, 2026

Related services and checklists

Continue with the service context or a neighboring planning tool that helps you act on what you found.