Contracts in practice: not one document, but a stack of documents
As noted in Module 2, sustainability commitments are rarely contained within a single clause or document. In practice, they are distributed across a stack of documents. For example, the main contract and its annexes may include
- Specifications
- A Code of Conduct (or Supplier Code of Conduct)
- Supplier Requirements
- Standard Terms and Conditions
- Internal policies
This stack-based structure is common and can be effective. It allows organizations to separate technical and commercial terms, operational requirements, and value-based commitments into different layers. However, the stack can also become fragmented and difficult to navigate. When sustainability commitments and requirements are dispersed across multiple documents, cross-references, and annexes, the overall picture may be hard to grasp. This creates cognitive overload and implementation risk.
If those responsible for product design, procurement, or production cannot easily see how the documents relate to each other - or which commitments apply in practice - sustainability expectations may remain abstract, inconsistently applied, or simply overlooked in day-to-day decision-making.
Module 4 addresses this challenge by focusing on how the contractual stack can be made visible, coherent, and manageable in practice.