Better decisions. More thoughtful work.

A service catalogue tells colleagues what work your team can accept

Colleagues at an office desk reviewing a neat set of service request cards with no legible text.
AI-generated photographic illustration; not documentary photography.

“Ask our team” sounds helpful until every request arrives with a different assumption about what the team does. A short service catalogue can turn an informal promise into a clear explanation of the work people can request.

The useful version is written from the requester’s point of view. It names an outcome, explains the information needed and gives a route into the work. It should not be a copy of the team’s organisation chart or a list of impressive capabilities with no way to use them.

Write one entry before building a portal

Take a common request and describe it in a few fields: service name, intended user, result supplied, required inputs, request channel and important boundaries. Add a named owner for the entry itself. Someone must keep the description aligned with how the team actually works.

For an illustrative communications team, “Review a customer email” might include one draft, an audience description and a requested deadline. The entry could explain that review covers clarity and house style while legal approval remains with the appropriate team. Those boundaries prevent a requester from mistaking a language review for approval of every claim.

  • What will the requester receive?
  • What must be supplied before work can start?
  • How is timing confirmed?
  • What is explicitly outside this service?
  • Where should an out-of-scope request go?

Test the entry with a colleague who regularly requests the work. If they still need a private explanation to submit it correctly, improve the description. Avoid solving every ambiguity by adding more mandatory fields; ask whether each field changes a real decision.

Keep exceptions visible

Urgent or unusual work may still need discussion. State how that discussion happens without promising that every urgent label overrides existing commitments. Record repeated exceptions as evidence that the catalogue or capacity plan needs revision.

Review the catalogue when services, staffing or request patterns change. A smaller set of accurate entries is more useful than an expansive menu of work nobody can reliably deliver. The catalogue succeeds when colleagues can make a sensible request and understand what happens after they send it.