Jira Service Management is now more powerful than ever as part of Service Collection. Unlock exceptional service experiences with Rovo, Assets, and our new Customer Service Management app.Try it now

IT service catalog: definition, examples and best practices

Key takeaways

  • A service catalog works like a menu of everything a service team can deliver, including who can ask for it and how long it takes

  • Requesters get faster answers when every entry spells out scope, eligibility and expected turnaround

  • ITIL 4 treats catalog upkeep as its own practice, distinct from managing the wider service portfolio

  • Strong catalogs launch small, cover the most frequent requests first and expand based on usage data

An IT service catalog lists the services an information technology (IT) team provides, along with what each one includes, who can request it, and how quickly it gets delivered. Employees use the catalog to find and request help, and service teams use it to standardize how that work is provided.

Without a service catalog, requests come in through email, chat and hallway conversations, often missing key details or landing with the wrong team. Agents lose time sorting and rerouting tickets, and requesters wait longer for answers.

A well-maintained catalog gives requesters a clear picture of what’s on offer and gives service desk managers cleaner demand data, which strengthens service request management across the board.

This guide explains what a service catalog includes, how it fits within the IT Infrastructure Library (ITIL) framework, and how it differs from a service portfolio. It also includes IT service catalog examples, instructions for building one, and tips for choosing service catalog software.

Implementing a service catalog is an efficient way to improve service request management. A service catalog helps your customers understand what issues your team can solve, resulting in fewer off-base requests and clear expectations of how you can help. This article explores service catalogs, offers best management practices, and highlights potential integrations with the IT service desk.

What is an IT service catalog?

An IT service catalog is a cornerstone of IT Service Management (ITSM), acting as a centralized repository of a company’s IT services. With a clear and organized view of available services, customers select a service from your catalog and submit the required information to set the IT team up for success.

Business vs. technical service catalogs

A business service catalog acts as a “storefront” where end users can browse and request services, while a technical service catalog is intended for internal use by service providers.

 Many organizations keep dual views of the same services to serve both audiences. The business view is written in plain language, while the technical view records the systems, teams and agreements behind each service.

Aspect

Business service catalog

Technical service catalog

Audience

Employees, customers and business stakeholders

IT staff, service owners and support groups

Language

Plain, outcome-focused descriptions

Technical detail and internal terminology

Typical contents

Service description, eligibility, cost, how to request and expected delivery time

Supporting systems, dependencies, support groups and underpinning agreements

Main purpose

Help people find and request the right service

Help teams deliver, support and change the service

Example entry

“Request access to the sales reporting tool”

Reporting application, identity provider integration, database and owning support group

The service catalog in ITIL 4

Much of the language used to describe service catalogs comes from ITIL, the most widely used framework for IT service management. ITIL 4, the current version released in 2019, organizes its guidance into 34 management practices that IT organizations adapt to fit their own needs. 

In ITIL 4, the service catalog is maintained through a dedicated practice called service catalog management. Its purpose is to provide one consistent source of information about every live service and service offering, and to make sure each audience can reach the details relevant to them. Requesters, service owners and leadership often work from different views.

The practice focuses on keeping entries accurate as services change and on tailoring views for different groups, so a single source of truth can serve requesters and support staff alike.

Implementing an ITIL service catalog is crucial for establishing a standardized system for managing IT services.

What is included in an IT service catalog?

An effective IT service catalog comprises two main parts: the catalog structure, which defines how services connect, and the entry details, which govern each request.

1. Core catalog structure

Service offerings a business provides 

In an IT service catalog, these offerings represent the various self-serve and ITSM-supported solutions that users can access. For instance, a service offering might include software installation, password resets, or network access.

Service options

On the other hand, service options are customized versions of these offerings tailored to specific customer preferences. For example, a standard software installation might have options for different software versions or additional configurations. By clearly defining service offerings and options, an IT service catalog ensures that users can easily find and request the services that best meet their needs.

Service relationships and dependencies

Understanding the relationships between different services is crucial for effective service management. For example, a password change might require a user to log out of all devices and log back in, potentially triggering additional security measures. By mapping out these relationships and clarifying them in the IT service catalog, IT teams can ensure a seamless user experience and avoid potential issues.

This interconnected view of services is a crucial aspect of an ITIL 4 service catalog, helping to provide a comprehensive understanding of how different services interact and depend on each other.

2. Details each service entry should list

