Request Management is ServiceNow's system for handling employee service requests like new equipment, software access, or account changes. Employees browse a service catalog, submit requests, and the system automatically routes them through approval chains and assigns tasks to the right teams. IT managers, service desk agents, and department heads use it to replace email chains and manual processes that slow down fulfillment and create confusion about request status. Once in place, Request Management transforms how your organization handles internal services. Employees get a consumer-like experience similar to online shopping, while IT gains visibility into demand patterns, can enforce approval policies automatically, and can measure how quickly different types of requests get fulfilled. The system connects to other ServiceNow modules so a laptop request can automatically create configuration items and link to knowledge articles.
Key Capabilities
Service Catalog
Employees browse and order services through a searchable catalog interface that looks like an online store. Each catalog item has descriptions, images, and forms that collect the right information upfront. This eliminates back-and-forth emails asking for missing details and ensures requests have everything needed for fulfillment.
Automated Approval Routing
Requests automatically go to the right approvers based on rules you define, like manager approval for requests over a certain cost or security team approval for access requests. Approvers get notifications and can approve from email or mobile without logging into ServiceNow. This prevents requests from sitting in inboxes and provides audit trails for compliance.
Task Assignment and Tracking
Complex requests automatically break into tasks assigned to different teams, like procurement ordering a laptop while IT prepares the software image. Everyone sees their piece of the work and overall progress. Requesters get updates without having to ask, and managers can spot bottlenecks before they cause delays.
Request Templates and Standardization
Catalog items use forms that capture information consistently and offer standard options instead of free-text descriptions. This reduces errors, speeds up fulfillment, and makes it easier to track costs and usage patterns. Teams spend less time clarifying what people actually want.
Self-Service Portal
Employees can check request status, see their order history, and find answers in knowledge articles without contacting the service desk. This reduces ticket volume for status updates and gives people the information they need immediately. Service desk agents can focus on complex issues instead of answering tracking questions.
Fulfillment Workflows
Behind each catalog item, workflows handle the actual work of fulfillment through automated tasks, integrations with other systems, and escalation rules. Simple requests might complete automatically, while complex ones follow multi-step processes with different teams. This ensures nothing falls through the cracks and maintains consistent service delivery.
How It Works
An employee visits the service portal and finds what they need in the catalog, filling out a request form that captures all necessary details. The system immediately applies approval rules, sending the request to managers or other approvers based on cost, type, or the requester's department. Once approved, Request Management creates tasks for fulfillment teams and begins tracking progress, sending automated updates to everyone involved. Fulfillment teams complete their assigned work and mark tasks complete, with the system automatically closing the request when all work is done and notifying the original requester.
Who Uses It and How
Global technology company
Their service catalog handles over 200 different request types from laptop orders to software licenses to facility access cards. Each request follows predefined workflows with automatic routing to procurement, IT, security, or facilities teams based on the request type. Employees can track everything through a single portal and managers get spending visibility across all departments.
Result: Request fulfillment time dropped from an average of 8 days to 3 days, and service desk call volume decreased by 40% as employees could self-serve status updates.
Large hospital network
Medical staff request access to clinical systems, new badges, and specialized equipment through catalog items tailored to different roles like nurses, doctors, and technicians. Each request automatically routes through medical records compliance, IT security, and department managers based on what systems are involved. The audit trail helps with regulatory compliance and security reviews.
Result: New employee onboarding that previously took 2 weeks now completes in 4 days, with 100% compliance on security approval requirements.
University IT department
Students and faculty request software installations, account resets, and classroom technology setup through separate catalogs with different approval chains. Student requests might auto-approve for standard software while faculty research requests go through additional security reviews. Integration with the student information system automatically validates eligibility and department budgets.
Result: Reduced service desk tickets by 60% during peak periods like start of semester, with students getting faster resolution for common requests.
Financial services firm
Employees request trading system access, mobile device approvals, and client data permissions through a catalog designed around strict compliance requirements. Every request captures business justification and automatically creates audit records. Multi-level approvals ensure risk management, compliance, and business managers all review sensitive access requests before fulfillment.
Result: Audit preparation time cut from weeks to hours, with complete documentation of who approved what access and when, plus automatic access reviews every quarter.
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Implementation: What to Know
You need your IT teams, HR, and key business departments involved from the start since they will design the catalog and approval processes that employees actually use. Plan for 3-6 months for a full rollout, starting with a few simple catalog items to test workflows before adding complex multi-step requests. Having your current service offerings documented and knowing who should approve what types of requests is essential before you start building. Most implementations stall because teams try to automate their current messy processes instead of first cleaning up and standardizing how work actually gets done.
Common Use Cases
New employee gets laptop and software access
Manager submits an onboarding request for a new hire that includes laptop, phone, building access, and system accounts. Request Management automatically creates separate tasks for IT to configure equipment, security to provision accounts, and facilities to create badges. The new employee gets everything they need on their first day without the manager having to coordinate with multiple teams.
Department requests recurring software licenses
Marketing manager orders 20 Adobe Creative Cloud licenses for the team through a catalog item that captures which users need access and which department budget to charge. The request goes to the manager's director for approval, then automatically creates a purchase order and tasks for IT to assign licenses once they arrive. The system tracks license usage and sends renewal reminders.
Employee needs urgent password reset during off hours
Someone locked out of their account uses the service portal to verify their identity and request a password reset. The system automatically validates their employee status, sends a verification code to their registered mobile number, and resets the password without human intervention. They get back to work immediately instead of waiting for the service desk to open.
Project team requests temporary contractor access
Project manager submits a request for external consultants to access specific systems for a 3-month engagement. Request Management routes the request through security for background check requirements, legal for contract verification, and IT for technical setup. All tasks coordinate automatically and access gets provisioned with automatic expiration dates.
Office relocation requires equipment and services transfer
Employee relocating to a different office submits a single request that triggers tasks for IT to transfer their equipment, telecom to move phone services, facilities to update seating assignments, and HR to update records. Everything coordinates through one request instead of the employee having to contact each department separately.
Key Tables
Best Practices
- ✓Start with your most common and simple requests first, then add complexity once people understand how the system works and you have worked out approval processes.
- ✓Make catalog item names and descriptions match how employees actually think about services, not internal IT terminology or department names.
- ✓Set up approval rules that default to auto-approve low-risk items rather than requiring manual approval for everything, which creates bottlenecks.
- ✓Use order guides for complex requests that need multiple related items instead of making people submit separate requests that should be coordinated.
- ✓Configure clear escalation rules and timeouts so requests do not sit indefinitely when someone is out of office or forgets to approve.
- ✓Build knowledge articles that answer common questions and link them to relevant catalog items so people can self-serve before submitting requests.
Common Pitfalls
Creating too many catalog items that overlap or confuse employees about which one to use
Start with broad categories and add specific items only when you see clear demand patterns and different fulfillment processes.
Setting up approval chains that require too many people to review simple requests
Design approval policies around risk and cost thresholds, not organizational hierarchy, and use automatic approvals for routine items.
Making catalog item forms that ask for information the fulfillment team does not actually need
Work backwards from what fulfillment teams need to do their job and only ask requesters for information that changes how the request gets handled.
Not training fulfillment teams on their new tasks and notifications before going live
Run pilot programs with key fulfillment teams and make sure they understand how to work their task queues and update request status.
Building workflows that are too rigid and cannot handle exceptions or special cases
Include manual task options and escalation paths so fulfillment teams can adapt when standard processes do not fit the situation.
Frequently Asked Questions
What is the difference between Request Management and Incident Management?
Request Management handles new services or changes that employees ask for, like getting a laptop or software access. Incident Management handles things that are broken and need to be fixed, like when email is down or someone cannot log in. Requests are planned work while incidents are unplanned problems.
Do I need Request Management if I already have a service desk?
Request Management makes your service desk more efficient by automating routine requests and giving employees self-service options. Your service desk agents can focus on complex issues instead of processing standard requests manually. Most organizations use both together.
Can employees submit requests without logging into ServiceNow?
Employees typically need to log in to submit requests so the system knows who they are and can route approvals correctly. However, you can set up anonymous catalog items for things like guest WiFi access or general inquiries that do not need authentication.
How do I handle requests that need multiple departments to work together?
Use request items that automatically create tasks for different fulfillment groups, or set up order guides that bundle related catalog items into one coordinated request. The system can track all the pieces and provide overall status to the requester.
What happens if someone needs to approve a request but they are on vacation?
You can configure delegate approvers, escalation rules that automatically reassign after a certain time, or group approvals where any member of a team can approve. The system can also send reminders and notifications to prevent requests from stalling.
Can I integrate Request Management with our procurement or HR systems?
Yes, ServiceNow can integrate with external systems through web services, email, or file transfers. This lets you automatically create purchase orders, update employee records, or sync with other tools your fulfillment teams use.
How do I measure if Request Management is working well?
Track metrics like average fulfillment time, approval delays, request volume by category, and employee satisfaction scores. ServiceNow includes dashboards and reports that show these metrics automatically, plus you can build custom reports for specific business needs.
Related Modules
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue