
Service request management: why a new laptop is not an incident
A new laptop, an extra licence, access to a shared folder: these are service requests, and they need a different process from a fault. Lump them together and you get a service desk that looks slow, approvals stuck in someone’s inbox and a new starter with no account on day one. This is how to set up service request management without turning it into a project.
A service request asks for something to be provided or arranged while nothing is broken. It deserves its own clock and its own reporting, separate from faults.
Most requests are standard: fixed content, fixed approval, fixed lead time. Agree them once and nobody needs to email about them again.
Measure service requests on time to fulfilment, and report time spent waiting for an approval or a supplier separately. Who may request and who approves is your decision.
Incident vs service request
An incident is something that worked and no longer does: the printer, the VPN, an application that will not start. A service request asks for something to be provided or arranged while nothing is broken: a laptop for a new starter, a second monitor, a licence, membership of a Teams channel, a guest account.
The distinction looks like admin and it is not. A fault has to go away as quickly as possible, so response time is what counts. A request has to be ready at an agreed moment, so fulfilment time is what counts. Report them together and the average means nothing: a quick password reset and a laptop that is three days in transit cancel each other out into a number you cannot act on.
There is a second reason. Requests are predictable and faults are not. If you know four people start next month, you can order the laptops now. That only works if requests do not disappear among the incidents.
Standard requests: agree once, then stop discussing
Most service requests are the same every time. A standard request has agreed in advance what is delivered, who may ask for it, who approves it and how long it takes. After that, every request is a matter of fulfilment rather than negotiation.
- Workstation for a new starter: which laptop model per role, which monitor and accessories, which standard software.
- Licence or subscription: which licences exist, who gets which type, and who confirms the cost centre.
- Access: to a shared folder, a mailbox or an application, with the owner of that data as approver.
- Replacement or addition: a second monitor, a headset, a docking station.
Anything not on the list is not a standard request. It becomes a request for a quote or a change, assessed on its own. Drawing that line up front prevents the argument about extra charges afterwards.
Who may request, and who approves
Nobody needs permission to fix a fault. A service request almost always needs one, and that is where fulfilment time slips most often. Not because someone says no, but because the approval sits in someone’s inbox.
Agree an approver for each type of request. For hardware and licences that is usually the line manager or budget holder. For access to data it is the owner of that data, which is not the IT team: the service desk can grant access, but does not decide who ought to have it.
- Approve inside the ticket, not in a separate email, so the approval can be found when someone asks about it later.
- A deputy for every approver, for holidays and sick leave.
- Pre-approved requests where possible: a headset or a mouse does not need to go past a manager.
A request form that removes the first follow-up question
A request that arrives as “Can Sarah get into the finance folder too?” triggers three questions before anything happens. A form per request type asks them straight away:
- For whom, and from when. A laptop needed today is a different request from one for someone starting in four weeks.
- Which cost centre, and who confirms it.
- Exactly which access, temporary or permanent. Temporary access gets an end date in the ticket.
- Delivery address, for hardware going to a home worker or another site.
One phrase should never appear: “same rights as colleague X”. It copies everything X was ever given, including access they have not needed for years. Ask what access the role needs, not what someone else happens to have.
Joiners, movers and leavers: the request that goes wrong most
The most important service request is really three: someone joins, someone changes role, someone leaves. All three start in HR rather than IT, and that is the problem: if nobody passes it on, the new starter arrives without a laptop and the leaver keeps their account.
- Joiner: HR notifies with a date, well in advance. Laptop, account, licences and access are ready on the first working day, not after it.
- Mover: the new access added and the old access removed. Everyone forgets the second part, which is how someone builds up rights over a few years that fit no role at all.
- Leaver: the account is disabled on the last day, the mailbox gets a destination and the hardware comes back, with a check that the data is off the device.
Make all three a standard request with a fixed checklist. How the device itself is set up and managed is covered under workplace management.
Measuring service request management: fulfilment time, not response time
What you measure decides what improves. For service requests that means different numbers from faults:
- Fulfilment time per request type, from request to delivery. Not one average across everything, but per line in your list of standard requests.
- Waiting time separately. Time spent waiting for an approval, or for a delivery from a manufacturer, pauses the clock and appears separately in the report. Otherwise the service desk looks slow at moments when it is waiting for you.
- Requests sent back because information was missing. That tells you the form is missing a question.
- Requests that were really faults, and the other way round. If that happens often, the categories are wrong.
How to write the agreements around this so they are achievable and measurable is in SLAs you can actually meet.
Where our work stops
What we do. We take service requests through a single point of contact, set up the standard requests and forms with you, deliver and configure the hardware, arrange accounts and licences and run the joiner and leaver checklists. We report fulfilment time per request type, with waiting time shown separately.
What we do not do. We do not decide who gets a laptop, a licence or access; that belongs to the approvers you appoint, and the budget is yours. We only grant access to data once its owner has approved. The HR system that starts a joiner or leaver belongs to your organisation and its supplier, and rights inside another vendor’s application are granted by that application’s owner.
Questions we get about this
The five that come up most often.
What is a service request?
A service request is a request to the service desk to provide or arrange something while nothing is broken. Examples are a laptop for a new starter, an extra licence, access to a shared folder or a guest account. It is handled and measured separately from incidents.
What is the difference between an incident and a service request?
An incident is a fault: something worked and no longer does, and it has to be restored as quickly as possible. A service request asks for something new or additional, and it has to be ready at an agreed moment. That is why an incident is measured on response and resolution time and a request on time to fulfilment.
What is a standard service request?
A standard request is one where what is delivered, who may ask, who approves and how long it takes are all agreed in advance. A workstation for a new starter or a headset are typical examples. Anything not on that list becomes a request for a quote or a change.
How quickly should a service request be fulfilled?
That is agreed per request type, because an access right and a laptop that has to be ordered cannot be delivered in the same time. Set a lead time for each standard request and have time spent waiting for an approval or a supplier measured separately. A single deadline for every request is either unachievable or meaningless.
Do you decide who gets a laptop or a licence?
No. Who may request what and who approves is decided by your organisation, and the budget is yours. We record those agreements with you, carry out what has been approved and only grant access to data once its owner has signed it off.
Further reading
What service requests connect to.
Shall we give your requests a fixed shape?
Send us the requests that come in most often. We will turn them into a list of standard requests, each with a form, an approver and a lead time; who gets what stays your decision.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.