NEC4 Project Alliance Contract: A New Era for Collaborative Contracting

The introduction of the NEC4 Project Alliance Contract (PAC) is a significant milestone in the evolution of collaborative contracting within the construction and engineering industries. Developed to replace the NEC4 Alliance Contract (ALC) and, over time, the PPC2000 Project Partnering Contract, PAC brings together the strengths of several well-established alliance models into a single, modern contractual framework.

According to the NEC website, the NEC4 PAC, which was announced in June 2026, “is a multi-party contract for the appointment of a number of suppliers to form an alliance with the client, working together to design and build an asset in a collaborative, two-stage environment”. Although announced in June 2026, the contract is intended for publication in the final quarter of 2026.

The contract has been designed to support organisations that want to move beyond traditional client-contractor relationships towards genuine collaboration. By creating a single agreement for all alliance members, NEC4 PAC promotes shared responsibility, collective decision-making and a common focus on achieving successful project outcomes.

The PAC adopts a governance structure centred on an Alliance Manager and a Core Group (senior decision-making body for the alliance), reflecting the increasing importance placed on integrated decision-making in major project delivery. This reflects the collaborative ethos of alliance contracting and appears to introduce a more clearly defined governance framework than that found in the NEC4 ALC.

The NEC4 PAC also incorporates a number of familiar NEC mechanisms, including early warnings, construction programmes, compensation events and performance incentives. These features will be familiar to experienced NEC users and may assist in providing greater structure and visibility around project risks and change management. However, their inclusion within an alliance environment raises important questions. Whilst such mechanisms can encourage proactive project management, careful drafting and implementation will be required if they are intended to have meaningful consequences for alliance members.

Another notable feature is the option to adopt a “no blame, no claim” approach. For many alliance practitioners, this principle lies at the heart of a true alliance model. The removal of traditional legal claims between alliance participants encourages collective problem-solving and helps ensure that project participants focus on achieving the best overall outcome rather than preserving individual contractual positions.

The principles behind PAC reflect a growing recognition across the industry that better performance is achieved when risks, objectives and incentives are aligned from the outset. Early engagement with the supply chain, integrated governance and joint performance management all form part of the contract’s approach, encouraging teams to solve problems together rather than relying on contractual positions.

However, experience has shown that a collaborative contract is only one part of the solution. Successful alliance programmes over the past two decades have demonstrated that the greatest improvements come when the contract is supported by effective delivery systems, strong leadership and a culture of continuous improvement.

In this context, NEC4 PAC should be viewed as an enabler rather than a guarantee of success. Its value lies in providing a contractual environment that encourages openness, shared accountability and collective problem-solving. When combined with the right behaviours and project management systems, it has the potential to help clients and delivery partners achieve better outcomes while fostering long-term collaborative relationships.

As the industry continues to tackle increasingly complex projects and ambitious delivery targets, NEC4 PAC represents an important step forward in supporting more integrated, collaborative and outcome-focused project delivery.

It will also be interesting to see how the final published form of PAC compares with its predecessor, the NEC4 ALC. One criticism occasionally levelled at the ALC was that it was shorter and less prescriptive than other established alliance contracts, such as those used by Network Rail and Infrastructure Ontario. While that flexibility appealed to some users, others preferred the greater degree of procedural detail provided by alternative alliance models. Whether NEC has sought to broaden adoption of PAC by providing a more comprehensive and detailed contractual framework remains to be seen, but the initial indications suggest an evolution towards a more structured approach to alliance governance and delivery.

As collaborative contracting continues to evolve, it is important that clients, contractors and consultants fully understand both the opportunities and the obligations that these arrangements create. Specialist legal advice at the outset can help ensure that alliance contracts are implemented effectively, risks are appropriately managed and the collaborative principles are reflected throughout project delivery.

Our international construction team has extensive experience advising on collaborative procurement, alliance and partnering arrangements, and we are well placed to support organisations considering the adoption of NEC4 PAC. If you are considering collaborative contracting, or have any queries regarding the NEC4 PAC, please contact Nadir Hasan or Karina Alibhai.