NEC4 Clause 10.2 - a practical and philosophical approach

Tim Leung

Sean Leung

Key points:

• NEC4 ECC Clause 10.2 says ‘The Parties, the Project Manager and the Supervisor shall act in a spirit of mutual trust and co-operation’. 
• This article provides both a practical and philosophical analysis of Clause 10.2 and the importance of leadership in putting its principles into practice. 
• NEC users should see Clause 10.2 not just as a contract clause but as a philosophy and a mindset, making NEC a real platform for culture change. 

Clause 10.2 of the NEC4 Engineering and Construction Contract (ECC) states, ‘The Parties, the Project Manager and the Supervisor shall act in a spirit of mutual trust and co-operation‘. Under Clause 11.2(13), the parties are defined as the client and the contractor, reinforcing that Clause 10.2 binds both commercial principals in a structural relationship based on unity rather than adversity. 

Few contract clauses are as concise and as widely misinterpreted as this one. For some, Clause 10.2 is viewed as a noble sentiment with little contractual weight. For others, its wording lacks enforceability. But to those with experience administering NEC contracts, it serves as a behavioural cornerstone for modern project delivery: a call to reshape working culture and rethink how trust is built on projects. 

This article follows from the lead author’s article in Issue 139 of the previous incarnation of the NEC Newsletter entitled ‘Embracing the NEC spirit: aligning HK practices for collaborative success’. It integrates operational contracting insight with philosophical analysis, offering both practical and reflective perspectives on Clause 10.2. By combining these perspectives, the article seeks to clarify the clause’s deeper significance and outline how leadership can turn principle into practice. 

Contractual perspective

Clause 10.2 should not be read as merely a preamble. It encapsulates NEC’s underlying ethos: to support collaboration, proactive risk management and fairness. These mechanisms, however, are only effective when supported by a foundation of trust. 

Trust cannot be manufactured at contract signature. It must be built and reinforced through daily actions, particularly under pressure. Collaboration thrives not when problems are avoided, but when they are surfaced early, discussed openly and resolved collectively. 

Critically, collaboration differs from co-operation. While co-operation means ‘you do your part, I will do mine’, collaboration implies shared ownership, ‘let us solve this together’. It demands transparency, joint responsibility and open communication. When parties retreat into silos or default to defensive behaviours, the spirit of Clause 10.2 is already lost. A useful diagnostic might be if a problem arises, and the instinctive response is ‘not my responsibility’, the collaboration test has already been failed. 

Clause 10.2 comes alive not through legal interpretation, but through leadership. It is leaders, who set the tone for collaboration to thrive. In NEC contracts leadership means: creating psychological safety that encourages early warnings without fear of blame; upholding integrity in decision-making, particularly in the assessment of compensation events; acting transparently, not just when convenient, but especially when issues arise; and demonstrating consistency, knowing that trust is earned not in isolated moments but through a pattern of fair engagement across projects and stakeholders. 

In this context, trust is not only situational, it is also reputational. Contractors and clients who consistently act with fairness and openness often enter new projects with a trust advantage. Clause 10.2, when practiced rather than merely quoted, has the potential to shape both individual relationships and wider industry culture. 

Despite advancements in procurement models and contract forms, many parts of the construction industry remain encumbered by transactional mindsets, defensive risk postures and adversarial habits. Clause 10.2 offers an alternative pathway, but only if its message is internalised. 

Forms and frameworks are necessary, but insufficient on their own. Collaboration is not activated by clause alone. It requires leadership, anchored in values, sustained through action, to create environments where trust can take root and flourish. 

Philosophical perspective

Clause 10.2 is more than aspirational language; it is a philosophical proposition. Its roots can be traced to timeless principles about human dignity, fairness and the ethics of reciprocity. 

Scottish philosopher David Hume (1711–1776) believed that trust is not blind, it is rational: people co-operate because they see long-term benefit. Clause 10.2 is not about being naïve. It assumes that collaboration, even when costly in the short term, yields collective efficiency, cost savings and reputational dividends. Mutual trust is built on reciprocal gain, not just good faith. 

German philosopher Immanuel Kant’s (1724–1804) ‘categorical imperative’ said people should never treat others as mere instruments. In contract terms, this forbids withholding information, strategic delay or gaming the programme. It demands transparency, timely action and respect. Clause 10.2, seen through Kant’s lens, is a moral stance, not a tactical one. 

English philosopher John Locke (1632–1704) maintained that individuals are naturally predisposed to peaceful coexistence. He argued that even in the absence of formal institutions, people are guided by natural law, a moral code discoverable through reason, which obliges them not to harm others and to uphold voluntary agreements. From this perspective, Clause 10.2 does not impose an artificial behavioural norm but rather formalises a co-operative impulse foundational to human interaction. It serves not as a safeguard against disorder, but as an institutional expression of the very principles that underpin stable and equitable relationships. 

Finally, American and German philosopher Hannah Arendt (1906–1975) taught that power emerges not from control, but from action in concert with others. Clause 10.2 invites a shift from transactional mindsets to shared authorship of outcomes. It values listening, plural viewpoints and shared accountability, echoing the collaborative ethos NEC was designed to foster. 

True NEC leadership today must therefore go beyond compliance and adopt the principles highlighted by thinkers like Stephen Covey (1932–2012) and Amy Edmondson, professor of leadership at Harvard Business School: they should trust and inspire, not command and control; they should foster psychological safety so team members speak up without fear; and they should promote ethical pragmatism, where clarity of contract meets humility in judgement. 

Conclusion

Ultimately, NEC is not only a contractual innovation but also a cultural project. Its success depends on more than procedures: it rests on ethics, reciprocity and human dignity. These philosophical foundations give clause 10.2 its real power, shaping behaviours that enable collaboration to flourish in practice. 

Clause 10.2 is not a legal loophole or a soft clause: it is NEC’s moral centre. It requires interpretation and more than that it requires intention. The clause does not make projects easier; it makes them better. It invites people to act not just as roles but as human beings with responsibility to the project, to each other and to the profession. It brings contract law into conversation with the enlightenment’s best ideals and challenges to bring those ideals to life, one decision at a time. 

The dual-lens authorship of this article, combining on-the-ground NEC leadership with philosophical inquiry, reflects exactly what Clause 10.2 calls for: unity of diverse perspectives in pursuit of better project outcomes. NEC users should reclaim Clause 10.2 not just as a contract clause but as a philosophy and a mindset. In doing so, NEC will not just be a framework for project delivery but a platform for culture change.  

Clause 10.2 reminds us that construction is not only about structures of steel and concrete or soil and rock mechanics, but also about structures of trust. It is here that philosophy and practice meet in the daily decisions that shape both projects and people.