Building a clause library: what to standardise first

Why start with a few clauses rather than a full library?

Most clause libraries fail the same way. Someone exports every clause from every template into a spreadsheet, the result has four hundred rows and six versions of confidentiality, and within a quarter nobody trusts it. A library is only useful if the people drafting and negotiating believe that the text in it is current and approved.

The better order is by negotiation frequency multiplied by cost of error. A handful of clauses carry most of the redlining and most of the risk in commercial agreements. Standardise those properly, with positions and approvals attached, and the library earns enough trust to grow. Boilerplate such as notices and severability can wait.

What does a library entry need besides the clause text?

A clause on its own is a template. What makes it a library entry is the structure around it, which tells a drafter what they may concede and who must be asked before they concede more. Each entry should carry:

• Preferred position: the text you open with, and a one-line statement of the interest it protects.
• Fallback positions: one or two pre-approved alternatives, in the order they may be offered.
• Walk-away line: the point beyond which the clause cannot be accepted at any approval level, or must go to the general counsel.
• Approval owner for each step: who may accept fallback 1, fallback 2, or anything outside the library.
• Applicability: contract types, counterparty types and value bands the entry applies to. A liability cap that suits a software subscription may be wrong for a construction contract.
• Drafting note: why the clause is written as it is, including any statutory or judicial reason, so the next lawyer does not 'improve' a deliberate choice.
• Version, owner and last review date.

Limitation of liability: why is it usually first?

It is the clause most often redlined and the one where an unauthorised concession is most expensive. Standardise the structure, not just the number: what the cap is measured against (fees paid in a period, contract value, insurance cover), which losses are excluded (indirect and consequential loss, loss of profit), and which liabilities sit outside the cap altogether, typically breach of confidentiality, data protection breaches, wilful misconduct and the indemnities.

Fallbacks here are usually numeric: a cap at twelve months' fees opening, rising to a multiple as a fallback, with a separate higher cap for data breaches rather than uncapped exposure. Tie each step to an approver.

Keep liquidated damages in the same family. Section 74 of the Indian Contract Act, 1872 entitles the injured party to reasonable compensation not exceeding the amount named in the contract, whether or not actual loss is proved. A named sum is therefore a ceiling on recovery, not a guaranteed payment, and the drafting note should say so.

Indemnity, confidentiality and termination

Indemnity comes second because it interacts with the cap. Section 124 of the Contract Act defines a contract of indemnity as a promise to save the other party from loss caused by the conduct of the promisor or of any other person. Commercial indemnities usually go further, covering third-party claims, legal costs and defined triggers such as intellectual property infringement or breach of law. Standardise the triggers, the claims procedure (notice, conduct of defence, no settlement without consent) and the relationship to the cap, and keep separate entries for the indemnity you give and the one you ask for.

Confidentiality is negotiated less fiercely but appears in almost every agreement, so a single approved text saves the most drafting time. Standardise the definition, the standard exclusions, compelled-disclosure wording, return or destruction on termination, and the survival period.

Termination needs entries for convenience (notice period, any termination fee), for cause (cure period, what counts as material breach), for insolvency events, and for consequences: transition assistance, return of data and survival. Watch any clause that cuts down the time to bring a claim. Section 28 of the Contract Act makes void an agreement that limits the time within which a party may enforce its rights by the usual legal proceedings, or that extinguishes rights on the expiry of a specified period. A short claims-notice window should be drafted with that in mind and reviewed by counsel before it enters the library.

Governing law and dispute resolution: what does the arbitration seat decide?

This entry is short and consequential, and it should be standardised early because ad hoc drafting here produces the most litigation about the clause itself. The point to get right is the seat of arbitration, which fixes the courts with supervisory jurisdiction.

In Bharat Aluminium Co. v. Kaiser Aluminium Technical Service, Inc. (6 September 2012), a Constitution Bench of the Supreme Court held that Part I of the Arbitration and Conciliation Act, 1996 applies only to arbitrations that take place within India, and said the law it declared applies prospectively to arbitration agreements executed after that date. The 2015 amendment then added a proviso to section 2(2): unless the parties agree otherwise, sections 9 (interim measures by court), 27 and parts of section 37 also apply to an international commercial arbitration seated outside India. If you want Indian courts available for interim relief in a foreign-seated arbitration, do not exclude those provisions by accident.

