What it means
A service offering packages goods, access to resources, and service actions into a defined proposition, while the service relationship covers provision, consumption, and relationship management.
Why it matters
Unclear offerings create mismatched expectations about what is included, who owns supporting resources, how requests are handled, and which responsibilities remain with the consumer.
Practical focus
- Describe each offering in terms of included goods, resource access, service actions, constraints, dependencies, and exclusions.
- Map provider and consumer responsibilities across provisioning, consumption, support, measurement, and relationship management.
- Review offerings after major technology, supplier, demand, regulatory, or threat changes.
- Preserve this evidence: Retain approved definitions, decisions, operating records, exceptions, test results, and change history that show how Service Offerings and Relationships works over time.
- Exercise this failure scenario: A consumer assumes backup, monitoring, or security work is included, but the provider treats it as an excluded responsibility after an incident.
Common mistakes
- Using Service Offerings and Relationships as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a diagram, policy, tool screen, or meeting as proof that Service Offerings and Relationships operates consistently in real work.
- Optimizing for a one-time review while leaving normal operating decisions, exceptions, and handoffs uncontrolled.
- Testing only the expected path and never rehearsing this failure condition: A consumer assumes backup, monitoring, or security work is included, but the provider treats it as an excluded responsibility after an incident.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: