Warranties and indemnity in a university license: what institutions will and will not give
Warranty and indemnity in a university license agreement in India: what IITs and ICMR refuse, what they may give, and how a licensee should cover the gap.
Part of the guide Licensing technology from Indian institutions: the complete guide for companies
Indian universities and public labs license technology on an 'as is' basis. IIT Kanpur's template refuses any warranty of non-infringement, and ICMR's 2024 guidelines give no warranty that the technology works. In both, the licensee indemnifies the institution. A licensee should seek title and authority warranties, full disclosure of known problems, and a cap on its own indemnity.
Every company that licenses from an Indian university or public lab hits the same clause. The draft says the technology comes "as is", the institution gives no warranties, and the company indemnifies the institution against everything. Legal teams used to private M&A deals push back hard, and the negotiation stalls.
Most of that fight is avoidable. Institutions are not being difficult for its own sake: their templates are built around what a public body can promise. This post explains what the clauses mean, what two published Indian templates actually say, and where a licensee can still win useful protection.
What do warranty and indemnity mean in a licence?
A warranty is a promise that a fact is true. If it turns out false, the other party can claim damages. In a licence, warranties cover things like who owns the patent or whether the technology works.
An indemnity is a promise to cover the other party's losses from a defined event. Section 124 of the Indian Contract Act, 1872 defines a contract of indemnity as one where a party promises to save the other from loss caused by the promisor's own conduct or by the conduct of any other person. In licensing practice, indemnities are drafted much wider than that definition, to cover third-party claims, legal costs and settlements.
The two clauses work together. Warranties decide who is at fault when something turns out wrong. The indemnity decides who pays when someone outside the deal sues.
What do Indian institutions actually put in the template?
Two published documents show the pattern clearly.
IIT Kanpur's technology transfer agreement template (an MoU form on the institute's website) says in Section 12 that the IP is provided on an "as is" basis and that IIT Kanpur makes no warranties of any kind, express or implied. It expressly gives no warranty of freedom from patent, trademark or copyright infringement. It excludes liability for indirect, special or consequential damages, and limits liability for design services to revised design documentation. Section 15 makes the licensee defend, indemnify and hold harmless the institute and its people. Section 16 requires insurance, with the amount left blank for negotiation.
ICMR's Guidelines for Technology Development Collaboration (2024) say in clause 13.3 that ICMR makes no warranty about the workability of the technology, that it is transferred on an "as is where is" basis, and that ICMR disclaims any implied warranty of merchantability. Clause 13.2 makes the licensee indemnify ICMR and its officers. Clause 12.1 puts the duty to obtain certifications and regulatory approvals on the licensee.
| Point | IIT Kanpur template | ICMR 2024 guidelines |
|---|---|---|
| Basis of transfer | "As is", no warranties express or implied | "As is where is" |
| Validity or workability | No warranty | No warranty of workability |
| Non-infringement | Expressly no warranty | Not given |
| Indemnity | Licensee indemnifies IIT Kanpur | Licensee indemnifies ICMR |
| Consequential loss | Excluded | Not stated in the clauses read |
| Regulatory approvals | Not covered in the clauses read | Licensee's responsibility |
| Insurance | Required, amount blank | Not stated in the clauses read |
Other institutions use their own forms, and each one deserves a careful read. Still, expect the same shape at most IITs, NITs, central universities and government labs. If your draft looks like this, it is normal.
Why won't a university warrant its own technology?
Three reasons, and each one makes sense from the institution's side.
First, the law does not guarantee patents either. Section 13(4) of the Patents Act, 1970 says the examination and investigations at the Patent Office do not warrant the validity of any patent. A granted patent can still be revoked. An institution that warranted validity would be promising what the government itself refuses to promise.
Second, the institution does not make the product. The licensee designs it, scales it, manufactures it, markets it and sells it. Most product claims will come from that work, and the university has no control over it.
Third, the money does not support the risk. A licence fee of a few lakh rupees and a royalty of a few per cent cannot fund an uncapped promise. A public institution answerable to auditors will not sign one.
What institutions usually refuse, and what they may give
Ask for facts the institution can check in its own records.
What warranties can a licensee realistically get?
Focus on facts inside the institution's own knowledge. These are fair to ask for and, in practice, often accepted after discussion.
- Title: the institution owns the licensed patents and know-how, or has the right to license them. If inventors came from a sponsor, another institute or a company, ask for the assignment documents. Our patent due diligence checklist covers how to read the chain of title on IP India.
- Authority: the person signing has authority under the institution's IP policy and the deal has the approvals it needs. ICMR's own template asks the other parties for exactly this representation, so it is a reasonable thing to ask back.
- No conflicting grant: the institution has not granted an exclusive or conflicting licence in your field and territory. This matters most when you pay for exclusivity. See exclusive licences and field of use licences.
- Disclosure of what it knows, as a knowledge-qualified warranty: "to the best of the institution's knowledge, it has received no notice of any claim that the licensed patents are invalid or infringe third-party rights." The institution is not promising the world is clean, only that it has told you what it knows.
- Co-owner consent: where a patent is jointly owned, written consent of the co-owner. Our post on joint patents between a university and industry explains why.
Two warranties are almost never available and are not worth a stalled deal: validity and non-infringement. Cover those risks yourself, with your own searches.
How should the licensee's indemnity be limited?
You will almost certainly indemnify the institution. The useful question is how wide. These limits are standard in commercial licensing and are reasonable to propose to any public body.
| Term to ask for | Why it is fair |
|---|---|
| Scope limited to claims from your products, use and sales | You control those; you do not control the institute's research |
| Exclusion for the institution's negligence or wilful misconduct | Nobody should pay for the other side's fault |
| Prompt written notice of any claim | You cannot defend what you hear about late |
| Your control of the defence and settlement | You are paying, so you steer |
| Cooperation from the institution and inventors | You may need lab records to defend the claim |
| Survival period after the licence ends | An open-ended tail is hard to insure |
Pair the indemnity with product liability insurance, and agree the cover amount in the agreement. The IIT Kanpur template leaves the figure blank, which means the institution expects to discuss it. Check the cover with your insurer before you sign, not after.
A worked example in rupees
The figures below are an illustration, not a real deal.
A Pune MSME licenses a coating technology from a public institute. It pays an upfront fee of ₹12,00,000 and a 3% royalty on net sales. In year three, net sales reach ₹4,00,00,000, so the royalty that year is ₹12,00,000.
A customer then sues both the MSME and the institute, claiming ₹80,00,000 for a failed batch.
- Under a broad indemnity, the MSME pays the defence costs and any award for both parties, with no cap.
- Under a negotiated indemnity limited to claims from the MSME's products, with insurance cover of ₹1,00,00,000, the insurer handles the claim and the MSME's exposure is its deductible.
- If the failure came from an error in the institute's own data, a negligence carve-out lets the MSME argue that part of the loss is the institute's to bear.
The licence fee was the same in all three cases. What changed was about six lines of drafting.
What can a licensee do instead of asking for warranties?
Buy the protection with diligence.
- Search freedom to operate in your target market before you sign. Our guide to freedom to operate in India sets out the steps.
- Test the technology in a short evaluation or option period. An option agreement is built for this.
- Tie money to milestones. If the technology fails a technical milestone, a smaller upfront fee and larger milestone payments mean less is lost. See upfront licence fees.
- Write a remedy for invalidity. Ask that royalty on a patent stops if a court or the Controller revokes the relevant claims. This is a payment term, so institutions accept it more readily than a warranty.
- Register the licence. Under Section 68 of the Patents Act, a licence is valid when it is in writing with all its terms and duly executed. Registration under Section 69 is not a condition of validity. An unregistered licence, though, cannot be admitted as evidence of your title under Section 69(5) unless the Controller or a court directs otherwise.
Negotiating the warranty and indemnity clauses
Common mistakes
- Spending weeks trying to get a validity warranty, then signing the original indemnity unchanged because everyone is tired.
- Accepting "as is" without asking the institution to disclose known claims or challenges.
- Leaving the insurance amount blank, or filling in a number the insurer has not confirmed.
- Forgetting that ICMR's guidelines put regulatory approvals on the licensee, then budgeting as if the institute will handle them.
- Copying warranty language from a private software or M&A contract into a public-institution licence. It signals that the licensee has not understood the counterparty.
My view is that the indemnity clause deserves more negotiating time than the warranties. Institutions rarely move on validity, but many will narrow an indemnity once the licensee explains its insurance and its control over the product. That said, each institution's approval process differs, and some will not change their template at all; then the decision is simply whether the technology is worth the risk.
For the full set of clauses around this one, read our guide to the technology licence agreement. If you are still choosing what to license, Zernyx Hub has mapped patents from universities across India, with AI business insight on each, so you can compare options before the drafting starts.
Common questions
Will an Indian university warrant that its patent is valid?
Almost never. Section 13(4) of the Patents Act says examination does not warrant the validity of any patent, and institutional templates follow that line. IIT Kanpur's template offers the IP 'as is'. Ask instead for a warranty that the institution knows of no challenge to validity.
Who gives the indemnity in a university technology licence?
The licensee. IIT Kanpur's template makes the licensee defend, indemnify and hold harmless the institute, and ICMR's 2024 guidelines require the licensee to indemnify ICMR and its officers. The licensee is the party that makes and sells the product, so the institution expects it to carry product risk.
What warranties can a licensee realistically get from a university?
Usually limited ones: that the institution owns or controls the licensed IP, has authority to sign, has not granted a conflicting licence, and has disclosed what it knows about claims or challenges. Each is a fact the institution can check in its own records.
Should a licensee accept an unlimited indemnity?
It should try not to. Ask for the indemnity to cover claims arising from the licensee's own products and conduct, to exclude the institution's negligence or wilful misconduct, and to require prompt notice and control of the defence. Back it with product liability insurance.