Three Typical Failure Patterns

1. Product level: Sustainability outside specifications

If sustainability is not translated into concrete design criteria, it may not be built into products. Contractual specifications may leave unclear, for example, what data is required, which materials are permitted or prohibited, and how sustainability expectations should shape design decisions.

“Comply with all laws” in a contract does not guide engineers or product managers. It may feel legally sound but it does not provide operational clarity required for action.

2. Operations level: Sustainability without concrete operational practices

Without appropriately defined operational responsibilities and processes, sustainability may not translate into practice.

For example, a Code of Conduct alone may not ensure implementation if it is not embedded in the contract and translated into defined responsibilities and processes.

3. Supply chain level: Sustainability without contractual alignment

Supply chains are built on contracts. They can address the parties’ roles and responsibilities at product level and operations level. Without such clarity, suppliers may not know what is expected or required of them.

If commitments are not calibrated to be fit for purpose, and if appropriate cascading across tiers is not embedded in contracts, responsibility may become fragmented rather than structurally managed.

The next module, Module 4, shows how contracts can embed sustainability:

• into specifications
• into operations
• into supply chains

through calibrated, structured, and actionable plain language commitments.