#EdTech: Spring-Clean Your School’s IT Department

By The Tech Shepherd — Guiding Schools to Better, Safer IT

Every year, schools deep-clean classrooms, reset curriculum plans, and gear up for the final push towards summer. But there’s one area that rarely gets the same attention: your IT department.

Whether you’re a Headteacher, COO, CFO, or Trust Leader—and whether you’re technical or not—a well-structured IT function can transform teaching, learning, safeguarding, and staff productivity. Spring is the perfect moment to declutter processes, reset expectations, and get more from the team you already have.

Here’s your practical, step-by-step guide to spring-cleaning your IT department and setting it up for success.

Refresh Your IT Vision and Priorities

Before you even think about devices or systems, take a step back and ask yourself:

• What are our priorities for the next 12 months?

• Is our IT aligned with our school improvement plan?

• Are we investing effort in the right places—or just firefighting?

• 
  

It’s easy for schools to drift into reactive mode, fixing what’s broken rather than building what’s needed. A spring reset gives you the chance to:

• Reconfirm your core IT principles (safeguarding, reliability, simplicity, accessibility)

• Dust off your digital strategy or MAT-wide vision

• Set three clear priorities for the year (e.g., tightening cybersecurity, improving classroom reliability, consolidating cloud tools)

• 
  

Top tip: You don’t need to be technical to set direction. Your job is alignment, not engineering. Focus on outcomes, not outputs.

Audit What You’ve Got (Without Needing to Know Every Cable)

A “light audit” is often enough to reveal gaps and quick wins. You don’t need to become a technician—ask the right questions.

Work with your IT team to check:

• Device age and suitability (teacher devices first—that’s your most significant ROI)

• Network health (Wi-Fi coverage, speed, bottlenecks)

• Cloud setup (Microsoft 365, SharePoint, OneDrive—are they properly configured?)

• Safeguarding tools (filtering, monitoring, MFA—are they actually functioning?)

• Licences (schools often pay for unused software year after year)

  
  

As a leader, you should:

• Ask for a simple, non-technical summary

• Request red/amber/green status—no jargon allowed

• Ask for the top 5 risks and top 5 quick wins

If your techs can’t explain things clearly yet, that’s a training and communication opportunity—not a failure. Make it part of their development.

Declutter Your IT Workflows

Every school IT department collects “process clutter” over time:

• Old tickets that never got closed

• Legacy systems are still limping along

• Outdated local servers gathering dust

• Manual tasks that could easily be automated

• Technicians are stretched thin because everything is urgent

  
  

Spring cleaning actions:

• Archive or resolve old tickets in the helpdesk

• Remove unused systems or software (yes, that includes the one “Dave set up in 2014”)

• Standardise device builds—no more one-offs

• Document the top 10 repeat tasks so anyone can do them

  
  

This frees up capacity—and morale—instantly.

Get the Most Out of Your Existing IT Team

Here’s the thing: you don’t need more technicians.

You need clarity, rhythm, and expectations.

Set Clear Roles and Ownership

Technical job titles vary wildly, but responsibilities should never be vague. Clarify who owns:

• Classroom support

• Network issues

• Cybersecurity

• Staff onboarding/offboarding

• Cloud systems (Microsoft 365, Google Workspace)

• MIS integrations

• Procurement and supplier management

When people know what “good” looks like, performance jumps.

Establish a Weekly Operating Rhythm

One of the biggest game-changers for schools is a simple rhythm:

• Monday: Priorities check-in (15 minutes)

• Midweek: Progress review (10 minutes)

• Friday: Wins + blockers (10 minutes)

Quick, structured, consistent. Technicians stay focused, and leaders stay informed without being dragged into the technical weeds.

Measure the Right Things

Don’t measure ticket volume. Don’t measure “who’s busiest.”

Measure:

• Percentage of classrooms ready for teaching at 8:30 am

• Device turnaround time

• Staff satisfaction

• Uptime of critical services (MIS, Wi-Fi, email)

• Completion of proactive tasks (patching, updates, testing backups)

These show outcomes, not just activity.

How to Line-Manage Technical People (Even If You’re Not Technical)

This is one of the most prominent pain points leaders raise during Tech Shepherd consultations.

The secret? You manage the outcomes and behaviours—not the technology.

Five rules for managing technicians effectively:

1. Ban jargon in leadership conversations

If a tech can’t explain something simply, they probably don’t understand it well enough themselves. Push back gently but firmly.

2. Use plain-English service levels

Instead of: “We need to optimise DNS latency” Try: “Teacher laptops should start and log in within 60 seconds”

3. Agree what “good” looks like

Fast response times, proactive maintenance, good communication with staff, tidy documentation. Be explicit.

4. Make documentation non-negotiable

If it’s not documented, it doesn’t exist. This protects you when staff leave and improves consistency across the team.

5. Focus on priorities, not preferences

Tech people sometimes love complexity for its own sake. Your job is to pull them back to impact:

“What difference will this make for a teacher on Monday morning?”

Tidy Up Your Cybersecurity (A Must-Do Every Spring)

Schools are being targeted more than ever. A quick annual reset can dramatically reduce risk.

Your spring cybersecurity checklist:

• Confirm MFA is enabled for all staff (not just some)

• Review admin accounts—remove or disable old ones

• Check device encryption is working

• Test that your backups actually restore (this is the one everyone forgets)

• Update your incident response plan

• Review filtering and monitoring logs for anomalies

If you’re a MAT, do this consistently across all schools. One weak link puts everyone at risk.

Re-Energise the Culture of Your IT Team

Your tech team becomes the culture you create.

Promote:

• Proactivity over firefighting

• Pride in tidy, well-documented systems

• Clear communication with non-technical staff

• Training and personal development

• Collaboration across sites (especially in MATs)

Avoid:

• Hero culture (“only one person knows how to fix it”)

• Blame culture

• Accepting “it’s always been like that”

• Tech silos and gatekeeping

A spring reset is the perfect time to re-establish expectations and rekindle enthusiasm.

Create a 90-Day Improvement Plan

End your spring clean with a short, punchy plan:

In the next 30 days:

Quick wins that restore reliability and morale (close old tickets, fix obvious problems, update documentation)

In the next 60 days:

Core system clean-ups and process improvements (standardise builds, automate repetitive tasks, audit licences)

In the next 90 days:

Bigger changes—cloud migrations, network upgrades, enhanced cybersecurity

This gives staff clarity and gives leaders visibility.

Final Thoughts

Spring-cleaning your IT department isn’t about wiping screens and ordering new kit.

It’s about creating clarity, structure, and momentum—so your technology truly supports your children, staff, and broader community.

You don’t need to be technical to lead a high-performing IT function. You only need the proper focus, the right questions, and the right rhythm.

And remember: if your tech team can’t explain what they’re doing in plain English, they’re not doing it well enough yet. Push for clarity. Demand simplicity. Your staff and pupils will thank you for it.

Drop me an email and find out how I can help spring clean your IT department. carl@thetechshepherd.co.uk