Solution 5: From unassigned to owned and supported responsibility

Module III showed that many problems in sustainable contracting stem from unclear ownership, accountability, and responsibility. Obligations may be assigned, but no one is clearly accountable for ensuring that they are understood, implemented, and followed in practice.

The aim is to make responsibility visible, clearly assigned, operational, and connected to implementation.

1. Assign ownership

Responsibility needs to be clearly assigned at two levels:

• contract and system level: who is responsible for maintaining the contract architecture and coherence across the contract stack
• operational and execution level: who is responsible for implementing, monitoring, and following up specific requirements

2. Connect responsibility to action

Ownership is not only about assigning roles, but about connecting responsibility to operational work and implementation:

• who ensures the requirement is understood
• who ensures it is implemented
• who verifies and follows up

3. Make responsibility operational

Responsibilities must be:

• clear and visible
• linked to processes and workflows
• supported by monitoring and follow-up mechanisms

If responsibility is not operationalised, ownership may remain formal or symbolic rather than supporting implementation.

Contracts deliver impact only when responsibility is clear and commitments are actionable.

Ownership does not mean centralising all decisions. It means clarity about who is responsible for ensuring that contractual requirements are intentional, implementable, and monitorable across the contract lifecycle.

Without such ownership, even well-designed clauses and tools fail to support implementation effectively. Implementation gaps go unnoticed, contract stacks become incoherent over time, and improvement becomes reactive rather than strategic. If ownership remains unclear, the same implementation problems will persist, regardless of how carefully clauses are drafted.