Planning Your School's 2027 IT Budget in Term 4

Part of: IT for schoolsBudgets, devices, cyber and support, planned around terms and the people who run the school.

School IT budget planning works best in Term 4. List every line as either a one-off project or a running cost: devices, Microsoft 365 licences, cyber security, network capacity and support. Decide the device refresh early, so laptops can be ordered, imaged and enrolled before Term 1 starts in 2027.

Most business managers I speak to know what they need to fund. The harder part is the order of operations. Budgets are approved before the year begins, but devices, Wi-Fi upgrades and security work all need lead time that does not fit neatly inside January.

This guide walks through each line worth planning, how to separate projects from running costs, the questions to ask any IT provider before you sign, and a simple timeline from October to January. It is written for business managers and principals at independent, Lutheran and other faith-based schools.

Key Takeaways

• Term 4 is the window because approvals, ordering, imaging and enrolment must all finish before Term 1.
• Split the budget into one-off projects and running costs, and attach the ongoing cost to every project.
• Devices are the easy part. The lifecycle (buying, warranty, spares, support and secure retirement) is where the real cost sits.
• Anchor cyber security spending to the ASD Essential Eight, ranked by your actual gaps, not by vendor claims.
• Choose a support model that fits your in-house capacity, and ask providers who will actually answer the phone.
• Work backwards from the first day of Term 1 and keep the timeline simple.

Summary Table

Why Term 4 Is the Window for School IT Budget Planning

Term 4 is the window because next year's budget is usually settled before the school year starts, and devices need weeks of work before students see them. Ordering, imaging, asset tagging and enrolment all sit between approval and the first lesson. Wait until January and you are planning a year already under way.

There are three practical pressures. First, supplier stock and delivery times tighten at the end of the year, and everyone is trying to order at once. Second, your own people are stretched, with end-of-year reports, events and staff leave. Third, your finance committee or board needs numbers, and Term 4 is when the current year's evidence is freshest.

Use that evidence. Pull this year's support requests, device failures, damaged units and any outages. A budget built from what actually happened is easier to defend than one built from a vendor's recommendations.

Also check software support dates. Microsoft ended support for Windows 10 on 14 October 2025, according to its published lifecycle information. Any device still on Windows 10 is now outside standard support, so it belongs on the refresh list or needs a documented decision.

How to Separate One-Off Projects From Running Costs

One-off projects have a start and an end, such as a device refresh, a Wi-Fi upgrade or a migration. Running costs repeat every year: licences, support, backup, monitoring and warranty extensions. Separating them shows your finance committee what the school is committing to permanently, and stops projects from hiding recurring costs.

A simple rule helps: every project approval should carry its running-cost tail. A new set of Wi-Fi access points may need ongoing licences and support. A new security tool adds a subscription. A new device program adds management licences and spare stock.

I suggest a three-column view for each line:

• Project cost: what you spend once to get it in place.
• Annual running cost: what it costs every year after that.
• Exit or renewal point: when you can change your mind without penalty.

This makes year-two and year-three budgets far less surprising. It also makes it obvious when a cheap project quietly creates an expensive commitment.

Device Refresh and the Full Lifecycle

A device refresh budget should cover the whole lifecycle, not just the purchase price. That means planning, selection, procurement, configuration, deployment, support, and secure retirement. Schools that budget only for the box tend to find the rest of the cost later, from operating budgets, and often at short notice.

Our products and lifecycle service is built around that view, which we describe as "the lifecycle, end to end": Plan, Select, Procure and warehouse, Configure, Deploy, Support and manage, Refresh and retire. Devices are the easy part. The lifecycle is the work.

Buy, lease or Device as a Service

Buying, leasing and Device as a Service differ mainly in how cost and responsibility are spread. Buying gives ownership and lumpy capital outlay. Leasing spreads the cost, with obligations at the end of term. Device as a Service bundles the device, deployment, support and retirement into one predictable running cost.

