
An IT service catalogue: what your supplier delivers, on one page
The contract says what your IT supplier must do, in legal language and spread across schedules. An IT service catalogue puts the same thing on one page, in the words of a colleague who needs something: what can I request, from whom, and when will it be ready. This is how to write one people actually use.
An IT service catalogue is the list of what your supplier delivers, written for the people who use it. It does not replace the contract; it makes it readable.
Each service has six fields: what is included and what is not, who can request it, how, how long it takes, and whether it is in the fixed fee or extra work.
Start from last year’s requests, not from a template. If it does not fit on one page, you are describing tasks rather than services.
What an IT service catalogue is, and what it is not
An IT service catalogue is the list of services an IT department or IT supplier delivers, described from the point of view of the person using them. Not “endpoint management”, but “a laptop for a new colleague, ready on their first day”.
It is often confused with three other documents, and it helps to keep them apart:
- The contract governs the relationship: scope, price, term, liability and exit. The catalogue refers to it and does not contradict it.
- The SLA governs performance: response and resolution times and how they are measured. The catalogue states which level applies to each service.
- The categories in the ticketing system are for the service desk. They look like a catalogue, but they are written in the language of whoever fixes things, not whoever asks.
ITIL also distinguishes a catalogue for users from a technical catalogue for the teams behind it. For an SME the first is enough; the technical side lives in your supplier’s documentation.
What each service in an IT service catalogue needs
Keep every entry short and always fill in the same six fields. A field left empty is usually exactly the agreement that has not been made yet.
- A plain name. The way a colleague would say it: “access to a shared folder”, not “file server permissions management”.
- What is included, and what is not. A new laptop including set-up and moving data across, but without the sector software another supplier installs.
- Who can request it, and who approves. Anyone, only a line manager, or only the IT contact. This prevents half the arguments about access.
- How to request it. The portal, a form, the phone. And which details are needed up front.
- Lead time and service hours. How long it normally takes and whether it can be done outside office hours.
- Included or extra. Is it in the fixed fee, or charged separately and approved by whom? No amount needs to appear here; the rule does.
One entry worked through: a new starter
The service that pays off most in almost any catalogue is a new member of staff joining. Worked through, it looks like this:
- Name: new starter, account and workstation.
- Included: account, mailbox and licence, a configured laptop, access to the standard folders and the team group. Phone number and access badge only if they are in scope.
- Not included: access to systems another supplier manages; the line manager requests that there.
- Who requests: the line manager or HR, with name, role, start date and team.
- Lead time: a fixed number of working days before the start date, agreed with the supplier.
- In the fee: yes, for a standard workstation. A non-standard configuration is extra work, approved by the IT contact.
A leaver belongs next to it as its own entry. It is the service most often forgotten, and the one an auditor asks about as a matter of course.
Building it from what already exists
Do not start from a template with fifty services. Start from what was actually requested over the past year.
- Export the requests from the ticketing system and group them. The ones that recur most are your first entries.
- Put the contract scope next to it. What is in scope and never requested still belongs in; what is requested and not in scope is your first conversation with the supplier.
- Ask the supplier for its own list. A good supplier has one, so you add to it instead of starting from a blank page.
- Have two colleagues outside IT read it. If they cannot see where to request a new laptop or a shared mailbox, it is not finished.
If it does not fit on one page, you are probably describing tasks rather than services. “Reset a password” and “unlock an account” are one service together: being able to sign in again.
Where the catalogue settles the extra-work argument
Most friction with an IT supplier is not about outages but about whether something is included. The catalogue is where you decide that once per service, instead of again with every invoice.
- Put the grey areas in. A printer for a home worker, a second monitor, a colleague working temporarily at another office. Those are exactly the entries that prevent arguments.
- Let the contract prevail. If the catalogue contradicts the contract, the contract wins. Align them at every change, and have each entry point to the clause the agreement comes from.
- Record who approves extra work, and up to what size without asking first.
How to set out the agreements underneath the catalogue is covered in our article on the IT support agreement; the performance targets per service belong in SLAs you can actually meet.
A catalogue that does not go stale
A catalogue nobody has touched for a year describes an environment that no longer exists. Three arrangements keep it current:
- One owner on your side and one at the supplier. Not a department, a name.
- A fixed slot in the quarterly review. New services, retired services, entries that caused an argument. Ten minutes is enough.
- The request form follows the catalogue. If a service is in the catalogue, there is a way to request it; if there is a form with no entry in the catalogue, something is being delivered that nobody agreed.
Put it where colleagues already look: on the intranet or in the service desk portal, not as an appendix to a contract only the board has seen.
Where our work stops
What we do. For the services we deliver, we draw up the IT service catalogue together with the client, keep it current in the quarterly review and set up requests in the service desk around it. Other suppliers’ services can appear in it with their own owner and request route, so colleagues have one list.
What we do not do. We make no promises in the catalogue for another supplier’s services: what it delivers, how quickly and on what terms is for that supplier to decide. And a catalogue is not a contract. Whether the agreements underneath are legally sound is for a lawyer to check; we are not lawyers.
Questions we get about this
The five that come up most often.
What is an IT service catalogue?
An overview of the services an IT department or IT supplier delivers, written for the people who use them. For each service it states what is included, who can request it, how, how long it takes and whether it is in the fixed fee. It makes the contract readable for the rest of the organisation.
What is the difference between a service catalogue and an SLA?
The service catalogue describes which services exist and how to request them. The SLA describes performance: response and resolution times and how they are measured. The catalogue states which SLA level applies to each service, so the two refer to each other instead of repeating each other.
What should be in a service catalogue?
Six things per service: a plain name, what is included and what is not, who can request it and who approves, how to request it, the usual lead time, and whether it is included or extra. Services such as a new starter and a leaver should always be in it.
What is the difference between a business and a technical service catalogue?
ITIL distinguishes a catalogue for users from a technical catalogue describing which systems and teams support each service. For most SMEs the first is enough. The technical side lives in the supplier’s documentation and should be available on request.
Is an IT service catalogue legally binding?
Usually not on its own; the commitments are in the contract and the SLA. Record that the contract prevails if the two conflict, and have each entry point to the clause it comes from. Whether the whole is legally sound is for a lawyer to check.
Further reading
What this catalogue connects to.
Shall we build your catalogue together?
Send us an export of last year’s requests and your current scope. You get a first one-page version back, with the entries that have no agreement behind them yet.
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.