Intellectual Property in Contracts: A Freelancer's Guide to Protecting Your Work

Intellectual property law grants creators automatic rights over their original work the moment it is fixed in a tangible medium. Understanding what you already own — before any contract modifies those rights — is the starting point for every IP negotiation.

The four main categories of IP:

Copyright covers original works of authorship: writing, software code, graphic design, photography, music, video, architectural drawings, and any other creative work expressed in a tangible form. Copyright arises automatically at the moment of creation and registration with the U.S. Copyright Office, while not required for ownership, is necessary to sue for infringement in federal court and enables recovery of statutory damages and attorney's fees. For freelancers, copyright is the most relevant form of IP — it protects the deliverables you create.

Trademark protects brand identifiers: names, logos, taglines, and other marks that distinguish goods or services in commerce. Trademark rights arise from actual use in commerce, not from registration (though federal registration confers significant advantages). As a freelancer, you are unlikely to own trademarks in client work you produce, but you may hold trademark rights in your own business name, logo, or creative brand.

Trade secret protects commercially valuable information that is kept confidential. Unlike copyright and patent, trade secret protection is indefinite as long as the information remains secret and reasonable steps are taken to maintain its secrecy. Freelancers may possess trade secrets in proprietary processes, methodologies, client lists, or pricing data. NDAs are the primary contractual mechanism for protecting trade secrets.

Patent protects inventions — novel, non-obvious, and useful processes, machines, or compositions of matter. Patent protection requires active registration (there is no automatic patent right), involves significant cost and complexity, and is most relevant to software functionality, hardware design, and technical processes. Most freelancers do not produce patentable work, but software developers and engineers should be aware that novel technical methods may be patentable and should address patent rights explicitly in any agreement.

The clause quoted above attempts a blanket transfer of all IP rights from the moment of creation. Whether this clause is enforceable, how broadly it reaches, and whether it can be successfully negotiated are the questions this guide addresses in detail.

The work-for-hire doctrine is the mechanism most commonly used by clients to claim ownership of work created by freelancers. Understanding exactly how it works — and where it does not apply — is essential to protecting your rights.

What work-for-hire actually means. Under the U.S. Copyright Act (17 U.S.C. § 101), a work is "made for hire" in two circumstances: (1) a work created by an employee within the scope of employment — the employer automatically owns this work; and (2) a work specially ordered or commissioned that falls into one of nine specific statutory categories, where there is a written agreement designating it as a work made for hire.

The nine statutory categories are: contributions to collective works, parts of motion pictures or other audiovisual works, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, and atlases. Notice what is not on this list: standalone software code, standalone graphic design, standalone written articles, standalone photography, standalone illustrations. These categories are not eligible for work-for-hire treatment when commissioned from an independent contractor.

The legal reality most clients ignore. When a client hires a freelancer (not an employee) and the work does not fit one of the nine statutory categories, the work-for-hire designation has no legal effect even if the contract says it does. A clause declaring a custom logo to be a "work made for hire" is legally inoperative for a freelance engagement — the designer retains copyright as a matter of law.

Why clients still use this language. Clients use work-for-hire language either because their legal templates were drafted without attention to this distinction, or because the clause is combined with an explicit IP assignment (discussed in the next section) as a belt-and-suspenders approach. A well-drafted client contract will typically include both a work-for-hire designation and a backup assignment of any rights that do not qualify for work-for-hire treatment.

Employment vs. contractor status matters enormously. If you are reclassified from independent contractor to employee — which tax authorities, courts, or state regulators may do based on the actual nature of your working relationship — everything you created within the scope of that employment may be owned by the client under the employment work-for-hire rule, regardless of what your contract says. This is one of many reasons accurate classification matters.

The difference between an assignment and a license determines whether you permanently give away your work or retain ownership while granting specific usage rights. This single distinction is worth more careful attention than any other clause in a creative services contract.

Assignment: a permanent transfer. An IP assignment transfers ownership of the intellectual property from you to the client. After assignment, the client is the owner — they can use, license, modify, sell, or sue to protect the work. You retain no rights unless the assignment agreement explicitly grants you a license back. The clause above is an all-rights-in-perpetuity assignment — the broadest possible form. Once signed, you have no legal interest in the work.

License: retained ownership with granted rights. A license allows the client to use your work under defined terms while you retain ownership. Licenses can be exclusive or non-exclusive, limited in scope (specific uses, territories, or media), limited in duration (one year, five years, perpetual), and revocable or irrevocable. A well-structured license gives the client everything they actually need while preserving your ownership.

What clients actually need. Most clients do not need full ownership of creative work — they need the right to use it in specific ways for specific purposes. A company commissioning a logo needs the right to use that logo in their business indefinitely and exclusively. They do not necessarily need to own the underlying artwork outright, the ability to license it to others, or the right to create derivative works. Understanding what usage rights the client actually needs is the foundation of IP negotiation.

When assignment may be appropriate. If the client is paying for work that will be deeply integrated into their product (e.g., custom software that will become part of their platform, writing that will be published as their own content), assignment is often the commercial norm. The question is whether the compensation reflects the value of the rights being transferred. A full assignment should command a higher fee than a limited license.

Reversion rights. Some assignment agreements include reversion clauses: if the work is never published or commercially exploited within a defined period (e.g., three years), ownership reverts to the creator. These provisions are common in book publishing contracts and can be negotiated into other creative agreements.

Recordation. Copyright assignments should be recorded with the U.S. Copyright Office to put third parties on notice and to establish priority in the event of conflicting assignments.

Pre-existing intellectual property — sometimes called "background IP" — is any work, tool, methodology, code library, or creative asset you owned or created before the engagement began. A blanket IP assignment without a pre-existing IP carve-out can inadvertently transfer ownership of your most valuable professional assets to a single client.

What constitutes pre-existing IP. For a software developer, pre-existing IP includes code libraries, frameworks, utility functions, and development tools built over years of practice. For a graphic designer, it includes template systems, icon libraries, typeface selections, and visual methodologies. For a writer, it includes structural frameworks, research databases, and style guides. For a consultant, it includes proprietary methodologies, analytical frameworks, and training materials developed independently. These assets are the foundation of your professional practice — and they belong to you.

The danger of the clause above. The clause includes "any pre-existing materials incorporated into the Deliverables." This is the most dangerous IP assignment language a freelancer can encounter. If you use your standard code framework, design template system, or consulting methodology in any deliverable under the contract, you have just assigned ownership of that foundational work to the client — permanently. Every future client who uses the same tools is now using someone else's intellectual property.

The "incorporated" problem. Many freelancers do not realize that pre-existing materials become part of the deliverable simply through use. A developer who includes a utility function they wrote years ago in a client project has "incorporated" that function into a deliverable. Without a carve-out, the assignment reaches backward to capture pre-existing work.

How a proper carve-out works. A pre-existing IP carve-out explicitly excludes specified materials from the scope of the assignment. These materials are typically described in an exhibit or schedule attached to the contract. The client receives a license (usually non-exclusive and limited to the purpose of the engagement) to use the pre-existing IP as incorporated into the deliverables, but ownership of the underlying assets remains with you.

Practical implementation. Before signing any contract with an IP assignment clause, prepare a written inventory of your pre-existing IP that is likely to be used in the engagement. This inventory becomes Exhibit A to the contract — the defined scope of what is carved out of the assignment.

Moral rights are a category of intellectual property rights that protect the personal and reputational connection between a creator and their work. They exist independently of economic rights (like copyright ownership) and generally cannot be transferred — only waived. Moral rights waivers in contracts are more significant than most freelancers realize.

What moral rights include. The most important moral rights recognized in international law are: (1) the right of attribution — the right to be identified as the author of your work; (2) the right of integrity — the right to object to modification, mutilation, or distortion of your work that would be prejudicial to your honor or reputation; and (3) the right of disclosure — the right to decide when and how to first publish your work.

