Since House Bill 3 (2023) reshaped campus safety expectations in Texas, school safety officers have carried a heavier documentation burden than ever: armed security requirements, mandatory facility standards, intruder detection audits, and a paper trail that has to hold up when the Texas Education Agency or a district safety and security committee comes asking.

This guide covers the practical layer most districts struggle with: how to run and document CPTED-based campus safety audits in a way that satisfies compliance reviews and actually reduces risk.

What HB 3 changed for Texas districts

House Bill 3 built on the Texas School Safety Center's framework and, among other provisions, pushed districts toward:

  • Armed security presence at every campus (with good-cause exceptions requiring board action).
  • Compliance with facility safety standards — door locking mechanisms, exterior access control, communications systems, and fencing expectations under TEA's school safety facilities standards.
  • Regular audits and inspections, including exterior door sweeps, with results that must be documentable and reportable.
  • District safety and security committees that review findings and drive remediation.

The common thread: it is no longer enough to *do* the walkthrough. You must be able to prove what was inspected, when, by whom, what was found, and what happened next.

Where CPTED fits in

CPTED — Crime Prevention Through Environmental Design — is the assessment discipline behind most credible campus safety audits. Instead of treating security as a bolt-on (cameras, locks, alarms), CPTED evaluates how the physical environment itself invites or deters problems across four classic principles:

  1. Natural surveillance — Can staff see what they need to see? Are sight lines blocked by landscaping, portables, or parked vehicles?
  2. Natural access control — Do the campus layout and entry sequence funnel visitors through a controlled point, or are there five ways to walk in?
  3. Territorial reinforcement — Does the campus clearly signal where public space ends and school space begins?
  4. Maintenance and management — Broken lighting, propped doors, and dead zones tell an assessor (and an intruder) how closely a campus is watched.

A CPTED-based audit walks every zone of a campus — perimeter, parking, entries, corridors, gym, portables — against a standardized checklist rooted in those principles.

The documentation problem: clipboards don't survive audits

Most Texas districts still run safety walkthroughs on paper checklists or ad-hoc spreadsheets. Three failure modes show up again and again:

  • Inconsistency between assessors. Two staff members walk the same campus and produce incomparable notes. Without a standardized instrument, year-over-year comparison is impossible.
  • No photo evidence. A finding like "east wing door does not latch" is an opinion until there is a timestamped photo attached to it. Photo-backed findings protect the district — they prove the condition, and later prove the fix.
  • Findings die in a drawer. The walkthrough happens, the binder goes on a shelf, and nothing routes the high-priority items to maintenance with a deadline. When an incident occurs, an undocumented-but-known deficiency is the worst possible position.

What a defensible audit workflow looks like

Whether you build it on software or discipline alone, a compliance-ready CPTED audit process has five properties:

  1. A standardized instrument — every campus, every assessor, same checklist, so results are comparable across the district and across years.
  2. Photo evidence on every finding — captured at the point of inspection, not reconstructed later.
  3. Priority ranking — findings triaged (e.g., life-safety vs. deferred maintenance) so committees see the critical items first.
  4. A remediation trail — each finding assigned, dated, and closed with verification, giving your safety and security committee a live punch list instead of a stale report.
  5. Offline capability — practical reality: the places you most need to inspect (stairwells, mechanical areas, remote gates, portables) are the places Wi-Fi doesn't reach. Your documentation tool has to work offline and sync later.

How TRIAD School Shield approaches this

We built TRIAD School Shield after running these walkthroughs ourselves as school and district administrators. It turns a CPTED field inspection into a structured, offline-first audit: standardized checklists by campus zone, required photo evidence per finding, automatic priority ranking, and audit records your committee can actually act on — and your district can stand behind in a compliance review.

A 30-day starting plan for safety officers

  • Week 1: Adopt one standardized CPTED checklist district-wide. Retire the per-campus variants.
  • Week 2: Pilot a full audit on one campus, photographing every finding. Time it — you're building the template for the rest of the district.
  • Week 3: Present prioritized findings to your safety and security committee with remediation owners and dates attached.
  • Week 4: Schedule the recurring cadence (including exterior door sweeps) and lock the calendar for the year.

Compliance is the floor, not the goal — but a documentation system that satisfies HB 3 is the same system that gets hazards fixed before they matter. If you want to see a standardized audit in action, look at the TRIAD School Shield case study or contact our team.