ServiceNow SPM Managed Support

What a Managed Support Engagement for SPM Covers

Strategic Portfolio Management in ServiceNow holds the records an organisation uses to decide what work to fund and to see whether that work is delivering: demands, projects and programs, portfolios, resource pools and allocations, budgets and cost plans, and the scoring that ranks one proposal against another. A managed support engagement with Oblytech keeps those records accurate and the configuration behind them stable once the implementation team has left. The work is deliberately unglamorous. Demand records get owners and sponsors. Project records stay current enough for the forum to trust them. Resource pools reflect who is actually available. Scoring criteria change only when the portfolio lead decides they should, and reports are retired when nobody reads them.

The engagement does not make portfolio decisions. Which demands are approved, which projects are paused and how budget is split between lanes remain decisions for the sponsor and the forum. Support exists so that those decisions are made on data that is complete and comparable, and so that the platform owner is not the only person who knows how the instance is configured.

Starting situations a managed team usually inherits

Most organisations do not ask for ongoing support on the day they go live. They ask after the first few forum cycles, when the symptoms of drift appear. The intake queue holds demands with no sponsor that nobody feels able to close. Projects marked as active have had no time booked against them for a long stretch, while others consume budget without a current status. A resource pool still lists people who have moved teams, so allocation reports show capacity that does not exist. Two departments have started using the same demand category for different kinds of request, and the scoring on recent proposals is no longer comparable with the scoring on the ones approved the year before.

A second common starting point is a portfolio office that has lost its administrator. The person who built the configuration has left or been promoted, the documentation stopped at go-live, and small changes have since been made directly in production without a record of why. The forum still meets, but it increasingly works from a spreadsheet kept alongside the platform because one manager stopped trusting the figures.

In both situations the first task is the same: establish what the instance currently holds, compare it with what the forum believes it holds, and write down the gaps before anything is changed.

Keeping demand intake usable

Demand intake is where drift begins. A good intake form asks for just enough to assess a proposal: the sponsor, the business need, the goals it supports, a rough size and the capability or application it touches. Over time fields are added for one stakeholder’s question and never removed, categories multiply, and submitters learn to leave fields blank because nothing checks them. Managed support watches the queue on a short cycle, returns incomplete demands to their submitters with a reason, and keeps the category list short enough that two people would classify the same request the same way. When the intake form itself is the problem, that is raised as a configuration change for the portfolio lead rather than worked around in the queue.

Project, program and portfolio records

The forum reads project records as a summary of reality, so the records have to be kept honest between meetings. Support checks that every project on the agenda has a current status, a budget that reconciles with finance and named people allocated to it, and flags the ones that do not. Closed projects are checked for budget that was never released and allocations that were never ended, because both quietly distort the capacity and spend the forum sees. Programs are reviewed for projects that were attached for convenience and no longer belong, and portfolio membership is reconciled with the lanes the sponsor has defined so that no project sits in two lanes and is counted twice.

Resource pools and allocations

Resource management is the part of SPM that decays fastest, because it depends on people data that changes every week. Joiners, leavers and transfers have to reach the resource pools, or allocation reports describe a workforce that no longer exists. Managed support reconciles pool membership against the directory on a regular cycle, reviews allocations that run past a project’s planned end date, and watches for the pattern where one named specialist is committed to several projects at once. Where the organisation records actual time, support compares actuals with allocations and raises the gaps with the resource manager, because a plan that is never corrected against actuals stops being a plan.

Scoring criteria and the reports the forum relies on

Scoring is governance expressed as configuration. The criteria, their weights and the fields they read decide which proposals rise to the top, so any change alters what the forum is comparing. Support keeps the current model documented in plain language, records every change with the decision that prompted it, and checks that new demands are being scored with the current criteria rather than carried over from an older version. Reports and dashboards get the same treatment: each has a named reader, its filters are reviewed when a category or field changes, and any report nobody has opened in a long period is retired rather than left to confuse the next person.

Financial records that reconcile without a special exercise

Budgets and cost plans attached to portfolio items are only useful if they agree with the finance system at each cycle. Support maintains the mapping between portfolio items and the cost centres or codes finance uses, checks that actuals are flowing in where an integration exists, and reconciles the totals the forum will see before the meeting rather than after a challenge. Where chargeback or cost allocation is practised, it lives in the organisation’s financial management arrangements rather than in the portfolio records, and support’s role is to make sure the two agree, not to run the allocation.

What typically drifts in the first year

The same handful of problems recurs across portfolios. Categories and fields are added without retiring old ones. Approved demands are converted to projects late, so the project calendar understates committed work. Allocations outlive the projects they were made for. Dashboards are copied and edited until several versions of one figure circulate. Delegated approvals keep working after the delegate has left. None of these is dramatic on its own, and that is why they persist: each is small enough to postpone. The sections that follow set out the rhythm, change control and access reviews that stop them accumulating.

