IP Assignment Clauses in India: The 5-Year Default Most People Miss

An IP assignment clause is the sentence in a contract that transfers ownership of copyright, patents, designs or other intellectual property from the person who made it to the person paying for it. Most founders assume that once this clause exists, the client or company owns the work outright and forever. In India, that assumption is often wrong. If the clause does not say how long the assignment lasts, the law does not read it as "forever." It reads it as five years. This one line from the Copyright Act, 1957 has quietly reopened ownership disputes years after everyone thought the deal was closed.

This guide is written by Adira, which makes contract review and CLM software, so we have an interest in you understanding clauses like this well. That said, everything below stands on its own, whether or not you ever use our tools. If you just want to check one contract by hand, Weave (Adira's free browser tool) lets you mark up a clause like this without signing up for anything.

Plain meaning: what an IP assignment clause actually does

An assignment is a transfer of ownership, not a permission to use something. When a contract says "the Contractor hereby assigns to the Company all right, title and interest in the Work Product," it is meant to move the copyright (or patent, design, trademark) out of the creator's hands and into the company's, as if the company had made it itself. This matters because under Indian copyright law, the person who creates a work is the "author" and, in most cases, the first owner of copyright in it, by default. A contract, a freelance invoice, or an internal HR policy does not automatically flip that ownership. Only a valid assignment, or the specific employment carve-out in Section 17, does.

Compare this with a licence, which only grants permission to use the work while the underlying ownership stays with the creator. A badly drafted contract sometimes says "assign" when it means "licence," or vice versa, and the difference decides who can sue for infringement, who can resell the work, and who owns the next version of it. (See our companion piece on assignment vs licence for the full comparison.)

Who it protects, and the moment it bites

The clause protects whoever is paying for the work: a company hiring a developer, a startup engaging a design agency, a client commissioning a logo, a business buying code from a contractor. It is meant to bite the moment the work is created, or at least the moment payment is made, so the paying party can use, modify, sell or licence the output without going back to the original creator for permission each time.

It bites the other way, too. The creator, freelancer, or agency needs to know exactly what they are giving up. Sign a sloppy "we own everything you make" clause and you may have signed away rights to reuse your own frameworks, templates or prior tools on your next project.

The dispute usually surfaces years later: a founder who wrote the first version of a product as a contractor before incorporating, an agency that built a client's original brand assets under an old MSA that never mentioned a time period, a startup whose first developer left in year three and now claims the codebase reverted to them.

What to look for in the actual text

Four things decide how strong an IP assignment really is:

• Does it say "assign" (not "licence," "grant a right to use," or "make available")? Only "assign" (or clear equivalent language transferring ownership) moves title.
• Does it state a duration? Silence is not "forever." It triggers a default period, covered below.
• Does it state a territory? Silence here triggers a default too.
• Does it cover future works, moral rights, and "work product" broadly enough to include drafts, source code, documentation, and derivative works, not just the final deliverable?

The Indian position: the five-year default almost nobody reads

This is the core trap. Section 19 of the Copyright Act, 1957 lays out how a valid assignment works, and it includes two default rules that apply automatically when the contract is silent.

Section 19(5) says:

"If the period of assignment is not stated, it shall be deemed to be five years from the date of assignment."

Section 19(6) says:

"If the territorial extent of assignment of the rights is not specified, it shall be presumed to extend within India."

Read both sections on India Code or Indian Kanoon's copy of Section 19. There is a third, less-discussed sub-section worth knowing too. Section 19(4) says that if the assignee does not actually exercise the assigned right within one year of the assignment, that right is deemed to have lapsed, unless the assignment says otherwise. So an assignment that is technically signed but never acted on for a year can also unwind, independent of the five-year clock.

Put together: an assignment clause that is silent on period and territory, which is exactly what most US-style "work for hire" templates look like, does not give an Indian company permanent, worldwide ownership. It gives them five years, inside India, and only if they actually use the right within the first year.

This is why the period and territory lines cannot be left as boilerplate filler. "In perpetuity and throughout the world" is not decorative language in an Indian-governed contract; it is the only thing standing between your company and a rights reversion clock that starts running the day the contract is signed.

There is a separate, related default worth knowing on the ownership side, before assignment even comes into the picture: Section 17 of the Copyright Act says the author is normally the first owner of copyright, but proviso (c) carves out an exception for employees. Where a work is made "in the course of the author's employment under a contract of service," the employer is the first owner, "in the absence of any agreement to the contrary." The important word is "employment." A contractor, freelancer, or agency working under a contract for service (as opposed to a contract of service, i.e. actual employment) is not covered by this proviso. Their work stays theirs unless a separate, explicit assignment clause moves it, which is exactly why so many startups that started with contractors and interns discover, on due diligence, that nobody ever actually owns the early codebase.

A named case: Pine Labs v Gemalto Terminals

The five-year default is not theoretical. In Pine Labs Private Limited v Gemalto Terminals India Private Limited (Delhi High Court, Division Bench, 2011), Pine Labs had developed software for Gemalto under a Master Service Agreement that used the word "assigns" but never stated a period or a territory for that assignment. The Division Bench (Sikri and Kait, JJ.) held that Sections 19(5) and 19(6) were "inevitably triggered" by that silence, regardless of how the assignment clause itself was worded. In effect, the court read the missing period as five years and the missing territory as India, and treated the assignment as lapsed after that window. You can read the judgment on Indian Kanoon.

The lesson for any contract you sign today: courts do not treat a missing period as a drafting oversight to be interpreted generously in favour of "obviously they meant forever." They apply the statutory default literally.

Red flags table

Normal	Red flag	Why it matters
Assignment states a clear period ("in perpetuity")	Silent on duration	Defaults to 5 years under s.19(5); ownership can revert
Assignment states worldwide territory	Silent on territory	Defaults to India only under s.19(6); no rights abroad
Covers all past, present and future work product	Covers only the "final deliverable"	Drafts, source code, internal tools may stay with the creator
Assignment is signed and the right is used promptly	Right sits unexercised for over a year	Can lapse under s.19(4) if not exercised within one year
Contractor/freelancer agreement has its own explicit assignment clause	Company relies on s.17 employer default for a contractor	S.17(c) covers employees under a contract of service, not independent contractors
Moral rights (authorship, integrity) are addressed with a waiver or acknowledgment	Moral rights not mentioned at all	S.57 moral rights survive assignment in India; creator can still object to derogatory treatment of the work
Consideration/royalty terms are stated where relevant	Silent on consideration for the assignment	S.19(3) expects assignments to specify amount payable; silence weakens the assignment's clarity
IP created by employees on payroll, under employment contract of service	IP created by interns, contractors, or "gig" hires with no written assignment	These are the exact people s.17's employer default does not automatically cover
Assignment identifies the specific work and rights assigned	Vague "all IP related to the engagement" language	S.19(2) requires the work to be identified; vague scope invites disputes over what was actually assigned

Bad clause versus better clause

Bad: "The Contractor hereby assigns to the Company all intellectual property rights in the deliverables created under this Agreement."

What is wrong: no stated period, no stated territory, no mention of future or derivative works, no reference to moral rights.

Better: "The Contractor hereby irrevocably assigns to the Company, in perpetuity and throughout the world, all right, title and interest, including copyright and all economic rights, in and to the Work Product, including all drafts, source code, documentation and derivative works created during the course of this engagement, whether created before or after the date of this Agreement. The Contractor waives, to the extent permitted by law, any moral rights under Section 57 of the Copyright Act, 1957 that would restrict the Company's use, modification or adaptation of the Work Product."

What changed and why: adding "in perpetuity" and "throughout the world" defeats the s.19(5) and s.19(6) defaults explicitly instead of relying on silence. Naming "drafts, source code, documentation and derivative works" widens scope beyond just the final deliverable. Addressing moral rights under Section 57 closes the one gap an outright ownership transfer cannot close by itself, since moral rights are personal to the author and survive assignment in India even after economic rights move.

How this interacts with related clauses

An IP assignment clause rarely stands alone. It should be read together with an assignment vs licence analysis, because a contract that says "licence" where it means "assign" (or the reverse) undoes everything above. It should also sit next to the confidentiality clause, since a company can own IP outright and still need confidentiality obligations to stop a former contractor from reusing the underlying know-how in a competing product. And it usually needs an indemnity clause covering third-party IP infringement, so the assigning party stands behind the claim that the work was actually original and free to assign in the first place.

US and global contrast

US contracts often use "work made for hire" language under the US Copyright Act, which, for qualifying categories of work made by an employee within scope of employment, vests copyright in the employer from the moment of creation, no separate assignment needed. For independent contractors, US practice still typically layers on an explicit assignment clause as a backstop, because "work for hire" for contractors only applies to a narrow, specifically listed set of work categories.

The trap for Indian-governed contracts is that founders and legal teams often copy a US-style "work for hire" template that assumes indefinite, worldwide ownership by default. India has no general "work made for hire" doctrine that vests ownership immediately and indefinitely the way the US default does for qualifying employee work. Indian law leans on the assignment mechanism in Section 19, with its five-year and India-only defaults, for almost everyone who is not a direct employee under proviso (c). A template written for US law and pasted into an India-governed contract without adjusting period and territory language is, functionally, a five-year, India-only licence dressed up as a permanent global assignment.

FAQ

Does the five-year rule apply to patents and trademarks too, or just copyright? Section 19(5) and 19(6) are specific to copyright under the Copyright Act, 1957. Patent assignments are governed separately under the Patents Act, 1970, which does not carry an equivalent automatic five-year default; a patent assignment silent on duration is generally read as transferring the patent for its full remaining term. Always check which IP right is actually being assigned in a mixed-IP contract, since the default rules differ by right.

If our assignment clause is silent, does the IP just come back to the creator automatically after five years? Based on Pine Labs, the deeming provisions apply on their own once the period is unstated, so the assignment is treated as having a five-year term without a separate court order. In practice, disputes still usually end up needing a court or arbitrator to confirm what actually happened.

Does an assignment clause automatically cover moral rights, like the right to be credited as the author? No. Moral rights under Section 57 of the Copyright Act are separate from economic ownership and survive assignment. An assignment clause that only says "all IP rights are assigned" does not, by itself, waive the creator's right to object to distortion of the work or claim authorship; a contract that wants to limit this needs to address Section 57 specifically, and even then some aspects of moral rights are debated as to how far they can be contracted away.

We hired someone as a "consultant" but they work full-time only for us, on our premises, on our schedule. Does Section 17's employer default apply to them? Probably not automatically. Section 17(c) turns on whether the work was made "under a contract of service," which usually means genuine employment, not just economic dependence. Misclassifying an employee as a consultant to avoid payroll obligations does not reliably convert them into an "employee" for the purpose of this default, and it can create other labour-law problems besides. The safer route is always a written, explicit assignment clause regardless of how the relationship is labelled.

What happens if we never used the assigned IP for the first year after signing? Section 19(4) says an unexercised right lapses one year after assignment unless the assignment specifies otherwise. If your company assigned itself the right but sat on it, unused, for over a year, you may have already lost it before the five-year period even became relevant. Most well-drafted assignments now include a line disapplying s.19(4), so it is worth checking whether yours does.

Is a verbal or email agreement to assign IP enough in India? No. Section 19(1) requires an assignment of copyright to be in writing and signed by the assignor (or their authorised agent). An email discussion or verbal understanding that "we'll own whatever you build" is not a valid assignment under Indian copyright law, even if both sides believed it was agreed.

This guide explains how IP assignment clauses generally work under Indian law and the statutory defaults that apply when a contract is silent. It is not legal advice, and it does not tell you whether your specific contract, relationship, or dispute is enforceable in your situation. For that, especially where real money, a departing co-founder, or a contested codebase is involved, talk to a lawyer who can look at your actual documents.