Explainer

What is an IT service catalog? A plain-English guide

Learn what an IT service catalog is, what belongs in each entry, how requests flow, and the mistakes that make catalogs stale.

By the Cloudverg engineering team · · 5 min read

What it is

An IT service catalog is the published list of services IT offers to employees, plus how to request each one. Treat it as a menu, not a project plan. A good entry answers four questions: who can ask, what they get, what approvals are needed, and how long it should take. Common items include a standard laptop, software access, a new hire setup, a shared mailbox, and a password reset. Each item has a service owner, a request form, and a fulfillment path.

The catalog is not an asset inventory or a knowledge base. The inventory says what you own. The knowledge base says how to fix or use things. The catalog says what someone can ask for and what happens after they ask. Link the three. A new hire item can point to an onboarding checklist, a device record, and an access matrix.

Write entries for the requester, not for IT. A label like Get access to the finance shared drive works better than RBAC provisioning request. Keep internal codes and queue names behind the form. If employees cannot tell which item to pick, the catalog is already too complex.

How it works

Every item needs a small set of fields: name, plain description, audience, request form, approval path, fulfillment tasks, response target, service owner, dependencies, and related articles. Publish only services you can support with a known process. An item that depends on a vendor ticket or a project can be listed as a request for a quote or a consultation, not as a fixed service.

The request flow is simple in principle. An employee opens the portal or ticket form, picks the item, fills required fields, and submits. The tool routes approval to a manager, a system owner, or security based on risk. It then creates tasks, assigns a queue, and shows status. The employee sees where the request sits without sending a follow-up email.

Keep the distinction between a service offering, a catalog item, and a request. Laptop support is a service. Request a standard laptop is a catalog item. The ticket for one employee's laptop is a request. Clean reporting depends on that separation. Categories and filters help people find items, but the search terms should come from how employees talk.

Governance is part of the design. Each item has an owner who approves changes and answers escalations. The owner reviews the entry on a set schedule and retires it when the process or tool changes. Version notes help the service desk explain what changed.

Why it matters for a business

A catalog removes guesswork. Employees stop asking around for the right form. IT gets complete requests on the first try. That cuts the back and forth that fills queues and makes people wait.

It makes approvals visible. Managers see what they are approving. System owners see who needs access. Security and finance get a record instead of a forwarded email chain. New hire setup becomes repeatable. Leaver steps can revoke access in order. When an auditor asks how access was granted, the request and approval are in one place.

The catalog also supports planning. Request volume by service shows where demand sits and which items need automation or better self-service. Service owners can see backlog and repeat issues. Finance can map internal cost to services if you use chargeback, without chasing emails for every small request.

It sets expectations. A target response time is not a promise that every request is instant. It is a shared reference point. The catalog also states what IT does not cover, which saves time for everyone.

Common mistakes

The first mistake is turning the catalog into every ticket category. A catalog is not a taxonomy. Start with a short list of services you can describe and support. Add items as owners are ready. A long list with vague entries trains people to avoid the portal.

The second is publishing items without an owner. An entry with no owner goes stale. The owner must review the description, approve changes, and handle escalations. Put that name in the entry, not only in a spreadsheet.

The third is too many approvals. Every extra step adds delay. Use risk-based approval: manager for general software, system owner for sensitive data, security for admin access. Do not route a mouse request through three people.

Other traps: copying a vendor catalog, hiding fulfillment steps, failing to link the inventory and knowledge base, and never retiring old items. If the form asks for information the service desk never uses, remove the field. If people keep choosing the wrong item, rename it.

How to get started

Pull the last month of tickets and pick the requests that repeat. Write one page for each: who can ask, what is included, what is not, approvals, target times, owner, and related articles. Interview the people who fulfill the work. They know the exceptions that a clean form must handle.

Test the forms with a small group outside IT. Watch where they hesitate. Fix labels before launch. Publish in the portal you already have, even if that is a service desk with a basic request form. Link the catalog from the intranet, the new hire checklist, and the ticket confirmation message.

Run a monthly review. Check request volume, time to approve, time to fulfill, and repeat issues. Update entries that cause questions. Retire items no one uses. Train service owners on how to edit their entries and how to read the report.

You can start with a spreadsheet and a form. A service desk tool helps when volume grows. If you need the intake and workflow behind the catalog, Cloudverg's IT service desk setup, $6,500/month, is one option among others. It covers ticketing categories, device inventory, new hire and leaver checklists, access approvals, and a seeded knowledge base in a fixed two-week scope.

Frequently asked questions

What is the difference between an IT service catalog and ITSM?

ITSM is the broader set of practices for running IT services. The catalog is one part: the published menu of services and request paths. ITSM also covers incidents, changes, assets, and service levels.

What should each catalog entry include?

At minimum: a plain name, description, who can request it, the form, approval path, target time, owner, and related articles. Add dependencies and fulfillment tasks for the service desk. Keep the requester view short.

Is an IT service catalog only for IT?

No. HR, facilities, and finance can publish their own catalogs. This guide covers IT because the request paths often touch access, devices, and security. Keep separate catalogs or clear categories so people know where to start.

Monthly plan

Want help with this? IT service desk setup

$6,500/month

2 weeks · Starts within 10 business days

Two weeks to set up a help desk with real categories, device inventory, access requests and onboarding checklists, plus the reports managers ask for.

Renews monthly. Cancel any time.
What is included

Related guides

More business systems guides   Business systems

Smallest way to start

Get a senior architect on your problem this week

Ninety minutes a month on the cloud, AI or security question that is blocking you, a pre-read of your material and a written summary within two business days.

$450/month

Renews monthly. Cancel any time.