If you’ve spent any time working with ITIL frameworks, you’ve probably encountered both terms and wondered whether they refer to the same thing. They don’t — and confusing them leads to poorly structured service management programs. This article breaks down the difference between a service catalog and a service portfolio, explains where each fits in your ITSM practice, and gives you practical examples and templates to put both to work.
What to Look for When Structuring Your Service Information
- Audience clarity: Service information should be structured for its intended reader — technical staff, business users, or IT leadership each need different views.
- Lifecycle coverage: Good service documentation captures services across their full lifecycle, not just what’s currently available.
- Ownership: Every service entry should have a named owner responsible for accuracy and updates.
- Alignment with strategy: Service definitions should tie back to business outcomes, not just technical functions.
- Tool support: Whether you use a spreadsheet or a dedicated platform, the structure should make it easy to update and query service data.
Service Catalog vs Service Portfolio at a Glance
| Concept | Purpose | Audience | Scope | ITIL Term |
|---|---|---|---|---|
| Service Portfolio | Strategic management of all services across their lifecycle | IT leadership, service owners | Pipeline + Catalog + Retired | ITIL service portfolio |
| Service Catalog | Publish available services to end users and IT staff | Business users, IT teams | Live/active services only | Service catalogue |
What Is a Service Portfolio?
The ITIL service portfolio is the complete set of services that an IT organization manages — past, present, and future. It’s a strategic management tool, not a user-facing document. Think of it as the master record that IT leadership uses to govern which services exist, which are being developed, and which have been retired.
The service portfolio is divided into three distinct pipelines:
- Service pipeline: Services under development or planned for future delivery. These are not yet available to users.
- Service catalogue: Active services that are currently delivered and available to customers or internal users. This is the subset that end users actually see.
- Retired services: Services that have been decommissioned. Kept for historical reference, compliance, or transition documentation.
Service portfolio management is an ongoing process owned by IT leadership or a dedicated service portfolio manager. It answers strategic questions: Are we investing in the right services? Are any services redundant or underperforming? What do we need to build or retire next quarter?
Service Portfolio Example
Imagine an IT department at a mid-size company. Their service portfolio might include:
- Pipeline: A new self-service password reset tool currently in development
- Active (catalog): Email and collaboration tools, VPN access, hardware provisioning, incident support
- Retired: A legacy remote desktop service replaced by a cloud VDI solution
None of this is visible to end users in its raw form. It’s internal governance documentation — the kind of content a CIO reviews during quarterly planning.
Service Portfolio Meaning in Practice
In practical terms, a service portfolio is often maintained as a structured document or database entry in your ITSM platform. It typically includes the service name, business owner, strategic justification, current status (pipeline/active/retired), cost and investment data, and associated SLAs or OLAs.
Some organizations maintain this in a spreadsheet, others in a tool like ServiceNow, which has a dedicated service portfolio module. What matters more than the tool is the discipline: the portfolio is only useful if it’s kept current and reviewed regularly.
What Is a Service Catalog?
The service catalogue (or catalog, in US spelling) is the customer-facing subset of the service portfolio. It lists only the services that are currently active and available for request. Its primary purpose is to give users a clear, accessible view of what IT offers — and how to request it.
A well-designed service catalog typically has two views:
- Business/user catalog: Describes services in plain business language. Focused on what the service does, not how it works. Intended for non-technical employees.
- Technical/support catalog: Describes the underlying components and supporting services. Used by IT teams to understand dependencies and delivery requirements.
The service catalog is the part of your ITSM practice that most end users actually interact with. In modern ITSM tools, it appears as a self-service portal where users can browse available services, submit requests, and track fulfillment.
Service Catalog Example
A typical business-facing service catalog entry for “New Employee Onboarding” might look like this:
- Service name: New Employee Onboarding
- Description: Provisioning of hardware, accounts, and access for new hires
- How to request: Submit via IT portal or contact HR
- Expected delivery time: 3 business days before start date
- Service owner: IT Operations Manager
- Support contact: helpdesk@company.com
This is actionable and user-friendly. It doesn’t include cost data, strategic justification, or pipeline details — those belong in the portfolio.
The Key Differences Between a Service Catalog and Service Portfolio
The simplest way to think about it: the service portfolio is the management view, and the service catalog is the customer view. The catalog is always a subset of the portfolio — specifically, the active services section of it.
Here’s where many teams go wrong: they build a service catalog and assume they’ve done service portfolio management. They haven’t. Without the portfolio context — pipeline planning, retirement decisions, strategic alignment — the catalog becomes a static list that grows stale and misaligned with business priorities.
Conversely, maintaining a portfolio without publishing a catalog means users don’t know what IT offers, leading to shadow IT, informal requests, and inconsistent service delivery.
Both are necessary. They serve different purposes and different audiences, but they depend on each other. The portfolio informs what goes into the catalog; the catalog is how the portfolio’s active services are operationalized.
Service Portfolio Template: What to Include
Whether you’re building from scratch or formalizing an existing approach, a basic service portfolio template should cover the following fields for each service entry:
- Service name and short description
- Business owner and IT service owner
- Current status: Pipeline / Active / Retired
- Strategic justification: Why does this service exist? What business outcome does it support?
- Associated costs and investments
- SLAs or performance targets (for active services)
- Dependencies: Other services or infrastructure components it relies on
- Last reviewed date and next review date
For the catalog portion, each active service should additionally have a user-facing description, request instructions, expected fulfillment time, and a support contact. This is the information that gets published in your self-service portal.
Service Portfolio in ServiceNow and Other ITSM Tools
Most enterprise ITSM platforms have built-in support for both concepts. Service portfolio in ServiceNow is handled through the Service Portfolio Management module, which allows organizations to define services, track their lifecycle status, and link them to the service catalog. Business cases, costs, and approvals can all be managed within the platform.
Other tools handle this differently. Some, like Jira Service Management, focus primarily on the service catalog and request fulfillment, offering limited native support for portfolio-level management. Others, like BMC Helix ITSM, provide more robust portfolio management capabilities aligned with ITIL 4 practices.
If you’re evaluating tools, it’s worth distinguishing between platforms that treat the catalog as a standalone feature and those that embed it within a broader portfolio management framework. For teams that need full lifecycle governance, the latter is the more sustainable approach.
InvGate Service Management, for example, includes a configurable service catalog with approval workflows and SLA tracking — useful for teams that want structured catalog management without the complexity of a full enterprise platform.
How to Choose the Right Approach for Your Organization
If you’re a small IT team supporting under 200 users, start with the service catalog. Get your active services documented, build a self-service portal, and standardize how requests come in. That alone will reduce ticket noise and set clearer user expectations. Portfolio management can come later as your team matures.
If you’re in a mid-to-large enterprise with multiple service domains, multiple business units, or significant IT investment decisions to make, you need both. The portfolio gives leadership the data to make informed decisions about where to invest, what to retire, and how IT spending maps to business value.
Teams undergoing ITIL adoption or a formal service management improvement program should implement the portfolio first, even if it starts small. It creates the strategic foundation that gives your catalog entries meaning and keeps the catalog from becoming an unmanaged list.
Whichever approach you take, designate ownership clearly. A service catalog with no owner becomes outdated quickly. A portfolio with no governance process becomes a document that nobody reads. Assign named owners for both, build review cycles into your calendar, and treat them as living documents rather than one-time deliverables.
Frequently Asked Questions
What is the main difference between a service catalog and a service portfolio?
A service portfolio covers all services across their full lifecycle — including those in development and those that have been retired. A service catalog is the subset of the portfolio that contains only currently active services, published for end users to browse and request. The catalog is customer-facing; the portfolio is a strategic management tool for IT leadership.
Is the service catalog part of the service portfolio?
Yes. According to ITIL, the service catalog is one of three components within the service portfolio, alongside the service pipeline (services in development) and retired services. You can think of the catalog as the “active” section of the portfolio.
What is service portfolio management?
Service portfolio management is the ITIL practice responsible for governing the full set of services an IT organization offers. It involves evaluating proposed services, approving them for development, tracking active services, and making retirement decisions. The goal is to ensure IT’s service offerings align with business strategy and deliver measurable value.
Do small IT teams need a service portfolio?
Not necessarily at the outset. Small teams often start with a service catalog to organize requests and set user expectations. A formal portfolio becomes more valuable as the team grows, takes on more services, or needs to justify IT investment to business stakeholders. Even a lightweight portfolio — a spreadsheet with lifecycle status for each service — is better than none.
What ITSM tools support service portfolio management?
ServiceNow has a dedicated Service Portfolio Management module with strong ITIL alignment. BMC Helix ITSM and Ivanti Neurons also support portfolio-level management. Tools like Jira Service Management and Freshservice are more catalog-focused but can be extended with custom configurations. The right choice depends on how mature your service management practice is and how much lifecycle governance you need.
Pricing accurate as of the publish date and subject to change. Verify current pricing on each vendor’s official site before purchasing.
Photo by Vitaly Gariev on Unsplash
