Module 3: Contract Drafting with AI

The standard contract structure is: (1) Title, (2) Date and Place, (3) Parties, (4) Recitals, (5) Definitions, (6) Operative Clauses, (7) Boilerplate, (8) Execution Block, (9) Schedules. Definitions come right after Recitals because they establish the meaning of key terms that will be used throughout the operative portions of the agreement.

The error is using trade name instead of legal entity name. "Tata Motors" is a trade/brand name, not the legal name. The correct legal name is "Tata Motors Limited" and should include the CIN (Corporate Identity Number). Proper party identification requires: full legal name, entity type, registration number (CIN/LLPIN), and registered address. Incorrect naming can make enforcement difficult or impossible.

Service Credits are the primary remedy mechanism in SLAs for performance failures. When the provider fails to meet agreed metrics (like 99.9% uptime), the customer receives credits against future fees. Service credits provide an automatic, pre-agreed remedy without requiring the customer to prove actual damages. They are typically calculated as a percentage of monthly fees based on the severity of the failure.

Payment terms and milestone schedules are NOT part of an NDA. NDAs focus on protecting confidential information and typically include: definition of what constitutes confidential information, obligations of the receiving party, permitted uses and disclosures, exclusions (public information, prior knowledge), duration of confidentiality obligations, and return/destruction requirements. Payment terms belong in service agreements or commercial contracts.

Under Section 27 of the Indian Contract Act, 1872, any agreement that restrains a person from exercising a lawful profession, trade, or business is void to that extent. Post-employment non-compete clauses are generally unenforceable in India, regardless of duration, geography, or additional compensation. However, non-compete restrictions DURING employment are valid. Courts may enforce reasonable non-solicitation clauses and confidentiality obligations as alternatives.

The clause is overly broad and may be unenforceable. It attempts to claim ownership of inventions unrelated to the company's business and created outside work hours - this overreach may render it partially or wholly void. Best practice is to limit IP assignment to: (1) inventions made during employment, (2) using company resources, (3) related to company's business or assigned duties. An overly broad clause also reduces employee morale and may be challenged in court.

Data Portability provisions address the critical question of what happens to customer data upon contract termination. These clauses should specify: data export formats available, transition assistance period, timeline for data deletion after export, and any fees for extraction services. Under DPDPA 2023, data portability is also a right of data principals. This is essential for avoiding vendor lock-in and ensuring business continuity.

Under DPDPA 2023, the SaaS provider is a Data Processor - an entity that processes personal data on behalf of a Data Fiduciary. The company (customer) remains the Data Fiduciary responsible for compliance. The Data Principal is the individual whose data is processed. SaaS agreements must include appropriate data processing terms, security requirements, sub-processor restrictions, and audit rights to ensure DPDPA compliance.

Unlimited indemnification for all third-party claims is a critical Red Flag requiring immediate escalation. This creates uncapped financial exposure - any lawsuit could theoretically result in unlimited liability. Red flags include: unlimited liability, uncapped indemnities, broad indemnification for all claims, and automatic renewal without notice. The other options (30-day notice, 12-month liability cap, Indian jurisdiction) are generally standard or acceptable terms that would be classified as green or yellow flags.

This is an example of Missing Clause Detection. AI can identify when expected provisions are absent from a contract. In this case, industry best practice requires that indemnification clauses be paired with liability caps to limit financial exposure. The AI has detected that a standard protective clause (liability cap) is missing, which creates risk. This is different from clause classification (identifying what type a clause is), syntactic ambiguity (unclear language), or compliance verification (checking against regulations).