The recurring work that keeps an SPM instance trustworthy after go-live

Once SPM is in daily use, much of the risk is not in big changes. It is in small, repeated tasks that nobody owns: a project closed without its budget being released, a resource pool that still lists someone who left, a demand category that two teams now use for different things. Managed support exists to make those tasks routine. The aim is an instance in which the portfolio view stays honest between forum cycles, not one that is tidied up once a quarter when someone notices it has drifted.

This guidance is for the portfolio office lead, the platform owner and the finance partner who will live with the instance after the project team leaves. It assumes the core SPM build is complete and that a forum is already making decisions from it.

An operating rhythm that matches how the portfolio actually moves

Different tasks need different cadences. Running everything monthly wastes effort on things that rarely change, and running everything quarterly lets errors compound. The table sets out a rhythm that most portfolios can adapt.

Cadence	Work to complete	Who signs it off
Weekly	Check new demand records for missing owners, categories and sponsors; clear unassigned items	Portfolio office coordinator
Before each forum	Confirm every project on the agenda has current status, budget and allocated people; flag stale entries	Project owners, reviewed by the portfolio lead
Monthly	Compare actual time and spend with plan for active projects; review resource pools against assignments	Resource manager and finance partner
Quarterly	Review portfolio configuration: categories, scoring fields, roles and any reports nobody has opened	Platform owner and sponsor

The weekly task is deliberately small. If it takes more than a short sitting, the intake form is asking for too much, and that is a design problem to raise at the quarterly review rather than a reason to skip the check.

Managing change to portfolio configuration without breaking history

Every change to a category, a scoring field or a workflow step alters how old and new records are read. A new scoring criterion added mid-year makes earlier scores look incomparable, and a renamed category can split one line of spend into two. Run configuration changes through a short change record that states the reason, the affected records, and whether historical data will be re-scored or left as it was. Keep the decision with the portfolio lead, not the platform team alone, because the change touches what the forum has been comparing.

1. Write the change in plain language and name the forum decision it supports.
2. List the records and reports affected, including any dashboard that filters on the field.
3. Trial the change on a sandbox built from recent records.
4. Agree whether history is re-scored, flagged, or left alone, and record that choice.
5. Release the change between forum cycles, never during one, and tell the forum members what moved.

Access reviews and offboarding for people who manage the portfolio

Portfolio roles can carry more authority than many ITSM roles. A demand manager can move work in or out of the approved list, and a resource manager can commit people’s time. When someone changes role or leaves, their access should be reviewed on the same day, not at the next annual audit. Build a short access review into the monthly rhythm: list everyone with a portfolio role, confirm each still holds that role, and remove any account that belongs to someone who has moved to another team. Give extra attention to delegated approvals, because they are easy to forget and continue to work after the person has gone.

Deciding between in-house support and an external managed service

Managed support makes sense when the portfolio office is small, the platform owner also runs other work, or the organization has had a difficult cut-over and needs steady hands for a while. It makes less sense when the portfolio office already has a trained administrator, a documented change process and a forum that meets reliably. The question to ask is which tasks would stop if the one person who understands the configuration went on leave. If the answer is most of them, the case for external support is strong. If the answer is few, the better investment is documentation and a second trained person.

Signs the managed service is working

A well-run instance shows steady, unremarkable signals. The forum agenda comes from the platform without manual edits. Demand records have owners within a short time of being raised. Budget figures reconcile with finance at each cycle without a special exercise. Reports that nobody has opened in a long period are retired rather than left to confuse new starters. The sign of trouble is usually a return to spreadsheets alongside the platform, which often starts with one manager who no longer trusts the numbers.

Questions about ongoing SPM support

How much of the platform owner’s time should a managed service take?

That depends on how many changes the forum requests in a typical quarter and how many people build reports. Ask for the change list and the time each change took, so the answer rests on evidence rather than estimate.

Who owns the scoring model when the managed support team changes?

The portfolio lead owns it. The support team maintains the configuration, but any change to how a score is calculated is a governance decision and should be recorded as one.

Can managed support also run the forum?

Support staff can maintain the records the forum uses. The decisions remain with the sponsor and the forum members. Blurring that line is the fastest way to make the portfolio look like the support team’s opinion rather than the organization’s.

What should happen to the instance if the contract ends?

The organization should be able to run the monthly and quarterly tasks without outside help. Keep the change record, configuration notes and access list in the organization’s own hands, and test that a named employee can run one full forum cycle unaided before the handover.

Next step

The managed support services page describes the wider model, and the service metric dictionary guide is a useful reference for agreeing what each reported figure means before it reaches the forum.