The Bottom Line
- IT suppliers and other expert service providers have a heightened legal duty to warn clients about the risks and consequences of changing project requirements (i.e., “scope creep”). A failure to document these warnings can lead to significant financial liability, even if the client is demanding the changes.
- This ruling shows that clients are not passive participants. A court may find a client partially liable for a project’s failure if their actions, such as making constant, poorly managed change requests, contribute to delays and budget overruns.
- The judgment underscores the critical need for crystal-clear contract clauses. Your agreements must detail the process for managing scope changes, define documentation standards, and explicitly allocate risk for project delays to avoid costly disputes.
The Details
The case before the Amsterdam District Court involved a familiar but costly corporate scenario: a multi-million-euro custom software project gone wrong. The client, a large manufacturing firm, had contracted a software development house to build a new Enterprise Resource Planning (ERP) system. When the project collapsed after significant delays and budget overruns, the client terminated the contract and sued the supplier for damages, alleging a complete failure to deliver. The supplier fired back with a counterclaim, arguing the client had made the project impossible through a constant barrage of undocumented change requests.
The court rejected an all-or-nothing outcome, instead finding that both parties shared the blame for the project’s demise. Central to its reasoning was the supplier’s professional duty of care and, more specifically, its duty to warn. The court established that as the technical expert, the supplier had an obligation not just to execute the client’s requests but to proactively and formally warn them of the impact those changes would have on the timeline, budget, and ultimate success of the project. Simply proceeding with the changes without a clear, documented warning was deemed a breach of this professional duty.
However, the client was not absolved of responsibility. The court ruled that their behavior breached their own duty to cooperate as a reasonable contracting party. By failing to manage its internal stakeholders and funneling chaotic and frequent change requests to the supplier, the client actively contributed to the project’s failure. This shared fault led the court to a pragmatic decision: it partially dissolved the agreement, ordering the supplier to refund a portion of the fees paid but denying the client’s much larger claim for consequential damages and lost profits, citing the client’s own role in creating the problem.
Source
Source: Rechtbank Amsterdam
