Service request management makes IT requests structured, trackable and consistently fulfilled: access, equipment, software, information. Done well, it takes repetitive work off the service desk, gives users a portal they trust and shows IT management what is requested and how fast it is delivered. Our ITIL v4 certified consultants design the catalogue, forms, approvals and SLAs, then configure them in your tool.
Service request management is the ITIL 4 practice that handles predefined, user-initiated requests for services in a consistent and efficient way. A service request is something a user is entitled to receive: a new starter's account, a laptop, access to an application, a shared mailbox. It is not a disruption and not a complaint; its fulfilment path is known in advance. It is one of the core practices of ITSM, next to incident, problem and change management.
That is what separates it from incident management. An incident is unexpected and needs diagnosis; a request is anticipated and follows a standard workflow with its own SLA. Merging both in one queue is the most common reason request SLAs are missed: incidents get handled like requests, requests wait behind incidents, and neither process performs.
The service catalogue is the list of services IT provides, each with a fulfilment procedure, an owner, the approvals it needs and an SLA users can see when they submit. Most IT catalogues cover four families:
| Family | Example items |
|---|---|
| Access and identity | New starter account, access rights change, role assignment, account unlock, leaver |
| Hardware and equipment | Laptop, smartphone, screen and peripherals, replacement device |
| Software and licences | Software installation, licence assignment, application access, subscription |
| IT services and infrastructure | VPN access, shared mailbox, distribution list, cloud resource, network access |
How big should it be at launch? Smaller than most teams think:
| Stage | Scope |
|---|---|
| Launch | The most requested items only, typically 15 to 25, each with a tested procedure and an SLA the team can keep |
| Extend | New items added when ticket data shows a recurring request handled by email or phone |
| Maintain | A quarterly review: retire unused items, update procedures, check SLAs against reality |
If the team cannot commit to a fulfilment time, the item is not ready to publish. An accurate catalogue of twenty items does more for adoption than a complete catalogue where half the procedures are out of date.
Categories follow how IT is organised, not what users look for. Nobody searches "end-user asset lifecycle" when they need a new laptop.
Long static forms ask for information users do not have. Dynamic forms that ask only what is needed, step by step, get completed.
When users cannot see where their request stands, they follow up by email or phone, and the portal loses its purpose.
Items pile up, procedures go stale, SLAs slip and users return to informal channels. Self-service is a service design and governance job, not a tool setting.
Request management is as much service design as platform configuration. We configure it natively in the tool your team already uses, on any of the 10 ITSM platforms we work on; when a tool change is on the table, HaloITSM is our pick for most mid-sized organisations. Our advice is independent. If you choose HaloITSM, we can also supply the licences as its certified partner, and we tell you so up front.
Items defined, structured and prioritised with IT stakeholders, written in the users' words, each with an SLA, approval chain and fulfilment procedure.
Logical categories, dynamic forms, clear status and mobile access. Adoption follows usability, not internal communication campaigns.
Multi-level approvals in the platform with timeouts, escalation and an audit trail, instead of email threads that nobody answers.
Directory provisioning, endpoint management, identity and cloud integrations: every automated step is one less manual task.
Hardware and software delivered through a request create or update the asset record at fulfilment, not weeks later by hand.
Fulfilment time per item, SLA breaches, approval bottlenecks and most requested services, reviewed to decide what to automate next.
From the user's click to the closed record. Each stage is a configuration choice in the tool; leaving it on default is where most request processes start to drift.
The user picks an item in the catalogue; a dynamic form collects exactly what fulfilment needs, in plain language.
The request is checked, classified and routed: standard items go straight to fulfilment, others to the right approver.
Manager, security or finance approval where needed, with timeouts and escalation configured in the platform.
The documented procedure is followed, automated where possible, assigned to the right team with the SLA clock running.
The user is updated at each stage and confirms that the request has been fulfilled.
A complete record feeds the reports that show which items to improve or automate next.
In a free 30-minute audit, a senior consultant reviews your catalogue, portal and request workflows with you and leaves you with your three priorities.
Account creation, access rights, software deployment and notifications are the first candidates. Fix the procedure, then automate it.
AI classifies requests, spots missing information before submission and answers routine status questions on chat or voice.
The same catalogue model works for HR, facilities and finance requests once the IT catalogue runs well.
Whose team spends its days on repetitive requests that arrive incomplete through email and phone.
Who want predictable delivery times and a clear view of what the business asks IT for.
Who need a catalogue, approvals and SLAs that stay accurate after go-live.
| KPI | What it tells you |
|---|---|
| Fulfilment time per item | The average time from submission to completion, measured per catalogue item rather than as one global average. |
| SLA compliance | The share of requests delivered within the committed time; a persistent gap means the SLA, the staffing or the approvals need work. |
| Self-service adoption | The share of requests submitted through the portal rather than email or phone. |
| First-time fulfilment | Requests delivered without rework or a clarification round; a low rate points to forms that miss information. |
| User satisfaction (CSAT) | How users rate the experience at closure: the indicator business stakeholders see first. |
For definitions and dashboard examples, see our guide to service desk KPIs.
An incident is an unplanned disruption that needs triage and diagnosis. A service request is a predefined need the IT team fulfils routinely, with a path known in advance. Handling both in the same queue degrades both. See incident management for how the two connect.
The structured list of services IT provides, each with a fulfilment procedure, an SLA and an approval chain. Without it, every request is handled ad hoc and users have no reference for what IT can do for them. A published, maintained catalogue is also the main driver of portal adoption.
Start with the most requested items, typically 15 to 25, each with a tested procedure and an SLA the team can keep. Add items when ticket data shows a recurring request arriving outside the portal. Accuracy matters more than coverage.
Make the portal faster and easier than sending an email: items users find in a couple of clicks, short forms, and a status they can follow without asking. Then keep the catalogue accurate. If the portal takes more effort than the alternatives, no communication campaign will fix adoption.
By removing manual steps from high-volume, low-complexity requests: account provisioning, access rights, software deployment, licence assignment and notifications. Each automated step frees time for higher-value work. Read more on ITSM automation and orchestration.
Hardware and software delivered through a request should create or update the asset record at the moment of fulfilment. Platforms that link requests and assets natively make this automatic. See IT asset management.
It depends on the number of catalogue items, the approvals and the integrations. A core catalogue, portal and approval workflows come first; fulfilment automation and directory integration follow. The two-week diagnosis of our method gives you a dated plan based on your own ticket data.
No. We configure request management in the tool you already use, on any of the 10 ITSM platforms we work on. HaloITSM is our pick when a tool change is on the table.
Book your free 30-minute ITSM audit. A senior consultant reviews your catalogue, portal and workflows with you and leaves you with your three priorities.
Learn how the ServiceNow MCP server connects AI agents to governed ITSM workflows, Action Fabric and secure enterprise automation, plus readiness steps for 2026.
Read more →
Learn how a HaloITSM Lansweeper integration connects discovery data to HaloITSM, enabling cleaner CMDB records, faster triage, and better change decisions.
Read more →
A practical ServiceNow migration cutover plan helps reduce risk, protect service continuity, validate integrations and support confident ITSM modernisation.
Read more →
