---
title: "service catalogues | Skills We Assign For | Azendo"
description: "Service catalogues — ownership, dependencies and keeping the data true, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/service-catalogues/"
---

[Skills](https://azendo.co/skills/) Cloud and infrastructure 

# service catalogues.

A service catalogue is the authoritative inventory of what runs in an organisation: each service, its owner, its dependencies, its documentation and its operational metadata. It is the reference an incident response starts from.

## Where service catalogues fits on a long engagement.

The questions a catalogue answers are the ones asked under pressure. Who owns this. What depends on it. Where are its runbooks. Which version is deployed. Without a catalogue those are answered by asking around, which is slow at the exact moment speed is worth most.

Accuracy is the whole game, and manual catalogues are inaccurate within a quarter. The only versions that stay true derive from reality — repository metadata, deployment records, infrastructure tags — rather than from a form somebody is asked to keep updated.

## What an assigned team does with service catalogues.

Ownership is the field that rots fastest, because reorganisations happen more often than anybody updates a catalogue. A service whose owning team no longer exists is the standard finding on a first audit.

Keeping ownership current is an organisational discipline supported by tooling rather than solved by it, and it sits inside the standing platform capacity described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use service catalogues for.

* Incident response that starts immediately Owner, dependencies and runbooks available without asking around.
* Dependency mapping for change planning Knowing what breaks before a service is changed or retired.
* Metadata derived rather than declared Data pulled from repositories and deployments, so it cannot silently go stale.

## How service catalogues capacity is assigned.

Catalogue work is assigned under [devops managed services](https://azendo.co/services/cloud-and-devops/), with automated derivation preferred over any process that depends on people remembering.

## Roles we assign service catalogues for

* [Platform Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/platform-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in cloud and infrastructure

* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [AWS — skill we assign for](https://azendo.co/skills/aws/)
* [Azure — skill we assign for](https://azendo.co/skills/azure/)
* [GCP — skill we assign for](https://azendo.co/skills/gcp/)
* [Terraform modules — skill we assign for](https://azendo.co/skills/terraform-modules/)
* [Pulumi — skill we assign for](https://azendo.co/skills/pulumi/)
* [CloudFormation — skill we assign for](https://azendo.co/skills/cloudformation/)
* [Crossplane — skill we assign for](https://azendo.co/skills/crossplane/)

## Tell us what your roadmap needs service catalogues for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)