Every entry in the catalog answers the same types of questions, so requesters can compare services quickly and agents receive consistent information. The fields below are a common starting point.

  • Service name: A clear, outcome-focused label written in plain language. 

  • Scope and description: A straightforward summary explaining exactly what the service delivers and what it excludes.

  • Eligibility and approvals: Who has permission to request the item, along with any managerial or budget approvals required before work begins.

  • Request method: The primary channel to submit the intake, typically a standardized self-service portal form.

  • Service level agreement (SLA): The expected response and delivery turnaround times so requesters know when to expect fulfillment.

  • Cost and chargeback: Any licensing fees, hardware costs, or department budget codes tied to the request.

  • Service owner: The specific team or manager accountable for maintaining the service and fulfilling requests

IT service catalog examples

Most IT service catalogs cover the same core categories, even though the services inside them vary by organization. The table below shows common categories with typical entries.

Category

Example services

Typical requester

Accounts and access

Password reset, new user account, access to a shared drive or application

Any employee

Hardware

New laptop, replacement monitor, mobile phone

Employees and managers

Software

License request, software installation, version upgrade

Any employee

Network and connectivity

Virtual private network (VPN) setup, guest Wi-Fi access

Remote and visiting staff

Onboarding and offboarding

New starter setup, equipment return, account deactivation

Managers and HR

General support

Get IT help, report a system problem

Any employee

Service catalog examples beyond IT

The same structure works for any department that handles repeat requests. Enterprise service management applies IT service practices to business teams. Their catalogs may cover the following themes:

  • HR: employment verification letters, benefits questions and parental leave requests

  • Facilities: desk moves and building access

  • Finance: expense reimbursements, purchase order approvals and new vendor setup

  • Legal: contract reviews and nondisclosure agreement requests

Service catalog vs. service portfolio

A service portfolio is the complete record of an IT organization’s past, present, and future services. In ITIL terms, the portfolio has three parts: the service pipeline (services in development), the service catalog (live services available to customers), and retired services. The catalog is the part requesters interact with.

Referencing a service portfolio will help your team understand what has been worked on in the past and what you are offering today. Many teams will also add aspirational services to their service portfolio while developing the capabilities needed to provide them to future customers.

Many IT teams adjust their service offerings over time. When asked why you don’t offer a service you used to, you should be able to find a ready answer within the service portfolio. Services are often discontinued due to various factors, which should be documented in your service portfolio. With a glance at your service portfolio, you can confidently answer a business leader’s question.

The two are closely linked, but they serve different purposes and audiences.

Aspect

Service catalog

Service portfolio

Scope

Live services available to request now

All services: planned, live and retired

Audience

Requesters, plus a technical view for IT

IT leadership, service owners and governance groups

Purpose

Help people find and request services

Guide investment and strategic decisions

Updated when

A service launches, changes or retires

Strategy, demand or budgets shift

Best practices for creating an IT service catalog

Creating an effective IT service catalog requires careful planning and execution. The ideas below cover the full cycle, from first research to ongoing upkeep.

Starting with user needs

The first step in creating an IT service catalog is to identify the needs of your users and customers. This involves gathering input from end-users to understand their unique needs and expectations.

Surveys, interviews and focus groups are reliable ways to gather this information. This will help you create a relevant service catalog that meets your users’ needs effectively.

Defining the purpose and scope

A catalog with a clear purpose is far easier to maintain. Agreeing early on which teams, services and audiences it covers keeps it from growing into an unmanageable list.

Prioritizing the most requested services

Launching with a small set of high-volume requests, such as password resets and access requests, delivers value quickly. Ticket history is a reliable guide to what belongs in the first release.

Writing descriptions in the requester’s language

Requesters search for outcomes, such as “I need a new laptop,” rather than internal service names like “End-user device provisioning.” Plain-language titles and short descriptions reduce misrouted requests and help portal search return the right result.

Grouping services into a consistent set of categories also makes the catalog easier to browse and update.

Connecting the catalog to ITSM tools

A catalog delivers the most value when each entry triggers a workflow. Linking entries to request forms, approvals and fulfillment queues in a service management platform turns a static list into a working entry point for requests.

Integration with knowledge bases and asset records also lets agents and requesters see related information without switching tools.

Testing and refining over time

Testing new entries with a small group of requesters surfaces confusing names and missing fields before launch. After launch, regular reviews keep the catalog aligned with changing needs and help retire services nobody uses.

Track core operational metrics

Data on usage, SLA performance, and customer satisfaction are great starting points for measuring an IT organization’s performance.

  • Usage data tells IT teams what services are in demand based on the volume of tickets. This information is easily accessible by filtering your tickets by “issue type.”

  • SLAs dictate what the customer can expect and how long the issue should take to resolve. Your goal is to use SLAs to gauge your success in delivering service within the time allotted.

  • Customer satisfaction is a valuable metric that keeps you focused on problems and the customers who experience them.

How the service catalog supports ITSM processes

ITSM is how IT teams manage the end-to-end delivery of IT services to customers. A self-service portal is crucial in facilitating user access to the service catalog, allowing users to view services, raise tickets, and make requests.

It’s tempting to think that your service catalog is just the beginning of your IT process, as it’s often the first thing a customer interacts with. However, your service catalog is one of the most essential components of ITSM, as it touches every stage of your IT service lifecycle. When adding a new service to your catalog, ITSM fundamentals will inspire you to build repeatable processes that create efficiency.

Service catalog and service request management

Service request management is the process the catalog supports most directly. Each catalog entry maps to a request type with its own form, approval path and fulfillment workflow.

When a requester picks a service, the request arrives with the right details, routes to the right queue and starts the right SLA clock. That makes the service request process repeatable from submission to closure.

Service catalog and change management

Let’s again focus on software provisioning as a service and imagine a customer who wants to spin up a new software solution for payroll. Given the complexity of change management, you’ve designed a change management workflow that these service desk tickets follow step-by-step.

Modern change management workflows break down silos by notifying other teams, providing context and transparency in the ticket, avoiding bottlenecks, and minimizing risk. A service catalog and service desk can run workflows to make sure that services that need a high level of care get it every time.

Service catalog and incident management

Incident management is the process used by development and IT operations teams to respond to an unplanned event or service interruption and restore the service to its operational state.

A service catalog aids your incident management efforts by helping surface incidents earlier so teams can respond faster. Identifying a spike in request types can alert your team to an incident related to service. A service catalog that kicks off an Incident Management workflow helps ensure that your team doesn’t miss any steps along the way.

Learn more about service desk.

What to look for in service catalog software

Service catalog software turns a list of services into something people can browse, request and track. The right tool depends on the size of the catalog and how many departments share it, but a few capabilities come up in almost every evaluation.

Capability

Why it matters

Self-service portal with search

Requesters find services without contacting the service desk

Customizable request forms

Each service collects the details its fulfillment team needs

Workflow automation and approvals

Routine requests move forward without manual handoffs

SLA tracking and reporting

Managers see demand and performance for each service

Knowledge base integration

Related articles can answer questions before a ticket is raised

Asset and configuration data

Agents see the hardware, software and dependencies tied to each request

Support for multiple departments

HR, facilities and other teams can run their own catalogs on one platform

Service catalogs are a feature of service management software like Jira Service Management. Catalog items become request types in the help center, with routing, approvals and automation built in, and departments across the business can set up their own service spaces.

Getting started with IT service catalogs

A first version of a service catalog doesn’t need to cover everything. A handful of well-described, high-volume services, each connected to a clear workflow, can reduce misrouted requests and start producing useful demand data early on.

From there, the catalog can grow one service at a time, guided by request data and requester feedback. Service owners who review it regularly keep it accurate as tools, policies and people change.

 Jira Service Management offers a flexible service management solution so you can implement a service catalog that fits the unique needs of your business. 

In Jira Service Management, the IT service management template comes with a ready-made catalog of common request types, such as getting IT help, requesting a new account and setting up a VPN. Each request type can be renamed or extended to match the services a team actually offers.

Frequently asked questions

What is the difference between a service catalog and a service desk?

A service catalog is the list of services people can request, while a service desk is the team and system that receive and fulfill those requests. The catalog defines what can be asked for and what to expect. The service desk handles the work, communicates with requesters and tracks each request through to completion.

How many services should an IT service catalog include?

There is no fixed number. Many organizations launch with 10 to 20 of their most frequently requested services and add more as demand data comes in. A smaller catalog with clear, accurate entries is usually more useful than a long list that requesters struggle to search and service owners struggle to maintain.

Who owns the IT service catalog?

Ownership usually rests with a service catalog manager or an ITSM lead, who maintains the catalog’s structure and accuracy. Individual service owners remain accountable for the details of their own services, such as descriptions, SLAs and fulfillment steps, and flag changes so the catalog stays current.

What is a service request catalog?

A service request catalog is a view of the service catalog limited to the items users can order directly, such as equipment, access or software. It hides technical detail and anything that can’t be requested, so employees see only the options relevant to them, each paired with its own request form.

Recommended for you

Whitepaper

The Total Economic Impact™ Of Atlassian For ITSM

The Total Economic Impact™ of Atlassian Jira Service Management. The report includes cost savings and business benefits enabled by Jira Service Management.

Whitepaper

Atlassian's guide to agile ways of working with ITIL 4

ITIL 4 is here—and it’s more agile than ever. Learn tips to bring agility and collaboration into ITSM with Atlassian.

Learn more about ITSM

Find more ITSM guides and resources in this hub.