{"id":7156,"date":"2025-12-27T06:02:44","date_gmt":"2025-12-27T06:02:44","guid":{"rendered":"https:\/\/dexpatent.com\/insights\/?p=7156"},"modified":"2025-12-27T06:09:53","modified_gmt":"2025-12-27T06:09:53","slug":"can-you-patent-your-university-project","status":"publish","type":"post","link":"https:\/\/dexpatent.com\/insights\/2025\/12\/27\/can-you-patent-your-university-project\/","title":{"rendered":"Can You Patent Your University Project?"},"content":{"rendered":"

\"Can<\/p>\n

A Student\u2019s Guide to Protecting Ideas<\/em><\/strong><\/p>\n

For many students, university projects begin as academic requirements but often evolve into commercially valuable ideas. In India, many such projects can be patented. However, whether you can file and who owns the invention depends on factors such as funding sources, institutional IP policies, inventorship, and whether the idea has been publicly disclosed under patent law timelines.<\/p>\n

What counts as patentable?<\/strong><\/h2>\n

If your project is new, involves an inventive step, and is industrially applicable, it may be patentable in India. Patentable subject matter includes products, processes, systems, compositions, and software\u2011enabled inventions, provided the invention demonstrates a technical effect or technical contribution and is not merely an algorithm or business method excluded under Section 3(k) of the Patents Act.<\/p>\n

However, be cautious: many activities that seem purely academic are legally treated as public disclosures under patent law. These include thesis uploads, posters, project demonstrations, conference presentations and online repositories. Once disclosed publicly, novelty is destroyed unless a patent application has already been filed.<\/p>\n

\"What<\/p>\n

India follows an absolute novelty standard, any public disclosure before filing can destroy patentability. The only limited exception is under Section 31, which applies to disclosures at government-notified exhibitions or presentations before learned societies. To rely on this exception, Form 31 must be filed under Rule 29A within 12 months of the disclosure.<\/p>\n

Because very few exhibitions are officially notified, the safest approach is to file a patent application before any public disclosure or to use NDAs (non-disclosure agreements) and access restrictions until filing is complete.<\/p>\n

Who owns the invention?<\/strong><\/h2>\n

Ownership in Indian academic settings typically depends on institutional IPR policies and AICTE\u2019s (All India Council for Technical Education\u2019s) National Innovation and Startup Policy. In general, student retain ownership where no substantial institutional resources are used and the work is done independently. In contrast the institute or a joint arrangement often claims ownership with revenue sharing when institutional facilities, funding, or sponsored projects contribute to the invention.<\/p>\n

Most policies require prompt disclosure to the IP cell, define revenue-sharing mechanisms for licensed technologies, and specify timelines for deciding whether the institution will file a patent. Students should review assignment clauses in course, agreements, incubation agreements, and sponsorship contracts before publishing or pitching their work.<\/p>\n

History that shaped student IP<\/strong><\/h2>\n

India did not pass a specific law for university inventions. Instead, Indian universities and institutions developed their own intellectual property policies and followed model IPR guidelines and frameworks. AICTE encouraged institutes to adopt clear policies that protect students and acknowledge their role as inventors. These policies made it common for students to have friendly ownership rights over their work, while also allowing universities to share patents and split revenue or equity when the campus provides significant support or funding.<\/p>\n

In parallel, Indian courts and the Patent Office refined the software\/Computer Related Invention (CRI) doctrine. Key decisions emphasize that computer\u2011implemented inventions demonstrating a concrete technical effect are not barred by Section 3(k), shaping how student software projects can be protected today.<\/p>\n

Together, these developments, policy standardization at HEIs (Higher Education Institutions) and jurisprudence clarifying what qualifies as a technical effect, now define the pathway for Indian students moving from campus projects to patents and eventual spin\u2011outs.<\/p>\n

Case law and cautionary tales<\/strong><\/p>\n