When Every Campus IT Request Is Urgent, How Do You Build the Budget?
A leaking roof on the science building and a tired student lounge both need money. Both are fair asks. Only one of them closes a lab next week.
Campus IT budgets put you in the same spot every year. The list is long, and nearly every item has a good reason behind it:
- Lab and classroom machines that are aging but still running
- An LMS or SIS renewal coming up in the spring
- The Exposure Management program your CISO keeps raising
- A department that wants its scheduling system replaced because it frustrates everyone, every day
Every one of those deserves a look. That does not mean they all get funded this cycle.
The real work of budgeting is deciding what gets money now, what gets a plan for later, and what can sit. Three questions help you sort the list before the budget committee sorts it for you.
1. What does waiting a semester cost?
Start with the cost of waiting, not the age of the request.
A faculty laptop that runs a bit slow but is still under support can wait. A weakness that exposes student records cannot. Neither can a system that drops during registration and leaves students and staff stuck.
For each item, picture the next semester without it. Will people lose time? Will the institution carry more risk to FERPA-protected data? Will a manageable problem get more expensive to fix later?
Rank by what waiting would cost, not by how long the item has sat on the list or how loudly its owner asks.
2. Which costs already have a date on them?
Many campus technology costs are predictable long before the bill arrives.
A new cohort or program means accounts, LMS course shells, licenses, and support. Contracts and warranties have dates on them. Grants have end dates, and the equipment they paid for does not stop needing support when the funding stops. Research projects that handle controlled data will bring NIST 800-171 work with them.
None of those are surprises. They are calendar items. Once you see them, you can plan: set money aside for a renewal, spread purchases across quarters, or push a lower-priority project back so the known costs fit.
3. What has the institution already decided to change?
New plans bring new IT needs.
Take a new satellite location or a big expansion of online programs. Along with the program itself come questions about network capacity, identity and access, classroom technology, security monitoring, and who supports it after hours. Leave those questions until the week before launch and you lose the time to compare options and plan the cost.
The same goes for new research centers, shifts in how staff work, or partnerships that bring outside users onto campus systems. Before you decide what gets funded, check that the IT request covers what leadership has already approved.
Use real data, not the loudest voice
The three questions work best with evidence behind them. Exposure Management and CTEM findings show which security gaps are actually exploitable and which are noise. Contract dates show what is coming. Enrollment and program plans show what is changing.
That data turns a budget meeting from a debate about who wants what into a conversation about risk and timing. It also gives you something solid to say to the committee when you recommend that an item wait.
Sort the list into three columns
When you are done, every request should land in one of three places:
- Fund now. Items that protect data, keep core systems like SIS and LMS running, or get more expensive with every month of delay.
- Prepare next. Known costs with a date attached: renewals, cohorts, grant transitions, announced initiatives.
- Can wait. Real improvements that will not create a bigger problem if they sit for another semester.
Campus IT requests rarely are all emergencies, even when they all arrive labeled that way.
The line with the least data
Here is the item most institutions rank with the least evidence: AI. Everyone feels the pressure. Faculty want tools, administrators want efficiency, and the board wants a plan. Very few campuses know how their people actually use AI today, where student data is at risk, or what training would make the biggest difference.
That makes AI hard to place in any of the three columns. Fund too much and you buy licenses nobody uses. Fund too little and people keep using personal tools with no rules.
Where NewPush fits
NewPush works with 75+ institutions supporting 1M+ students and 100k faculty, and we see the same pattern: the requests that survive the committee are the ones backed by real data. Give your AI line the same treatment. Phase 0 of Project NoéMI measures where your people actually stand, so you can rank AI on evidence instead of headlines. It comes with a Trainer login, the practice seat where faculty and staff build governed AI habits.
(Use your institution name even if the form field says company.)
More for campus IT leaders: https://newpush.com/blog?category=higher+education