Employee submitting an IT service request

An IT service catalog is a single, plain-language list of the IT services your organization offers to its users, with what each service is, who can request it and how. For a small business, it turns “who do I ask about this?” into a page employees can read and act on. Below you will find what belongs in a catalog, the entries most small companies need, how to design the structure and how to keep it accurate.

Mavericks Office Solutions
Make IT Support Easier to Navigate
Mavericks provides managed IT services and a local, USA-based help desk to support small businesses with day-to-day technology needs.

Explore IT services

TL;DR

  • A service catalog lists only the services that are active today, written in the words your employees use, not in technical terms.
  • It is not the same as a service portfolio (the full lifecycle view) or a self-service portal (the place where requests are submitted).
  • Each entry needs a short description, the audience, the benefits, the cost and a way to request it.
  • Start with 10 to 15 common requests, such as onboarding, password resets and printer problems, and name an owner for every entry.
  • Review the catalog on a schedule, because a stale catalog sends people back to email and hallway questions.

Table of Contents

What an IT service catalog is

Think of the catalog as the menu. Your IT team, or the provider that runs IT for you, does a lot behind the scenes. The menu shows what a user can order or ask for, in terms that make sense to them.

The standard definition is a centralized, consumer-facing database of the IT services that are active right now, as described in this ITIL service catalog guide. The key word is “active.” Ideas, pilots and retired services do not belong on the menu your employees see.

In a 20-person company, the catalog may be a single page with a dozen entries. In a 300-person company, it may be a searchable portal with forms and approvals. The logic is the same. People should be able to find what exists, understand what it does for them and ask for it without guessing.

What an IT service catalog is

Why small businesses need one

Larger IT departments built catalogs because requests piled up in inboxes and chat threads. Small companies have the same problem with fewer people to absorb it. When there is no catalog:

  • New hires wait days for equipment because nobody knows who orders it.
  • The same question about VPN or shared drives gets answered five different ways.
  • The owner or office manager becomes the unofficial help desk.
  • Nobody can say what IT actually covers, so requests drift outside what you are paying for.

The benefits the ITIL guidance points to are better transparency and more standardized service delivery. In practice that means fewer surprises for users and a clearer picture of workload for whoever supports them.

Catalog vs. service portfolio vs. self-service portal

These three terms get mixed up constantly, and mixing them up is one of the common mistakes with catalogs. Here is how they differ.

Term What it is Who sees it What it contains
Service catalog The customer-facing list of active services Employees and business users Descriptions, audience, cost, how to request
Service portfolio The complete view of all services across their lifecycle IT and management Services in development, active, being phased out, retired or internal-only
Self-service portal The interface where requests and incidents are submitted Employees and business users Forms, ticket status, knowledge articles

Cornell’s IT department explains that the catalog is the customer-facing portion of the portfolio. The portfolio is the whole inventory, including services still being planned or on their way out. The catalog is the slice users should see.

The portal is different again. It is the transactional layer. When a catalog is connected to a portal, users can go from discovering a service to submitting a request in one place. A catalog without a portal still works as a reference page. A portal without a catalog is a blank form that people do not know how to use.

What goes into a catalog entry

Every entry should answer the questions a user would ask before picking up the phone. According to Cornell’s guidance, a service record covers the service description, audience, benefits, costs, alias and who the service is available to.

For a small business, a practical entry template looks like this:

  1. Service name. The value the user gets, such as “New employee setup,” not “Active Directory provisioning.”
  2. Description. What it is and when to use it.
  3. Who can request it. All staff, managers only, or new hires through HR.
  4. What it costs. Included in your agreement, charged to a department, or quoted per request.
  5. How to request it. A form, an email address, a phone number or a portal link.
  6. Expected response. Your target for acknowledging and completing the request.
  7. Owner. The person or team accountable for keeping the entry correct.

Writing the service description

Keep it short. One catalog guide recommends no more than three sentences for a description. A good test is whether an employee in accounting could read it and know whether it applies to them.

Compare two versions of the same entry:

  • Weak: “Provisioning of a managed endpoint with domain join, MDM enrollment and baseline software image.”
  • Better: “We set up a laptop for a new hire with their accounts, email and standard software, ready on their first day. Submit the request at least five business days ahead.”

The second version names the value and the user’s next step. The first lists delivery details the user never needs. Cornell’s guidance says the same thing: names should reflect value, and entries should avoid listing technical components and delivery details. If you want a deeper look at writing entries that put the customer first, these content design principles cover clear structure and wording that carry over well to catalog fields.

IT service catalog examples for a small business

Most small companies do not need hundreds of entries. They need a short, well-organized list that covers the requests that actually happen. Here is a starter set, grouped the way users think about their work.

Category Example entries Typical audience
Getting started and leaving New employee setup, employee offboarding, role change HR, managers
Accounts and access Password reset, multi-factor authentication help, shared folder access, new software license All staff
Devices and printing Laptop or phone issue, new equipment request, printer or copier problem, scan-to-email setup All staff
Communication Phone extension change, desk phone or softphone setup, voicemail help, conference room setup All staff, office manager
Security Report a suspicious email, lost or stolen device, security awareness training All staff
Facilities technology Door badge or access request, camera footage request Managers, facilities
Business applications Email and calendar setup, file sharing and storage, new application request All staff, managers
Other A catch-all request for anything that does not fit All staff

Bundles save time

Some requests always arrive together. A new hire needs a laptop, accounts, a phone line and access to the right folders. Instead of making a manager file four requests, create a bundle. Practitioner guidance on catalogs gives exactly this example: a new-employee bundle with equipment, system access and orientation scheduling. The same source also recommends an “Other” entry for requests that do not fit a category, so nobody gives up and sends an email instead.

Good bundle candidates for a small business:

  • New hire package: device, email, phone extension, building access, standard software.
  • Departing employee package: account disable, device return, mailbox handoff, access removal.
  • Office move or new location: network, phones, printers, badge readers.

A catalog also shows what a provider covers

If you outsource IT, the catalog doubles as a plain statement of what your provider handles. Our own service lines are a useful illustration of how categories work: managed IT support, cybersecurity, cloud hosting, Microsoft 365, voice and unified communications, managed print, cameras and access control, and fractional IT leadership. A business that works with a single provider can mirror those categories in its own catalog, so an employee asking about a desk phone and an employee asking about a copier both land in the right place.

Designing the catalog around your users

Design starts with the person asking, not with the IT org chart. The ITIL guidance recommends familiar business terminology, logical service domains and dynamic forms that keep user effort low.

Use categories people can scan

Top-level categories should group similar capabilities so users can sort through them quickly, which is the approach Cornell describes for organizing services into top-level categories. Five to eight categories is plenty for a small company. If you find yourself creating a category for a single entry, fold it into a neighbor.

A few naming rules help:

  • Use the words your staff already say (“Wi-Fi,” not “wireless network access”).
  • Start request names with a verb where possible (“Request a new laptop”).
  • Avoid internal acronyms unless every employee uses them.
  • Keep names consistent: if one entry says “Request,” do not label the next one “Procure.”

Two views, one source of truth

Many organizations keep a business-facing view for employees and a separate technical view for IT staff. The business view says “New employee setup.” The technical view lists the systems, steps and vendors needed to deliver it. The ITIL guide notes that organizations often run a business service view for users and a technical service view for fulfillment.

Business service view paired with technical fulfillment view

For a small team or an outsourced provider, that technical view can be as simple as a checklist behind each request. The user never sees it. Cornell frames this as the point of service management: abstracting technical details so customers do not worry about the infrastructure or vendor complexity behind a service.

Keep request forms short

Ask only for what the fulfiller needs. A password reset form needs a name and contact method. A new-hire form needs a start date, a role, a manager and a location. If a field does not change what happens next, remove it. Forms that adapt to earlier answers, such as showing laptop options only when “laptop” is selected, keep the effort low.

Tie entries to service targets

A catalog entry is a promise, so it should state a target. If you work with an IT provider, those targets usually come from your service agreement, and your provider’s internal teams need their own commitments to meet them. Our guide to SLA vs OLA explains how customer-facing targets translate into internal actions.

How to build your first catalog in six steps

You do not need special software to start. A shared document or a page on your intranet works for the first version.

  1. Collect real requests. Pull the last three to six months of emails, tickets and chat messages sent to IT. Group them by type. The most frequent ones become your first entries.
  2. List services, not tasks. “Employee onboarding” is a service. “Create Microsoft account” is a task inside it. Keep tasks in the technical view.
  3. Assign an owner to each entry. That person confirms the description, the audience and the process stay correct.
  4. Write entries in plain language. Use the template above and keep descriptions to three sentences or fewer.
  5. Choose where users request. Even a single shared mailbox or service request page beats scattered messages, as long as every entry points to it.
  6. Test before you publish. Ask two or three employees from different departments to find and request something using only the catalog. Fix where they hesitate.

