Service Catalog Examples: Templates and Real-World Ideas

If your users still submit IT requests by emailing someone directly or walking up to a technician’s desk, a well-structured service catalog can change that. A service catalog gives employees a clear, self-service menu of everything IT offers — from password resets to software provisioning — reducing ticket chaos and setting accurate expectations on both sides. This article walks through real service catalog examples, practical templates, and the key categories every IT team should consider, whether you’re building from scratch or improving what you already have.

What Makes a Good IT Service Catalog?

• User-friendly language: Written for employees, not IT staff. Avoid acronyms and technical jargon in service names and descriptions.
• Clear request and fulfillment process: Each service entry should tell users what to expect — what they need to provide, how long it takes, and who handles it.
• Logical categorization: Services grouped by function (hardware, software, access, etc.) so users can find what they need without guessing.
• Defined SLAs per service: Different services carry different priorities. A server outage isn’t the same as a new laptop request.
• Regular maintenance: A catalog that lists retired software or stale services erodes trust. Treat it as a living document.

Service Catalog Categories at a Glance

Service Catalog Examples by Category

1. Hardware and Device Services

This is one of the most requested categories in any IT catalog. It covers the physical equipment employees need to do their jobs. A well-built hardware section reduces back-and-forth between employees and IT by setting procurement timelines upfront.

• Laptop/desktop provisioning: New hire or replacement machine request. Includes form fields for department, manager approval, preferred OS, and delivery date.
• Peripheral replacement: Keyboard, mouse, headset, or monitor requests — often low priority, but high in volume.
• Mobile device setup: Company phone enrollment, MDM configuration, SIM card activation.
• Hardware repair: Submit a broken device for diagnosis and repair, with estimated turnaround time displayed upfront.

For this category, the catalog entry should include expected lead times (especially if procurement is involved) and any eligibility rules — for example, whether a manager signature is required above a certain cost threshold.

2. Software and Licensing Services

Software requests are common and often mishandled. Without a catalog entry, employees email random IT contacts or buy software on personal cards and request reimbursement. A structured software section prevents both problems.

• Licensed software installation: Requests for standard tools (Office, Adobe, project management apps). The catalog should show which software is pre-approved vs. requires additional review.
• License renewal or upgrade: Annual renewals or version upgrades for existing tools.
• New software evaluation: A separate service entry for tools not yet approved — routes to IT procurement and security review.
• Software removal: Offboarding or license reclamation requests.

3. Access and Identity Management Services

This is typically the highest-volume category in any IT service catalog, and the one most suited to automation. Most access requests should be resolvable without a human touching a ticket.

• Password reset: If not already handled by self-service (it should be), a catalog entry with quick routing.
• Account unlock: Locked accounts after failed login attempts.
• New system access: Request access to a specific application or data system, with manager approval workflow built in.
• Access removal: Used for offboarding, role changes, or project end.
• Privileged access request: Admin rights or elevated permissions, requiring security team approval.

4. Onboarding and Offboarding Services

These are composite services — each one triggers multiple tasks behind the scenes. In a service catalog, they appear as a single request to the user (or HR/manager) but spawn automated workflows across IT, HR, and facilities.

• New employee IT setup: Creates accounts, assigns hardware, configures email, enrolls in MDM. Ideally triggered from HR’s hire date in the HRIS.
• Employee departure checklist: Revokes system access, recovers equipment, backs up data, and deactivates accounts.
• Role change / internal transfer: Updates access permissions to reflect new responsibilities, removes access that no longer applies.
• Contractor onboarding: Scoped access setup with an expiration date built into the workflow.

5. Network and Connectivity Services

Network requests often require more lead time and coordination than software requests. The catalog should set those expectations clearly.

• VPN access setup: Configure remote access for an employee, including any required security checks.
• Network drive or share access: Request read/write access to a shared folder or mapped drive.
• Guest Wi-Fi provisioning: Temporary network access for contractors or visitors.
• Firewall exception request: Routes to security team, includes justification field and expiration date.

6. Communication and Collaboration Services

With hybrid work now standard in most organizations, collaboration tools have become infrastructure. These services belong in every modern IT catalog.

• Email account creation: Standalone account setup (for roles not covered by automated onboarding).
• Shared mailbox or distribution list: Create or modify a shared inbox for a team or project.
• Video conferencing license: Assign a Zoom, Teams, or Google Meet license, including room account setup.
• Collaboration tool provisioning: Set up a new Slack workspace, Teams channel, or SharePoint site.

7. Infrastructure and Cloud Services

This category is typically scoped to internal IT teams and development groups rather than general employees. The requests are more complex and SLAs are longer.

• Virtual machine provisioning: Spin up a VM with defined specs, OS, and network configuration.
• Cloud resource request: Provision storage, compute, or database resources in AWS, Azure, or GCP — routed through IT with cost center tagging.
• Backup request: Schedule or restore a backup for a specific server or dataset.
• SSL/TLS certificate request: Issue or renew a certificate for an internal or external service.

What a Single Service Catalog Entry Should Include

Each item in your catalog needs more than a name. A usable catalog entry includes enough information that the requester knows exactly what they’re getting and what’s expected of them. Here’s a practical template for a single service entry:

• Service name: Clear, plain-language name (e.g., “Request Software Installation” not “SWREQ-ITSM”)
• Short description: One or two sentences explaining what this service does and who it’s for
• Who can request: All employees, managers only, IT staff only, etc.
• What you need to provide: List of required information in the form (machine name, justification, manager approval, etc.)
• Expected fulfillment time: Realistic SLA, not aspirational — e.g., “3 business days” not “as fast as possible”
• Cost (if applicable): Whether this is covered by IT budget or charged back to a department
• Related services: Links to adjacent services (e.g., software install links to license request)
• Owner: Which team handles the request (visible internally if not to end users)

