Why Your Teachers Are Losing an Hour a Week to Tech Problems

IT Service Desk Best Practice: Raising Standards Across Schools & MATs

I'm going to level with you. Most school IT isn't broken because of a lack of budget. It's broken because nobody's actually designed it.

Teachers lose about 37 minutes a week dealing with tech issues. In a school of 58 staff, you're haemorrhaging 35 hours of teaching time every single week. That's more than a full-time teacher's worth of hours, just... evaporated into password resets and "the projector won't connect."

Multiply that across a year. Multiply it across a MAT of eight schools. The numbers get horrifying fast.

1. Team Structure (Or: The Dave Problem)

Every school has a Dave. He "does IT" along with teaching Year 9 Computer Science. When Dave's off sick, the entire network could catch fire, and nobody would know what to do. When Dave goes on holiday, people just... wait.

This isn't a Dave problem. This is a we-never-actually-built-a-proper-team problem.

The Real Consequences

Staff just give up asking for help. They stop logging issues because "IT are always too busy anyway." Year 7 teacher Mrs Patterson starts using personal Gmail to share files because the school system "doesn't work properly." Head of Science sets up a WhatsApp group because "it's easier."

Congratulations. You now have shadow IT, compliance nightmares, and safeguarding risks you don't even know about.

Your best staff leave. I watched a head of department quit a perfectly good school last year. She left because she spent two terms fighting with technology that should have just worked. She moved to a school that paid £2k less. Their IT just worked.

You get blindsided by crises. No structure means no visibility. You don't know that 40% of Year 11 laptops are about to hit end-of-life until they fail during mock exams. Schools report that unplanned IT staff absence caused "significant disruption" to teaching and learning.

Your technical staff burn out. When everything depends on one or two people, they work evenings, weekends, and holidays. I know a technician who worked through his wedding day because the exam system went down. He quit three months later.

The Solution

Stop building teams around people. Build roles around needs.

1st Line Support - Password resets, device swaps, simple fixes. Get staff back working within minutes. A good 1st line tech handles 15-20 tickets a day.

2nd Line Support - Network troubleshooting, system administration, complex fixes. Should spend 30% of time on preventative work, not just firefighting.

3rd Line / IT Leadership - Strategic planning, cyber security, project delivery. Looking three terms ahead, not three tickets ahead.

For MATs: Hub-and-spoke model. Central expertise + local support in each school. One MAT cut overall IT costs by 20% while improving service quality.

Every role needs: a written remit, clear KPIs, escalation paths, and training opportunities.

One MAT restructured (same budget, different allocation) and reduced average ticket resolution time by 47%—same money. Actual structure.

2. Tooling (Or: The Spreadsheet of Doom)

Someone emails "IT Support." Someone catches a technician in the corridor. A Post-it appears: "Room 14 - projector??" with no name, no date, no context.

One technician keeps a notebook. Another uses a spreadsheet. Nobody knows what's been done, what's waiting, or what's actually urgent.

This is normal in schools.

The Consequences

You can't see the patterns. You miss that every Year 8 Chromebook fails at 18 months. That Room 23's network port has been reported broken six times. Those three departments use incompatible versions of the same software.

You're doing the same work multiple times. No ticketing means no institutional memory. Three technicians troubleshoot the same issue three different ways because nobody documented what worked.

Your staff think you're incompetent. Teacher logs an issue. Hears nothing. Logs again. Corners the IT lead: "I sent you THREE emails!" The IT lead has no record. Trust evaporates.

You cannot prove your value. Budget meetings come around. "We need another technician" gets met with "Really? What for?" You've got no data. Just "We're really busy."

You waste staggering amounts of money. While specific benchmarking data for schools is limited, the inefficiency of managing tickets through spreadsheets and email chains rather than using proper ITSM tools is substantial and well-documented across industries. 

The Solution

Stop treating ITSM software as a luxury. It's infrastructure.

You need: ticketing with categorisation, asset management, SLA tracking, reporting, self-service portals, and automation.

Tools that work: Halo ITSM (strong in UK education), Freshservice (clean interface, good value), Zoho Desk.

Cost-benefit: A 500-student school might spend £2,000-£3,000 annually. Compare to £30,000+ lost teaching time and £8,000-£10,000 wasted technician time.

One school resisted for three years ("We can't afford it"). Finally bought in. Within one term: ticket resolution and staff satisfaction measurably up; caught a warranty claim worth £1,400. Paid for itself.

3. Triage & Process (Or: Why Everything Feels Urgent)

Your technician arrives on Tuesday to: an urgent email about projector assembly, a voicemail about Year 11 coursework access, a headteacher's "quick question," a walk-up about a mouse, and a week-old ticket about the entire humanities department being blocked.

Which first? In most schools, whoever shouts the loudest.

The Consequences

Critical issues get buried. The projector gets fixed because the assembly is visible—Year 11 coursework slides. I've seen safeguarding IT alerts sit behind "printer out of paper" because nobody had flagging systems in place.

Technicians repeat work endlessly. Wi-Fi drops in Room 14. Tech A fixes it, doesn't document. Two weeks later, same issue. Tech B troubleshoots from scratch, 45 minutes gone.

Your best people leave. Never finishing anything or improving anything. Just endless firefighting. That's not a job—it's a treadmill.

The Solution

Seven-step workflow:

1. Capture everything - No verbal requests. In the system, or it doesn't exist.

2. Categorise - Device / Network / Software / Account / Safeguarding

3. Prioritise by impact × urgency - Not "who's shouting loudest"

   • Critical: Exam systems down, safeguarding, whole school affected

   • High: Whole class blocked, time-sensitive

   • Medium: Individual issues, non-urgent

   • Low: Nice-to-haves

4. Assign to the right tier - Match complexity to capability

5. Communicate expectations - Ticket number, priority, expected response time

6. Document properly - Not "fixed it"—actual detail

7. Review weekly/monthly - Spot patterns, prevent recurring issues

One secondary implemented this properly. First month: complaints about "having to log everything." By month three, resolution time dropped significantly. In our work with schools and MATs, we've seen significant improvements after implementing proper triage processes—though specific metrics vary widely depending on starting point and implementation quality.

Same technicians. Same budget. Just process.

4. SLAs & Expectations

Define and publish what staff can expect:

• How to log tickets

• Response times (Critical: 30 min / High: 2 hours / Medium: 1 day / Low: 3 days)

• What IT will/won't support

• Escalation procedures

One school published SLAs and saw complaint tickets drop 41% in the first term. Staff knew what to expect and when.

5. Quick Wins

Knowledge base - Well-implemented knowledge bases can significantly improve first‑contact resolution, often covering the majority of routine requests.

Termly dashboards - Ticket volume, resolution performance, top recurring issues, and cybersecurity posture.

Training integration – In my experience, 30-40% of tickets aren't technical—they're training gaps. One MAT reduced ticket volume by 23% after monthly "Tech Tea" sessions.

Automation - New starter provisioning, scheduled reports, and device monitoring. Saving 30 minutes daily = 130 hours annually.

Conclusion

The difference between chaos and high performance comes down to: clear team roles, modern tooling, standardised processes, and managed expectations.

You're not necessarily spending more money—you're spending it strategically.

Start with one area. Pick your biggest pain point and fix that first. Build momentum.

Because every minute you save your staff from technology frustration is a minute back in the classroom, where it belongs.

Need help? The Tech Shepherd works exclusively with schools and MATs to build resilient IT services that protect teaching time. Let's talk about what's possible for your schools.