Sign up free

Solution · For schools & education

Keep the classroom running, on a school budget.

In a school, IT failure is a teaching failure: the lesson that cannot start, the exam that cannot be taken, the register that cannot be completed. The IT team is small, the budget is smaller, and the users number in the hundreds.

By itserva Editorial Team Updated November 20, 2026 Reviewed by [REVIEWER NAME, CREDENTIAL]

Incidents reported simply, by any teacher, in one place.

Teaching-time failures fixed before anything else.

A small desk staffed to the real volume, term by term.

The problem

Why school IT is hard to run

School IT has a shape other sectors do not: hundreds of users, a handful of staff, a budget set a year in advance, and a timetable that cannot move when the network does.

Hundreds of users, one small team

Teachers, students and office staff all rely on the same few people. When the network fails at 9 a.m., thirty classrooms notice at once — and the team cannot be in thirty rooms.

Reports arrive by corridor

A teacher mentions a broken projector in passing, a student tells a technician at lunch. Nothing is logged, so nothing is tracked, and the same projector fails again next week.

The timetable cannot move

A lesson starts at a fixed time whether the system is ready or not. An outage that would be an inconvenience in an office is a lost lesson in a school — and lessons do not come back.

Budgets set a year ahead

Spending is approved annually, so an unexpected failure means waiting for the next budget round. The case for spending has to be made with numbers, months before the money exists.

The process

Five steps, and the itserva page for each

Five steps, built around the school day.

  1. 01

    Log incidents simply

    Give every teacher one simple way to report a problem, and one record where it lands. The easier the report, the sooner the team knows — and the sooner the lesson can start.

    Service Desk →

  2. 02

    Prioritise by impact on teaching

    Score urgency against impact, with teaching time counting as high impact. A projector in a classroom in use outranks a printer in an empty office, every time, whoever reports it.

    Incident Priority Matrix →

  3. 03

    Staff a small desk on a tight budget

    Work out how many people the ticket volume actually needs at the service level the school promises. The number makes the budget conversation concrete — and protects the team from an impossible promise.

    Help Desk Staffing Calculator →

  4. 04

    Know the cost per ticket

    Work out what each resolved ticket costs, fully loaded. The number shows where the time goes — and it is the evidence for the next budget request, written in the language governors understand.

    IT Support Cost Per Ticket →

  5. 05

    Agree term-time service levels

    Write down what the school promises during term time, and what is different in the holidays. A service level that respects the school calendar is one the small team can actually keep.

    SLA Template →

What’s included

Tools, templates and guides for schools & education

Template

Incident Report Template

Record what happened, who was affected, and what was done — in one page.

Tool

Incident Priority Matrix

Set priority from urgency and impact, consistently every time.

Tool

Help Desk Staffing Calculator

Estimate how many agents a ticket volume needs at a given service level.

Tool

IT Support Cost Per Ticket

Work out the fully loaded cost of resolving one support ticket.

Template

SLA Template

A service level agreement you can adapt: targets, exclusions and remedies.

Product

Service Desk

Log every request and incident in one place, with priority and SLA timers built in.

Measure it

The four numbers worth tracking

Four numbers, reviewed each term, show whether the school’s IT is keeping up with the timetable. Bring them to the budget conversation.

MTTR

How fast the team recovers when a teaching system fails. A falling MTTR means fewer lost lessons; a rising one means the team needs help before the next term.

Calculate your MTTR →

Tickets per term

How many requests arrive each term, and what they are about. A rising count in one category — logins, projectors, printing — is a fix waiting to be made once, properly.

Calculate staffing needs →

Cost per ticket

What each resolved ticket costs the school. It is the number that turns we need another technician from a plea into a case the budget can answer.

Calculate cost per ticket →

SLA met rate

Whether the term-time targets were met. A rate the team can show, term after term, is the strongest argument a school IT team can make.

Check your SLA allowance →

Frequently asked questions

How do teachers report problems without adding work?

One simple form, and one record where every report lands. The report should take a minute; the logging, the priority and the tracking are the team’s job, not the teacher’s.

What counts as high priority in a school?

Anything that stops teaching: a classroom system during a lesson, the register at the start of the day, the exam system in exam season. Impact on teaching outranks everything else.

How do we make a budget case for IT?

With numbers per term: tickets, resolution times, and the cost per ticket. Governors decide on evidence, and a term’s worth of numbers is more persuasive than a list of things that broke.

Should service levels differ in the holidays?

Yes. Term time needs fast response for teaching systems; the holidays need cover for maintenance and preparation. One agreement for both either overpromises in term or wastes effort in the holidays.

Make the next term’s case with this term’s numbers.

Run the staffing calculator on this term’s ticket volume and the cost-per-ticket calculator on the same numbers. A free workspace saves both, ready for the budget conversation.

Create a free workspace