Challenge
Northside Independent School District in San Antonio, Texas serves over 100,000 students across 134 schools. Cherry Hill Public Schools in South Jersey serves close to 11,000 students across 19 schools with a 16-person IT team. On paper, these districts have almost nothing in common. In practice, Miranda Snider (Director of Technology Training and Development, Northside ISD) and Mark Pavinsky (Director of Technology, Cherry Hill Public Schools) described the exact same blind spots.
Both districts said their most common signal that something is wrong is a frustrated teacher poking their head into a hallway — not a help desk ticket.
“I get ‘it just doesn’t work’ and it never works, and it takes a lot of follow-up to get the information we need to trace down where along the route the problem actually exists.”
Mark Pavinsky, Director of Technology, Cherry Hill Public Schools
“We rely a lot on user reporting… are people out there suffering in silence when perhaps I have a team of people that could help be the solution finders, if only we knew there was a problem?”
Miranda Snider, Director of Technology Training and Development, Northside ISD
Three specific pain points came up in both districts, regardless of size.
- Device mismatch. Chromebooks look identical, and both districts described students swapping devices with siblings or classmates with no easy way to know who’s actually logged in on a given machine.
- Idle inventory. Neither district has an efficient way to spot devices that haven’t been touched in weeks — the “Chromebook under the bed” problem — so fiscally responsible reallocation is mostly guesswork.
- App outages nobody can prove. Both leaders described the same maddening loop: teachers say an app is down, the vendor’s status page says everything is fine, and IT is stuck confirming the outage manually before it can even start troubleshooting.
Lightspeed’s own data backs up what Mark and Miranda described anecdotally: technology usage and support demand are consistent regardless of district size — smaller districts have just as much to manage, often with smaller teams
Solution
Lightspeed Signal™ was built around the three problem areas both districts named independently: devices, apps, and network.
Devices — know who’s actually on the machine
Unassigned login detection flags when the person logged into a device doesn’t match who it’s assigned to — the
Johnny-and-Susie problem, solved without a manual asset-management pull.
- Filterable by school, grade band, or campus, so IT can see patterns rather than one-off tickets.
- Security-oriented alerts on unknown user access, lost/stolen devices, and student use of VPNs, proxies, or Tor.
- A dedicated report surfaces devices unseen for a set window — a day, a week, six months — so idle inventory becomes visible instead of anecdotal.
Miranda described the same gap when it comes to verifying a student is on their own assigned device: the data exists somewhere, but nothing flags it until someone already suspects a problem.
“Can I find that out? Yes. But what would trigger me to even look into that?”
Miranda Snider, Director of Technology Training and Development, Northside ISD
Network — see what’s happening beyond the access point
- Device-level monitoring shows real-world network conditions, not just whether an access point is technically up.
- Data is filterable by on-campus vs. off-campus, so districts supporting community learning sites can see where kids
are actually getting online. - A general connectivity report flags students without adequate internet access, regardless of location.
Apps — stop waiting on vendor status pages
- Continuous monitoring (every five minutes) of error rates and performance across apps in actual use.
- Impact data shows how many schools, students, and staff are affected — the “show your homework” evidence both
Mark and Miranda said they need to get vendors to take an outage seriously. - Distinguishes a single-district issue from a broader, multi-customer outage, so IT knows whether to escalate internally or wait on the vendor.
“We’re kind of in that holding pattern of ‘no, it’s not working, no it’s really not working’ — and the vendor’s like, ‘no, we think it’s working.’”
Miranda Snider, Director of Technology Training and Development, Northside ISD
Why This Matters
Two very different districts, the exact same need for proof.
Both leaders were candid that most of what they currently do is manual, reactive, and dependent on someone noticing a problem and speaking up. Signal is built to flip that model for districts at either end of the size spectrum.
- For a 134-school district like Northside, Signal replaces spreadsheet comparisons and guesswork with a single, filterable view across every campus.
- For a smaller, leaner team like Cherry Hill’s 16-person department, Signal gives outsized leverage — the same visibility a much larger team would need to build manually, without adding headcount.
Both districts also pointed to the same non-technology lesson: relationships matter as much as tools. Miranda and Mark independently named “building deliberate relationships with the right stakeholders” — curriculum teams, vendor contacts, campus staff — as the thing that’s helped them most so far. Signal doesn’t replace that; it gives those relationships better information to work with.
Result
Two districts, wildly different in size, with the exact same need — proof, not guesswork, when
something breaks.
