LAUSD's fight data reveals a teacher blindspot nobody is talking about

A teacher watches two students square up in a hallway. She radios the office. A monitor writes something on a clipboard. By third period, both students are back in class. Nothing was entered into the district system. The fight, for the record, never happened.

That gap — between what staff witness and what actually gets documented — sits at the center of new LAUSD data published by CBS Los Angeles investigative reporter Kati Weis (cbsnews.com). The district recorded 6,131 student fights in the 2024-2025 school year, a 21% increase over four years ago, alongside 4,015 student threats, up 11.5% since the 2022-2023 school year. LAUSD covers roughly 420,000 students across more than 1,000 schools.

The headline numbers are alarming. But the operational story behind them is about what teachers and campus monitors are asked to do — and what systems either support or fail them when they try.

Teachers are not the problem. The workflow is.

Most classroom educators are not trained security professionals. They are asked to teach, manage 30-plus students, meet curriculum benchmarks, and also identify and report behavioral escalations — all through whatever reporting mechanism their school has set up, which varies wildly across a district this size.

Ronald Stephens, executive director of the National School Safety Center and professor of education emeritus at Pepperdine University, has been clear in interviews that districts face serious legal exposure when they document elevated risk but cannot show a responsive operational change. That burden lands not just on principals and district administrators. It lands on the staff doing the actual witnessing.

When a teacher reports a threat and gets no visible follow-up, two things happen: their confidence in the system drops, and they start making quiet decisions about what is worth the paperwork. Over time, that calculus produces underreporting — which makes the official numbers look better than the situation actually is.

What underreporting costs at the classroom level

Monica Harmon, executive director of Speak Out Against Bullying Inc., attended an anti-bullying assembly at an LAUSD elementary school and noted afterward that students who fight or threaten peers routinely return to class the next day without formal consequences. Staff on those campuses already knew that. Many had stopped filing reports for low-level incidents because nothing changed when they did.

The practical result: campus monitors and teachers end up carrying informal threat intelligence in their heads rather than in any system. They know which students have a history together. They know which stairwell gets loud on Tuesdays. None of that knowledge transfers when a monitor calls in sick, or when a student moves to a different period, or when a new teacher takes over a class.

Campuses that use structured digital logging — tools like XGuard that let a monitor record an incident in real time with location, parties, and behavior type — give that informal knowledge somewhere to live outside any one person's memory.

The shift handoff problem

School security operates in shifts and across roles: morning monitors, classroom teachers, lunch supervisors, afternoon security staff, after-school program coordinators. Every handoff is a point where context gets lost.

A fight that happened at 10:15 a.m. near the gym may not reach the afternoon supervisor unless it was logged. If the same two students escalate again at 2:45 p.m., the afternoon monitor has no context — and no way to know this is a second incident in the same day.

This is where LAUSD's numbers become a staffing and process problem, not just a discipline problem. Effective campuses treat incident documentation the same way a hospital treats a patient handoff: structured, consistent, and mandatory regardless of perceived severity.

What that looks like in practice:

• Every physical altercation and every credible threat gets logged before the reporting staff member moves to their next task — not at the end of the shift.
• Location tagging is required. "Near the gym" is not sufficient; "east hallway outside gym storage, between periods 3 and 4" is.
• The log entry names any witnesses, including students who may have intervened or been bystanders.
• Supervisors run a brief weekly review of repeat names and repeat locations before those patterns become crises.

Pro tip: Ask your campus security lead to pull every incident report from the past 60 days and sort by student name. If any name appears more than twice and no formal intervention was initiated, your reporting process is generating data that nobody is reading. That is a liability, not a safety program.

The staff trust equation

There is one more factor the district data does not capture: whether staff believe reporting is worth the effort.

When a teacher files a threat report and the student is back in class the next morning with no explanation — not even a brief "we looked into it" acknowledgment — the message received is that the report went nowhere. Repeated enough times, that impression becomes policy by default. Staff stop reporting. Incidents stop appearing in the data. Leadership looks at flat numbers and assumes conditions have stabilized.

LAUSD's four-year comparison suggests that is exactly what has not happened. The fights and threats are there. Whether they are being captured, and whether the staff doing the capturing feel like it matters, is the operational question the headline number cannot answer on its own.

Need protection where you are? XGuard connects you with licensed, vetted security operators in minutes — for events, residences, retail, executive protection, and fire watch. Available globally.

Source: us-cbs-news — 2026-10-09