In BGS SGS Soma JV v. NHPC Ltd. (10 December 2019), the Supreme Court held that where a clause expressly designates a 'venue', designates no other place as the 'seat', the arbitration is governed by a supranational body of rules, and there is no other significant contrary indicia, the stated venue is the juridical seat. The library entry should therefore name the seat expressly, using the word 'seat', and treat venue as a separate, optional choice.

Two more points belong in the drafting note. Section 12(5) of the Act, inserted in 2015, makes a person ineligible to be appointed arbitrator if their relationship with the parties, their counsel or the subject-matter of the dispute falls within the Seventh Schedule, which includes an employee, consultant or adviser of a party; the parties can waive this only by express written agreement after disputes have arisen. A clause letting one side's officer act as sole arbitrator should not be in the library. And Exception 1 to section 28 of the Contract Act preserves agreements to refer disputes to arbitration, so the arbitration entry is not caught by the bar on restraining legal proceedings.

Data protection: is a DPDP processor clause now standard?

For any agreement where a vendor processes personal data on your behalf, yes. Section 8(2) of the Digital Personal Data Protection Act, 2023 allows a Data Fiduciary to engage a Data Processor only under a valid contract, and section 8(1) keeps the fiduciary responsible for processing done on its behalf irrespective of any agreement to the contrary. Rule 6(1)(f) of the Digital Personal Data Protection Rules, 2025 requires appropriate provision in that contract for reasonable security safeguards. Rule 6 comes into force eighteen months after the Rules were published, which puts it in May 2027.

Because the Act lists no mandatory processor terms, this entry is a module rather than a single clause: roles and purpose, security safeguards, breach notification to you, sub-processing, deletion on completion and audit. Keep it as one versioned schedule that every vendor template references, so a change to it reaches every new agreement at once.

Stamp duty and execution: why does a boilerplate clause belong in the first set?

Because a wrong answer here shows up only when you need to rely on the document. Section 17 of the Indian Stamp Act, 1899 requires an instrument chargeable with duty and executed in India to be stamped before or at the time of execution, and section 35 makes an instrument not duly stamped inadmissible in evidence and prevents it being acted upon until duty and any penalty are paid. Several states have their own stamp statutes with different rates and procedures.

In its December 2023 decision In re: Interplay between Arbitration Agreements under the Arbitration and Conciliation Act, 1996 and the Indian Stamp Act, 1899, a seven-judge bench held that agreements not stamped or inadequately stamped are inadmissible under section 35 but are not void or unenforceable, that non-stamping is a curable defect, and that stamping objections are for the arbitral tribunal rather than the court at the referral stage. Curable is not the same as costless. The library entry should state who bears stamp duty, which state's law the parties expect to apply, the execution method (wet ink, e-stamp with electronic signature, or another approved route), counterparts, and that the stamped copy is the one retained.

How should the approval matrix be built?

Write the matrix against the library, not against contracts. Each row is a clause and position; each column is an approval level. Accepting the preferred position needs no approval; fallback 1 might sit with the contract owner's legal reviewer; fallback 2 with the head of legal or finance; anything outside the library with the general counsel. Liability and indemnity rows often need a value band as well, so a fallback acceptable on a small contract escalates on a large one.

Keep the matrix short enough to use on a negotiation call. Where your contract tool supports it, route approvals from the matrix automatically rather than by email, so the record of who accepted which deviation sits with the contract. IntelloContract, for example, combines a template library with multi-stage, value-based approval workflows and AI review against your playbooks to flag deviations and missing clauses; any tool you use should keep that record attached to the agreement.

How do you version a clause library without breaking live contracts?

Treat the library like code. Every entry has a version number, an owner, a change note and an effective date. Changes go through a named reviewer. Old versions are retained, never overwritten, because executed contracts will be read against the text that was current when they were signed.

• Record which library version each new contract drew from, so you can find every agreement that carries a clause you later change.
• Review on a calendar, at least annually, and on a trigger: a new statute or rule, a relevant Supreme Court judgment, or a dispute that exposed a weakness.
• When the law changes, update the drafting note and the effective date, and decide explicitly whether existing contracts need amendment or only new ones change.