Skip to content
Interface language: English
Imperium / Signal

An internal service catalogue: what a team does, for whom and on what terms

Explain which requests a team accepts, what it needs to start and what it hands back. Test one service card with an actual request.

Article language: English

A woman in a red apron beside a round glass lens in a gold-coloured housing.
In this article

“Send it to marketing” sounds like an instruction until marketing asks what it is supposed to do. An internal service catalogue explains which requests a team accepts, what it needs to start and what result it hands back. It need not resemble a shop of tiles or a document made for an anniversary. It should help one employee request the right work and another accept it without three days of clarification.

A small company can use one too. One person may look after the website, sales materials and automation, but those tasks still have different starting conditions. The following is our proposed way to describe a team's services and check the descriptions against real requests. The examples are working illustrations, not client results or universal delivery times.

Describe the requester's need, not the organisation chart

An employee may know they need an offer corrected, a form restored or a translation ordered. They need not understand which specialist currently has that responsibility. Name the service by its action and result. “Update an approved service description” says more than “digital support”, under which almost anything, including finding a charger, might fit.

Review recent requests and questions. Find which recur in a similar form and which need a separate conversation. Do not create an entry for every possible task at once. The catalogue should reflect real work and help people choose. If every path ends at an “other” form, examine the names and the division of services.

Atlassian describes a service catalogue as a collection of available services, including services beyond IT, that people can find and request. It distinguishes the customer view from the technical backstage. This is useful inspiration for organising information, not evidence that your company needs a particular product or that software alone will shorten handling times.

Separate a service from an individual task

A service has a repeatable purpose and recognisable result. A task is one instance of that service. “Update contact information” can be a service; changing a phone number on particular pages is its execution. If the catalogue names every past project, an employee has to know company history to request a simple correction.

Do not combine results that are too different. A new sales page and a typo correction need different materials and acceptance. For a website, distinguish routine maintenance, individual requests and development. The guide to website maintenance (in Polish) explains this distinction. A catalogue can reflect the distinction without multiplying names nobody remembers.

Build a card for one service

Each card should answer who the service is for, when to use it, what to supply and what result to expect. Add scope boundaries, the person responsible and how to accept the result. A requester should not discover after submission that they ordered a different kind of work. Put decision conditions before the button, not in an owner's hidden instruction.

  • Name: an action the recipient understands.
  • Use: situations in which this route is appropriate.
  • Materials: specific information and decisions needed at the start.
  • Result: a document, change or action handed back for checking.
  • Boundaries: what needs another service or a separate quote.
  • Handling: owner, cover and contact route.
  • Acceptance: how the requester recognises completion.

For research, the result might be sources with their limitations, not a promise to find a partner. For a website, it might be a published change whose operation has been confirmed. A precise card reduces mismatched expectations; it does not establish a team's availability for a particular date.

Collect only what is needed to start

A form should help work, not test the requester's knowledge of the department. Ask about the goal, location of the change, material and approver. If a field is mandatory, the team should be able to explain how it will use the answer. Do not demand a detailed technical specification from someone reporting a malfunction.

Jira Service Management documentation describes request types as a way to organise requests and choose the fields collected. This is an example of a specific product, not a requirement for a company catalogue. Whatever platform you use, check whether answers allow the team to accept a case and whether questions are understandable.

Use the principles of a guide to B2B contact forms (in Polish), especially clear labels and confirmation of receipt. An internal process must also distinguish submission from starting work. An automatic “we received your request” should not suggest that a deadline has already been agreed.

Define material readiness without bureaucratic language

Instead of demanding “complete substantive input”, say what that means: approved text, a link to the current offer, the language and the person reviewing the preview. If partial materials are acceptable, show how to complete them. The requester needs a next action, not a notice that the request fails an abstract idea of completeness.

Accepting an unready request can make sense, but it needs its own status. The team identifies what is missing, names an owner and records what it awaits. Do not show the whole case as being worked on. Otherwise the recipient expects a result while the worker believes the clock has not started. Both may be right under different definitions nobody agreed.

Separate urgency from the handling order

“Yesterday” is a popular deadline, although the calendar still has no such option. Describe situations requiring a fast response: an important form unavailable, wrong information affecting current orders or another agreed consequence. Distinguish those from a request for a new feature before an event the team has only just heard about.

For an incident, give a separate route and minimum information. A guide to responding to website incidents (in Polish) connects the report to its observed effect. The catalogue should not force an employee to choose an infrastructure type if all they know is that an enquiry was not delivered. Diagnosis belongs to those handling the incident.

Show a route for unusual requests

You cannot anticipate every need. Offer a way to identify a request that does not fit the catalogue. Explain the minimum to provide and who will indicate the next step. “Other” can be an honest exception route, provided it has not become the main entrance because the categories are unclear.