The ITIL guidance supports this order: manage the catalog centrally, coordinate with service owners so information stays accurate and test the catalog and workflows before publishing.

Connect it to your assets

A catalog gets more useful when it connects to what you own. A laptop request is easier to fulfill when you know which devices are in stock, under warranty or due for replacement. Our IT asset lifecycle management guide covers how small businesses track equipment from purchase to retirement, which feeds directly into hardware entries.

Keeping the catalog accurate

A catalog is only as good as its last review. Services change: you add a new phone platform, retire an old application, switch printers. If the catalog does not follow, users stop trusting it.

Assign a catalog manager, even if that is a part-time role. ServiceNow’s community guidance notes that organizations often assign a catalog manager to keep entries accurate, current and aligned with standards through ongoing governance. In a small company, that might be your office manager, your IT lead or your provider’s account manager.

A simple maintenance rhythm:

  • Every quarter: each owner confirms their entries are still correct.
  • After any change: when you add or retire a service, update the catalog the same week.
  • Twice a year: review request volume and see which entries are used often, which never, and which “Other” requests keep repeating. Repeats are your next new entries.

Our perspective

We run IT for small and mid-sized businesses, and the pattern is the same almost everywhere: the technology works, but nobody can tell employees what they are entitled to ask for. A service catalog fixes that, and it does not need to be elaborate.

When we take on a client as their outsourced IT department, one of the first things we do is make the services visible. Managed IT support, security, phones, print, cloud and Microsoft 365 each become something an employee can recognize and request, instead of a vague “call IT.” Our help desk is based in the USA, in Ohio, and our average help desk response is under 12 minutes. A catalog is what lets that speed reach the right problem quickly, because the request arrives with the right details.

Our advice: start small, write for the person asking, and put one name beside each entry. A ten-entry catalog that is current beats a hundred-entry catalog nobody trusts. And when your business has no full-time IT staff, a provider who handles the technical side behind the scenes lets you keep the catalog simple while the details are covered.

Jeffrey

Benefits and pitfalls to plan for

The benefits are straightforward. Employees know what exists and how to ask. Managers see what is included in the IT arrangement. Support teams receive requests in a consistent format. The ITIL guide lists improved transparency and standardized service delivery among the main gains.

The same source points to two common challenges, and both are avoidable:

  • Confusing the catalog with other constructs. If your “catalog” lists retired services, internal projects and ticket categories, it is a portfolio or a CMDB view in disguise. Keep it to active, requestable services.
  • Technical language. If users cannot understand an entry, they will skip it. Rewrite names and descriptions from the user’s point of view.

Two more traps we see in small businesses:

  • Too many entries too early. Fifty entries on day one means fifty things to maintain. Begin with the top requests.
  • No named owner. Entries without owners go stale within months.

Putting it into practice with Mavericks

If you would rather not build and run all of this yourself, we can take it on. Mavericks Office Solutions operates as an outsourced IT department for small and mid-sized businesses in Ohio and Michigan. Our managed IT services include proactive support and 24/7 monitoring, backed by a USA-based help desk. We also handle cybersecurity, voice, print and cloud, so your catalog can point to one provider across categories.

Mavericks Office Solutions

If you are comparing providers, our scorecard of eight criteria for choosing a managed IT provider helps you ask the right questions. To see how we work, visit Mavericks Office Solutions and tell us what your team asks IT for most.

FAQ

What is included in an IT service catalog?

Each entry typically includes a service description, the intended audience, benefits, cost, an alias or alternate name and who the service is available to. Many teams also add a request method, an expected response time and a named owner. Group entries into categories so users can browse.

How is a service catalog different from a service desk or ticketing tool?

The catalog is the list of what you offer. The service desk is the team that responds, and the ticketing tool or portal is where requests and incidents are logged. They work best together: the catalog tells users what to ask for, and the portal captures the request and tracks it.

How many services should a small business list?

Start with 10 to 15 of the most common requests, such as new employee setup, password help, device issues, printing, phones and access. Add entries when repeated requests show up under “Other.” A smaller catalog that stays current is more useful than a large one that does not.

Who should own the service catalog?

Assign one catalog manager to oversee quality and consistency, and one owner per entry who confirms its accuracy. In a small company the manager can be an office manager, IT lead or the account manager at your IT provider.

Do I need special software?

No. A well-organized shared page with a request form or a shared mailbox is enough to start. Software becomes worthwhile when you need approvals, automation, request tracking and reporting across many users.

Sources