IT Service Catalog
What is IT Service Catalog?
An IT service catalog is a structured list of the technology services an organization offers, describing each service, how to request it, its service levels and often its cost.
Updated November 2026 · 5 min read
An IT service catalog is the menu of what the technology organization provides. It lists services such as laptops, email, collaboration tools, application access, hosting, data storage and support, and for each one describes what it includes, who is eligible, how to request it, what service levels apply and who owns it. Many catalogs also show the cost or price of each service, especially where costs are shown back or charged to business units through IT showback.
The service catalog is a core concept in IT service management frameworks such as ITIL, where it supports requests and service delivery. It is equally important for IT financial management, because services are the natural unit for costing, pricing and discussing technology with the business. A clear service catalog makes it possible to say what each service costs and what business units are consuming.
Definition of IT Service Catalog
An IT service catalog is a documented, organized collection of information about the IT services available to an organization's users. It describes each service in business terms, rather than technical ones, and gives users and IT one agreed list of what IT offers.
In ITIL, the service catalog is part of the broader service portfolio, which also includes services in development and those being retired. The catalog contains the services currently available for use.
Business and Technical Service Catalogs
A business service catalog is the customer-facing view, listing services that users and business units can request and consume, such as a new laptop, access to an application or a collaboration account. It uses language business users understand.
A technical service catalog lists the underlying services that support business services, such as hosting, storage, networking, identity and databases. It is used mainly by IT teams and shows how business services depend on technical ones.
Linking the two views shows which technical services each business service relies on, which is essential for costing business services accurately.
What a Catalog Entry Contains
A typical entry includes the service name and description, what is included and excluded, who can request it and how, service levels such as availability and response times, the service owner and related services.
Where cost information is included, entries may show the unit of consumption, such as per user or per device, and the unit cost or price, often derived from IT service costing.
Options and tiers, such as standard and premium laptops or different storage service levels, are often listed with their respective costs, which helps users make informed choices.
Importance of the IT Service Catalog in IT Financial Management
Services are the most meaningful way to discuss technology costs with business leaders. The service catalog defines those services, providing the structure that costing, showback and chargeback depend on.
It also shapes demand, since users see what is available and, where included, what it costs.
Without a catalog, discussions about technology costs tend to focus on cost types, such as salaries or hardware, which mean little to business leaders.
Foundation for Costing and Pricing
Each catalog service becomes a cost object. Costs are allocated to services, divided by consumption to produce unit costs and presented back to consumers. Without a defined catalog, service costing has no consistent structure.
For IT chargeback and showback, the catalog provides the price list: the services that can be consumed, the units in which they are measured and the rates that apply.
Keeping the catalog and the cost model aligned, with the same service names and definitions, ensures that costs and catalog entries match.
Shaping Demand and Standardization
A catalog that shows options and costs encourages users to choose standard, lower-cost options where they meet their needs. For example, showing the cost difference between standard and high-performance laptops or storage tiers can shift demand toward cheaper options.
The catalog also supports standardization, which reduces costs. When users choose from a defined set of services rather than requesting custom solutions, IT can deliver more efficiently and negotiate better prices with vendors.
Retiring services from the catalog is also a way to manage demand, directing users toward newer, more efficient alternatives.
How to Build an IT Service Catalog
Building a service catalog involves identifying services, describing them in business terms, assigning owners and connecting the catalog to request, costing and reporting processes.
The catalog should be maintained as services change, rather than treated as a one-time document. An outdated catalog quickly loses the trust of users and undermines the costing built on it.
Identifying and Describing Services
Services are identified by looking at what IT delivers from the user's perspective, not by listing systems or teams. A user wants email that works, not a list of the servers and licenses behind it. Interviews with business users and IT teams, along with analysis of service requests, help identify the right services.
Each service should be described clearly, with a defined owner, unit of consumption and service levels. Starting with the most common and highest-cost services keeps the effort manageable.
Aligning service definitions with frameworks such as the TBM taxonomy makes costing and benchmarking easier.
Connecting to Processes
The catalog should be integrated with the service request portal, so users can request services directly, and with the cost model, so each service has an up-to-date cost.
Regular reviews, often annually, update the catalog to reflect new services, retired services and changes in costs and service levels. Service owners are responsible for keeping their entries accurate.
Usage data from requests and consumption shows which services are popular and which are rarely used, informing decisions about investment and retirement.
Examples of IT Service Catalogs in IT Financial Management
The examples below show how a service catalog supports cost management.
Both use illustrative figures for a mid-sized enterprise.
In each, making services and their costs visible changed behavior.
Shifting Demand to Standard Devices
A company's catalog offers a standard laptop at $1,200 and a high-performance laptop at $2,600. Before costs were shown in the catalog, 45 percent of the 2,000 laptops bought each year were high-performance models.
After adding costs and clear guidance on which roles need high-performance devices, the share falls to 20 percent. Annual laptop spending falls by about $700,000. Users who need high-performance devices still get them, but the choice is now deliberate rather than a default.
Pricing Storage Tiers
The catalog lists three storage tiers: high-performance at $300 per terabyte per year, standard at $120 and archive at $30. Application teams previously used high-performance storage by default.
With tiers and costs visible, teams move 400 terabytes of infrequently accessed data to the archive tier and 300 terabytes to standard, reducing annual storage costs by about $162,000. The infrastructure team also uses the tier data to plan future storage purchases more accurately.
Conclusion
An IT service catalog is a structured list of the technology services an organization offers, describing each service, how to request it, its service levels and often its cost. It includes business-facing and technical views.
In IT financial management, the service catalog provides the structure for service costing, showback and chargeback, and shapes demand by making options and costs visible. Defining services in business terms, assigning owners, connecting the catalog to request and costing processes and keeping it current help organizations manage technology costs more effectively.
Related terms
IT Showback
IT showback is the practice of reporting to business units what their technology consumption costs, without billing them for it. It builds cost awareness while budgets stay unchanged.
IT Service Costing
IT service costing is the process of calculating the full cost of delivering each IT service, such as email, hosting or the service desk, by assigning direct costs and allocating shared costs to it.
IT Chargeback
IT chargeback is the practice of billing business units for the technology services they consume, moving those costs from IT's budget into theirs. It ties technology spending to the teams that drive it.
TBM Taxonomy
The TBM Taxonomy is the TBM Council's standard model for classifying technology costs. It organizes spending into cost pools, resource towers, solutions and consumers so costs can be compared and traced.