None of these is right for every school. Buying suits schools with strong capital funding and in-house capacity. Leasing helps where capital is tight. Device as a Service suits schools that want a predictable cost and one party accountable for the fleet, with the trade-off of a longer commitment and less flexibility mid-term.

Confirm with your auditor how each option is treated in your accounts before you compare them. Then compare on total cost across the full cycle, including support, spares and retirement, not on the price of the box.

Warranty and buffer stock

Match your warranty to your planned refresh cycle, and hold buffer stock so a broken device is swapped the same day. A student or teacher without a working device loses lesson time. Spares sitting imaged and ready in a storeroom are cheap insurance against that.

Budget for three things explicitly:

• Warranty cover that lasts as long as you plan to keep the device.
• Accidental damage arrangements, and who pays for them.
• A pool of spare devices, kept configured and updated, not boxed and forgotten.

Secure retirement and data wiping

Retirement is the line most budgets forget. Old laptops hold student records, staff files and saved passwords. They need a verified data wipe, a record in your asset register, and a responsible end destination before they leave the school.

Retired devices can be securely wiped and recycled through PonyUp for Good, SCCS's program. Data is destroyed, devices are refurbished and resold, and half the profits are converted into meals. By our own count, the program has funded more than 150,000 meals and diverted around 40 tonnes of technology from landfill. For a school, it means the retirement line is handled properly and the outcome is something your community can be proud of.

Student and Staff Device Programs: 1:1 or BYOD

A 1:1 device program gives every student a school-managed device, so the school controls software, security and support. BYOD lets families supply the device, which reduces school capital cost but increases variation in security and support. Most schools settle on a hybrid by year level.

The budget question is who carries which cost. Under 1:1, the school (or families through a levy or lease) funds devices, and the school carries management and support. Under BYOD, the capital cost shifts to families, but the support load often lands on your IT team without a matching budget line.

If you run BYOD in any year level, set a minimum specification, decide how personal devices connect to the network, and be clear about what your support team will and will not fix. Budget for a loan pool so students without a working device are not left behind.

Treat staff devices as a separate cycle. Teachers' laptops carry more sensitive data and are used differently, so they should not be an afterthought to the student program.

Microsoft 365 Licensing for Schools

Microsoft 365 for education is licensed per user, with different plans for staff and students, and eligibility depends on your education agreement. It is a running cost that moves with enrolments and staffing, so review it every year rather than letting it renew by default.

A sensible annual review covers four things:

• Headcount accuracy: leavers, graduates, casual staff and new enrolments should all be reflected.
• Plan fit: education plans differ in security and device management features, so check that each group has what it needs.
• Security features: confirm which protections your plans include before buying separate tools that duplicate them.
• Add-ons: treat any extra product as its own decision, with a clear use case and a small pilot before a school-wide rollout.

Also ask a question that surprises many schools: what is your recovery position for Microsoft 365 data? Retention settings are not the same as a tested backup. If you are planning a migration or tenant tidy-up, we use a simple sequence we call "how a move works": Assess, Migrate, Manage. It avoids risky cutovers during term.

Cyber Security Uplift Without the Fear

Base your cyber budget on the ASD Essential Eight, ranked by the gaps your school actually has. Start with multi-factor authentication, tested backups and patching, then add staff awareness. Aim for measured progress against the maturity levels, not a shopping list of tools.

The Essential Eight is the Australian Signals Directorate's set of eight mitigation strategies, published with the Australian Cyber Security Centre on cyber.gov.au. It includes application control, patching, restricting administrative privileges, multi-factor authentication and regular backups, and it defines maturity levels from zero to three. ASD updates the model from time to time, so use the current version on cyber.gov.au when you set targets.

Our cyber security service follows four disciplines in order, which we call "the whole job, in order": Assess, Protect, Detect, Recover. Assessment comes first because it tells you what is already fine. If something is fine, we say so. We want schools to be safe, not scared.

