Buying school IT: from requirement to accepted service

Define the requirement before the buying route

Write down what the school needs, why it needs it and when it must be ready. Describe users, quantities, locations and the tasks the technology must support. Include accessibility, support and integration needs early, so they are part of the evaluated offer.

The Department for Education's purchasing guidance recommends a specification whatever buying process is used. A clear requirement helps the school compare proposals and reduces the risk of discovering an essential omission after the price has been agreed.

Confirm the applicable procurement process

Follow the school's or responsible body's current procurement policy and approval arrangements. The route can depend on value, contract type, funding and the relevant procurement regime. England's DfE guidance discusses frameworks, quotations and regulated procedures, including the Procurement Act 2023 where applicable.

Do not rely on a remembered threshold or divide a requirement artificially to avoid a process. Check the total expected contract value and obtain procurement advice when needed. A framework is not simply a directory: its own award rules and permitted scope must be followed.

Specify outcomes and acceptance evidence

Describe what success looks like in observable terms. A wireless project might need suitable service in identified teaching spaces under the planned load. A parent system might need a successful import, accurate permissions and a demonstrated reconciliation workflow. Avoid a vague instruction to provide "a complete solution".

List the school's responsibilities too. State who supplies existing data, arranges access to rooms, approves content and makes decisions. Proposals are easier to compare when every bidder understands the same boundary between included work and school-side work.

Compare the whole cost

Ask for one-off and recurring costs separately, along with the assumptions behind them. Include configuration, migration, training, support, licences, accessories and any unavoidable dependencies. Record price review mechanisms, renewal dates and notice periods.

For a service contract, understand the charging unit. A price per pupil, user, device or site can change differently as the school grows. The budgeting guide explains how to compare a common period without confusing annualised cost with cash flow.

Evaluate with a consistent method

Set criteria and weighting before reviewing offers. Include essential pass conditions, such as an integration the school cannot operate without, and separate them from scored preferences. Record evidence behind each score rather than awarding marks for an impressive demonstration.

Use the same realistic scenarios for every shortlisted option. Ask people who perform the task to test it, with synthetic or appropriately controlled data. Include a difficult case: a duplicate record, a lost account, a failed import or a user who needs an alternative access route.

Review data, security and service terms

Identify the information the service will handle, the access it needs and the parties involved. Involve the relevant data protection and safeguarding staff where their responsibilities are affected. Ask for written answers on data access, export, retention, incident handling and deletion at the end of the arrangement.

Clarify service hours and what support commitments mean. A rapid acknowledgement is not the same as a restoration promise. Identify exclusions and what happens when a fault spans two services, so the school is not left coordinating unresolved blame between contracts.

Make acceptance a planned stage

Agree the evidence needed before signing off delivery. This might include configured accounts, migration totals, a working backup or recovery process, staff training and documentation. Record unresolved issues with owners and dates rather than accepting an indefinite promise to finish later.

Check that the school has the agreed administrative access and can obtain its own data in a usable format. Keep contract documents, renewal details and service ownership in the relevant registers. A delivered box or activated subscription is not necessarily a ready service.

Plan the exit before it is needed

Understand how the school can export information, recover domain or account control and transition to another arrangement. Ask about charges, notice periods and the format of returned data. Test a representative export when it is practical to do so.

After the first operational period, review whether the purchase solved the original problem. Feed that evidence into the IT strategy. Good procurement includes learning from the result, not only proving that a buying process was completed.