U.S. moral rights: limited scope. The United States has the narrowest moral rights protections in the developed world. Under the Visual Artists Rights Act (VARA), moral rights apply only to works of visual art — paintings, drawings, prints, sculptures, and photographs produced for exhibition in a single copy or limited edition of 200 or fewer copies. VARA explicitly excludes works made for hire, commercial art, advertising, and digital works from moral rights protection. Most freelance work does not benefit from VARA protection.

International moral rights: much stronger. Most of Europe, Canada, and many other countries recognize moral rights in a much broader range of works. Under the Berne Convention (which the U.S. is a signatory to), member countries are required to recognize at minimum the rights of attribution and integrity. European creators cannot fully waive their moral rights — contracts purporting to do so may be unenforceable. If you are an international freelancer working with U.S. clients, or a U.S. freelancer working with international clients, the applicable moral rights regime depends on which country's law governs the contract.

Practical consequences of moral rights waivers. A client who obtains a moral rights waiver can: modify your work without your consent (including changes you would find objectionable or that misrepresent your skills), publish your work without attribution (as their own or anonymously), and create derivative works that bear no resemblance to your original while still being associated with you in the client's internal records. For visual artists whose reputation depends on the integrity of their portfolio, this is a significant concern.

Attribution in commercial contexts. Even where moral rights are legally weak (as in the U.S.), contract provisions about attribution can be negotiated. Many freelancers negotiate for the right to have their name in credits, to be acknowledged in publications, or to reference the work in portfolio materials — these are separate from statutory moral rights but serve similar purposes.

Joint ownership of intellectual property sounds equitable but is almost always a poor outcome for both parties — particularly under U.S. copyright law, where the default rules for co-ownership create severe practical problems.

U.S. copyright law and joint works. Under 17 U.S.C. § 101, a "joint work" is a work prepared by two or more authors with the intention that their contributions be merged into a unified whole. Each co-author of a joint work owns an undivided interest in the entire work — meaning each can use, reproduce, and license the work without the consent of the other co-author. The licensing co-author must, however, account to and share profits with the other co-owner. There is no right of veto.

Why joint ownership creates problems. Suppose you and a client are joint owners of a software module you built together. The client can license that software to your direct competitors without your consent — and owes you only a proportional share of any licensing revenue. They can also incorporate your jointly owned code into larger proprietary products and license those products, with only accounting obligations to you. You, as co-owner, have symmetric rights — but as a freelancer, you are typically not in a position to exploit those rights commercially.

Joint ownership and derivative works. Each co-owner can create derivative works based on the jointly owned work without the consent of the other. This means a client can substantially modify your jointly owned design or code and own that modification outright — potentially eliminating your contribution and your leverage.

Joint patents: even harder. In patent law, each co-owner of a U.S. patent can exploit the patent (make, use, sell, license) without the consent of the other co-owner and without accounting for profits. If a client jointly owns a patent covering your invention, they can license it to anyone, anywhere, for any price, without your involvement or compensation.

When joint ownership is proposed. Joint ownership clauses typically appear when: (1) both parties have contributed to the development of a new invention or creative work; (2) the parties cannot agree on who should own the work outright; or (3) the client wants ongoing rights but the freelancer is unwilling to assign. In most cases, a cross-license arrangement — where each party retains their contribution and grants the other a license — is a more practical alternative than true joint ownership.

IP clauses vary significantly across contract types — and the stakes are highest in employment agreements, where the reach of IP assignment clauses can extend far beyond your work for the employer.

Freelance contracts. In a typical freelance services agreement, IP clauses address ownership of deliverables. As discussed, the default is that the freelancer owns copyright until assigned by written agreement. Freelance contracts often include work-for-hire language, an IP assignment clause, and (in well-drafted agreements) a pre-existing IP schedule. The negotiating position of a freelancer depends on their leverage, the client's sophistication, and the type of work.

Employment agreements — the broadest reach. The clause above is from a typical employment IP assignment provision. Note the scope: all inventions conceived during the term of employment, whether or not during working hours, whether or not using Company resources. This means an employee who builds a mobile app on personal time, on their personal computer, with no connection to the employer's business, may have inadvertently assigned ownership of that app to their employer if the IP assignment clause is this broad.

State law carve-outs. California, Delaware, Illinois, Minnesota, North Carolina, Washington, and several other states have statutes limiting the reach of employment IP assignments. California Labor Code § 2870, for example, exempts inventions that (1) are developed entirely on the employee's own time, (2) do not use employer equipment or resources, (3) do not relate to the employer's business or anticipated R&D, and (4) do not result from work performed for the employer. Employers must typically provide written notice of these statutory limitations. If you are in a protected state and sign an employment agreement, verify whether the agreement includes the required statutory notice.

Consulting agreements. Consulting contracts frequently include IP assignment clauses that mirror employment agreements. Many consulting clients insist on full assignment of all work product. In consulting, where you may be simultaneously engaged with multiple clients, pre-existing IP protection and clear boundaries on what is "within scope" of the engagement are especially important.

NDAs and IP. Non-disclosure agreements protect confidential information — which may include IP — but NDAs do not transfer IP ownership. An NDA protects the client's confidential information you receive, and may protect your own confidential methodologies. Some NDAs include "residuals" clauses — allowing a party to use information retained in unaided memory even if it is technically confidential — which can create tension with the disclosing party's IP rights.

The claim that IP clauses are "non-negotiable" is itself a negotiating tactic. Understanding what is actually non-negotiable — and what clients routinely accept when asked — puts you in a stronger position.

What clients actually care about. Most clients who insist on broad IP assignment clauses are motivated by a core concern: they do not want the freelancer to reuse the work in ways that compromise the client's competitive position. A logo designed for Company A should not appear on Company B's products. Code built for Client X's platform should not be resold to Client X's competitors. Understanding the underlying concern often reveals compromise positions.

The sliding scale of IP negotiation. IP negotiations generally follow a spectrum: - Full assignment with no carve-outs — worst case for the freelancer - Assignment with pre-existing IP carve-out — protects your tools and methodologies - Assignment with pre-existing IP carve-out and portfolio license — adds the right to display in your portfolio - Exclusive license in lieu of assignment — you retain ownership, client gets exclusive usage rights - Non-exclusive license — client can use the work; so can you

Rate as leverage. IP rights have value. A full, perpetual, worldwide assignment of all rights is worth more than a limited license. If a client insists on full assignment, the appropriate response is to price the engagement accordingly — not to give away rights for free. Many freelancers use tiered pricing explicitly: "I can deliver this under an exclusive license for X, or under a full assignment for 1.5X."

Field-of-use limitations. Even when a client insists on assignment, you can negotiate field-of-use limitations in the pre-existing IP carve-out license. The client gets to use your tools in their business, but you retain the right to use the same tools with other clients in different industries or geographies.

Term and territory. Assignments can be limited by term (e.g., five-year exclusive period, then reverts to you) and by territory (U.S. rights only, rather than worldwide). These limitations are more common in publishing and entertainment than in general commercial freelancing, but they can be negotiated.

Red lines. Some IP provisions should be dealbreakers: (1) any assignment that reaches pre-existing IP without a carve-out; (2) any employment IP clause that covers personal projects developed without company resources and unrelated to the company's business; (3) any provision that allows the client to display your work in misleading ways or attribute it to a different creator.

Portfolio rights — the right to show your work to prospective clients — are frequently overlooked in IP negotiations, yet they are essential to your ability to attract new business. The clause above, combined with an IP assignment, can leave you unable to reference your best work.

Why clients restrict portfolio display. Clients restrict portfolio display for several legitimate reasons: competitive sensitivity (they do not want competitors to know the direction of their branding or product design), pre-launch confidentiality (the product has not yet launched and cannot be publicly shown), ongoing litigation (the work may become relevant to a dispute), or simply a desire for control over how their brand is presented.