In budget terms, that usually means:

• Multi-factor authentication: staff accounts first, then administrator accounts, then students where appropriate.
• Backups: separate from your main systems, with a restore test on the calendar, not just a backup job that reports success.
• Patching and endpoint protection: a running cost with someone clearly accountable.
• Staff awareness: short, regular, practical sessions, because most incidents start with a person making a reasonable decision on a bad email.

Independent schools are generally covered by the Privacy Act 1988 and the Notifiable Data Breaches scheme. The OAIC publishes Notifiable Data Breaches reports, and the latest edition shows how breaches are occurring across sectors. Read it before your budget meeting, so your priorities rest on published evidence.

Cyber Insurance: What Your Insurer Will Ask

Cyber insurers typically ask whether you have multi-factor authentication, tested backups, regular patching, endpoint protection and an incident response plan. Answer these honestly before renewal, because gaps can affect cover or premium. Budget the controls first, then the policy, and keep evidence on file.

Proposal forms vary between insurers, so read yours line by line. Your IT provider should be able to help you answer each question accurately and produce the evidence behind it. Overstating your controls on a proposal form can cause problems at the worst possible time, which is when you claim.

Network and Wi-Fi Capacity

Plan Wi-Fi for the busiest classroom hour, not the average. Every added device, online assessment and cloud-based tool increases load on access points, switches and your internet connection. Check coverage, capacity and equipment age before ordering any new devices, or the new fleet will inherit an old bottleneck.

A sensible network review covers:

• Coverage and density: a wireless survey shows where classrooms, halls and outdoor spaces are weak.
• Switching and cabling: enough ports and power for access points, and cabling that suits the equipment you are adding.
• Internet link: capacity for peak use, and what happens if it fails.
• Comms room basics: power protection, cooling and tidy documentation, because the boring stuff, done brilliantly, forever, is what keeps lessons running.

Online assessments make this more than a convenience issue. If a cohort cannot connect reliably during a test, the cost is not only technical.

Choosing a School IT Support Model

The right school IT support model depends on whether you have in-house staff. Onsite suits large campuses, remote suits routine fixes, hybrid combines both, and co-managed lets your IT coordinator keep daily control while a partner covers projects, security and after-hours cover.

Each model answers a different question:

• Onsite: a person on campus for hands-on needs, with cover arrangements for leave.
• Remote: fast fixes for common issues without waiting for a visit.
• Hybrid: remote first, with scheduled and urgent onsite visits.
• Co-managed: your team runs the day-to-day, and a partner adds depth, security, projects and backup for absences.

Our managed services work as building blocks, not packages, so a school can combine fully managed support with co-managed and project work as its needs change. What matters most is that there is real people, not a ticket queue, and a named person who owns the outcome.

Questions to Ask Any IT Provider Before Signing

Before signing, ask who will actually answer the phone, what the monthly fee includes and excludes, how long the term is, and what happens at exit. Ask for named people, documented systems and plain-English reporting. A good provider answers all of these without hesitation.

Here is the list I would take into any meeting:

1. Who will I speak to when something breaks, and will it be the same person next time?
2. What is included in the fee, and what is billed separately?
3. How do you handle the term-time rhythm, including exam periods and the first week of each term?
4. Who is accountable for projects after handover, and will the people who build it also support it?
5. How do you document our systems, and do we own that documentation?
6. How do you report on security, and will you tell us when things are fine?
7. What is your approach to backups, and when did you last test a restore for a school like ours?
8. How do you handle device retirement and data wiping, and what evidence do we receive?
9. What are the term length, notice period and exit arrangements?
10. Can we speak to a school of similar size and type that you have supported for several years?

Project contractors leave. Partners answer the phone. The answers to questions one and four will tell you which one you are dealing with.

A Simple Planning Timeline: October to January

