5.1 Ambiguity Errors
Ambiguity is the cardinal sin of legal drafting. An ambiguous document invites disputes and leaves courts to determine meaning that the drafter should have made clear.
When sentence structure allows multiple interpretations.
"The Seller shall deliver goods to the Buyer in sealed containers within 30 days."
Does "within 30 days" modify "deliver" or "sealed containers"?
"Within 30 days, the Seller shall deliver goods to the Buyer. All goods shall be delivered in sealed containers."
When it's unclear what a pronoun or reference refers to.
"If the Company fails to pay the Contractor, it shall be liable for interest."
Does "it" refer to the Company or the Contractor?
"If the Company fails to pay the Contractor, the Company shall be liable for interest."
The notorious "and/or" construction creates uncertainty about whether conditions are conjunctive or disjunctive.
Courts have struggled with "and/or" for decades. Instead, clearly state: "A and B" (both required), "A or B" (either), or "A or B or both" (any combination). Be explicit about your intent.
5.2 Inconsistency Errors
Inconsistency within a document creates confusion and potential conflicts. Courts must then decide which provision prevails - a decision you should have made yourself.
Using different terms for the same concept. If you define "Services" in Clause 1, don't refer to "work," "deliverables," or "scope" elsewhere to mean the same thing.
Provisions that contradict each other. Common examples: Different termination notice periods in different clauses, conflicting payment terms, inconsistent definitions of breach.
Clause 5.2: "Either party may terminate with 30 days' notice."
Clause 12.1: "Termination shall require 60 days' written notice."
Clause 12.1: "Either party may terminate this Agreement by providing 30 days' prior written notice to the other party."
[Single termination clause referenced throughout]
Before finalizing, do a "defined terms audit" - search for each key concept and verify it's referred to the same way throughout. Use your word processor's Find function to locate all instances.
5.3 Omissions and Gaps
Missing provisions leave parties without guidance when situations arise. What happens if a party dies? If government regulations change? If a third party interferes? These gaps become disputes.
Commonly Omitted Provisions
- Force Majeure: Events beyond control that excuse performance
- Assignment: Can parties transfer their rights/obligations?
- Notices: How must formal communications be delivered?
- Dispute Resolution: Court or arbitration? Which jurisdiction?
- Confidentiality: What information must be kept secret?
- Intellectual Property: Who owns work product created?
- Insurance: What coverage must parties maintain?
- Compliance: Who ensures regulatory compliance?
Missing "What If" Scenarios
- What if a party breaches - what are the consequences?
- What if performance becomes impossible?
- What if laws change making performance illegal?
- What if a party becomes insolvent?
- What if there's a dispute about quality or conformity?
- What happens at the end of the term?
For every obligation, ask: "Who does what, when, where, how, and what if they don't?" If any answer is missing, the provision is incomplete.
5.4 Procedural and Technical Errors
Technical errors can render documents unenforceable or cause rejection by courts and registrars. These are often the easiest to prevent with careful attention to formalities.
Failing to pay proper stamp duty renders documents inadmissible as evidence under the Indian Stamp Act. Each state has different rates - always verify before execution.
Missing signatures, unauthorized signatories, lack of required witnesses, or improper corporate authorization (missing board resolution) can invalidate agreements.
Documents requiring registration under the Registration Act, 1908 (e.g., immovable property transfers over Rs. 100, leases over one year) are unenforceable if unregistered.
Wrong court fee, improper verification, missing affidavits, incorrect formatting, late filing - all can result in rejection or dismissal of pleadings.
Pre-Execution Checklist
5.5 Error Prevention Strategies
The best way to deal with errors is to prevent them. Implement systematic review processes and use checklists to catch problems before they become disputes.
Review Process
- First Draft Review: Focus on substance - are all key terms addressed?
- Consistency Check: Verify terminology, defined terms, cross-references
- Completeness Review: Apply "what if" test to each provision
- Technical Review: Check formalities, execution requirements, procedural compliance
- Fresh Eyes: Have someone unfamiliar with the matter read it
Use of Checklists
- Create document-type-specific checklists (contract, plaint, notice, etc.)
- Include jurisdiction-specific requirements
- Update checklists when you discover new errors
- Make checklist completion mandatory before finalization
In later modules, we'll explore how AI tools can assist with error detection - from checking consistency of defined terms to identifying potentially missing provisions. But AI is a supplement, not a replacement, for careful human review.
Key Takeaways
- Ambiguity: The worst error - be explicit about meaning, avoid "and/or"
- Inconsistency: Use defined terms consistently throughout
- Omissions: Apply the "what if" test to identify gaps
- Technical errors: Check stamp duty, registration, execution formalities
- Prevention: Use systematic review processes and checklists