Out-Law / Your Daily Need-To-Know

Out-Law Analysis 2 min. read

TCC case highlights contract negotiations requirements


A recent Technology and Construction Court (TCC) case in the UK highlights several important issues that preoccupy outsourcing and technology lawyers during contract negotiations.

One important point in the case involved the degree to which parties could depend on specific, agreed-upon timelines within the contract’s relief mechanism, especially when these timelines had not been adhered to consistently in practice. The ruling in this case determined that if the parties deviate from the contractual process through their conduct, they may be precluded from later invoking that process.

The case related to a dispute over a technology transformation and outsourcing project which was plagued by delays. Tata Consultancy Services Ltd (TCS) sought relief for one of the delays, alleging that Disclosure and Barring Service (DBS) had breached its contractual duties, referred to in the contract as an “Authority cause”. TCS needed to prove that the delay was due to the cause and that if not for this cause, the milestone date would have been achieved.

The contract stipulated that TCS was required to submit a notice seeking relief, referred to as an “exception report” in the agreement, within five days. This was a condition precedent for being eligible to claim compensation for the authority cause. However, TCS did not submit the exception report within this timeframe. TCS argued that it had believed the submission was unnecessary because neither party had been adhering to this procedure and therefore the requirement had become obsolete.

The judge sided with TCS, stating that DBS could not claim TCS was ineligible for compensation due to missing the five-day deadline for submitting the exception report.

This is a common issue in negotiating outsourcing and technology transformation projects that involve project work with set milestones and penalties for not meeting agreed deadlines.

Typically, these projects include a relief mechanism for the supplier. This mechanism ensures that if a delay or failure results from the customer's inability to meet an agreed-upon dependency, the supplier is relieved from its obligation to deliver by the specified date.

Usually, this mechanism outlines a specific process for the supplier to claim relief, such as providing notice within a certain number of days after becoming aware of the issue and submitting written notice detailing the cause. It is often stipulated in the contract that following this process is a prerequisite for the supplier's entitlement to relief. 

When discussing relief provisions, suppliers frequently resist formal procedures for claiming relief or, if they do agree to the process, balk at making it a prerequisite for relief. They contend that in a complex transformation project, cooperation and flexibility are essential when obstacles emerge. Strict notification timelines, they argue, create an overly adversarial environment, hindering collaboration and the pursuit of mutual objectives. 

Even though this concern is understandable, in numerous transformation and outsourcing initiatives, the client relies substantially on the supplier's expertise to meet the established milestones. Therefore, the distribution of responsibilities is uneven, making it reasonable to establish specific dependencies and relief mechanisms. Worries about projects turning overly "legal" at the cost of relationships are legitimate, but ultimately, the essence of a contract is to safeguard both parties' interests. Negotiating these terms yet failing to apply them defeats their purpose.

When delays occur, a useful tactic is to activate the formal contract terms concerning notices and similar procedures while concurrently holding business discussions, potentially on a without prejudice basis, to address the problem. This dual approach ensures legal protections are in place while maintaining commercial communications to resolve the situation.

The essential lesson from the ruling is that parties can only depend on a contractual mechanism if they have adhered to it diligently. Neglecting this process introduces the risk of estoppel. This situation frequently occurs in transformation and outsourcing disputes. The contract often offers effective solutions but is sidelined for "practical commercial talks." When these talks fall through and conflicts arise, reviving the contractual remedies becomes challenging unless there has been a well-defined reservation of rights, or the party has simultaneously engaged in both formal and informal communications.

We are processing your request. \n Thank you for your patience. An error occurred. This could be due to inactivity on the page - please try again.