Configuration Risk in NEC Management: Lessons from United Utilities v Northstone

Contract management software should reduce risk, not create new arguments about what the contract requires.

A recent Technology and Construction Court decision, United Utilities Water Ltd v Northstone (NI) Ltd t/a Farrans Construction [2026] EWHC 1057 (TCC), is a useful reminder of a practical problem many NEC users will recognise: what happens when the contract is amended, but the contract management platform is not updated to match?

The case did not decide that an automatically generated platform date invalidated a payment notice. Nor did it decide that the platform caused the dispute. But it does highlight a wider risk pattern: if the live contract, system configuration and project team practice diverge, parties may later find themselves arguing about dates, notices, permissions, evidence and what a reasonable recipient would have understood.

That is not just a legal issue. It is a software governance issue.

Key takeaways

• NEC systems must reflect the live contract, including amendments.
• Automated dates and workflows can become risky if they are not updated.
• A mismatch between contract and system can undermine confidence in notices, payment processes and audit records.
• Configurability is a compliance control, not just an admin feature.
• FastDraft helps reduce these risks through configurable templates, workflows, roles, approvals, audit trails and reporting.

The case in brief

The judgment was handed down on 6 May 2026 by Her Honour Judge Kelly, sitting as a Judge of the High Court in the Technology and Construction Court in Leeds. The parties were United Utilities Water Limited and Northstone (NI) Limited, trading as Farrans Construction. The project related to water supply infrastructure works in West Cumbria under an amended NEC3 Engineering and Construction Contract. The original contract was NEC3 Option C with bespoke amendments, with later agreements increasing the contract price and changing the payment arrangements. Commentary records that the contract moved to a fixed-price milestone model with an accelerated payment cycle. 

The parties used CEMAR, described in the judgment as a cloud-based IT system used to assist with managing construction contracts. The system had been set up in 2017 to reflect the original payment process. The later contractual amendments introduced different payment timescales, but the system-generated payment dates were not updated to reflect those amended terms.

The dispute concerned payment notice PA-70, issued on 11 October 2024. The Project Manager assessed the amount due as a negative sum of £3,269,328.05, meaning the employer said money was due from the contractor. The contractor argued that the notice was invalid, including because the platform displayed an incorrect due date of 8 November 2024, which did not reflect the amended payment regime.

United Utilities succeeded in adjudication. Farrans then brought Part 8 proceedings, seeking declarations on what it said were short points of law. The court declined to determine those issues under Part 8 because the validity of the notice depended on a wider factual matrix, including how the parties used the system, what they understood about the mismatch, and how a reasonable recipient would have understood the notice in context. Summary judgment enforcing the adjudicator’s decision was granted. 

What went wrong from a configuration perspective?

The record indicates that the parties’ contract administration platform continued to generate dates based on the original contract setup, even after the payment process had been amended.

That matters because NEC payment administration is date-sensitive. Assessment dates, certification dates, due dates, final dates for payment and pay less notice deadlines can all have significant consequences. If a platform displays a date that is inconsistent with the amended contract, users may be left asking:

• Is the system date contractual or merely advisory?
• Does the notice itself remain valid?
• What did the receiving party know about the system mismatch?
• Who had authority to amend the system configuration?
• Was there a documented workaround?
• Did the parties preserve evidence of how the process was meant to operate?

Those were not abstract questions in this case. The judgment records that one party argued the system date was materially misleading, while the other relied on the wider context, including the parties’ knowledge of the amended payment process and how CEMAR had been used in practice.

The legal lesson for NEC users

The court’s reasoning reinforces an important point: contractual notices are not interpreted in a vacuum.

In deciding whether a notice is valid, the court may need to consider the objective context, including what a reasonable recipient, with the parties’ knowledge and contractual background, would have understood. In this case, the judge considered that the available evidence was insufficient to determine that question in the streamlined Part 8 process.

