Enrollment Is the Risk Everyone Watches. The Spreadsheet One Person Maintains Is the One That Actually Breaks
Higher ed watches enrollment decline but ignores the spreadsheet one person maintains. 39% admin growth, 58% burnout, and processes that break when someone leaves. The operations deficit is the risk nobody presents.
Key Takeaway
This article examines two coexisting risks facing higher education institutions: enrollment decline and operational fragility. Drawing on NCES data showing 39% growth in administrators per 100 students (1993-2007), EDUCAUSE 2024 survey data indicating 58% IT staff burnout and 70% reporting excessive workload, Goldwater Institute findings of 129 administrators per 100 faculty at UNC-Chapel Hill, and AEI IPEDS analysis, it argues that while enrollment decline is a visible strategy problem, operational fragility — undocumented processes, single-person dependencies, manual spreadsheet workflows — is an invisible architecture problem requiring a fundamentally different response.
Everyone in higher education is watching enrollment numbers. Rightfully so — declining enrollment threatens institutional survival, and the data gets worse every year.
But there's a second risk that doesn't show up in board presentations.
There's a spreadsheet at your institution that tracks compliance deadlines for every course offered online. It lives on someone's desktop. Maybe it's in a shared drive, but only one person actually updates it. Everyone knows this. Nobody talks about it.
When that person takes a two-week vacation, nothing happens — because nothing is due. When that person leaves for a different job, everything happens at once.
Enrollment decline is a strategic crisis with strategic responses — new programs, partnerships, marketing spend. The spreadsheet problem is different. It's an operational architecture problem — invisible, compounding, and far harder to fix with a budget line item. And while institutions pour resources into the enrollment fight, this second risk is eating them from the inside.
The numbers nobody wants to publish
Between 1993 and 2007, the number of full-time administrators per 100 students at American universities grew by 39%. Employees engaged in teaching, research, or service grew by 18%. Administrative spending now accounts for nearly a quarter of total university expenditure, and it increased 6.3% between 2016 and 2021 alone.
You'd think that doubling the administrative workforce would make operations smoother. It hasn't.
In 2024, EDUCAUSE surveyed over 400 IT professionals across higher education. 58% reported burnout. 70% described their workloads as "somewhat excessive." 68% said workloads had increased over the prior year.
So the institution hired more administrators, spent more money, and the people doing the work are more burned out than ever. Something in the model is broken.
The compounding problem
Here's what most enrollment-focused conversations miss: operational debt compounds.
Every semester, an institution adds courses, modifies programs, updates compliance requirements, onboards adjuncts, and generates reports for accreditation. Each of these creates a small process. A checklist. A form. A recurring task that someone absorbs into their workflow.
None of these processes, individually, is a crisis. But they accumulate. And unlike financial debt, operational debt doesn't show up on a balance sheet. It shows up as:
- The accessibility audit that was supposed to happen last quarter but got pushed because the person who runs it was also handling LMS migrations.
- The 47 courses still listed in the catalog that haven't been offered in three years, because cleaning the catalog requires cross-referencing three systems that don't talk to each other.
- The enrollment report that takes 6 hours to compile every month because it involves pulling data from the SIS, merging it with LMS completion rates in Excel, and manually formatting it for the provost's office.
None of this is visible until it breaks. And when it breaks, the response is always the same: hire someone, or ask the existing team to absorb one more thing.
Why more staff isn't the answer
The instinct to hire is reasonable. If the work exceeds capacity, add capacity. But there are three problems with this in higher education:
First, the hiring timeline is wrong. Academic hiring cycles run 3-6 months minimum. The operational need is immediate. By the time the new hire is onboarded, the acute problem has either been patched (poorly) or has caused visible damage.
Second, institutional knowledge doesn't transfer. The person who left didn't just do a job — they were the system. Their knowledge of which reports the provost actually reads, which compliance deadlines are real versus soft, which workarounds are necessary because the SIS doesn't support a particular workflow — none of that is documented. The new hire starts from scratch.
Third, the economics don't scale. At UNC-Chapel Hill, there are 129 administrators for every 100 faculty members. Yale has more administrators than undergraduate students. Adding headcount has a ceiling, and many institutions hit it years ago.
83% of institutions surveyed by EDUCAUSE in 2024 said they're considering or implementing cost-reduction solutions through new technologies. The assumption that adding technology automatically reduces burden hasn't borne out in higher ed. Optimism isn't a strategy.
What an operations architecture actually looks like
The phrase "digital transformation" has been so thoroughly strip-mined of meaning that I hesitate to use it. So I won't. Instead, let me describe what a functional operations architecture does:
It makes the implicit explicit. The process that lives in one person's head gets codified — not in a wiki that nobody reads, but in a system that actually executes. The compliance audit doesn't depend on someone remembering to run it. It runs.
It produces receipts, not promises. When a course is built, you see every step: content created, accessibility checked, LMS pages generated, quizzes formatted. Duration: 4 minutes. Cost: $0.31. This isn't a dashboard. It's an audit trail.
It separates knowledge from dependency. The institutional knowledge about how to format a provost's enrollment report doesn't disappear when someone leaves. It's encoded in a process that any authorized person can trigger.
None of this requires a specific technology. It requires a specific mindset: treat operations as architecture, not as a collection of individual jobs.
The fragility test
Here's a diagnostic you can run this week. Pick any three operational processes at your institution — course creation, compliance reporting, enrollment data compilation, adjunct onboarding, anything — and ask two questions:
- If the person who runs this process left tomorrow, how long before someone else could do it at the same quality? If the answer is "weeks" or "we'd have to figure it out," you have a fragility problem.
- Can you tell me, right now, what this process cost the institution last month in staff hours? If the answer is "no idea," you have a visibility problem.
Fragility and invisibility together are the operational deficit. The institution is spending more than it knows on processes that depend on people it can't afford to lose.
What changes the math
I'm not going to pitch you software. Not yet. What I want you to sit with is the structural argument:
Higher education's cost crisis is usually framed as a revenue problem (enrollment is declining) or a spending problem (tuition is too high). But there's a third frame that gets almost no attention: it's an efficiency architecture problem. The institution does enormous amounts of operational work, most of it manually, much of it invisibly, and almost none of it is designed to survive personnel changes.
The institutions that figure this out first won't just save money. They'll be able to reallocate human attention to the work that actually requires human judgment — advising students, designing curriculum, building relationships with donors — instead of burning it on tasks that are important but mechanical.
That reallocation is the real prize. Not cost savings. Capacity.
The question isn't whether your institution has an operations deficit. It does. Every institution does.
The question is whether you know where it is — and what it's costing you.
Data sources: NCES Digest of Education Statistics; EDUCAUSE IT Workforce Survey 2024; American Enterprise Institute analysis of IPEDS staffing data; UNC-Chapel Hill administrator-to-faculty ratio via Goldwater Institute; Yale administrator count via Bowdoin Review analysis.
About the author: Yogesh Pandey is the founder of Quad, where he's building operational systems that work like trained staff for EdTech institutions. Before Quad, he spent 17 years implementing learning systems for institutions that kept running into the same problem: the technology worked, but the operations around it didn't.