Work backwards from the first day of Term 1. Use October to gather evidence, November to draft and price, December to approve and order, and January to image, enrol and test. Keep the plan short enough that everyone involved can hold it in their head.

• October: audit your asset register, device ages, warranty dates and operating system versions. Collect this year's support history. Ask teachers where technology cost them lesson time.
• November: draft the budget with project and running costs separated. Request quotes, decide on buy, lease or Device as a Service, check your cyber gaps against the Essential Eight, and review insurance requirements.
• December: secure approvals, place device and infrastructure orders, confirm the imaging and enrolment schedule, and book any network work around school closure dates.
• January: receive stock, image and enrol devices, test them on the real network, label spares, and prepare teacher devices first. Do a spot check in the week before Term 1.

If you want a second set of eyes on any of this, the School IT and Cyber Readiness Checklist is a practical place to start, and our education page shows how we support schools.

What I Would Budget For That Most Schools Miss

The line most budgets miss is not a product. It is the quiet week: the stretch of term where nothing goes wrong, no one rings IT and teachers simply teach. We measure ourselves on your quiet weeks, and that changes how I think about budgeting.

My view is that a school IT budget should start with the teacher test: if technology steals a minute of the lesson, it failed. Before you open a single quote, ask a handful of teachers for the moments this year when technology cost them lesson time. A slow login, a Wi-Fi drop in one wing, a trolley of laptops that would not update. Then rank your budget lines against those minutes. It is a less glamorous way to set priorities, and it tends to put networks, spares and support ahead of new hardware.

That is also why I argue against buying on box price alone. The cheapest device with no spares, no imaging plan and no retirement process often costs more over its life. The total cost of a properly managed fleet is the number that matters.

I have seen what the alternative looks like. An independent school came to us needing its network, cyber security and day-to-day IT support handled. We took end-to-end responsibility for all three, and the outcome was simple: staff could return to teaching instead of troubleshooting. That is the standard I would hold any IT budget to.

If you would like a calm, no-pressure view of where your school stands before you lock in 2027, you can book a free school IT health check. We will tell you what is fine, what needs attention and what can wait.

References

• Australian Cyber Security Centre, Essential Eight
• Office of the Australian Information Commissioner, Notifiable Data Breaches
• Microsoft, Product and Services Lifecycle Information

Frequently asked questions

When should a school start planning its IT budget?

Start in October, early in Term 4. Budgets are typically approved before the school year begins, and devices need time to be ordered, imaged and enrolled before Term 1. Starting in October leaves room for quotes, approvals and a calm January.

Should our school buy, lease or use Device as a Service?

It depends on your capital position, in-house capacity and appetite for a longer commitment. Buying gives ownership, leasing spreads cost, and Device as a Service bundles support and retirement into a predictable running cost. Compare total cost across the full lifecycle, and check accounting treatment with your auditor.

How often should school devices be refreshed?

There is no single answer. Base the cycle on warranty length, battery condition, software support dates and how the device is used. Align your warranty with your planned refresh cycle, and keep spares so a failed device does not cost lesson time.

What should be in a school's cyber security budget?

Start with the ASD Essential Eight and rank your gaps. Multi-factor authentication, tested backups and patching usually come first, followed by endpoint protection, staff awareness and an incident response plan. Include the running costs and evidence your cyber insurer is likely to ask for.

What should we do with old school devices and the data on them?

Wipe them securely, keep evidence of the wipe, update your asset register, and recycle or refurbish them responsibly. Through PonyUp for Good, SCCS wipes and recycles retired devices, and the program has funded more than 150,000 meals and diverted around 40 tonnes of technology from landfill.

Keep reading

Essential Eight for schools

The Essential Eight for Independent Schools: Where to Start

16 min read

IT solutions Australia

Comprehensive IT Solutions for Australian Businesses: Powering Growth and Efficiency

14 min read

network solutions Australia

Designing Robust Network Solutions for Australian Businesses: A Strategic Guide

16 min read