admin

1. Introduction – The Myth of the ‘Standard’ Clause

May it be the price, the timelines or the deliverables, in contract negotiations, the focus revolves around commercial terms as the foremost priority. Once these are settled, the last few pages of the agreement, often filled with dense legal language, are brushed aside as “standard.” These are the boilerplate clauses, generic-looking provisions that recur across contracts, from service agreements to M&A deals.

The problem? Standard does not mean harmless. 

In fact, many lawyers have seen their cases turn on a single boilerplate clause that everyone assumed was routine. Courts treat these clauses as binding and enforceable, even when they seem to be buried in fine print. What looks like filler may determine whether you can sue, where you can sue and also how much you can recover.

 

2. Why Boilerplate Clauses Matter More Than You Think

Boilerplate clauses are not merely the decoratives in an agreement but are the very foundation of contracts. When relationships go awry, they have an impact on jurisdiction, liability, conflict resolution and even remedies, which makes the existence of an agreement without them impossible. These clauses specify terms including:

•       Parties may be forced to litigate in an awkward or surprising venue due to an unclear jurisdiction clause.
•       Damages may be significantly reduced by a limitation of responsibility clause, sometimes to a negligible amount.
•       Even in cases where the risk might have been controlled, a badly written force majeure provision can justify non-performance.

Consider the 2017 Indian case of Energy Watchdog v. CERC, in which the Supreme Court made it clear that business problems could not be covered by a general force majeure clause. The lesson is that minor drafting decisions can have significant legal repercussions.

Similar to this, the Supreme Court of India ruled in BALCO v. Kaiser Aluminium (2012) that the relevant procedural legislation is determined by the “seat of arbitration.” The entire course of dispute settlement might be altered by a single misspelt word in an arbitration agreement.

To put it briefly, omitting boilerplate phrases may be the difference between a successful and unsuccessful legal case.

 

3. Key Boilerplate Clauses
4. Governing Law & Jurisdiction

This section specifies which law will apply to the contract and how disagreements will be settled. Applying Indian law with Delhi jurisdiction has somewhat different ramifications than choosing New York law with exclusive jurisdiction in London courts. One of the most important provisions in cross-border contracts is this one.

1. Arbitration / Dispute Resolution

Arbitration is frequently chosen because it is efficient; however, shoddy drafting can lead to turmoil. Is the arbitration ad hoc or institutional? Which seat is it? Which regulations are relevant? If these are ambiguous, the sentence itself could be contested.

1. Force Majeure

This clause, which was previously thought to be boilerplate, made headlines during COVID-19. Performance is excused when extraordinary circumstances arise. However, the definition of “extraordinary” determines whether or not strikes, government laws or pandemics are covered.

1. Entire Agreement & Amendment

This specific clause guarantees that, aside from earlier verbal or informal agreements, the written contract is the only legally valid agreement. It can void sincere understandings that aren’t expressed in writing, even while it avoids disagreements over side commitments.

1. Severability Clause

This ensures that if one part of the contract is found invalid or unenforceable (for example, due to being illegal), the rest of the agreement still stands. Without it, a single bad clause could potentially invalidate the entire contract.

1. Notices Clause

This provision clarifies how official communications such as termination notices, breach notices, etc, must be given either by email, registered post or courier service and when they are deemed to have been received. In litigation, the absence of a clear notice clause can lead to disputes over whether a party was properly informed or not. 

 

4. Common Misconceptions About Boilerplate Clauses

1. “They are simply a routine.”
   Not true. Boilerplate terms are seen as legally obligatory by courts, which frequently decide the outcome of disputes.
2. “Every contract is the same.”
   False. Enforceability may be altered by small phrase changes (“seat of arbitration” vs. “venue of arbitration”).
3. “They won’t be enforced by the courts.”
   It depends. Courts have the authority to invalidate unfair provisions in consumer contracts, but they typically uphold the terms of business agreements between sophisticated parties.

 

5. Risks of Overlooking Boilerplate Clauses

•   Complacency vs. Efficiency: While standardised templates expedite the drafting process, an uncritical dependence on them breeds complacency.
•   Expensive Disputes: Due to inadequate drafting, multi-crore lawsuits based on jurisdiction or liability clauses have been filed.
•   Effect on Enforceability: Boilerplates that are poorly integrated or conflict with the primary provisions may make the overall agreement less enforceable.

For instance, preliminary litigation is frequently required for contracts lacking a clear dispute resolution process simply to determine where the matter should be heard, which delays settlement and raises expenses.

 

6. Conclusion

Although boilerplate clauses may appear to be an extra-formal effort, they actually influence the fundamental enforceability of all contracts. They determine how conflicts are settled, whose rights are upheld, and how risks are distributed, so they are not merely afterthoughts.
The most common misconception is that “standard” equates to “safe.” In actuality, what is usual is just typical and may not be fair or suitable for your transaction. Like business terms, each boilerplate clause should be carefully considered, examined, and negotiated.
The lesson learnt is to always read the boilerplate before signing a contract. Those final few pages could make the difference between your offer being flawless and having a lot of hidden flaws.

In today’s world, technology underpins nearly every business. It is no longer a specialised sector—every company is now, in some sense, a tech company. Technology-driven businesses rely on contracts to allocate risks, define rights, and ensure smooth operations. Drafting and negotiating technology agreements requires lawyers to understand which provisions are most critical and how they shape business relationships—far beyond simply inserting boilerplate terms.