ServiceNow Service Catalog Examples

ServiceNow is one of the most widely deployed platforms for building IT service catalogs in enterprise environments. Its catalog module supports hierarchical categories, request variables, approval workflows, and catalog items that trigger backend workflows automatically.

In a typical ServiceNow service catalog setup, you’ll see three tiers: categories (top-level groupings like Hardware or Access), catalog items (individual services like “Request a Laptop”), and record producers (simplified forms that create records in other modules). ServiceNow also supports order guides — bundled catalog items for complex requests like onboarding, where multiple items need to be ordered together.

A common ServiceNow service catalog example for onboarding might include a single order guide titled “New Employee Setup” that automatically triggers separate fulfillment tasks for hardware procurement, account creation, email setup, and badge access — each routed to a different fulfillment team, all tied to one parent request.

If you don’t use ServiceNow, the same structural logic applies to any ITSM platform that supports service catalog functionality — including Jira Service Management, Freshservice, and InvGate Service Management, which offers catalog items with custom forms and approval workflows out of the box.

IT Service Catalog Template: Free Starting Point

Before investing in a dedicated ITSM platform, some teams build their service catalog in Excel or Google Sheets as an interim step. While this doesn’t give you automation or self-service, it helps you define services, SLAs, and ownership before migrating to a tool.

A basic IT service catalogue template in Excel or Sheets should include these columns:

• Service ID: Unique identifier (e.g., HW-001, SW-003)
• Category: Hardware, Software, Access, Network, etc.
• Service Name: Plain-language name
• Description: Brief explanation of what the service covers
• Eligible Requesters: All staff / Managers / IT only
• SLA (business hours): Target fulfillment time
• Approval Required? Yes / No, and who approves
• Fulfillment Team: Which IT group handles it
• Cost/Chargeback: If applicable
• Status: Active / Under review / Retired

This spreadsheet approach works for getting alignment across IT leadership, but it doesn’t scale past a certain point. Once your catalog has 30+ services, self-service and automation become essential — which is where a proper ITSM platform pays for itself quickly.

Business Service Catalog vs. Technical Service Catalog

This distinction matters when designing your catalog structure. A technical service catalog is the internal view — it maps services to underlying infrastructure components, dependencies, CIs in the CMDB, and fulfillment procedures. It’s primarily used by IT staff for planning and incident management.

A business service catalog is the customer-facing view. It presents services in terms employees understand, without exposing technical dependencies or internal routing logic. This is what most people mean when they talk about “the service catalog” in the context of self-service portals.

ITIL recommends maintaining both views, with the business catalog derived from the technical one. In practice, many organizations — especially mid-sized ones — start with the business catalog and add the technical layer as their CMDB matures. The two don’t need to be separate tools; most ITSM platforms manage both within the same system using role-based visibility.

How to Choose the Right Tool for Your Service Catalog

Your service catalog is only as effective as the platform hosting it. A spreadsheet or static webpage won’t handle approvals, SLA tracking, or fulfillment workflows. If you’re evaluating ITSM tools with a strong catalog module, consider what level of complexity your catalog needs to support today and in the next two years.

For smaller IT teams (under 20 agents), tools like Freshservice or InvGate Service Management offer catalog functionality with quick setup and reasonable pricing. InvGate Service Management includes service catalog items with custom forms, approval workflows, and SLA configuration starting at $24.98/agent/month billed annually (5-agent minimum). For teams needing more configuration depth without ServiceNow’s complexity, this is a practical middle ground.

For enterprises already invested in the ServiceNow ecosystem, the native catalog module is the natural choice — it integrates directly with the CMDB, change management, and workflow automation. The tradeoff is implementation complexity and cost.

If your organization has mature DevOps practices, Jira Service Management may already be in use and its catalog module integrates well with Jira Software. For organizations in regulated industries that need detailed audit trails on every service request, BMC Helix ITSM or Ivanti Neurons offer more governance controls.

Frequently Asked Questions

What is a service catalog in ITSM?

A service catalog is a centralized, organized list of IT services that an organization offers to its employees or customers. It defines what each service includes, who can request it, how long fulfillment takes, and any associated costs or approvals. In ITSM, the service catalog is typically part of a self-service portal where users submit requests without needing to contact IT directly.

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

The service portfolio is broader — it includes all services across their entire lifecycle: services in development (pipeline), live services (catalog), and retired services. The service catalog is the subset of the portfolio that is currently active and available to users. Think of the portfolio as the strategic view and the catalog as the operational, customer-facing view.

What should be included in an IT service catalog?

At minimum, each catalog entry should include the service name, a plain-language description, who is eligible to request it, the expected fulfillment time (SLA), required information from the requester, any approval steps, and the team responsible for fulfillment. Cost or chargeback information should be included where applicable.

Can I build a service catalog in Excel?

Yes, and it’s a reasonable starting point for defining your services before moving to an ITSM platform. An IT service catalog template in Excel can capture service names, categories, SLAs, owners, and approval requirements. However, it can’t automate workflows, route requests, or track SLA compliance. Once you have more than 20–30 services or meaningful request volume, a proper ITSM tool with catalog functionality is worth the investment.

How often should you update a service catalog?

At minimum, review your service catalog quarterly. Services should be added when new capabilities are deployed, updated when processes change, and retired when tools or services are decommissioned. An outdated catalog — with broken links, retired software, or stale SLAs — reduces user trust and increases direct contacts to IT staff, defeating its purpose. Assign a catalog owner responsible for maintaining accuracy.

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