For NEC users, the lesson is practical. If your software, contract and project practice do not align, the dispute may become less about one document and more about the whole operating environment: configuration, knowledge, usage, permissions, amendments and evidence.

That is expensive territory.

The configuration risk pattern

Poorly configurable, rigid or poorly maintained systems tend to fail in predictable ways.

First, process breakdown. Users follow the platform because it appears to be the agreed workflow, even though the contract has moved on.

Second, auditability gaps. If the system was known to be wrong but the workaround was informal, it may be difficult to prove who knew what, when and why.

Third, permission issues. If project teams cannot safely amend templates, dates or workflows, they may rely on manual fixes, side emails or assumptions.

Fourth, version control failures. Old templates, old clause references or old date logic remain live after a deed of variation, Z clause amendment or procedural change.

Fifth, approval routing errors. A communication may appear to have followed the platform workflow but not the amended contractual process.

Sixth, evidence preservation weakness. In a dispute, the organisation needs a complete record: contract terms, system settings, issued communications, attachments, approval history and any configuration changes.

This is the configuration risk pattern: the software continues to administer yesterday’s contract while the parties are operating today’s contract.

How FastDraft helps reduce these risks

FastDraft is built around the idea that NEC contract management software must be configurable, controlled and auditable.

Rule-based templates help ensure communications are generated from controlled templates aligned to the contract setup. This reduces the risk of outdated wording, incorrect clause references or legacy payment assumptions appearing in live notices.

Configurable workflows allow processes to reflect the contract being administered, including project-specific approval steps, response requirements and communication routes. Where the contract changes, the workflow can be reviewed and updated through a controlled process.

Clause libraries and contract-specific configuration help project teams work from the relevant NEC form, option structure and agreed amendments, rather than relying on generic templates.

Role-based access controls reduce the risk of unauthorised changes or communications being issued by the wrong person. Different users can be given appropriate drafting, review, approval or submission permissions.

Approval gates create practical checkpoints before important notices, payment communications or contractual responses are issued. This is particularly important where dates, sums or clause references could have legal consequences.

Audit trails preserve who did what, when, and in what sequence. That supports defensibility if a notice, approval or workflow step is later challenged.

Reporting and dashboards help teams monitor overdue actions, outstanding responses, payment deadlines and compliance trends across a contract or portfolio.

Controlled rollouts support governance when templates, workflows or settings are changed. This helps organisations update the operating model without losing historical records or confusing current users.

The point is not that software removes the need for contractual judgment. It does not. The point is that well-configured software reduces avoidable ambiguity and gives project teams better evidence when decisions are scrutinised.

Configurability checklist for NEC contract tools

Before relying on any NEC contract management platform, ask:

• Can the system reflect the live contract, including later amendments?
• Can payment dates, workflows and templates be changed safely?
• Is there a controlled approval process for configuration changes?
• Are historic records preserved when settings are updated?
• Can user permissions be aligned to NEC roles and delegated authority?
• Are notices, attachments, approvals and timestamps held in a clear audit trail?
• Can outdated templates or workflows be retired or version-controlled?
• Can reports show overdue actions, missed deadlines and workflow bottlenecks?
• Is it clear whether system-generated dates are contractual, calculated or advisory?
• Is there governance for testing configuration before rollout?

Final thought

United Utilities v Northstone is not a case about software liability. It is a case about adjudication enforcement, payment notice validity and whether complex factual issues were suitable for Part 8 determination.

But for NEC users, it carries a broader warning. If your contract management platform is not configurable enough to keep pace with the live contract, the system can become part of the dispute.

FastDraft is designed to help avoid that failure mode through configurable workflows, controlled templates, role-based access, approval gates, audit trails and reporting.

To see how FastDraft supports compliant NEC contract administration, request a demo or speak to the FastDraft team.

This article is for general information only and is not legal advice. Parties should take project-specific legal advice on notices, payment provisions and contract administration procedures.

Talk to the FastDraft team