A program revision is cleared by the curriculum committee in March. It reaches the registrar in June. Nobody lost it. It moved through four inboxes, two shared drives, and one spreadsheet that three people maintain and no one owns. The work got done. It just took a season to travel a distance that should have taken a week.
This is the efficiency gap, and higher education has stopped noticing it.
The efficiency gap in higher education is the distance between what the system of record was built to do and the structured administrative work that happens at its edges: the approvals, exceptions, routing, and documentation that run on email, spreadsheets, and PDFs because no system was ever assigned to own them. It is not a technology failure. It is a category of work that the ERP, the SIS, and the LMS were never designed to carry.
For years, this was the work everyone did and no one measured. That has changed. EDUCAUSE ranked administrative simplification as the number two issue on its 2025 Top 10 list of institutional priorities, and named the target without euphemism: administrative bloat. The sector is now saying out loud that streamlining processes, data, and technologies is a strategic problem, not a back-office chore.
The difficulty is that the people who would close the gap are already past capacity. In the 2025 EDUCAUSE workforce study, 75 percent of higher education technology leaders described their workloads as excessive, up from 70 percent the year before, and named insufficient staffing as the most common cause. More than a third said their institution had taken no action to address it. You cannot clear an efficiency gap by adding work to the team that is already drowning in it.
Banner, Workday, Ellucian, PeopleSoft, and Colleague do what they were built to do. They maintain the records, process transactions, and enforce the rules for standard processes. Ask any of them to route a non-standard purchase that falls outside policy, track an IRB amendment across three reviewers, or assemble a curriculum decision trail for an accreditor eighteen months later, and you find the edge. The transaction the system understands is fine. The judgment, the exception, and the handoff around it are not.
Institutions are spending to modernize the core. The Tambellini Group reports that selections of SaaS-architected student systems rose from 1 percent in 2014 to 30 percent by the end of 2024 and calls modernizing administrative technology a top priority for resource-constrained institutions. But a new ERP does not absorb the work at the edges. It re-platforms the center and leaves the email chains exactly where they were. The gap survives the upgrade.
The gap is structural, not a matter of effort, and three forces hold it open.
The result is predictable. Departments solve their own problems with the tools they can buy on a credit card, and the institution accumulates a layer of ungoverned work it cannot see.
The cost of the efficiency gap is rarely a line item, which is why it survives budget cycles. It shows up instead in four places that leadership feels but does not always trace back to the source.
When evidence of a decision lives in six inboxes, assembling it for a reaffirmation visit becomes a project rather than a query. The same EDUCAUSE panel lists "too many shadow systems and data silos" among the primary reasons institutions replace their ERP at all, which tells you how much undocumented process accumulates at the edges before anyone acts.
Every spreadsheet tool a department adopts to bridge a gap carries a renewal, a security question, and a place for student data to land outside governance. Across organizations, more than one-third of applications now qualify as shadow IT, according to Zylo's 2024 SaaS Management Index. The CIO discovers the sprawl during an audit, not before it.
An applicant who waits three weeks for a transfer-credit evaluation has often already accepted an offer elsewhere. The revenue stakes are not abstract: the average tuition discount rate at private institutions reached 56.3 percent for first-time, full-time undergraduates in 2024-25, while net tuition revenue rose just 1.4 percent after inflation. When margins are that thin, every manual handoff that loses a student is a cost the institution cannot absorb.
Time spent chasing approvals is time not spent on the work the institution hired these people to do. The gap taxes the staff you can least afford to slow down.
Operational drag now meets an existential demographic. WICHE projects the number of high school graduates will peak in 2025 and then decline about 13 percent through 2041, and Moody's opened 2026 with a negative outlook, warning that "a shrinking population of high school graduates" is creating an increasingly difficult operating environment. Public confidence has fallen at the same time, with the share of Americans expressing confidence in higher education dropping from 57 percent to 36 percent in a decade. An institution under that much pressure cannot afford an operating model that runs on institutional memory and luck.
Closing the gap does not mean replacing the ERP, and it does not mean asking IT to build every workflow by hand. It means giving the work at the edges a place to run that is governed from the first deployment rather than retrofitted with control after the fact.
A governed execution layer sits alongside the system of record. The process owner builds and owns the workflow. IT governs the standards it runs under. Each step routes to the correct approver, every decision is recorded with a timestamp and an owner, and a complete record exists on demand instead of on request. Kissflow is the platform built for this layer: an enterprise application platform that uses AI and visual development to build, automate, and govern the processes the ERP was never meant to handle.
The mechanism matters more than the label. When a curriculum revision moves through a governed workflow instead of an inbox, the question an accreditor asks eighteen months later becomes a report, not a search. When a department needs a tracker, it builds one inside the governance model IT already manages instead of buying one IT cannot see.
The efficiency gap is too broad to close all at once, and trying to is how transformation programs stall. Start where the pain is sharp and the boundary is clear: a single cross-department process that runs on email today and produces no record anyone trusts. Prove the layer there, then let it compound.
It is the gap between what the ERP or SIS was built to do and the structured administrative work that happens around it: approvals, exceptions, routing, and compliance documentation that run on email and spreadsheets because no system owns them. EDUCAUSE describes the same problem as administrative bloat, and ranked simplifying it as the second-highest institutional issue for 2025.
No. A governed execution layer runs alongside Banner, Workday, or Ellucian, not instead of them. The ERP remains the system of record. The execution layer handles the exception-heavy, cross-department work the ERP was never designed to carry.
Shadow IT solves the same problem without governance. A spreadsheet tool gives a department flexibility but no audit trail, no IT visibility, and no control over where student data lands. A governed execution layer gives the department the same flexibility inside the standards IT already manages.