When School IT Constantly Fails: How Tech Glitches Disrupt Learning (And What Parents Can Actually Do)
It was 7:47 on a Tuesday morning, and I was idling in the elementary school drop-off line, half-listening to my 8-year-old ramble about her art project, when my phone buzzed in the cup holder. The text was from my 13-year-old son Leo, already at the middle school down the road: can u bring my math worksheet? google classroom won’t load again and ms lopez says we need a printed copy by first bell.
I’d dropped Leo 20 minutes earlier, chromebook tucked under his arm. I turned the car around as soon as my daughter hopped out, and logged into the district parent portal on my phone while I waited at a stoplight. The screen sat on the spinning blue login circle for three minutes, then kicked me back to the homepage with a generic “something went wrong” message. I tried twice more, then called the school office, which went straight to voicemail. The district IT line reported a 47-minute wait, then cut to scratchy 90s soft rock that paused every 10 seconds to remind me my call was important.
I got home, logged in on my laptop, and got the same error. By the time I made it back to the middle school with a screenshot of the worksheet (Leo had gotten a photo from a friend off the school network, sent to my personal Gmail), the first bell had already rung. He hovered by the front door, hood up, and said half his class was in the same spot. Ms. Lopez couldn’t pull the assignment up on her classroom desktop either. The whole school’s Wi-Fi had been spotty since 7 a.m., and the only on-site IT tech was already over at the high school fixing a server crash.
That night, Leo dumped his backpack on the kitchen table, flipped his chromebook open to work on history, and got the same login error for the fourth time that day. He slammed the lid shut so hard his pencil bounced off the table. “My school IT sucks ass officially,” he said. I didn’t correct him for swearing. I’d spent 45 minutes that afternoon trying to add money to his lunch account, and I’d gotten the same error every single time.
Our district rolled out this new “unified” tech system over summer break. The old setup was clunky – five different passwords for five different sites, a parent portal that looked straight out of 2012 – but it worked most days. All summer, the district sent emails promising the new single-sign-on system would cut lost work, simplify grading, and pull every tool – classroom, gradebook, lunch payments, conferences – into one easy place. It was supposed to be fully functional by the first day of school. It’s now mid-October.
I ran into Leo’s math teacher after last month’s virtual parent-teacher conferences, when the whole district video system went down for three hours. We talked for 15 minutes while she sat in her parked car after school, calling parents from her personal cell because she couldn’t access conference links. She loses 20 to 30 minutes of every 90-minute class troubleshooting tech: resetting locked accounts, waiting for pages to load, re-sending assignments that vanish mid-server outage. That adds up to almost two full class periods of lost instruction time every month.
District admins have mostly waved this off as “growing pains,” saying kids today need to learn flexibility with tech anyway. That misses what constant, unpredictable outages actually do to kids, especially kids like Leo who have ADHD. He’ll spend 10 minutes working up the focus to start an assignment, pull it up, get his notes out, and hit the loading spinner. By the time the page loads 15 minutes later, he’s pulled out his sketchbook, gotten distracted by a text, and can’t pull his focus back. This isn’t building resilience. It’s just eating learning time. It also hits kids without personal phones or unlimited data the hardest; when school Wi-Fi cuts out, kids who can’t hop on a personal hotspot miss the work entirely, and too many end up with missing grades they never had a chance to earn.
We didn’t organize a dramatic protest. We just started small, with workarounds that don’t require waiting for the district to get its act together. The first thing I did was send a short note to all of Leo’s core teachers the second week of school: “Quick heads up – we’ve had consistent login and submission issues with the new district system. If an assignment from Leo shows up missing or late, just check in before marking it down, and I can confirm he finished it on time.” Every teacher wrote back within an hour, saying they’d heard the same from dozens of parents. Most have since added an automatic 24-hour buffer for all digital deadlines, no questions asked.
Leo now keeps a $1 spiral notebook for every core class, even when assignments are supposed to be fully digital. He writes answers and notes on paper first, then types them into the portal when the system works. If it’s down at deadline, he takes a photo of the page and sends it to his teacher’s regular school Gmail, not the district portal. It’s a tiny change, but it’s cut his after-school panic almost entirely. Ms. Lopez now keeps a milk crate of printed worksheets by her desk, enough for half the class, just in case Wi-Fi cuts out. It uses a little extra paper, she says, but it’s better than wasting half a period waiting for IT to call back.
Our PTA started a shared online doc (hosted on a personal account, not district servers) where parents and teachers log every outage, its length, and how many kids were affected. We brought 12 pages of logs to last month’s school board meeting, and the board finally voted to bring in an outside company to audit the system, instead of relying on the two overstretched IT staff who cover three whole schools. We’ve also raised enough for 15 cheap portable hotspots kids can check out from the library for the day, no questions asked, when the school network goes down.
As of this week, the login system still crashes at least twice a school day. The audit isn’t scheduled until next month, and there’s no guarantee the district will break its multi-year contract with the software company even if the audit finds major problems. Leo still comes home at least once a week complaining he couldn’t turn in an assignment during class.
But he doesn’t slam his chromebook shut anymore, most days. He just pulls out his spiral notebook, does the work, and sends the photo later. It’s not the seamless, tech-powered learning the district promised in those summer emails. But for now, it’s enough to keep him from falling behind while the adults sort it out.
Please indicate: Thinking In Educating » When School IT Constantly Fails: How Tech Glitches Disrupt Learning (And What Parents Can Actually Do)