Managed vs Co-Managed IT: Which Model Suits Your School?

One of the first decisions a school faces when looking at IT support is whether to go fully managed or co-managed. Both models work well — but they suit different situations. Choosing the right one can mean the difference between a smooth-running IT environment and one that’s constantly frustrating staff.

Let’s break down what each model looks like in practice and help you figure out which is the better fit for your school.

What Is Fully Managed IT?

With a fully managed IT service, your external provider takes complete responsibility for your school’s technology. That includes day-to-day support (helpdesk, troubleshooting, user requests), strategic planning, infrastructure management, security, and everything in between.

You don’t need an in-house IT person. Your provider is your IT department.

This model typically suits:

• Schools without any internal IT staff
• Small primary schools where employing a full-time technician isn’t practical or affordable
• Schools that have had a bad experience relying on a single in-house technician (the “what happens when they’re off sick?” problem)
• Schools that want a predictable monthly cost for their IT

The advantages:

• Access to a full team of specialists, not just one person
• Cover during holidays, sickness, and staff turnover
• Strategic advice and planning included
• Consistent service levels backed by agreed response times
• No recruitment headaches when your IT person moves on

Things to consider:

• You’re placing a lot of trust in your provider, so choose carefully
• Response times for on-site visits may not be instant (though remote support usually is)
• You’ll need a good internal contact — typically a school business manager — to liaise with your provider

What Is Co-Managed IT?

Co-managed IT is a partnership model. Your school has an internal IT person (or team), and they work alongside an external provider. The external partner handles the things your in-house team can’t — or shouldn’t — be doing alone.

That might include escalated technical support, cyber security, infrastructure projects, strategic planning, or simply providing cover and a second pair of eyes.

This model typically suits:

• Schools with an existing IT technician or network manager
• Multi-academy trusts (MATs) with a small central IT team that needs additional capacity
• Schools where the in-house IT person is strong on day-to-day support but needs help with security, compliance, or infrastructure projects

The advantages:

• Your in-house person keeps doing what they’re good at
• They get expert backup for complex or specialist tasks
• You retain local knowledge and quick on-site response
• Your internal team gets professional development through working with specialists
• Better resilience — you’re not dependent on one person

Things to consider:

• Clear role definition is essential. Who handles what? Without this, things fall through the gaps
• Your in-house person needs to be comfortable working with an external partner
• Communication between internal and external teams must be excellent

A Simple Decision Framework

Not sure which model is right for you? Ask yourself these questions:

Do you currently have an in-house IT person?

• No → Fully managed is likely the better fit. See our Managed IT Support page.
• Yes → Read on.

Is your in-house IT person handling everything well — security, compliance, strategy, and day-to-day?

• Yes, genuinely → You might not need external support right now (but consider what happens when they leave).
• No, they’re stretched → Co-managed could give them the backup they need. See our Co-Managed IT Support page.

Are you a MAT with a central IT team?

• Yes → Co-managed is often ideal. Your central team handles strategy and oversight while an external partner provides additional hands and specialist expertise.

Is your biggest concern cost?

• Managed IT is often more cost-effective than employing a full-time technician when you factor in salary, training, cover, and the breadth of skills required. Co-managed adds cost on top of your existing staff, but the value is in filling gaps you can’t cover internally.

Real-World Scenarios

Scenario 1: Small village primary school, 120 pupils, no IT staff. Fully managed is the obvious choice. The school gets a complete IT service — helpdesk, maintenance, security, strategic planning — for a predictable monthly fee. The school business manager acts as the main point of contact.

Scenario 2: Secondary academy, 900 pupils, one IT technician. Co-managed works well here. The technician handles day-to-day requests and is on-site for immediate issues. The external partner manages infrastructure, security, and compliance, and provides escalation support when the technician hits something beyond their expertise.

Scenario 3: MAT with 6 schools and a central IT manager. Co-managed again. The central IT manager sets strategy and standards across the trust. The external partner delivers on-the-ground support at each school and provides specialist skills the central team doesn’t have in-house.

The Bottom Line

There’s no single right answer — it depends on your school’s size, staffing, and needs. The important thing is to choose a model deliberately, not just drift into one by default. Whichever model you choose, make sure your provider understands the education sector, has clear service level agreements, and communicates well.

If you’d like to talk through which model would work best for your school, we’re always happy to have that conversation.