ServiceNow SPM for Higher Education: Portfolio of Record
- David Holstein
- 2 days ago
- 12 min read
TLDR: ServiceNow SPM higher education deployments fail for a reason that has nothing to do with the product. Enterprise portfolio guidance assumes a single intake path, a role-based resource pool, a rolling approval process, and a fiscal calendar that bends to the business. A campus has none of those things. Demand arrives through five front doors. Capacity is a handful of named people. The academic calendar is immovable. Approval runs through multiple governing bodies with different memberships and different meeting schedules. Funding source changes what a project is even allowed to do. This piece walks through each of those realities, what SPM has to model to survive them, and why the portfolio of record is the first deliverable rather than the last.
The Project Count Depends on Who You Ask
Ask a higher education CIO how many projects the IT organization is currently committed to. You will get a number. Then ask the director of strategic initiatives the same question, and you will get a different number. Ask the college IT directors and you will get a third set of answers that includes work central IT has never heard of.
None of those people are wrong. They are counting different things because there is no single place where commitment gets recorded. The PMO has a spreadsheet. The CIO has a slide from the last governance meeting. The colleges have their own lists. Somewhere there is a shared drive with a folder called Project Tracking that stopped being accurate two fiscal years ago.
This is the condition ServiceNow SPM for higher education is supposed to fix. Most institutions we talk to have already bought the entitlement or are about to. Very few have a clear picture of what has to be true about the configuration for it to survive contact with a campus.
What follows is what we see across R1 and large public institutions. The pattern is consistent enough to plan around.
Five Front Doors and No Queue
Enterprise portfolio management assumes work enters through a request process. On a campus, work enters through whatever channel the requester has access to.
A department chair emails the CIO directly. A dean raises something at a cabinet meeting and it becomes a commitment before IT has scoped it. A compliance deadline arrives from the general counsel and is not a request at all. A college submits a line item during the budget cycle. And a faculty member catches an application administrator in a hallway, and three weeks of unplanned work begins with no record anywhere.
Each of those paths is legitimate. That is the part that gets missed. The hallway request is not a process failure, it is how a distributed institution with real relationships actually works. The problem is not that people ask in different ways. The problem is that only some of those asks produce a record, so the portfolio reflects the requests that happened to arrive through the formal channel.
The move is not to shut the doors. It is to make every door lead to the same queue. Demand in ServiceNow SPM is the mechanism for that, and the configuration decision that matters most is how little you require at the point of entry. If intake asks for a business case, a cost estimate, and a sponsor signature before a request can be recorded, the hallway ask will never make it in and you are back to a partial portfolio.
We recommend intake that captures the requester, the unit, the outcome being asked for, the constraint driving the date, and the funding source. Five fields. Everything else gets added during triage by someone whose job it is to add it. The scoring model runs after the record exists, not as a condition of creating one.
What ServiceNow SPM for Higher Education Has to Model
Once demand is in one place, the next question is what the system does with it. This is where enterprise defaults do real damage, because three constraints that are background noise in a corporate portfolio are load-bearing on a campus.
Capacity is named people, not roles
Corporate resource management works in role pools. You need four hundred hours of integration developer, the pool has six of them, the plan is feasible.
Higher education does not work that way. There is one person who understands the student information system integration layer. There is one person who owns identity and access. There is one person who has ever successfully modified the degree audit interface. Those people are not interchangeable with anyone, and they are named in every project plan the institution has.
If you configure resource management with role-based pools, SPM will tell you the portfolio is feasible when it is not. The capacity model has to run at the person level for the small number of individuals who are actually the constraint, even if the rest of the organization is planned at the group level. That is not the textbook approach. It is the accurate one.
There is a second half to this. Most higher education IT staff are split between operations and projects, and the split is rarely documented. A person who is nominally fifty percent available to projects is functionally twenty percent available during incident-heavy weeks. Building an allocation model that ignores operational load produces a plan that fails quietly, one week at a time.
The academic calendar is a portfolio constraint
Term start. Registration. Census day. Finals. Commencement. Add-drop. Financial aid disbursement. These are not preferences. Nothing goes into production near them, and in practice the freeze extends further on both sides than anyone admits in planning.
In an enterprise portfolio, blackout windows are a change management detail. In higher education, they are a portfolio-level constraint that determines how much work the institution can absorb in a year, full stop. An institution with heavy freeze coverage does not have twelve months of delivery capacity. It has a materially smaller number, and the portfolio should be planned against the real number rather than the calendar number.
Encoding those windows in the portfolio, rather than discovering them project by project, changes the conversation with governance. It stops being a debate about whether a specific project can go live in late August. It becomes a shared understanding of how much the institution can take on at all.
Funding source changes the rules
Two projects of identical scope and identical cost are not the same project if one is funded by the general fund and the other by a grant. Restricted funds carry sponsor requirements and spending deadlines. Gift funds carry donor intent. Auxiliary funds belong to a unit that expects to control the decision. Student fee funds come with a committee that approves the use. One-time state money has to be spent in the year it arrives, which is why so much of it goes to work that was never sequenced.
Carry-forward is its own dynamic. Work that gets funded in June because a unit is about to lose the balance is not work that the portfolio prioritized. It is work the calendar prioritized.
SPM should carry funding source as a first-class attribute on demand and on the project, because it drives approval path, spending constraints, and reporting obligations. When it is missing, the portfolio can tell you what is being worked on but not what is actually allowed to move.
Approval Is Not One Step on a Campus
The default approval model is a single approver, possibly two. Higher education routinely runs work through an IT governance council, a provost-level prioritization body, a data governance group for anything touching student records, a security review, an accessibility review, and in some cases a faculty senate technology committee. Those bodies have different memberships and different meeting cadences, and several of them do not meet during the summer.
This is where a lot of well-intentioned portfolio work goes to die. Institutions map the approval chain accurately, encode all of it, and produce a workflow so heavy that people route around it to get anything done. Now there are two portfolios again, the official one and the real one.
The version that survives is tiered. Small work with a known owner and a known funding source gets a light path. Work that crosses units, touches protected data, or commits a named constraint person gets the full sequence. The distinction has to be defined by attributes the intake form actually captures, or the tiering becomes a judgment call and the judgment call becomes a bottleneck.
EDUCAUSE named this dynamic directly in its 2026 Top 10, which identified measured approaches to new technologies as a priority and pointed at stronger and more consistent IT governance as the mechanism. The same report notes that most technology leaders say quick-fix technology purchases are common at their institution, a finding drawn from EDUCAUSE research on institutional debt. Quick-fix purchasing is what happens when there is no visible queue. If the portfolio cannot show what is already committed, every new request looks affordable.
Strategic Plan Alignment Is the Reporting Layer That Earns the Budget
Every institution publishes a strategic plan with named pillars. Student success. Research excellence. Operational effectiveness. Community and belonging. Those pillars are public, the board knows them, and the president refers to them constantly.
Almost no IT portfolio is tagged to them.
This is the highest-leverage configuration decision in a higher education SPM deployment and it costs almost nothing. Tag demands and projects to strategic pillars at intake. Report investment by pillar. When a vice president asks what technology is doing to support the research mission, the answer stops being a narrative and becomes a number with a list behind it.
It also works in the other direction, which is the part institutions underuse. If eighty percent of the IT portfolio maps to operational effectiveness and the institution has been telling the board that student success is the top priority, that is not a reporting problem. That is a finding, and it is a much easier conversation to have with a chart than with an opinion.
Reporting on the mission is also the thing that makes the portfolio survive a leadership change. A portfolio that reports on projects is an IT artifact. A portfolio that reports on institutional priorities is an institutional one.
Start With the Portfolio of Record
The instinct with SPM is to configure the whole thing. Demand scoring, project workspace, resource plans, financials, agile boards, time cards, executive dashboards. All of it is in the product and all of it is available.
We advise against that, and not because of scope discipline for its own sake. It is because the first thing an institution needs is not a better process. It is one list.
The portfolio of record is a complete inventory of what the institution is currently committed to, with an owner, a funding source, a status, and a strategic tag on each item. Nothing more. It is unglamorous and it is the deliverable that changes the conversation, because until it exists every prioritization discussion is a debate about whose list is right.
Once the list exists and people trust it, the next capabilities have something to attach to. Scoring means something when the queue is complete. Resource plans mean something when they run against the real constraint people. Dashboards mean something when the underlying data is not a snapshot someone assembled by hand the week before the meeting.
There is a consistent theme here with the other platform work we do in higher education. CMDB health determines whether ITOM delivers anything. Knowledge governance determines whether AI deflection works. The portfolio of record determines whether SPM reporting means anything. The foundational layer is boring and it is the difference between a platform that gets used and one that gets abandoned.
Where ServiceNow SPM Deployments Stall in Higher Education
Three failure patterns account for most of what we see.
Time tracking arrives too early. Time tracking is where higher education SPM implementations most often break, and the reason is cultural rather than technical. Asking staff who have never logged time to start logging it, in the same release that introduces a new intake process and a new governance workflow, guarantees that the change management budget gets spent on the least valuable capability. There are real reasons to get there eventually, including sponsored effort and capitalization, and there is almost never a reason to get there first.
The scoring model becomes a negotiation. Institutions build elaborate weighted scoring models, and then the first time the model ranks a vice president's request below a compliance item, the weights get adjusted. A simple model that is applied consistently outperforms a sophisticated model that gets renegotiated, because the value of scoring is not precision. It is a defensible and repeatable rationale.
The portfolio is built for IT instead of the institution. If SPM only contains central IT work, it will show a partial picture from the day it goes live, and the units whose work is missing will keep running their own lists. Extending intake to HR, student affairs, advancement, and the colleges is the same orchestration argument that applies everywhere else on the platform. You are not consolidating those units into central IT. You are giving their work a shared record so the institution can see itself.
FOR THE CIO READING THIS
The pressure you are under is to produce a roadmap. The board wants three years. The provost wants to know what the AI investment buys. Your own team wants to know what gets dropped.
A roadmap built on an incomplete inventory is a forecast built on a guess, and it will be wrong in the specific way that damages credibility, by omitting commitments that were already made. Get the portfolio of record first. It is a smaller ask, it is defensible, and it is the only thing that makes the roadmap survive its first budget cycle.
Where This Connects to the Rest of the Platform
SPM is not a standalone purchase for most institutions. It usually shows up after ITSM has matured, when the institution has enough operational credibility to be asked harder questions about investment. That sequence is worth naming, because SPM works far better on an instance that is already healthy.
If the platform has drifted since go-live, portfolio reporting will inherit the drift. We wrote about that pattern in our piece on closing the gap between the platform you bought and the one you are running. If the institution is still working through the operational maturity that precedes portfolio work, the ITSM modernization path in higher education covers that ground. And if the institution recently moved up a licensing tier and is looking for where the value is, the ITSM Advanced use case walkthrough is the closest companion piece to this one.
EDUCAUSE also placed scenario modeling and forecasting on the 2026 Top 10 list, framed as moving institutions from reactive to proactive planning. That capability sits directly on top of portfolio data. An institution that cannot describe its current commitments cannot model what happens to them under a budget reduction, which is a question a growing number of CFOs are asking.
Frequently Asked Questions
What is ServiceNow SPM in a higher education context?
ServiceNow SPM is the strategic portfolio management application that handles demand intake, prioritization, project execution, resource allocation, and portfolio reporting. In higher education the value is less about project execution mechanics and more about producing a single institutional record of what technology work is committed, who owns it, what funds it, and which strategic priority it serves.
Do we need ITSM working well before we deploy SPM?
Not strictly, but it helps considerably. SPM depends on the same platform hygiene everything else does, including clean user and group data, an accurate organizational structure, and a functioning change process. Institutions with significant platform drift usually get more value from addressing that first, because portfolio reporting built on unreliable data will not be trusted.
Should the portfolio include work outside central IT?
Eventually, yes. The institutional value of the portfolio comes from completeness. Starting with central IT is reasonable because that is where governance authority already exists, but a portfolio that permanently excludes college IT, HR, advancement, and student affairs will always show a partial picture. Plan the extension path from the beginning even if the first phase is central only.
Do we have to implement time tracking?
No, and most institutions should not start there. Time tracking is worth doing when there is a specific requirement driving it, such as sponsored effort reporting, capitalization, or a chargeback model. Introducing it alongside a new intake process and new governance workflow tends to consume the change management capacity that the more valuable capabilities need.
How do we handle demand that arrives outside the intake process?
Record it anyway. The goal is a complete portfolio, not a well-behaved one. Someone in the strategic projects function should be able to enter a request on behalf of a requester in under two minutes, which means intake has to stay short. Enforcement of the process comes later, after people trust the list, and it works better as a reporting expectation than as a gate.
What does the first phase of an SPM deployment usually deliver?
A configured SPM foundation, demand intake with a scoring model, an idea and approval workflow, the project portfolio of record, project workspace with status and milestones, an executive dashboard, and baseline resource allocation. That combination gives the institution one queue, one list, and one view without committing to financial management or time tracking before there is a reason to.
The Honest Summary
ServiceNow SPM for higher education is not difficult because the product is complicated. It is difficult because campuses run on constraints that enterprise portfolio guidance does not account for, and configuring around those constraints is a design decision rather than a deployment task. Intake has to be short enough that the hallway request survives it. Capacity has to be modeled on the named people who are actually the constraint. The academic calendar has to be a portfolio input rather than a scheduling surprise. Approval has to be tiered or it will be bypassed. Funding source has to be visible or the portfolio will show work that cannot move.
Get those right and the portfolio of record follows, and everything worth building on a portfolio needs that list to exist first.
Talk it through with us
If you are looking at SPM and want to work through what the intake model, capacity model, and governance path should look like at your institution, we are happy to have that conversation. No deck required.
Start a discovery conversation with Bettera or read more about our roadmapping engagements.
About the author. David Holstein is the founder and CEO of Bettera, a ServiceNow consulting and implementation partner built exclusively for higher education. Bettera works with colleges and universities on ITSM, ITOM, CSM, SPM, and AI governance, with an AI-native delivery model.