In this blog, we explore the essential clauses in tech law agreements that every lawyer should know, along with their practical significance.

1. Intellectual Property (IP) Ownership Clause

IP lies at the heart of most technology agreements. Parties want certainty about ownership—whether it’s digital content, databases, algorithms, software, or source code. Disputes over IP can destroy partnerships, trigger litigation, and even impact valuations.

Key considerations:

• Clearly define any pre-existing IP owned by each party before the agreement.

• Allocate ownership of the foreground IP (newly created IP during the engagement).

• If one party retains ownership but grants usage rights, specify the terms of such a license.

• Watch for “work-for-hire” or “assignment” clauses in service agreements.

• Ensure IP ownership clauses align with the commercial intent of the parties, especially startups.

2. Confidentiality and Non-Disclosure Clause

Sharing sensitive data—such as source code, customer databases, algorithms, or business models—is common in IT transactions. Without robust confidentiality obligations, trade secrets risk being exposed.

Key considerations:

• Define what information is considered “confidential.”

• State exclusions (e.g., publicly available information).

• Specify the duration of obligations (typically 2–5 years; indefinite for trade secrets).

• Clarify obligations upon termination (return or destruction of confidential materials).

Avoid ambiguous definitions—too narrow leaves gaps, while overly broad may make the clause unenforceable.

 

3. Data Protection and Privacy Clause

With data-driven business models, privacy regulations like India’s DPDPA 2023, the GDPR (EU), and the CCPA (California) impose strict obligations on handling personal data. Contracts must reflect compliance responsibilities.

Key considerations:

• Identify roles: controller, processor, or sub-processor.

• Include obligations for cross-border transfers, breach notifications, and data security.

• Ensure compliance with sector-specific laws (healthcare, finance, telecom).

• Require subcontractors to follow the same standards.

Never treat privacy lightly—regulators increasingly demand demonstrable contractual accountability.

 

4. Indemnity Clause

Indemnities shift financial risks. In tech contracts, these often cover non-performance, data breaches, or IP infringement. Poorly drafted indemnities may impose unlimited liability on a party.

Key considerations:

• Define the scope of indemnity (only third-party claims or also direct losses?).

• Exclude indirect or consequential damages unless expressly agreed.

• Consider reciprocal indemnities where both parties require protection.

• Avoid broad-form indemnities that unfairly shift excessive liability.

 

5. Limitation of Liability Clause

No company wants unlimited liability if a project fails. This clause sets caps on damages to provide predictability.

Key considerations:

• Common caps: fees paid under the contract (often for the preceding 12 months).

• Carve-outs may exclude data breaches, fraud, indemnity, or willful misconduct.

• Specify whether caps apply per claim or in aggregate.

Clients should negotiate carve-outs to avoid being left without remedies, as providers often push for strict caps.

 

6. Service Levels and Warranties Clause

Technology contracts often involve ongoing services—software support, cloud hosting, or managed IT. Service level commitments and warranties ensure performance standards are met.

Key considerations:

• Define uptime guarantees, response times, and resolution times.

• Specify remedies for service level failures (credits, termination rights).

• Clarify warranty scope (fitness for purpose, freedom from defects, compliance with laws).

• Exclude unrealistic “absolute performance” promises that may backfire.

 

7. Termination Clause

Not all business relationships last. Termination clauses provide a structured exit, but poorly worded provisions can trap parties.

Key considerations:

• Termination for cause (e.g., breach, insolvency).

• Termination for convenience (exit with prior notice).

• Define notice periods and transition obligations (especially for services).

• Address post-termination rights—data return, IP ownership, and final payments.

 

8. Dispute Resolution Clause

This clause determines how disputes will be handled—through arbitration, mediation, or litigation.

Key considerations:

• Choose governing law and jurisdiction carefully, especially for cross-border deals.

• If arbitration is chosen, specify the rules, seat, and institution.

• Consider escalation mechanisms (negotiation → mediation → arbitration).

• Tech disputes may benefit from faster, less adversarial options like expert determination.

Unclear or absent dispute resolution clauses can cause costly jurisdictional battles before substantive issues are even addressed.

 

9. Force Majeure Clause

COVID-19 underscored the importance of clauses covering unforeseen events. In tech contracts, force majeure may also cover cyberattacks or regulatory changes.

Key considerations:

• Define force majeure events broadly but realistically.

• Clarify obligations during disruption (notice, mitigation).

• State rights after prolonged events (termination, suspension).

• Explicitly include cyber incidents as possible force majeure events.

 

10. Governing Law Clause

Cross-border tech contracts are the norm. Without a governing law clause, parties risk prolonged uncertainty and litigation.

Key considerations:

• Align governing law with the chosen dispute resolution forum.

• Consider enforceability of judgments or arbitral awards in relevant markets.

• Account for mandatory local laws (e.g., data protection, consumer law).

• Avoid defaulting to “laws of X country” without assessing enforcement practicality.

Conclusion

Clauses in technology agreements are not mere formalities—they are powerful tools of risk management. Each provision, from IP ownership to liability caps, shapes the rights, responsibilities, and protections of the parties involved.

For young lawyers, mastering these clauses is the first step toward becoming a trusted advisor in the digital economy. Businesses that approach contracts with precision and foresight can transform agreements into enablers of growth, rather than sources of costly disputes.

Lesson: Never dismiss IT contracts as boilerplate. Carefully drafted provisions can mean the difference between a successful partnership and an expensive conflict.