Service catalog design

Service catalog design is the work of building the list of services a customer can actually order today. If an item cannot be ordered, it does not belong in the catalogue. Each entry carries a description, a price and an owner.

The catalogue is not the portfolio. The catalogue is the live, orderable subset of the portfolio — the part a customer can request right now, while service portfolio management also covers what is planned and what has been retired.

It is also narrower than the portal it appears in. A self-service portal is the shop window; the catalogue is the stock list behind it, and a portal with no agreed catalogue just moves an unanswered question online.

Key takeaways

• Orderability is the test: if a customer cannot request it today, it stays out of the catalogue.
• Every item needs a description in the user’s words, a price, an approval path and a named owner.
• The catalogue is the live, orderable subset of the wider service portfolio.
• A catalogue nobody maintains becomes a price list for services that no longer exist.

How it works

Service catalog design works by turning each service into a standard record: what you get, who can ask for it, what it costs, who approves it, how long fulfilment takes, and who owns the result.

Write each entry in the words the person asking would use. The GOV.UK Service Standard makes the same point: focusing on the problem a user is trying to solve, not a solution often surfaces needs you did not expect.

What goes in the catalogue is a commercial decision before it is a technical one. Offering strategy decides which services are worth running at all, and catalogue design then describes the survivors.

Pricing is where most catalogues stall. A line reading “cost: contact us” is not orderable, so either publish a rate, publish a band, or move the item back to the portfolio until somebody will stand behind a number.

Publish the fulfilment target as well as the price. An item promising delivery in five working days creates a measurable commitment, and the gap between that promise and reality is the first thing a service review should show.

Grouping matters more than people expect. Users scan by the outcome they want — a new starter, a leaver, or access to a system — so grouping by internal team sends them to the wrong form and then to the service desk anyway.

Approval is not the same as fulfilment. A request that clears its approver in an hour and then sits unassigned for a week still misses its target, so the record needs an owner for the work, not just a signature.

Approval paths belong on the record too, not in somebody’s head. Enterprise service management applies the same discipline to finance, HR and facilities, where the approver is a budget holder rather than a technical lead.

The catalogue also has to say what is not in it. Published boundaries stop a value added service being quietly absorbed into the base fee by whoever asks loudest.

Federal buyers run a formal version of the same idea. Under the Federal Acquisition Regulation, agencies must satisfy requirements in a descending order of priority from named mandatory sources before looking anywhere else.

Examples

Catalogue design looks different depending on who is ordering. The three cases below are an internal technology desk, an outsourced managed service, and a public buying catalogue — one discipline, three levels of formality.

An internal technology desk publishes around 40 orderable items and retires the rest. Laptops, access requests and software installs carry fixed prices and fulfilment targets, while anything bespoke routes to a form that opens a conversation.

An outsourced provider selling it managed services builds the catalogue into the contract. Each line names a unit, a price per unit and a response target, so adding a site next quarter is an order rather than a renegotiation.

The delivery shape matters. A managed service model sells an outcome against a standing fee, so its catalogue lines read as service levels and unit rates rather than as one-off tasks.

Public buying catalogues are the formal extreme. A government framework lists agreed suppliers, rates and terms, so a department orders from the list instead of running a fresh competition for every requirement.

Keeping it current is the unglamorous half. Set a review date on every item, and treat any entry whose owner has left the business as a defect rather than as a detail somebody will get to eventually.

Related terms

• enterprise service management: applies catalogue discipline beyond technology, to HR, finance and facilities.
• offering strategy: decides which services should exist; the catalogue describes the ones that do.
• value added service: an extra sold alongside the core line, which the catalogue prices separately.
• service improvement: the practice of raising quality once catalogue items are live and measured.
• cloud managed services: a catalogue whose items are provisioned and metered rather than installed.

FAQ

What is the difference between a service catalogue and a service portfolio?

The catalogue is the live, orderable subset of the portfolio. The portfolio also holds services still in design and services already retired.

How many items should a service catalogue have?

Fewer than most teams expect. Around 30 to 60 orderable items cover the great majority of requests, and a longer list usually hides duplicates.

Who owns a service catalogue?

One named owner per item, plus a single owner for the catalogue itself. Shared ownership is how entries go stale without anyone noticing.

Does every catalogue item need a price?

Yes, or at least a published band. An item with no number attached cannot be approved by a budget holder, so it is not really orderable.

How often should the catalogue be reviewed?

Review content quarterly and pricing annually, adding a service only once it is genuinely orderable.

Benchmark your own published catalogue against the providers listed in the Outsource Accelerator hubs.