Common contract issues are the ones that appear repeatedly in the same forms, in the same clause types, across contracts of different types and sizes. They are common not because they are obvious but because they are easy to overlook under time pressure, because business teams accept language from counterparties without understanding the implications, and because legal review is sometimes performed without a systematic checklist.
For Indian in-house legal teams, the list of contract issues that require consistent attention has India-specific dimensions: stamp duty compliance, MSME payment obligations, DPDPA data processing requirements, and regulatory clause requirements from RBI, SEBI, and IRDAI are all categories that global contract review checklists do not cover. This article covers the twelve contract issues that Indian in-house legal teams most commonly need to catch, with practical guidance on what to look for and why it matters.
1. Missing or Undefined Liability Cap
The absence of a liability cap in a commercial contract means that one or both parties face unlimited financial exposure if the relationship deteriorates. This is the most consequential gap in many standard commercial agreements.
What to look for: Does the contract include a limitation of liability clause? What is the cap expressed as, and is it commercially proportionate to the contract value? What are the exceptions to the cap, and do those exceptions create effectively unlimited liability for the categories of loss most likely to generate large claims?
Why it matters: A vendor agreement worth INR 10 lakhs with an unlimited indemnity for data breaches and IP infringement can create liability exposure of hundreds of lakhs. The cap needs to be present, appropriately sized, and the exceptions need to be reviewed as carefully as the cap itself.
2. Vague or Unlimited Indemnification Scope
Broad indemnification language, such as “the vendor shall indemnify the customer against all losses arising from this agreement”, can cover losses that are indirect, consequential, and far exceeding the contract value. Under Indian law, indemnification can cover losses that would not be recoverable as damages under Section 73 of the Contract Act, making the scope of the indemnity particularly important.
What to look for: Is the indemnification clause limited to specific triggering events and specific loss categories? Does it include or exclude indirect and consequential losses? Is there a cap on indemnification liability?
Why it matters: Unlimited indemnification exposure is one of the most common and most serious contract issues in technology services, SaaS, and vendor agreements. It requires active negotiation, not acceptance of the counterparty’s standard language.
3. Auto-Renewal Without Adequate Notice Period
Auto-renewal clauses renew a contract for a further term unless the buyer serves non-renewal notice within a defined window. When the notice window is short, typically 30 days or less, and the contract is not actively tracked, the renewal triggers before the buyer is aware it is approaching.
What to look for: Does the contract auto-renew? What is the notice period for non-renewal or termination? Is the notice period long enough to allow a meaningful commercial decision, or is it a trap that assumes you are tracking every contract in the portfolio?
Why it matters: Auto-renewals at outdated rates, or for services that are no longer needed, are a consistent source of unnecessary spend. For BFSI enterprises, auto-renewed agreements with regulatory compliance implications may need regulatory notification at renewal, creating additional risk if the renewal is not managed proactively.
4. Missing or Non-Standard Governing Law and Jurisdiction
The governing law and dispute resolution clause determines which law applies to the contract and where disputes are resolved. Accepting a foreign governing law clause without understanding its implications, or agreeing to arbitration in an inconvenient or costly forum, can make enforcement disproportionately expensive.
What to look for: Does the contract specify governing law? Is it Indian law, or foreign law? Where is the dispute resolution forum, and is it arbitration or litigation? If arbitration, what are the rules and seat of arbitration?
Why it matters: For Indian enterprises, contracts governed by the law of a foreign jurisdiction require legal advice in that jurisdiction to understand the rights and remedies. Arbitration in Singapore or London with Indian parties can add significant cost to even relatively modest disputes. Indian law and Indian arbitration under MSME Arbitration or institution-based rules is the standard position for domestic contracts.
5. No DPDPA-Compliant Data Processing Provisions
For contracts involving the processing of personal data of Indian citizens, the Digital Personal Data Protection Act, 2023 requires specific data processing provisions in the agreement. Contracts that do not include these provisions leave the data fiduciary exposed to regulatory risk.
What to look for: Does the contract involve the processing of personal data? If so, does it include provisions covering purpose limitation, data retention and deletion obligations, breach notification timelines, audit rights over the data processor, data return at contract end, and compliance with DPDPA obligations?
Why it matters: Under the DPDPA, data fiduciaries are responsible for the data handling practices of their data processors. A contract that does not include DPDPA-compliant data processing provisions is non-compliant regardless of how the processor actually handles data. The regulatory risk falls on the fiduciary.
6. Ambiguous or Missing SLA Definitions
Service level agreements that define the supplier’s performance commitments without specifying how performance is measured, what counts as a service failure, or what the remedy is for non-performance are not effectively enforceable. An SLA that says “the system will be available 99.9% of the time” without defining how availability is calculated, how downtime is reported, and what service credits apply for missed SLAs gives the buyer nothing actionable when performance falls short.
What to look for: Are SLA commitments defined with objective measurement criteria? Is there a defined reporting mechanism? Are the remedies for SLA failures, specifically service credits, termination rights, or liquidated damages, clearly specified? Is there a claim window for SLA credits?
Why it matters: Vague SLA definitions produce disputes about whether a failure occurred and how large the remedy should be. Precise SLA definitions produce enforceable standards and, when performance is poor, actionable remedies.
7. Inadequate Termination Rights
Contracts that give only one party the right to terminate for convenience, or that impose punitive termination fees, leave the other party locked into a relationship that may no longer serve them. Termination for cause provisions that require notice and a cure period can delay exit from a relationship where the counterparty’s breach is serious and continuing.
What to look for: Does either party have a right to terminate for convenience? What notice period is required? Are there financial consequences for early termination, and are those consequences proportionate? What constitutes a material breach for the purposes of termination for cause, and is the cure period reasonable?
Why it matters: Contracts that are difficult to exit create ongoing financial and operational exposure when a counterparty relationship deteriorates. Balanced termination rights are particularly important in long-term vendor and services agreements.
8. Missing MSME Payment Clause Compliance
For contracts with MSME suppliers, the MSME Development Act requires payment within 45 days of delivery or acceptance. Contracts with MSME suppliers that specify a longer payment period, or that are silent on the MSME payment obligation, create compliance risk.
What to look for: Is the counterparty an MSME? If so, does the payment term in the contract comply with the 45-day MSME obligation? Does the contract include the standard MSME payment clause or does it override the statutory requirement?
Why it matters: Non-compliance with the MSME payment obligation attracts compound interest at three times the bank rate notified by the RBI. Listed companies also face SEBI disclosure obligations for delayed MSME payments. The financial and reputational consequences of inadvertent non-compliance are material.
9. Incorrect or Missing Stamp Duty Provisions
Contracts executed in India attract stamp duty under state stamp acts. An incorrectly stamped contract, or one executed without the required stamp, is inadmissible as evidence in Indian courts. This is not a minor administrative issue. A contract that cannot be produced as evidence in a dispute is a contract that provides no protection when it is most needed.
What to look for: Has the applicable stamp duty been assessed for this contract type in the state where it is being executed? Is the stamp duty provision in the contract correctly allocating responsibility for payment? Is the correct instrument type being used for the document?
Why it matters: Multi-state enterprises executing contracts across Maharashtra, Karnataka, Delhi, Tamil Nadu, and other states face different stamp duty rates and instrument classifications in each state. Systematic stamp duty assessment should be part of the contract execution workflow, not an afterthought.
10. Unrestricted Assignment Rights
A contract that allows either party to assign their rights and obligations without the other party’s consent may result in the counterparty transferring the contract to a different entity without notice. In M&A contexts, change of control clauses that trigger assignment rights or termination rights can have significant transaction implications if not identified during due diligence.
What to look for: Does the contract include an assignment clause? Can either party assign the contract without consent? Is there a change of control provision that treats a change in ownership as an assignment? Does the restriction on assignment apply to both parties or only one?
Why it matters: For technology and vendor contracts, an assignment to a less capable or less creditworthy entity, or to a competitor, can materially affect the value and risk of the agreement. Change of control clauses in target company contracts are a standard due diligence item in M&A that can affect transaction structuring.
11. Intellectual Property Ownership Ambiguity
Contracts involving development work, customisation, or creative services frequently fail to specify clearly who owns the intellectual property created under the contract. Where the contract is silent on IP ownership, the position under Indian law may be different from what either party assumed.
What to look for: Who owns the intellectual property developed under the contract: the commissioning party, the developer, or are they joint owners? Are background IP rights licensed for the purpose of the engagement? What happens to developed IP at contract termination? Does the work-for-hire provision comply with the Copyright Act, 1957?
Why it matters: IP ownership disputes are expensive and disruptive. In technology development contracts, software development agreements, and creative services engagements, an IP ownership clause that is not explicit can result in the commissioning party not owning the output they paid for.
12. No Force Majeure or Inadequate Force Majeure Scope
Force majeure clauses excuse a party from performance obligations when events beyond their control make performance impossible or impractical. Contracts without a force majeure clause, or with a clause that is narrowly defined, may not protect a party when performance is genuinely disrupted by circumstances outside their control.
What to look for: Does the contract include a force majeure clause? What events are covered: is the list exhaustive or illustrative? Does it cover pandemic, regulatory change, labour disputes, and cyberattacks, categories that have become relevant in recent years? What are the notice obligations for invoking force majeure? Does force majeure suspend the obligation or terminate it?
Why it matters: Indian courts have interpreted force majeure clauses strictly: only events specifically listed or clearly within the scope of the clause will qualify. A narrow clause may not cover events that would intuitively seem to fall within the concept of force majeure. Post-pandemic, the drafting of force majeure clauses in Indian commercial contracts has received significantly more attention.
How to Build a Systematic Contract Review Process
Catching these twelve issues consistently across a high volume of contracts requires a systematic review process, not reliance on individual lawyer recall.
The most effective approach is a playbook-based review, where each of the twelve issue categories has a defined standard position, fallback positions, and an escalation threshold. Applied to every incoming contract, the playbook review ensures that deviations from the standard on each issue are identified before execution rather than discovered after a problem arises.
AI-assisted contract review, applied against a well-designed playbook, catches these issues automatically across the full contract volume, freeing the lawyer to focus their judgment on the flagged deviations rather than the routine review of standard clauses.
For Indian enterprise legal teams, the playbook needs to include the India-specific issue categories: stamp duty assessment, MSME payment clause compliance, and DPDPA data processing provisions. These are not in global playbook templates, and their absence creates precisely the compliance gaps that become visible during regulatory inspections and commercial disputes.
Conclusion
These twelve contract issues are common because they are easy to miss under time pressure and because counterparties routinely include them in their standard terms in forms that favour themselves. Catching them consistently requires a systematic approach: a defined playbook, a structured review process, and the right tools to apply them at scale.
For Indian in-house legal teams managing high volumes of contracts across multiple business units and regulatory frameworks, systematic contract review is not a luxury. It is the operational foundation that determines whether the contracts the organisation signs actually protect it.
Frequently Asked Questions
What are the most common contract issues that lead to disputes?
The most common contract issues that lead to disputes are vague or unlimited indemnification scope, missing or poorly defined SLAs with no specified remedies, ambiguous IP ownership in development agreements, unclear termination rights and conditions, and missing or non-standard governing law provisions. Each of these creates uncertainty about the parties’ obligations that becomes a dispute when the relationship deteriorates.
How should in-house legal teams catch these contract issues systematically?
A playbook-based review approach is the most effective systematic method. The playbook defines the standard position and fallback positions for each common issue category, and the lawyer applies it to every incoming contract to identify deviations. AI-assisted contract review can automate the initial pass against the playbook, ensuring consistent coverage across high volumes of contracts. Regular playbook reviews keep the standard positions current with regulatory changes and market practice.
What are the India-specific contract issues that global checklists miss?
The most significant India-specific contract issues that global checklists do not cover are: multi-state stamp duty compliance, MSME payment obligation clauses for contracts with MSME suppliers, DPDPA-compliant data processing provisions for contracts involving personal data, and regulatory clause requirements for contracts in BFSI, insurance, and other regulated sectors. These require India-specific playbook entries and India-specific AI training to be caught systematically.
How does the DPDPA create new contract review requirements?
The DPDPA, which came into force in 2024, requires specific data processing provisions in contracts where personal data of Indian citizens is processed. Legal teams must now check whether contracts involving data processing include provisions for purpose limitation, data retention and deletion, breach notification timelines, audit rights, data return at contract end, and compliance with the fiduciary’s DPDPA obligations. Contracts that lack these provisions expose the data fiduciary to regulatory risk regardless of how the processor actually handles the data.
What is the practical consequence of a missing or incorrectly applied stamp duty?
A contract executed without the required stamp duty, or with an incorrect stamp, is inadmissible as evidence in Indian courts under the applicable state stamp act. This means the contract cannot be used to prove the parties’ rights and obligations in a legal dispute. The contract may be compoundable, meaning the stamp duty can be paid later with a penalty, but the timing of discovery and the cost of the penalty make proactive stamp duty compliance significantly preferable to post-execution correction.