Why portfolio rights matter for freelancers. Your portfolio is your primary sales tool. Work you cannot show does not build your reputation or attract new clients. Over time, if a significant portion of your best work is covered by broad confidentiality and no-display clauses, the public face of your portfolio understates your actual capabilities.

What portfolio rights should include. A standard portfolio rights clause grants you: (1) the right to display the Deliverables in your portfolio and on your professional website; (2) the right to identify the client as the company for whom the work was created (though clients sometimes prefer anonymity); (3) the right to describe the nature of the engagement and your role; and (4) the right to include the work in award submissions, case studies, and speaking materials.

Confidentiality carve-outs for portfolios. If a client's primary concern is confidentiality of unreleased work, a reasonable compromise is a time-limited embargo: no public display until the product launches or for a period of 12–18 months, after which portfolio display is permitted. This addresses the client's confidentiality need without permanently suppressing your portfolio rights.

Password-protected portfolios. Some clients will consent to portfolio display in a password-protected setting (accessible only to vetted prospective clients) but not public display. This is a workable middle ground for sensitive engagements.

Case studies and process documentation. Beyond finished work, case studies documenting your creative process are increasingly valuable in competitive pitches. Negotiate the right to create anonymized or client-approved case studies documenting the scope of your work and the problems you solved.

Open source software is ubiquitous in modern software development — but open source licenses are not all equal, and some create obligations that attach to any code they are combined with. For freelance developers, this warranty clause is a meaningful legal risk that requires careful attention.

The spectrum of open source licenses. Open source licenses range from highly permissive to strongly "copyleft":

Permissive licenses (MIT, BSD, Apache 2.0) allow incorporation into proprietary software with minimal obligations — typically attribution (keeping the copyright notice) and, for Apache 2.0, patent grant considerations. Most corporate clients have no objection to permissive open source components.

Weak copyleft licenses (LGPL, Mozilla Public License) require that modifications to the licensed library itself be released under the same license but do not require proprietary code that uses the library to be open-sourced. The scope of what constitutes a "modification" versus mere "use" matters.

Strong copyleft licenses (GPL v2, GPL v3, AGPL) are the ones most relevant to the warranty clause above. GPL-licensed code, when incorporated into a larger program and distributed, requires the entire combined work to be distributed under the GPL — which means making the source code available. If a developer incorporates GPL code into a client's proprietary software and the client distributes that software, the client may be required to release their proprietary source code. AGPL goes further: it applies the GPL obligations to software used over a network, not just distributed software.

What this means for freelancers. If you incorporate a GPL or AGPL component into a client deliverable — even if you do so unknowingly through a dependency chain — you may be in breach of the warranty quoted above. Dependency chains in modern software (npm, pip, Maven) can introduce transitive dependencies with restrictive licenses without obvious disclosure.

Software Bill of Materials (SBOM). A Software Bill of Materials is a structured inventory of all components in a software product, including their licenses. Generating an SBOM before delivering software is increasingly a standard practice (it is required for federal government software contracts under Executive Order 14028) and is the most practical way to identify open source license obligations in complex dependency chains.

Dual-licensed projects. Some open source projects offer dual licensing: a copyleft version for open source use and a commercial license for proprietary use. If a key component you plan to use is GPL-licensed, check whether a commercial license is available and budget for it.

The intersection of artificial intelligence and intellectual property is one of the most rapidly evolving and legally uncertain areas in all of contract law. Freelancers who use AI tools in their work face several distinct IP risks that most contracts have not yet caught up with.

Copyright in AI-generated works. The U.S. Copyright Office has taken the position that copyright protection requires human authorship and that purely AI-generated content — content created without meaningful human creative control — is not copyrightable. In February 2023, the Copyright Office refused to register the AI-generated images in a graphic novel, while registering the human-authored text. In August 2023, a federal court confirmed this position. This creates a practical problem: if you deliver AI-generated content to a client under an IP assignment, you may be assigning something that neither you nor the client can actually own under U.S. copyright law.

The warranty problem. The clause above requires the freelancer to warrant that all deliverables are "original works created solely by Contractor." If you use an AI tool — even as a minor part of your workflow — and the output is incorporated into the deliverable, you may be breaching this warranty. The client could potentially recover damages for warranty breach if the lack of copyright protection causes them harm (e.g., a competitor copies the AI-generated portion without liability).

Training data and infringement risk. AI image generators, code generators, and text generators are trained on vast datasets that may include copyrighted material. There is ongoing litigation (including class actions against major AI companies) alleging that AI-generated outputs infringe the copyrights of the training data creators. While courts have not yet definitively resolved this question, there is a non-trivial risk that AI-generated content may be found to infringe third-party copyrights — which would breach IP indemnification and warranty provisions in client contracts.

Practical implications for freelancers. Many clients now specifically ask whether AI tools were used in creating deliverables. The range of client positions varies: some prohibit AI entirely, some require disclosure, some are indifferent. Understand your client's position before signing a warranty of non-AI origin.

Emerging contract language. The contractual landscape around AI is evolving rapidly. Some agreements now include: AI disclosure requirements (the freelancer must identify which AI tools were used and how); AI usage policies (prohibiting AI use in specified deliverable types); AI indemnification carve-outs (excluding AI-related IP claims from the standard indemnification regime); and AI work acknowledgments (both parties acknowledge that AI-assisted work has different IP characteristics than purely human-authored work).

A governing law clause determines which jurisdiction's laws apply to interpret and enforce the contract — including the IP provisions. This has concrete consequences for IP protection that most freelancers do not consider when selecting governing law.

State-level IP protections: the employment context. As discussed in Section 07, several U.S. states limit the reach of employment IP assignments. California's Labor Code § 2870 is the most protective — it voids employment IP assignments that reach personal projects unrelated to the employer's business. Delaware, where many companies are incorporated, provides weaker protections. If you are negotiating an employment agreement, California law is more favorable than Delaware law for employees.

Trade secret law variation. The federal Defend Trade Secrets Act (DTSA) provides a uniform federal trade secret regime, but state trade secret laws also apply and may differ. California's trade secret law does not require physical misappropriation — acquiring trade secrets through improper means (including wrongful access to confidential systems) is actionable. Understanding the state law that governs your trade secret protections matters.

International IP: the Berne Convention and moral rights. The Berne Convention requires member countries to recognize the copyright of creators from other member countries. However, the scope of protection varies: moral rights (discussed in Section 05) are much stronger in France, Germany, and most EU countries than in the U.S. A freelancer based in France who signs a U.S.-governed contract may be giving up protections under French law that are not available under U.S. law.

EU perspective: strong worker protections. The EU has significantly expanded IP protections for workers and contractors in recent years. The EU Directive on Copyright in the Digital Single Market, for example, provides creators with transparency rights regarding how their work is used and revenue-sharing rights for significant commercial exploitation. U.S.-based clients seeking to avoid these protections through governing law clauses may find that EU-based freelancers can assert rights regardless of contract choice of law.

Canadian moral rights. Canada's Copyright Act provides moral rights that apply broadly and cannot be assigned (only waived). Canadian courts have been protective of moral rights, including the right of integrity. If you are a Canadian freelancer or working with Canadian clients, moral rights waivers in contracts should be evaluated carefully.

Forum selection. In addition to governing law, contracts typically specify a forum (court or arbitration venue) for disputes. For international freelancers, a forum selection clause requiring disputes to be resolved in a U.S. federal court in Delaware is practically problematic — even if you win, enforcement in a foreign jurisdiction requires additional proceedings.

Certain IP clause patterns are so one-sided or so practically dangerous that they warrant heightened scrutiny — or outright rejection. Recognizing these red flags quickly can save you from inadvertently surrendering rights you will spend years regretting.

Red flag #1: "Ideas and concepts." The clause above assigns not just deliverables but "ideas, concepts, developments, discoveries, inventions." Ideas alone are not copyrightable under U.S. law — only the expression of ideas is protected. A clause assigning ownership of your ideas purports to give the client property rights over unprotected thought. More practically, it creates ambiguity about whether work you develop for other clients — which may spring from similar ideas — belongs to this client.

