Services Inventory and Attributes - Contractual and Legal attributes for the Services Inventory

Services Inventory and Attributes

Chapter 22. Contractual and Legal attributes for the Services Inventory

Authored and Published By: The International Foundation for Information Technology (IF4IT), LLC

Executive Summary: Chapter Overview

IF4IT

The Bottom Line

Three contractual attributes — Governing Contract Reference, Contract Type, and Right to Audit — capture the contractual surface around each Service. These reference the planned Contracts and Agreements Inventory rather than duplicating contract terms; the inventory points at the contract record, the contract record holds the terms.

Core Concepts

Concept	Definition & Strategic Role
Governing Contract Reference	The contract that governs the Service — Master Services Agreement, Statement of Work, EULA, Subscription Agreement, or internal MOU — referenced by Semantic ID.
Contract Type	The form of the governing contract — drives compliance discipline appropriate to the contract structure.
Right to Audit	Whether the governing contract grants the enterprise the right to audit the Service Provider — critical in regulated industries.

Quick Q&A

Question: Why are detailed contract terms like penalty clauses, notice period, and limitation of liability not included as Service-level attributes?

Answer: Because those terms live in the Contract record itself — duplicating them on every Service record creates two systems of record for the same data and guarantees drift when the contract is amended. The Services Inventory references the contract through Governing Contract Reference; the contract record holds the substantive terms. Compliance and contract teams traverse from Service to contract for the detail.

Question: How does the Service Agreement Reference (in the Operational category) differ from the Governing Contract Reference here?

Answer: The Service Agreement Reference points to the formal Service Agreement — the SLA or service commitment that defines Service Expectations. The Governing Contract Reference points to the broader commercial contract under which the Service is delivered. For many vendor Services they are the same document; for complex Services they are distinct — the contract is the legal commercial structure, the Service Agreement is the operational commitment that operates under it.

Read More Below

Contractual and Legal attributes capture the contractual surface around each Service — the governing contract, its type, and whether audit rights are granted. For substantively contract-governed Services, these attributes connect the inventory to the Contracts and Agreements Inventory.

Attribute Name	Maturity	Description and Notes
Governing Contract Reference	Walk	Description — A reference to the contract that governs the Service — typically a Master Services Agreement, Statement of Work, EULA, Subscription Agreement, or internal MOU. References the planned Contracts and Agreements Inventory by Semantic ID. Benefit(s) — Connects Services to their governing contracts. Enables compliance and contract teams to traverse from Service to contract and from contract to governed Services. Source — Manual. Examples — CON-SALESFORCE-MSA-2025; CON-AWS-EDP-2024 Notes — For consumed Services, this is the vendor contract that governs the Service. For internally-provided Services, this may be an internal MOU or service charter. Refer to the planned Contracts and Agreements Inventory.
Contract Type	Walk	Description — The type of governing contract. Drives compliance discipline appropriate to the contract form. Benefit(s) — Enables analysis of Service governance by contract structure. Supports contract management discipline aligned to contract type. Source — Manual. Examples — Master Services Agreement, Statement of Work, EULA, Subscription Agreement, Internal MOU, Open Source License Notes — Should match the contract type recorded in the Contracts and Agreements Inventory where one exists.
Right to Audit	Walk	Description — Whether the governing contract grants the enterprise the right to audit the Service Provider’s performance, compliance, or controls. Benefit(s) — Supports compliance discipline: which Services have audit rights and which do not? Critical for regulated industries where audit rights are required. Source — Manual. Examples — Yes; Yes (with conditions); No; Limited (record details in Notes) Notes — For Services where audit rights are limited (e.g., audit only of specific aspects), use Notes to capture specifics. Refer to the governing contract for authoritative terms.

Attribute Name

Maturity

Description and Notes

Governing Contract Reference

Walk

Description — A reference to the contract that governs the Service — typically a Master Services Agreement, Statement of Work, EULA, Subscription Agreement, or internal MOU. References the planned Contracts and Agreements Inventory by Semantic ID.

Benefit(s) — Connects Services to their governing contracts. Enables compliance and contract teams to traverse from Service to contract and from contract to governed Services.

Source — Manual.

Examples — CON-SALESFORCE-MSA-2025; CON-AWS-EDP-2024

Notes — For consumed Services, this is the vendor contract that governs the Service. For internally-provided Services, this may be an internal MOU or service charter. Refer to the planned Contracts and Agreements Inventory.

Contract Type

Walk

Description — The type of governing contract. Drives compliance discipline appropriate to the contract form.

Benefit(s) — Enables analysis of Service governance by contract structure. Supports contract management discipline aligned to contract type.

Source — Manual.

Examples — Master Services Agreement, Statement of Work, EULA, Subscription Agreement, Internal MOU, Open Source License

Notes — Should match the contract type recorded in the Contracts and Agreements Inventory where one exists.

Right to Audit

Walk

Description — Whether the governing contract grants the enterprise the right to audit the Service Provider’s performance, compliance, or controls.

Benefit(s) — Supports compliance discipline: which Services have audit rights and which do not? Critical for regulated industries where audit rights are required.

Source — Manual.

Examples — Yes; Yes (with conditions); No; Limited (record details in Notes)

Notes — For Services where audit rights are limited (e.g., audit only of specific aspects), use Notes to capture specifics. Refer to the governing contract for authoritative terms.

How to cite this page

When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.

Example (informal web citation):

The International Foundation for Information Technology (IF4IT), LLC. Contractual and Legal attributes for the Services Inventory | Services Inventory and Attributes. https://if4it.org/best-practices/services-inventory-and-attributes/contractual-and-legal-attributes-for-the-services-inventory/ (accessed 2026-07-23).

See About Us for content governance and site-wide citation guidance.

Legal Disclaimers

💡 The Bottom Line

📝 Core Concepts

🤖 Quick Q&A

How to cite this page

The Bottom Line

Core Concepts

Quick Q&A