When old IT starts making school work harder

Start with a specific example

Ask staff what happens: a computer takes too long to open a lesson, an app no longer works properly or a repair keeps returning.

Record the equipment, date and effect on the job. Ask IT to confirm the cause and current support arrangements.

The device's age can help the conversation, but it should not be the whole reason for a purchase.

Explain the work being added

An awkward setup may require staff to repeat steps, borrow equipment or call support often. Use actual requests and staff accounts to understand that work.

Avoid inventing a financial loss or a percentage score when the school has not measured it. A clear example can still justify further checking.

The phrase “technical debt” is sometimes used for problems left by earlier technology choices. Staff can discuss the actual problems without needing that label.

Ask for suitable options

IT might recommend a repair, an approved software change, a different use for the device or replacement. Ask which options can safely support the required task.

Compare complete costs, including preparation and accessories. Say what each option improves and what would remain unresolved.

Check any effect on other systems or staff work before approving a change.

Put the decision into the school plan

Explain the problem, options, price information and date by which a choice is needed. Name the person arranging the work and the person who can approve spending.

If it must wait, agree how staff will manage meanwhile. After the change, ask a user to try the original task.

The useful result is a practical improvement based on confirmed needs. The school does not need an impressive score to explain why a recurring problem deserves attention.