Red flag #2: "Conceived during the term." Limiting the assignment to work conceived during the engagement, rather than work arising from or created for the engagement, casts a much wider net. An idea you have while showering — completely disconnected from the client's work — could arguably be "conceived during the term." This language is particularly dangerous in long engagements.

Red flag #3: No geographic, temporal, or purpose limitation. An assignment "throughout the universe, in perpetuity, in all media now known or hereafter invented" for a limited-scope engagement is disproportionate. While some limitation categories (e.g., throughout the universe) are legally standard in entertainment contexts, a freelancer creating a company's internal training materials does not need to sign away "universe"-wide rights.

Red flag #4: Unilateral modification rights. Some IP clauses grant the client the right to modify, adapt, or create derivative works from your deliverables without any limitation. Without a moral rights clause or minimum standards clause, a client can alter your work in ways that are inconsistent with your professional reputation or artistic integrity.

Red flag #5: Work product "including all information" or "all things created." Catch-all language that extends beyond the defined scope of deliverables is a significant risk. If you take notes, write internal emails, or create draft documents that are not part of the contracted deliverable, do those belong to the client under "all things created"?

Red flag #6: Retroactive reach. Some agreements purport to assign IP rights in work created before the agreement was signed. Retroactive IP assignment requires separate written documentation of the pre-existing work and additional consideration — a signature on a new contract alone is insufficient under copyright law.

Red flag #7: No carve-out for independently developed work. The absence of any carve-out for work developed independently, without client resources, and outside the scope of the engagement is a structural defect that should always be corrected before signing.

IP misappropriation — when someone uses your work without authorization, or when a client exploits rights that were not properly transferred — is distressingly common. Knowing your options before it happens is far better than trying to learn them after.

Identifying misappropriation. Common scenarios include: a client using your work beyond the scope of the license (e.g., using a logo designed for one product on an entirely different product line); a client sharing your deliverables with a third party in breach of your contract; a former client continuing to use your work after the contract term ends; a client assigning rights to another company without your consent when the contract prohibits assignment; and third parties plagiarizing your work without any connection to your client relationship.

Copyright registration: the threshold requirement. In the United States, you cannot file a copyright infringement lawsuit without a registration. More importantly, you can only recover statutory damages (up to $150,000 per willful infringement) and attorney's fees if your work was registered before the infringement occurred (or within three months of publication). If you discover infringement and your work is not yet registered, register immediately — it will not enable statutory damages for past infringement, but it enables the lawsuit and statutory damages for ongoing infringement.

Cease and desist letter. The first step in most IP disputes is a cease and desist (C&D) letter from an attorney. A C&D puts the infringer on notice, documents the dispute, and often resolves straightforward cases without litigation. For clear-cut infringement (e.g., a former client continuing to use your design after the license expired), a C&D may be sufficient.

DMCA takedown. For online infringement (websites, social media, e-commerce platforms), the Digital Millennium Copyright Act provides a notice-and-takedown mechanism. You can submit a DMCA takedown notice to the platform hosting the infringing content without initiating a lawsuit. Platforms are required to remove the content upon receiving a valid notice. Note that DMCA takedowns are not available for patent or trade secret claims — only copyright.

The clause above: loss of enforcement rights. The clause above is particularly concerning — it assigns enforcement rights entirely to the client. If the client is unwilling to pursue an infringer (perhaps because the infringer is a business partner), you have no contractual right to protect your own work. If you must accept an IP assignment, insist on a provision allowing you to enforce rights if the assignee fails to act within a defined period.

Trade secret misappropriation. If a client discloses your confidential methodologies or processes to a competitor, the Defend Trade Secrets Act (DTSA) provides a federal cause of action and the possibility of ex parte seizure orders in egregious cases. Time is critical — delays in pursuing trade secret claims can be used to argue the information was no longer reasonably protected.