IT teams struggle to organize and present their services in a way that end users can easily understand and request. A well-structured service catalog solves this by creating a standardized menu of IT services, but many teams don’t know where to start or what good service catalog examples look like in practice.
This guide provides 15 real-world service catalog examples across different categories, complete with templates and practical ideas you can adapt for your organization. Whether you’re building your first catalog or improving an existing one, these examples will help you create a user-friendly service experience.
What Makes an Effective Service Catalog
Before diving into specific examples, understand the key elements that make service catalogs successful:
- User-focused language: Written from the end user’s perspective, not IT jargon
- Clear service descriptions: What the service does, who can request it, and expected delivery times
- Logical categorization: Services grouped by function or department for easy navigation
- Self-service options: Automated fulfillment where possible to reduce manual work
- Approval workflows: Built-in processes for services requiring management approval
Hardware and Equipment Service Catalog Examples
New Computer Setup
Service Description: Request a new laptop or desktop computer for new employees or equipment replacement. Includes hardware procurement, imaging with standard software, and delivery to the user’s location.
Information Required: Employee name, department, manager approval, preferred delivery date, specific software requirements
SLA: 3-5 business days for standard configurations
Mobile Device Request
Service Description: Provision smartphones or tablets for business use, including device setup, mobile device management enrollment, and corporate app installation.
Information Required: Device type preference, data plan requirements, business justification, cost center
SLA: 2-3 business days
Hardware Repair and Replacement
Service Description: Repair or replace malfunctioning hardware including laptops, monitors, keyboards, and other peripherals.
Information Required: Asset tag number, problem description, urgency level, preferred repair method
SLA: Same day for critical issues, 1-2 business days for standard repairs
Software and Application Service Examples
Software License Request
Service Description: Request access to licensed software applications including productivity suites, design tools, or specialized business applications.
Information Required: Software name, business justification, duration needed, budget approval
SLA: 1-2 business days for standard software, 3-5 days for procurement
Application Access Request
Service Description: Gain access to internal business applications, databases, or cloud services with appropriate security permissions.
Information Required: Application name, access level required, manager approval, training completion status
SLA: 4 hours for standard access, 1-2 days for elevated permissions
Custom Software Development
Service Description: Request development of custom applications, automations, or integrations to support business processes.
Information Required: Detailed requirements document, project timeline, budget allocation, stakeholder approval
SLA: Initial consultation within 5 business days, timeline varies by complexity
Account and Access Management Examples
New User Account Setup
Service Description: Create user accounts for new employees including Active Directory, email, and standard application access based on role.
Information Required: Employee details, department, role template, start date, manager information
SLA: Account ready by employee start date
Password Reset
Service Description: Reset forgotten passwords for various systems and applications with proper identity verification.
Information Required: Username or email, identity verification, system affected
SLA: 30 minutes during business hours
Access Permission Changes
Service Description: Modify user access permissions due to role changes, promotions, or project requirements.
Information Required: Current access level, requested changes, business justification, manager approval
SLA: 4-8 hours for standard changes
Network and Infrastructure Service Examples
Network Access Request
Service Description: Request network connectivity for new locations, temporary setups, or guest access requirements.
Information Required: Location details, bandwidth requirements, security level needed, duration
SLA: 2-3 business days for standard requests
VPN Access Setup
Service Description: Provision secure remote access to corporate network resources for employees working remotely.
Information Required: Employee information, remote work justification, device details, security training completion
SLA: 4 hours during business hours
Website Hosting Request
Service Description: Set up web hosting for departmental websites, project sites, or internal applications.
Information Required: Site purpose, expected traffic, security requirements, content management needs
SLA: 3-5 business days
Training and Support Service Examples
IT Training Sessions
Service Description: Schedule group or individual training sessions for software applications, security awareness, or IT policies.
Information Required: Topic requested, number of attendees, preferred dates, skill level
SLA: Training scheduled within 10 business days
Technical Consultation
Service Description: One-on-one consultation for complex technical questions, project planning, or technology recommendations.
Information Required: Consultation topic, urgency level, preferred format (phone, email, in-person)
SLA: Initial response within 4 hours, meeting scheduled within 2 business days
Equipment Installation Support
Service Description: On-site support for installing and configuring new equipment or software at user workstations.
Information Required: Installation type, location, preferred time, special requirements
SLA: Scheduled within 3 business days
Service Catalog Templates and Formats
Effective service catalogs can be implemented using various formats depending on your ITSM tool and organizational needs:
Excel Template Format
For organizations starting with basic service catalog management, an Excel template can include columns for Service Name, Description, Category, SLA, Required Information, and Approval Process. This format works well for initial planning and can be imported into ITSM tools later.
ServiceNow Service Catalog Examples
ServiceNow provides robust service catalog capabilities with drag-and-drop form builders, automated workflows, and integration with other ITSM processes. Popular ServiceNow catalog items include hardware requests, software provisioning, and access management services with built-in approval chains.
Self-Service Portal Design
Modern service catalogs emphasize self-service capabilities through user-friendly web portals. These typically feature search functionality, service categories, and guided request forms that collect all necessary information upfront to minimize back-and-forth communication.
Best Practices for Service Catalog Implementation
Start small with your most commonly requested services and expand gradually. Focus on services that can be standardized and partially automated to maximize efficiency gains. Regularly review catalog usage metrics to identify popular services that could benefit from streamlined processes.
Ensure clear ownership for each service with defined roles for catalog maintenance, fulfillment, and continuous improvement. Service descriptions should be updated regularly to reflect changes in processes, technologies, or organizational requirements.
Involve end users in catalog design and testing to ensure services are presented in terms they understand. Conduct periodic surveys to gather feedback on catalog usability and identify gaps in service offerings.
Integrate your service catalog with existing ITSM processes including incident management, change management, and asset management to create a cohesive IT service experience.
Frequently Asked Questions
What’s the difference between a service catalog and service portfolio?
A service catalog contains only live services available to end users, while a service portfolio includes all services across their lifecycle – including those in development, retired, or under consideration. The catalog is the customer-facing subset of the broader portfolio.
How many services should be in a service catalog?
Start with 10-20 core services that represent 80% of your request volume. Most successful catalogs contain 30-50 services organized into 5-8 main categories. Too many options can overwhelm users, while too few may not meet their needs.
Should all IT services be in the catalog?
No, focus on standardized, repeatable services that benefit from self-service or structured workflows. Complex, one-off requests are often better handled through general support channels rather than catalog items.
How do you measure service catalog success?
Key metrics include catalog adoption rate, request fulfillment time, first-call resolution rate, user satisfaction scores, and reduction in email/phone requests for cataloged services. Track these monthly to identify improvement opportunities.
What information should be collected for each service request?
Collect the minimum information needed for fulfillment, approval, and tracking. Common fields include business justification, urgency level, delivery location, and approver information. Use conditional logic to show relevant fields based on service type and user selections.
Pricing accurate as of the publish date and subject to change. Verify current pricing on each vendor’s official site before purchasing.
Photo by Cherrydeck on Unsplash
