IT Service Catalog: How to Build, Structure & Maintain One

What Is an IT Service Catalog and Why Does It Matter

An IT service catalog is a centralized, customer-facing list of all IT services available to an organization's users. It describes each service in business terms (not technical jargon), defines how to request the service, specifies the expected delivery time and service levels, and provides transparency into what IT delivers.

A service catalog is not:

• A CMDB (Configuration Management Database) listing every server and application
• A technical architecture document
• A project portfolio
• A helpdesk ticket category list

A service catalog is:

• A menu of services written in language the business understands
• A self-service portal where users can request what they need
• A commitment document defining what IT will deliver and when
• A communication tool that makes IT's value visible to the organization

Business Benefits

For IT consumers (employees and business units):

• One place to find and request any IT service
• Clear expectations for delivery times and service levels
• Self-service options that reduce wait times
• Transparency into request status and progress

For IT leadership:

• Visibility into service demand and consumption patterns
• Data-driven resource allocation based on actual service requests
• Improved customer satisfaction through clear expectations
• Foundation for chargeback or showback models
• Evidence of IT's value contribution to the business

For the organization:

• Reduced shadow IT as employees can easily find approved services
• Standardized processes that improve efficiency and reduce errors
• Audit trail for compliance requirements
• Faster onboarding as new employees can discover available services

The numbers support the investment. Organizations with mature service catalogs report 30-40% reduction in service request resolution times, 25% reduction in helpdesk call volume (through self-service), and measurable improvements in employee satisfaction with IT.

Service Catalog Structure

A well-structured catalog organizes services into categories that make sense to the people using them, not to the IT team providing them.

Service Categories

Organize services into 8-12 high-level categories. Here is a proven structure that works for most organizations:

1. Access and Accounts

• New employee account setup
• Application access requests
• Permission changes and role modifications
• Password resets and account unlocks
• Contractor and vendor account management
• Account deactivation (offboarding)

2. Devices and Hardware

• New laptop or desktop request
• Mobile device provisioning
• Monitor and peripheral requests
• Hardware repair or replacement
• Device refresh and upgrades
• Equipment return (offboarding)

3. Software and Applications

• Standard software installation
• Non-standard software request (requires approval)
• SaaS application access
• Software license requests
• Application upgrades
• Custom application development request

4. Email and Communication

• Email account setup and configuration
• Distribution list management
• Shared mailbox requests
• Video conferencing setup
• Phone and voicemail configuration
• Messaging platform access (Slack, Teams)

5. Network and Connectivity

• VPN access setup
• WiFi access requests
• Network drive and file share access
• Remote access configuration
• Guest network access
• Site-to-site connectivity requests

6. Printing and Document Services

• Printer access setup
• New printer installation request
• Scanning and document management
• Large format printing
• Secure printing setup

7. Security Services

• Multi-factor authentication enrollment
• Security certificate requests
• Encryption setup
• Security incident reporting
• Vulnerability scan request
• Security awareness training enrollment

8. Data and Analytics

• Database access requests
• Report and dashboard requests
• Data extract requests
• Business intelligence tool access
• Data warehouse access
• Data archival and retention requests

9. Cloud Services

• Cloud account and subscription setup
• Cloud resource provisioning
• Cloud storage allocation
• Cloud migration assistance
• Cloud cost optimization review

10. Support and Troubleshooting

• General IT support (break/fix)
• Application troubleshooting
• Performance issues
• Connectivity problems
• Audio/visual equipment support
• Conference room technology support

Defining Individual Services

Each service in your catalog needs a complete definition. This is where most catalog initiatives fail by either providing too little information (unhelpful) or too much (overwhelming). Strike a balance with these essential fields.

Service Definition Template

For every service, document the following:

Service identity:

• Service name: Clear, concise, jargon-free (e.g., "New Laptop Request" not "End User Computing Device Provisioning")
• Service description: 2-3 sentences explaining what the service provides in business terms
• Service category: Which catalog category this service belongs to
• Service ID: Unique identifier for tracking and reporting

Service availability:

• Who can request: All employees, specific departments, managers only, etc.
• How to request: Self-service portal link, form, email, phone
• Approval required: Yes/No, and who approves (manager, IT lead, security team)
• Cost: Free, department chargeback amount, or requires budget approval

Service delivery:

• Fulfillment time: Target time from approved request to delivery (e.g., "2 business days")
• Service hours: When the service is available (e.g., "Monday-Friday 8 AM - 6 PM ET")
• Delivery method: In-person, remote, automated, shipped
• Dependencies: Prerequisites the requester needs (e.g., manager approval, completed training)

Service levels:

• Availability target: Expected uptime for the service (e.g., 99.9%)
• Response time: How quickly IT acknowledges the request
• Resolution time: How quickly the request is fulfilled
• Escalation path: What to do if the service is not delivered within the expected timeframe

Support information:

• Service owner: The IT team or individual responsible for this service
• Support contact: How to get help if something goes wrong after delivery
• Knowledge articles: Links to self-help documentation and FAQs

Example Service Definition

Here is a fully worked example:

Service Name: New Laptop Request

Description: Request a new laptop computer configured with standard software and security tools. Available for new hires, equipment refreshes (devices older than 4 years), and replacements for damaged devices.

Category: Devices and Hardware

Who Can Request: Any employee. Managers can request on behalf of new hires before their start date.

How to Request: Self-service portal > Devices and Hardware > New Laptop Request

Approval Required: Yes. Manager approval plus budget holder approval for non-standard configurations.

Cost: Standard laptop: allocated from IT budget. Premium laptop (for developers, designers): $500 department chargeback above standard allocation.

Fulfillment Time: Standard configuration: 3 business days. Custom configuration: 5-7 business days. New hire: delivered before start date if requested 5+ business days in advance.

Service Hours: Requests processed Monday-Friday, 8 AM - 6 PM ET. Delivery via shipping or in-person at IT support desk.

Options:

• Standard laptop (13" or 14", 16GB RAM, 256GB SSD)
• Developer laptop (15", 32GB RAM, 512GB SSD)
• Design laptop (15" or 16", 32GB RAM, 512GB SSD, dedicated GPU)

Dependencies: Manager approval, completed security awareness training (for new hires).

Service Owner: End User Computing Team

Support Contact: IT Support Portal or ext. 4357

The Service Request Workflow

A catalog is only useful if requests flow smoothly from submission to fulfillment. Design your workflow with these stages:

Standard Request Workflow

1. Discovery: User browses the catalog or searches for the service they need
2. Request submission: User fills out the request form with required information
3. Automated validation: System checks for completeness and applies business rules
4. Approval routing: Request is routed to the appropriate approver(s) based on service rules
5. Fulfillment assignment: Approved request is assigned to the fulfillment team or individual
6. Fulfillment execution: The service is provisioned, configured, or delivered
7. Verification: The fulfillment team confirms the service is working as expected
8. User notification: Requester is notified that the service is ready
9. Satisfaction survey: Short survey (1-3 questions) collects feedback on the experience
10. Closure: Request is closed and metrics are recorded

Automation Opportunities

Identify services where you can automate part or all of the fulfillment:

Fully automatable:

• Password resets (self-service with identity verification)
• Distribution list membership changes
• Standard software installations via software center
• VPN access provisioning (with manager approval automation)
• Multi-factor authentication enrollment

Partially automatable:

• New employee account creation (automated provisioning triggered by HRIS, manual verification)
• Application access requests (automated for standard roles, manual for exceptions)
• Cloud resource provisioning (infrastructure-as-code templates with approval gate)
• Device configuration (automated imaging with manual shipping)

Require manual fulfillment:

• Custom application development requests
• Hardware repair and replacement
• Complex network changes
• Security incident response
• Architecture and consulting engagements

Target automating 40-60% of your highest-volume requests within the first year. Each automated service reduces resolution time from days to minutes and frees staff for higher-value work.

Aligning with ITIL Best Practices

The service catalog is a core component of ITIL (Information Technology Infrastructure Library) Service Management. Here is how it connects to the broader ITIL framework.

ITIL 4 Service Value Chain

In ITIL 4, the service catalog supports multiple value chain activities:

• Engage: The catalog is the primary engagement channel between IT and its customers
• Design and Transition: Service definitions document how services are designed and transitioned into operation
• Obtain/Build: Request workflows trigger provisioning and build activities
• Deliver and Support: SLAs and support contacts in the catalog define how services are delivered and supported

Service Portfolio Relationship

The service catalog is one component of the broader service portfolio:

• Service pipeline: Services under development or consideration (not yet in the catalog)
• Service catalog: Active services currently available to users (the customer-facing view)
• Retired services: Services that have been decommissioned (removed from the catalog but retained for reference)

Connecting to Other ITIL Processes

Incident Management: When users experience issues with a cataloged service, the incident is linked to the service for tracking and trend analysis.

Change Management: Changes to services in the catalog follow change management processes. Service definitions are updated to reflect changes.

Service Level Management: SLAs defined in the catalog are monitored and reported. SLA breaches trigger reviews and improvement actions.

Knowledge Management: Each service in the catalog links to relevant knowledge articles, FAQs, and self-help guides.

Financial Management: The catalog provides the foundation for IT cost transparency, chargeback, and showback models.

Building Your Catalog: Step-by-Step Process

Step 1: Define Scope and Objectives (Weeks 1-2)

• Identify the initial audience (start with one department or location before rolling out organization-wide)
• Set clear objectives with measurable targets (e.g., "reduce average request fulfillment time by 30% within 6 months")
• Secure executive sponsorship from both IT leadership and a business leader
• Assign a service catalog manager who owns the initiative

Step 2: Inventory Existing Services (Weeks 3-4)

• Interview IT team leads to identify every service they provide
• Review helpdesk ticket categories and request types
• Analyze ticket volume to identify the most frequently requested services
• Talk to business users about what they need from IT
• Document undocumented services (the tribal knowledge that lives in people's heads)

Step 3: Define and Prioritize Services (Weeks 5-6)

• Write service definitions using the template above
• Prioritize which services to include in the initial catalog launch
• Start with the 20-30 highest-volume services that cover 80% of requests
• Define fulfillment workflows for each service
• Set realistic SLAs based on current performance (do not promise targets you cannot meet on day one)

Step 4: Select and Configure the Platform (Weeks 5-8)

Your service catalog needs a platform. Options include:

• ITSM platforms (ServiceNow, Jira Service Management, BMC Helix, Freshservice) that include built-in service catalog modules
• SharePoint or Confluence for simpler implementations without workflow automation
• Custom-built portals for organizations with unique requirements

Platform requirements checklist:

• User-friendly portal with search and browse functionality
• Customizable request forms with conditional logic
• Approval workflow engine with multi-level routing
• Integration with Active Directory / identity provider for authentication
• SLA tracking and alerting
• Reporting and analytics dashboard
• Mobile-responsive design
• API for integration with other systems (HRIS, CMDB, monitoring)

Step 5: Pilot and Iterate (Weeks 9-12)

• Launch the catalog with a pilot group (100-200 users)
• Collect feedback through surveys and direct conversations
• Measure key metrics: adoption rate, fulfillment time, user satisfaction
• Refine service definitions, workflows, and the user interface based on feedback
• Fix issues before broader rollout

Step 6: Organization-Wide Launch (Week 13+)

• Communicate the launch through email, intranet, and team meetings
• Provide training or walkthrough videos showing how to use the catalog
• Designate "catalog champions" in each department to help with adoption
• Monitor adoption metrics daily for the first month
• Continue adding services based on demand and feedback

Maintaining Your Service Catalog

A catalog that is not maintained becomes a liability rather than an asset. Users lose trust quickly if they find outdated information or broken request forms.

Ongoing Maintenance Tasks

Monthly:

• Review and update service definitions for accuracy
• Check that all request forms and workflows are functioning
• Analyze request data to identify new services to add
• Remove or archive retired services
• Review SLA performance and adjust targets if needed

Quarterly:

• Conduct user satisfaction survey (Net Promoter Score or similar)
• Review and update the service category structure
• Assess automation opportunities for high-volume manual services
• Report catalog metrics to IT leadership
• Update pricing and chargeback rates if applicable

Annually:

• Comprehensive review of all service definitions
• Benchmark SLA performance against industry standards
• Assess platform capabilities and evaluate upgrades or migrations
• Strategic planning for new services aligned with business priorities
• Budget review for service catalog operations and improvements

Governance Model

Assign clear ownership for catalog governance:

• Service Catalog Manager: Overall ownership of the catalog, responsible for quality, adoption, and continuous improvement
• Service Owners: Each service has an owner responsible for the accuracy of its definition, SLA performance, and fulfillment quality
• Change Advisory Board: Reviews and approves changes to service definitions, SLAs, and pricing
• User Advisory Group: Business representatives who provide feedback on catalog usability and service needs

Measuring Service Catalog Success

Track these metrics to demonstrate value and drive improvement:

Adoption Metrics

• Catalog usage rate: Percentage of IT requests submitted through the catalog versus email, phone, or walk-ups. Target: 80%+ within 12 months
• Self-service resolution rate: Percentage of requests resolved without human intervention. Target: 30-40%
• Search success rate: Percentage of searches that result in a service request (indicates users are finding what they need)

Efficiency Metrics

• Average fulfillment time: Time from request submission to delivery, tracked by service and compared against SLA targets
• SLA compliance rate: Percentage of requests fulfilled within the defined SLA. Target: 90%+
• First-time resolution rate: Percentage of requests fulfilled correctly without rework
• Cost per request: Total fulfillment cost divided by request volume, tracked over time to demonstrate efficiency gains

Satisfaction Metrics

• User satisfaction score: Post-fulfillment survey results. Target: 4.0+ on a 5-point scale
• Net Promoter Score (NPS): Would users recommend the catalog to colleagues? Target: 30+
• Complaint rate: Number of complaints or escalations per 100 requests

Business Impact Metrics

• Shadow IT reduction: Decrease in unapproved software and services discovered through audits
• Onboarding time: Time from new hire start date to fully productive with all required IT services
• IT perception scores: Improvement in annual employee survey scores related to IT satisfaction

Implementation Checklist

Use this checklist to guide your service catalog initiative:

• Secure executive sponsorship from IT and business leadership
• Assign a dedicated service catalog manager
• Inventory all IT services through interviews, ticket analysis, and documentation review
• Define service categories that align with how users think about IT services
• Write service definitions for the top 20-30 highest-volume services
• Define fulfillment workflows and approval chains for each service
• Set initial SLAs based on current performance data
• Select and configure a service catalog platform
• Integrate with Active Directory, HRIS, and existing ITSM tools
• Pilot with a small user group and collect feedback
• Refine based on pilot feedback
• Launch organization-wide with communication and training
• Monitor adoption and satisfaction metrics daily for the first month
• Establish monthly, quarterly, and annual maintenance cadence
• Report results to leadership and plan continuous improvements

For more IT operations frameworks, explore our IT Management hub, IT Operations resources, and the IT Manager's resource center. These resources provide templates and guides that complement your service catalog initiative.