An IP assignment agreement is the single document standing between you and a founder’s worst nightmare: building a product for months, or years, only to discover you never actually owned the code, the design, or the idea behind it. I’ve watched this exact scenario play out with founders who assumed a handshake deal, an invoice, or even a signed NDA was enough to secure ownership of what they paid for — it isn’t, and the gap between what founders assume and what Indian law actually says is exactly where ownership disputes come from. This guide covers what an IP assignment agreement actually does, why it’s legally distinct from an NDA, what happens when one is missing, and how to fix the gap before it becomes a dispute.
IP Assignment Agreement vs. NDA: A Confusion That Costs Founders Real Money
This is the misunderstanding I see most often, and it’s worth clearing up before anything else: an NDA protects confidentiality — it stops someone from disclosing or misusing information they were given access to. It does nothing to establish ownership. A founder can have a rock-solid NDA in place with a freelance developer and still not own a single line of the code that developer wrote, because confidentiality and ownership are two entirely separate legal questions, addressed by two entirely different documents. An IP assignment agreement is the document that actually transfers ownership from the person who created the work to the business that commissioned it. Skipping this step because “we already have an NDA” is one of the most common and costly assumptions I encounter in practice.
The Default Rule Nobody Reads: Section 17 of the Copyright Act
Every IP assignment agreement exists to override a default rule most founders have never read. Under Section 17 of the Copyright Act, 1957, the author of a work — the person who actually created it — is its first legal owner. This is the baseline. Everything else is an exception carved out of that baseline, and the exceptions matter enormously depending on who created the work and under what kind of relationship.
- Employees under a genuine contract of service: Section 17(c) makes the employer the first owner of copyright in work created by an employee during the course of employment — but only if there’s no contract stating otherwise, and only if the relationship is a true employer-employee “contract of service.”
- Freelancers, consultants, and agencies under a contract for service: This is where founders get caught out. The Section 17(c) employer exception does not apply. For nearly all software, design, copywriting, and product work, a freelancer or contractor remains the legal owner of what they create — regardless of who paid for it, who commissioned it, or how much was paid — unless a proper IP assignment agreement transfers that ownership in writing.
- A narrow exception for commissioned works: Section 17(b) creates a specific carve-out for commissioned photographs, paintings, portraits, engravings, and films, where the commissioning party owns the work by default. This exception is narrow and does not extend to software, most design work, or written content.
The Freelancer Trap: Why Paying an Invoice Doesn’t Transfer Ownership
Here’s the sentence that should be on every founder’s wall: paying someone for their work does not transfer copyright in that work. This surprises almost every first-time founder I explain it to. If you hire a freelance developer to build your product’s core codebase, and there’s no IP assignment agreement in place, the legal reality is that the developer owns that code — you’ve paid for a license to use it, at best, not for the code itself. Without an assignment, that same developer could legally reuse, resell, or relicense substantially the same code to a competitor the next day, and you would have very limited legal ground to stop them. This isn’t a theoretical risk; it’s the direct, predictable consequence of relying on an invoice and a Slack message instead of a proper IP assignment agreement signed before the work even begins.
What About Patents? The Rules Get Even Murkier
If copyright ownership defaults are already easy to get wrong, patent ownership is even less intuitive. Unlike copyright, the Patents Act, 1970 doesn’t contain an explicit statutory provision automatically vesting patent rights in an employer the way Section 17(c) does for copyright. Indian courts have generally applied a “master and servant” style doctrine, looking at whether an invention was created within the scope of employment and using company resources — but this is far less predictable and far less codified than the copyright position. For inventions created by employees, and especially by contractors or consultants, an IP assignment agreement specifically addressing patent rights — not just copyright — is essential. Relying on an employment contract’s general confidentiality language, or assuming “we paid them, so we own it,” leaves a genuine gap that an employee-inventor could exploit to claim rights to a patent your company assumed it already owned.
What a Legally Valid IP Assignment Agreement Must Include
Under Section 19 of the Copyright Act, 1957, a valid IP assignment agreement isn’t just a sentence buried in a longer contract — it has specific formal requirements:
- It must be in writing and signed by the person assigning the rights (the assignor).
- It must identify the specific work being assigned, clearly enough that there’s no ambiguity about what’s covered.
- It must specify the rights being transferred — copyright can be assigned in whole or in part, for specific uses, so vague language creates exactly the kind of ambiguity an IP assignment agreement is meant to eliminate.
- It should state the duration of the assignment. If left unspecified, Section 19(5) deems the assignment to last five years from its date — which may be far shorter than a founder actually intends for a core product asset.
- It should state the territory the assignment covers. If left unspecified, Section 19(6) presumes the assignment is limited to India only — a serious gap for any startup with global ambitions or customers outside India.
- Royalty terms, if any, though no monetary consideration is legally required for a valid copyright assignment.
An IP assignment agreement that skips the duration or territory clauses doesn’t fail outright — but it silently defaults to terms the founder almost certainly didn’t intend, which is arguably worse than an obvious gap, since nobody notices it until years later.
What Happens When IP Isn’t Assigned Properly
The consequences of a missing or defective IP assignment agreement rarely show up immediately — they show up at exactly the moment a business can least afford them:
- Fundraising due diligence. Investors and their lawyers specifically check IP chain of title during diligence. A gap here — a key freelance developer with no signed assignment, an early co-founder who left without one — can delay or kill a round, exactly the kind of risk I’ve seen surface during the angel investment agreement process when a startup’s cap table and IP ownership don’t line up cleanly.
- A departing team member walking away with real leverage. If a co-founder or early contractor leaves without a proper IP assignment agreement covering their contributions, they may retain genuine legal rights over core parts of the product — leverage they can use in a dispute over equity, severance, or anything else.
- A competitor legally obtaining your own codebase. As covered above, an unassigned freelancer can legally resell or relicense their work, including to a direct competitor.
- Acquisition risk. A buyer’s legal team will scrutinize IP ownership as closely as investors do, and unresolved gaps can reduce a valuation or scuttle a deal entirely at the worst possible moment.
How to Fix a Missing or Weak IP Assignment Agreement
If you suspect gaps exist in your company’s IP ownership, here’s the practical path to closing them:
- Audit who created what. Go through your codebase, designs, and content, and map each significant asset back to who created it and under what kind of agreement (employee, freelancer, agency, unpaid co-founder).
- Execute retroactive assignment deeds for anything created without a proper IP assignment agreement at the time. A retroactive assignment, signed now by the original creator, can close historical gaps — but only if that person is still reachable and willing to sign, which is exactly why waiting is risky.
- Standardize your IP assignment agreement across every future engagement — employees, freelancers, agencies, and consultants — rather than relying on informal trust or a generic clause buried in a longer contract.
- Pair it with, but don’t confuse it for, an NDA. Both documents should exist for anyone with access to sensitive product information, but they solve different problems and neither substitutes for the other.
- Address patents separately, if your business involves anything patentable, since a general IP assignment agreement focused only on copyright may not adequately cover invention rights under the murkier framework described above.
- Have the assignment reviewed by a lawyer, particularly for anything involving a departing co-founder or a significant piece of your core product — this is exactly the kind of jurisdiction-specific, fact-sensitive drafting where AI-generated contract language reliably falls short.
Employment vs. Freelance IP Assignment Agreements: What Actually Changes
An IP assignment agreement for an employee can often be shorter, since Section 17(c) already does much of the work by default — the clause mainly needs to confirm the relationship and close any ambiguity about scope. An IP assignment agreement for a freelancer, consultant, or agency needs to do far more heavy lifting, since there’s no favorable default to rely on at all — every right needs to be explicitly transferred, in writing, before work begins ideally, and certainly before final payment. This is exactly the distinction I built into the founders agreement template, where the IP assignment clause is deliberately drafted to cover co-founders regardless of whether they’re technically employees, since founder relationships often blur that line in ways formal employment law doesn’t anticipate.
Conclusion: Ownership Isn’t Assumed — It’s Assigned
The uncomfortable truth about intellectual property in India is that ownership defaults to the person who did the work, not the person who paid for it, in far more situations than most founders realize. An IP assignment agreement is the only document that actually closes that gap, and it needs to be signed — properly, in writing, with the right scope, duration, and territory — before the work happens, not after a dispute makes it urgent. If you’re not certain your company’s codebase, designs, or inventions are properly owned, that’s worth confirming now rather than during your next fundraise or acquisition conversation. You can reach out here for a review, or explore more founder-focused legal guides on the blog.
Frequently Asked Questions (FAQ)
1. What is an IP assignment agreement? An IP assignment agreement is a legal document that formally transfers ownership of intellectual property — such as copyright in code, designs, or written content, or rights in a patentable invention — from the creator to another party, typically the business that commissioned the work.
2. Does paying a freelancer for their work automatically give me ownership of it? No. Under Section 17 of the Copyright Act, 1957, a freelancer engaged under a contract for services remains the legal owner of their work regardless of payment, unless a valid, written IP assignment agreement transfers that ownership.
3. Is an NDA the same as an IP assignment agreement? No, and confusing the two is a common and costly mistake. An NDA protects confidential information from being disclosed or misused; an IP assignment agreement transfers actual ownership of the work itself. Most businesses need both, but neither substitutes for the other.
4. Who owns IP created by an employee in India? Under Section 17(c) of the Copyright Act, an employer generally owns copyright in work created by an employee during the course of employment under a genuine contract of service, unless the employment contract states otherwise.
5. Do startups need a separate IP assignment agreement for patents? Yes, ideally. The Patents Act, 1970 doesn’t provide the same clear employer-ownership default that copyright law does, so a general copyright-focused IP assignment agreement may not adequately secure patent rights over an employee or contractor’s inventions.
6. What must a valid IP assignment agreement include under Indian law? Under Section 19 of the Copyright Act, it must be in writing, signed by the assignor, identify the specific work, and specify the rights transferred. It should also state duration and territory, since unspecified terms default to five years and India-only under Sections 19(5) and 19(6) respectively.
7. Can I fix a missing IP assignment agreement after the work has already been done? Yes, through a retroactive assignment deed signed by the original creator, but this depends on that person remaining reachable and willing to sign. It’s significantly harder and riskier than securing the assignment before or during the engagement.
8. Why do investors care about IP assignment during due diligence? Investors need confidence that the company actually owns its core assets — code, designs, inventions — free of claims from past employees, freelancers, or departed co-founders. Gaps in IP assignment agreements are a common due diligence red flag that can delay or derail a funding round.
9. Does an IP assignment agreement need to specify a royalty payment? No, monetary consideration is not legally required for a valid copyright assignment in India, though the parties are free to agree on royalty terms if that reflects their commercial arrangement.
10. What happens if an IP assignment agreement doesn’t specify a duration or territory? Under Sections 19(5) and 19(6) of the Copyright Act, the assignment is deemed to last five years and to be limited to India only, respectively, if those terms are left unspecified — defaults that can significantly undercut a founder’s actual intentions for the assignment.
Internal linking note: All internal links above point to real, live pages on parvezali.me, connecting this guide to NDA in India, the Founders Agreement template, Angel Investment Agreement, and Can AI Draft a Contract — extending the core founder legal-literacy content cluster.
Keyword density note: This draft targets roughly 1% density for the focus keyword “ip assignment agreement” and its close variants (intellectual property assignment clause, IP ownership freelancer India). Run it through Rank Math’s live content analysis after pasting into WordPress, since exact density shifts slightly with final formatting and any edits you make.