Most organisations meet ISO/IEC 20000-1 the way they meet every other standard: as a line in a tender, or a tab in a customer’s vendor questionnaire, with a deadline attached.
It is the service management standard. Where ISO 9001 asks whether you can produce the same result every time, 20000-1 asks a narrower version of the same question about a service that runs continuously: can you deliver it to an agreed level, and show how, when the people involved change and the week goes badly?
The idea underneath it
Every provider has a good week. The work is in the bad one.
A service management system is what makes the bad week look like the good one from outside: the same route for an incident at 02:00 as at 14:00, the same change process when the fix is urgent, the same escalation when a supplier is the cause, and a record of all of it afterwards.
The standard is not about tooling. You can meet it with an enterprise service desk platform or with something much simpler, as long as what you claim to do is what actually happens.
What the standard requires
In outline, ISO/IEC 20000-1 asks you to:
- Agree what the service is, with the people who depend on it, in terms that can be measured
- Plan capacity, availability and continuity rather than discovering them
- Handle incidents and service requests through a defined route, and record what happened
- Separate problems from incidents, so recurring faults get a cause rather than another ticket
- Control changes, including the urgent ones, and know what changed when something breaks afterwards
- Manage the suppliers behind your service, because your customer experiences their failures as yours
- Review performance with the customer, and act on what the review finds

What changes in practice
Questionnaires. The service management section of a security or vendor questionnaire is answered from one set of facts rather than written fresh each time, which is also how contradictions stop appearing in your own answers.
Handovers. A service that depends on one person’s memory survives their holiday badly. Written process is how a team stops being a single point of failure.
Supplier failures. Most serious outages involve somebody else’s infrastructure. The standard asks what you agreed with them, and what happens when they miss it.
Reviews. Service review with a customer stops being a presentation about how well things went and becomes a short conversation about numbers both sides already have.
What it does not do
ISO/IEC 20000-1 certifies a service management system. It does not guarantee uptime, it certifies no SLA figure, and it says nothing about the performance you actually achieved last quarter.
That matters more in this field than most, because reliability is exactly what providers are tempted to promise. A certificate that could promise uptime would be worth a great deal and would also be a lie. What it offers instead is evidence that the discipline behind the promise exists and is examined every year by somebody independent.
Where it starts
With scope. Which services, which customers, which locations. A certificate scoped to one managed service says nothing about the rest of what you sell, and the buyer who matters will read that line first.
If a tender has asked you for it, the honest sequence is scope, then an assessment of where the system already exists in practice, then the gaps. Most competent providers are further along than they think, and the work is usually writing down what the best people already do.
