ITIL Service Request Management: Request Models, Fulfilment and Approvals

Not everything users contact IT about is a failure. Most of the time they simply want something: access to a shared folder, a new phone, a software licence. Service request management supports the agreed quality of a service by handling all pre-defined, user-initiated service requests effectively and in a user-friendly manner. In most organisations requests outnumber incidents, so this practice shapes how users experience IT every week.

What Is a Service Request?

A service request is a request from a user or a user’s authorised representative that initiates a service action which has been agreed as a normal part of service delivery. Requests are usually low risk, frequent, well understood and have a defined procedure. If it needs a design discussion or carries significant risk, it is probably a project or a change instead.

CategoryExamples
AccessNew account, shared mailbox, folder permission, VPN
EquipmentNew laptop, monitor, headset, mobile phone
SoftwareInstall approved application, licence extension
InformationHow do I connect to the printer? Report on licence usage
Joiner, mover, leaverOnboarding bundle, role change, offboarding checklist

Request Models

For each type of request, define a request model, a repeatable way of handling it so that each request follows the same steps. A good model records:

  • The name, description and who can request it.
  • The information the requester must supply (a form, with required fields).
  • Approvals needed, and from whom.
  • The fulfilment steps, owners and target times.
  • Any costs and the way they are charged.
  • How the requester is kept informed and how the request is closed.

Approvals: Use Them Sparingly

Approvals add delay. Ask of each one: does it ever say no? If the manager approves 99% of requests without reading them, the approval is a ritual that costs time. Reserve approvals for requests with real cost, security or compliance impact, and pre-approve standard bundles. Common approval types include line manager (for cost), data owner (for access to sensitive data) and security (for privileged access).

Self-Service and Automation

The best request is one that fulfils itself. A portal with a clear catalogue (see Service Catalogue and Service Design) lets users find and submit requests without calling anyone. Behind the scenes, automation can create accounts, add users to groups or reset passwords with no human touch. ITIL’s guidance to “optimize and automate” (see ITIL Guiding Principles) applies: first fix the process, then automate the stable steps.

Request Fulfilment Flow

  1. The user submits a request through a portal, email, chat or phone.
  2. The system records it and checks it against a request model.
  3. Required approvals are obtained automatically where possible.
  4. Fulfilment tasks are assigned to the right team or automated.
  5. The user is updated and asked to confirm completion.
  6. The request is closed and satisfaction is recorded.

Worked Example: A New Starter Bundle

HR submits a joiner form that includes the start date, role and manager. The request model for “New employee” creates linked tasks: create the account and mailbox, order a laptop from the standard list, add the person to role-based groups, assign a licence and book a welcome session. No approval is needed because HR owns the hiring decision and the role defines the equipment. The tasks run in parallel, the line manager is notified when the laptop is ready and the request closes on the start date once the new starter confirms they can log in.

Metrics

  • Fulfilment time against target, by request type.
  • Share of requests fulfilled through self-service or automation.
  • User satisfaction after fulfilment.
  • Volume by type, to show where to improve or automate next.

Common Mistakes

  • Handling requests as incidents, which muddles reporting and priorities.
  • Making forms long and confusing, so users call instead.
  • Building approval chains for everything “just in case”.
  • Automating a poor process and making mistakes faster.
Key takeaways
  • A service request is a user-initiated ask for something that is a normal, agreed part of the service.
  • Build repeatable request models with forms, approvals, fulfilment steps and target times.
  • Use approvals only where they add value, and favour self-service and automation.
  • Track fulfilment time, self-service share and user satisfaction.

Related Lessons