Aeneia conceptual photography

Review those requests regularly. If a repeatable result with similar conditions appears, consider a new card. If cases are very different, do not invent a shared name. A brief scoping conversation may be the right service. Its result should be an understanding and a proposed next step, not a promise to undertake any project. Separate self-service tasks from the point requiring a person so the catalogue starts an unusual request rather than shuttling it between categories. For an analogy in customer service, see the article on self-service and human support (in Polish).

Do not hide an absent owner behind a form

If nobody can confirm a service's scope, a new request channel will not solve the problem. First name someone able to accept responsibility for the result or pass the case to the right role. Otherwise the portal merely collects work more efficiently without increasing the capacity to start it.

For a shared service, distinguish coordinating from performing a part of the task. One person may communicate with the requester while an expert prepares text and a website owner publishes it. The card should show the path as far as the recipient needs it, not the entire organisation chart. People need to know who will return with a question and where they will hear about the result.

Practise cover with a controlled example. Can another authorised person find the materials, status and latest agreement? If they need a private message from an absent colleague, update the shared source. Do not copy all data into an open catalogue. Access to a service description and access to the materials of a particular request are separate needs and should be handled accordingly.

Measure flow so you can understand why work waits

Distinguish receipt, readiness of materials, start of work and acceptance of the result. Each is a different event. Total elapsed time can reveal a problem but not immediately its cause. If most waiting is for the content owner's approval, adding another technical worker may not shorten the whole process. If cases wait after work has begun, check whether too many tasks are already in progress before changing only the form or adding a category. The guide to work in progress (in Polish) offers a way to examine this.

Agree how statuses are recorded and try the definitions on several cases. Do not reward fast closure if the internal client must reopen the task because the result is missing. Record cancellation, withdrawal of the need and correction after acceptance separately. Such distinctions improve the service; one green number without a definition may only improve the mood in a presentation.

Review questions asked before submission too. If the team explains the same boundary every day, improve the card or service name. Do not merely blame people for failing to read instructions. The information may be hidden, unclear or about a different case. Check the catalogue where uncertainty arises.

Practise with an offer-update card

In a fictional company with a Polish website and English material, sales requests a change to the first stage of a service. The card asks for the current scope, approving owner and affected channels. It does not require the salesperson to know the publishing system; the person doing the work identifies technical dependencies.

After acceptance, the team checks whether the change also affects a downloadable file and an automatic message. The information owner approves the text and the publisher checks the result. Acceptance refers to the named addresses and language versions. A need for a new form is recorded as an extension, rather than unexpectedly consuming the time allocated to an ordinary update.

Keep the example as a short instruction on the card. It shows use better than a long definition of support. Remove real client data if a case comes from completed work. A catalogue should explain the process, not turn company history into an openly accessible collection of attachments.

Check whether the user chooses the right service

Prepare descriptions of several needs and ask people outside the team to find the request route. Observe which names make them pause and what they ask. Do not immediately point to the correct category. If someone chooses incorrectly, the catalogue may be failing, not their willingness to read procedures.

Plan the exercise with the guide to hypothesis cards (in Polish). For example, suppose naming the result will help distinguish a correction from a new project, then test it on prepared tasks. A few observations can improve the wording; they do not justify claiming a percentage increase in the entire company's productivity.

Maintain the catalogue as the team changes

When responsibilities change, check the owner, substitute, request channel and service scope. A perfect-looking card without a current person can lead nowhere. When withdrawing a service, show the next route or explain that the company no longer provides it. Do not leave an active form beside a promise nobody fulfils.

Connect definitions such as “ready”, “urgent” and “approved” to a company glossary. Organise materials and their owners using a knowledge architecture. For guidance, see the article on company glossaries (in Polish) and the article on knowledge architecture (in Polish). The catalogue can then point to current sources rather than making a newcomer collect rules from colleagues' private messages.

Show the requester a status that explains something

After submission, an employee should know whether the case was accepted, whether material is missing and who will return with information. “In progress” alone can cover a week of very different situations. Choose a few understandable states and describe the action needed when the request awaits the requester.

On closure, identify the result and where to check it. Give the address for a website change or the approved version for a document. A closed task number alone leaves the recipient searching. A catalogue should carry a service through to a usable result. The close button ends an item in a tool; acceptance tells you whether the person's case has also ended.

Start with one frequently requested task

Choose a service where materials are routinely missing or expectations about the result differ. Describe its card, test the choice and handle several real requests. Record corrections. Only then consider whether a larger portal is needed. An elaborate catalogue cannot fix a service whose scope the team still cannot agree.

Aeneia Audit may help organise questions about AI tools and information flows. For a website's presentation of services, explore Aeneia Design.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear