Findings in this brief are drawn from two decades of fieldwork and data analysis, working alongside hundreds of higher education institutions and watching their operating models evolve through every stage of this arc.
What this brief argues, in six lines.
- 01The administrative side of a college runs projects constantly. Marketing, Advancement, Admissions, Academic Affairs, Student Affairs, Alumni Relations, IT, Operations, and the PMO all run them side by side. This brief covers that administrative work, not classroom teaching or research administration.
- 02How that work is run follows a predictable four-stage arc: Hands-On Coordination, The Visibility Cliff, Operational Drag, and Project Operations at Enterprise Scale[5][6]. Tiers are anchored to enrollment[7], but complexity also scales with colleges, schools, and campuses[8]. A smaller research university with eight colleges and three campuses can sit a tier higher than its headcount alone would suggest.
- 03Two rhythms shape every plan. The academic calendar sets hard windows (census, grades, commencement, accreditation, board cycles), and most major admin work batches into the 12-week summer trough. With the enrollment cliff[9] now in motion, slow execution is measured in students lost.
- 04One shared place to run project work delivers more than faster projects. It frees leadership time from chasing status and firefighting, and redirects it to the strategic decisions that compound across enrollment, advancement, academic operations, student experience, and alumni engagement.
- 05Each stage has its own breaking point: Tier 1 work is invisible outside its owner; Tier 2 departments tighten up but the cross-institution view goes dark (often across six or more overlapping tools); Tier 3 coordination eats more time than the work itself; Tier 4 boards and accreditors expect a live portfolio view. The failure is never the work, it is the coordination around it.
- 06Use the tier-by-tier framework to locate your institution, the interactive explorer to see the challenges and fixes at your stage, and the self-audit to benchmark your operating maturity against peers at your size.
Administrative project work runs constantly. How it is run follows a predictable arc.
Every department runs projects: Marketing, Advancement, Admissions, Academic Affairs, Student Affairs, Alumni Relations, IT, and Operations, with the PMO wrapping around all of it. Most of this work repeats on the academic calendar, and a meaningful slice of it touches more than one department at a time[2][3].
How that work is run follows a predictable four-stage arc. Early on, personal coordination holds everything together. As the institution grows, each department tightens up its own work but the view across departments goes dark. Eventually the time spent coordinating outweighs the time spent on the work itself, and one shared place to run cross-department projects becomes the only way through[5][6]. The tools are the visible symptom at every stage, not the cause.
Departments outgrow their tools but keep using them out of habit. The work still gets done, just not on time, on budget, or in sync across departments.
Four tiers of operating maturity, by enrollment.
Each tier is defined less by enrollment than by how the average department works, and the moment that breaks it. We use enrollment because complexity inside departments, regulatory burden, and program breadth all grow with it.
Hands-On Coordination
Everyone knows what is going on because everyone knows each other. Until they do not.
Project work runs on personal coordination. Department heads know each other, know the work, and hold the plan in their heads. Spreadsheets, shared drives, and email threads are just where bits of it get written down. The real plan lives in one person’s memory.
It stops working the moment one person leaves or goes on sabbatical and work stalls in three different departments because the plan lived in their inbox.
The Visibility Cliff
Each department can see its own work. Nobody can see across them.
Each department has tightened up and can answer for its own work. What has gone dark is the space between them. Most departments picked their own task tool to replace spreadsheets, but the tools do not talk to each other.
It stops working the moment leaders realize the institution is paying for half a dozen project tools and still cannot answer one question: what is in flight across campus right now?
Operational Drag
There is a project office now. The slowest part of any strategic program is no longer the work, it is the coordination across departments.
A project office or transformation team stands up, often a small group reporting to the CIO, COO, or CFO. Most departments have moved past spreadsheets and run their own tools well. The new problem is the time spent coordinating across them.
It stops working the moment a major system migration or accreditation cycle exposes how much time gets spent just chasing status, and the case for one shared place to run cross-department work becomes undeniable.
Project Operations at Enterprise Scale
Project work runs as a real system. Reporting holds up to the board, the regents, and the accreditors.
Project work runs as a real institution-wide system. Every department uses one shared place; specialized systems feed into it; the project office’s standards are followed by default; and the status of strategic programs flows continuously into board, regents, and accreditor reporting.
It stops working the moment one bad execution (a botched system cutover, a missed audit deadline, a stalled campaign) becomes a board-level event, and project status becomes a standing line in board materials.
Find your stage. See the challenges, the impact, and what fixes them.
Drag the slider to your enrollment. The rest of this section shows the project challenges most likely to be hurting your departments right now, what they look like institution-wide, what they look like on the ground, and the fix for each.
The Visibility Cliff
Each department can see its own work. Nobody can see across them.
This is the most common stuck point. Each department picked a tool that fits its own work. The view inside any one department is sharper than it used to be. The view across departments is actually worse than at Tier 1, because the tools do not talk to each other. Leadership reporting becomes a manual reconciliation across tools, and cross-department programs slip on handoffs no one can see.
Pick the department you care about most. The challenges below filter to the ones that team feels first. Pick All to see the full view across departments.
Six different tools, no shared view
Marketing has its tool. IT has its tool. Advancement runs proposals in the advancement system. Admissions runs campaigns in the CRM. Academic Affairs tracks program reviews in spreadsheets. Student Affairs runs programs in a service tool. Alumni Relations runs events in another tool. None of them combine into one picture.
Leaders can ask any one department what is on its plate, but cannot see the whole picture without a manual rollup.
Cross-department project owners spend half their week translating between tools and rebuilding the view in Excel.
Land on one shared place for collaborative project work, and keep specialized systems only where each one is genuinely needed.
Workzone gives every department the same workspace with department-tailored views, and rolls everything up into one view leaders can actually use.
Score your operating maturity in 2 minutes.
Set your enrollment, answer 15 yes-or-no questions, and get a score, your tier, and the highest-impact gaps to close first.
12000 students · Tier 2 · The Visibility Cliff
Mark each statement yes if it is true today, no if it is not.
- 01Critical at T2
Every department (Marketing, Advancement, IT, Admissions, Alumni Relations, PMO) runs collaborative project work in one shared platform, not its own private spreadsheet or task tool.
- 02Critical at T2
Leadership has one portfolio view of every active project across departments, with sponsors, owners, status, and dependencies.
- 03Critical at T1
Requests for internal service functions (e.g., Marketing, IT) come in through one front door with a structured brief, not via email, hallway conversations, or Microsoft Teams DMs.
- 04Critical at T1
Recurring programs (accreditation, recruitment, orientation, commencement, IPEDS, annual fund, reunions, board prep) run from reusable templates, not memory.
- 05Critical at T2
Cross-department projects (SIS or CRM rollouts, campaigns, rebrands, accreditation cycles, new program launches) have one shared plan with a named owner per team.
- 06Critical at T1
Reviews and approvals run through a structured workflow with comments on the asset and a per-version record, not email.
- 07Critical at T1
Project files (brand, policies, accreditation evidence, donor proposals, admissions packets, project plans) live attached to the project with versioning, not scattered across drives.
- 08Critical at T2
Outside partners (agencies, accreditors, auditors, implementation partners, consultants) work in the same workspace as internal teams, with controlled access.
- 09Critical at T2
Department heads can show committed work versus team capacity in real time, by person and by team.
- 10Critical at T2
Leadership can see, on demand, which projects are on track, at risk, or slipping, with the late milestones, blocked tasks, and overdue approvals behind the status.
- 11Critical at T2
When one project depends on another, that link is tracked in the system, not in a program manager’s head.
- 12Critical at T2
A new employee in any department can land and contribute in their first two weeks because templates, owners, and current state are documented in the system.
- 13Critical at T2
Policy changes, brand updates, system rollouts, and template changes go live on the same day across every campus, branch site, and online division, with one shared go-live view.
- 14Critical at T3
When a project misses deadlines or budget, the team can clearly identify the root cause of the variance.
- 15Critical at T3
Leaders can accurately forecast project timelines, budgets, and resource needs before issues occur.
The operating layer that resolves these challenges.
Most of the failures above are not strategy failures. They are coordination failures across departments, tools that do not talk to each other, recurring work rebuilt from memory, approvals stuck in email, bandwidth decided by gut feel, outside partners bolted on through workarounds.
Project management software does not replace the systems your teams already rely on for student records, advancement, alumni, and academics, and it should not try to. It sits alongside them and runs the collaborative work that wraps around them. The capabilities below are what a platform like Workzone delivers, mapped back to the challenges above[5][6].
One shared place every department runs project work
One platform for collaborative work across every department, with each one getting its own view inside it. Specialized systems for the SIS, LMS, CRM, advancement, and alumni database stay where they belong.
One front door for project requests
A simple request form with the right questions, automatic routing to the right team, and a status link the requester can check.
Reusable playbooks for recurring work
Reusable templates for every program that runs more than once, with the right teams named as owners and dates pre-wired to the academic calendar.
One list of every project across campus
A live view of every active project, filterable by department, sponsor, or program. The board view becomes a saved view rather than a quarterly rebuild.
Online proofing and structured approvals
Reviews run in order, with comments pinned on the asset, named approvers, deadlines, and a permanent record of every version.
Who has bandwidth, at a glance
A forward view of committed work versus available time, by person and by team, so commitment conversations start from data.
A clean way to work with outside partners
Controlled access for outside partners so their work shows up in the same view as in-house work, with the same review and approval flow.
Reporting the board and accreditors trust
Consistent program status, milestones, and risks that roll up from project to portfolio. Enrollment, academic, and financial KPIs keep coming from the systems built for them.
How to read your tier if you are an R1, an SLAC, a community college, or a multi-campus system
The four-tier model is anchored to enrollment because complexity broadly scales with it, but enrollment alone misses how different institution types actually run. Use the segments below to adjust where you sit on the framework. Most readers find themselves a half-tier above or below where pure headcount would put them.
R1 research universities
Doctoral universities with very high research activity, usually 15,000+ students, often multi-campus with academic medical centers, 10+ colleges, and large central administrations. Carnegie R1.
Almost always Tier 3 or Tier 4 on the administrative side, regardless of total enrollment. The research enterprise is carved out of this brief, but its volume of administrative project work (faculty hiring, sponsored programs ops, capital construction) lands here too.
Punch above their headcount. A federated college structure and a medical center add governance layers that smaller institutions do not face.
R2 and doctoral universities
Doctoral universities with high research activity, typically 8,000–25,000 students, fewer colleges than R1s, less central infrastructure.
Usually Tier 2 or Tier 3. Often have a PMO in name but not yet in function, the classic Operational Drag profile.
Sit close to where their headcount puts them. The growing research portfolio is the most common stressor on administrative project capacity.
Regional comprehensive (master's) universities
Master's-granting universities, often public, usually 5,000–20,000 students, frequently with branch campuses and online divisions, heavy state-system reporting.
Most sit in Tier 2 with one foot in Tier 3 because of state-system and branch-campus reporting demands that exceed what their headcount would suggest.
Punch above their headcount because of branch campuses, online divisions, and state-system office relationships that add reporting layers.
Small liberal arts colleges (SLACs)
Baccalaureate colleges, often residential, usually under 3,000 students, lean central administrations, deeply embedded shared governance.
Sit in Tier 1 by headcount but routinely face Tier 2 problems on advancement campaigns and accreditation. Often hit visibility-cliff symptoms two or three years earlier than the framework would predict.
Punch above their headcount. Heavy shared governance, board-level visibility on small projects, and an outsize advancement function add complexity.
Community colleges and two-year institutions
Open-access institutions, often multi-site within a district, large workforce and dual-enrollment operations, state-system or district governance.
Map by district headcount, not by individual campus. A multi-site district often sits a tier higher than any one of its sites would alone.
Punch above headcount on rollout and consistency (a policy change has to land at every site at once) and on state and federal compliance reporting.
Multi-campus public systems and system offices
State system offices and multi-campus systems (e.g., a UC, SUNY, or Texas A&M System layer), coordinating across many constituent institutions.
Always Tier 4 at the system layer. Constituent campuses sit at their own tier and report up through the system office on the project layer that crosses them.
An entirely different complexity profile. The system office is itself a Tier 4 operation managing a portfolio of Tier 1–Tier 4 constituent institutions.
Carnegie Classification[8] and IPEDS[7] are the standard references for placing your institution. When in doubt, read the inflection point for each tier and pick the one whose breaking point is happening to you right now.
Why we publish on higher education.
Workzone is project management software built for departments running collaborative project work side by side, Marketing, Advancement, Admissions, Academic Affairs, Student Affairs, Alumni Relations, IT, and Operations. We have more than 23 years of real-world experience and a 7-year average customer lifetime, focused on organizations where work has to land consistently across many teams.
Higher education is one of the categories where that focus matters most. Colleges and universities run real cross-department complexity, an aggressive cadence of recruitment, campaigns, system modernization, and accreditation, and board- and regulator-grade reporting pressure across every department, alongside, not inside, the specialized systems each one depends on.
We publish briefs like this one because the project-management conversation is one of the highest-leverage ones a department leader can have, and it is rarely had with the specificity it deserves.
See what an institution-wide project layer looks like in Workzone.
Book a 30-minute walkthrough with a Workzone higher-education specialist. We will map the framework above to your current tier and show you how department leaders and PMO teams at other institutions run their work side by side in one shared platform.
"We serve 11 departments inside the College of Agriculture as well as Purdue extension offices located in all 92 counties in Indiana. With 35 people on my team serving over 300 individual clients, improving client relations was my number one goal. I probably researched over 50 different solutions and finally settled on Workzone. As a department we now work better together to build stronger communication plans and our clients could not be happier."
Sources.
- [1]EDUCAUSE: Top 10 IT Issues and research on enterprise IT, data, and digital transformation in higher education. https://www.educause.edu/research-and-publications/research/top-10-it-issues
- [2]NACUBO: Operating model and administrative leadership research for college and university business officers. https://www.nacubo.org/
- [3]Deloitte: Higher Education Industry Outlook on operating model and digital transformation. https://www2.deloitte.com/us/en/industries/public-sector/higher-education.html
- [4]CASE: Voluntary Support of Education and benchmarks for advancement and capital campaigns. https://www.case.org/
- [5]Project Management Institute (PMI): Pulse of the Profession on portfolio and program management practices. https://www.pmi.org/learning/library
- [6]Gartner: Collaborative work management and strategic portfolio management research. https://www.gartner.com/en/information-technology/insights/program-portfolio-management
- [7]National Center for Education Statistics (IPEDS): Enrollment, staffing, and institutional characteristics across U.S. degree-granting institutions. https://nces.ed.gov/ipeds/
- [8]Carnegie Classification of Institutions of Higher Education: Standard framework for grouping U.S. colleges and universities by mission and size. https://carnegieclassifications.acenet.edu/
- [9]Inside Higher Ed and The Chronicle of Higher Education: Ongoing reporting on the demographic cliff, leadership turnover, and institutional consolidation. https://www.insidehighered.com/
- [10]AGB (Association of Governing Boards of Universities and Colleges): Guidance on board effectiveness, cabinet cadence, and strategic-plan oversight. https://agb.org/