Intellectual Property Assignment vs. License in a Service Contract: Which One Protects Your Business

You hired a designer to build your brand identity, a developer to write custom software, or a copywriter to produce web content. The project wrapped up, you recieve the final files, pay the invoice, and move on — confident that everything in those files belongs to your business. Two years later, you discover that designer is using the same visual concept for a direct competitor. When you contact your attorney, the answer is unpleasant: without an explicit assignment clause in your contract, copyright law may have left full ownership with the contractor, not with you. You were paying for a service, not buying intellectual property.

This is the single most common IP mistake small businesses make in service contracts, and it plays out across every creative and technical field. The fix is not complicated, but it requires knowing the difference between an assignment and a license — and drafting each one in a way that actually holds. This article walks through both, with ready-to-use clause language, the statutory rules behind them, and the practical situations where each one is the right tool.

What "Intellectual Property" Actually Means in a Service Relationship

In the context of a service contract, intellectual property typically means the copyrightable output the contractor produces: written content, graphic designs, source code, photographs, video, audio, and architectural drawings. It can also include patentable inventions and trade secrets, though most small-business service contracts deal primarily with copyright.

Under the U.S. Copyright Act (17 U.S.C. § 102), copyright attaches to an original work the moment it is fixed in tangible form — the second a developer saves a file or a designer exports an image. No registration is required for the right to exist. This is important because it means a contractor owns the copyright in everything they create for you unless your contract says otherwise. Payment is not enough. A verbal promise is not enough. An email saying "this work is yours" is not enough. Only a written, signed instrument can transfer copyright ownership.

If you are using a general service agreement template that does not include an IP section, you are almost certainly relying on implied rights — which courts interpret very narrowly in favor of the original creator. That is a gap worth closing before the next project starts.

The Core Distinction: Assignment Transfers Ownership, License Grants Permission

An assignment is a sale of intellectual property. The contractor creates the work, then permanently transfers all rights to the client. After a valid assignment, the client owns the copyright exactly as if they had created the work themselves. They can modify it, sublicense it, register it, sell it, or destroy it. The contractor has no further claim.

A license, by contrast, is a permission slip. The contractor keeps ownership but allows the client to use the work under defined conditions. Those conditions can be broad or narrow: exclusive or non-exclusive, perpetual or time-limited, worldwide or restricted to a specific territory or industry. A license can be revoked if the contract allows it, and it expires or terminates under whatever terms the parties set.

The practical impact is significant. With an assignment, your business has full flexibility: you can bring in another developer to build on the code, sell the brand assets if you sell the company, or modify the content without asking permission. With a license only, every one of those actions may require going back to the contractor.

The Work-for-Hire Doctrine and Why It Does Not Cover Most Contractors

Many business owners have heard the phrase "work for hire" and assume it automatically means they own whatever they pay for. It does not work that way. Under 17 U.S.C. § 101, a work qualifies as "work made for hire" in exactly two situations. First, it is created by an employee within the scope of their employment — in that case, the employer is the author and owns the copyright from the start. Second, it is specifically commissioned from an independant contractor, but only if the work falls into one of nine statutory categories: a contribution to a collective work, a part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas.

Notice what is not on that list: custom software, standalone web copy, logos, photographs taken at an event, podcast recordings, marketing graphics. If your contractor produces any of these, the "work for hire" doctrine does not apply by default, no matter what your contract says. Courts have been consistent on this point. In Playboy Enterprises, Inc. v. Dumas, 53 F.3d 549 (2d Cir. 1995), the Second Circuit held that even when a contract called work "made for hire," if the category did not qualify under the statute, the label was meaningless and the contractor retained copyright. The standard is statutory, not contractual.

This is why the assignment clause exists — to accomplish by explicit transfer what the work-for-hire doctrine cannot accomplish on its own. If you are working with a freelance developer, a graphic designer, or a copywriter, you need an assignment clause, not just a work-for-hire label. You can find a solid starting point in a well-structured freelance contract template that separates the IP section from the general service terms.

When Your Business Needs an Assignment — Not a License

An assignment is the right choice in most situations where a contractor is creating something specifically for your business that you intend to own, modify, and build on over time. Here are the clearest examples:

• Brand identity work — logos, color systems, typography guides — that will define your business for years and may be part of its value if you ever sell.
• Custom software or source code built to your specifications, where you need to hire other developers to maintain and extend it.
• Marketing content — articles, white papers, videos — that will be published under your business name and modified over time.
• Product photographs or other visual assets that will appear on your website, in ads, and in print materials across multiple years.
• Website design files, including PSD, Figma, or Sketch source files, that your internal team or future vendors will need to edit.

In all of these cases, a license — even an exclusive one — creates friction. Every time you need to modify, sublicense to an agency, or include the work in a company sale or merger, you may technically need the original contractor's consent unless you own the IP outright. Assignment removes that friction entirely and gives your business clean title.

Standard Assignment Clause Language That Courts Uphold

The clause needs to accomplish four things: identify what is being assigned, confirm the assignment is complete and immediate, cover derivative works, and include a representation that the contractor actually owns what they are assigning. Here is a template that covers those elements:

Intellectual Property Assignment. Contractor hereby irrevocably assigns, transfers, and conveys to Client all right, title, and interest in and to any and all Work Product, including all copyrights, patents, trade secrets, and other intellectual property rights therein, throughout the world, for the full term of such rights and all renewals and extensions thereof. "Work Product" means all deliverables, works of authorship, code, designs, content, and other materials created by Contractor specifically for Client under this Agreement. This assignment takes effect upon creation of each item of Work Product, and no further instrument is required to effectuate it. Contractor represents and warrants that Work Product is original to Contractor, that Contractor has full authority to make this assignment, and that Work Product does not infringe any third-party intellectual property right.

Several features here deserve attention. The phrase "irrevocably assigns" is more legally precise than "agrees to assign" — courts have held in some jurisdictions that a present-tense assignment operates as an automatic transfer upon creation, while a promise to assign in the future requires a separate act. The worldwide scope and term reference matter if you ever sell the business or license your own product internationally. And the warranty provision shifts liability back to the contractor if they used someone else's material and did not disclose it. Make sure your actual contract includes this clause in a signed, written instrument — oral assignments of copyright are invalid under 17 U.S.C. § 204(a).

When a License Is Actually the Better Choice

Not every project calls for a full assignment, and insisting on one in every contract can cost you money or deals. Contractors charge more — sometimes significantly more — for assignments than for licenses, because they are permanently giving up a right they could otherwise exploit. In some situations, a well-crafted license gives your business everything it actually needs at lower cost and less negotiating friction.

Consider a consulting firm that delivers a proprietary methodology framework, a software vendor that provides a platform built on its own codebase, or a photographer who sells you a license to use specific images in your marketing. In all of these cases, the contractor's value proposition is their reusable, proprietary system — asking for a full assignment would require them to give up their business model. An exclusive license, properly scoped to your industry and use case, gives you the protection you need without demanding something the contractor will never agree to.

A license is also appropriate when you are buying access to a third-party tool that the contractor integrates or configures for you. If a developer builds your website on a commercial framework, they cannot assign you rights in code they do not own. In that case, the contract should be clear about what is licensed versus what is assigned, and the license terms for the underlying platform should be reviewed separately. Many disputes arise precisely here — a client assumes they own "the website," while the developer has only licensed the platform code and assigned only the custom layers on top.

Standard License Clause Language: Scope, Territory, Duration

A license clause must define at minimum four things: exclusivity, scope of permitted use, geographic territory, and duration. Leaving any of these open to interpretation is asking for a dispute. Here is a workable exclusive license clause for situations where assignment is not the right fit:

License Grant. Contractor grants Client an exclusive, irrevocable, royalty-free, fully paid-up license to use, reproduce, display, distribute, modify, and create derivative works of the Deliverables within the United States for commercial purposes in connection with Client's [industry/product category], for the duration of the copyright in the Deliverables. This license includes the right to sublicense to Client's affiliates, employees, and third-party service providers acting on Client's behalf. Contractor retains ownership of all intellectual property in the Deliverables but may not grant any license that conflicts with the exclusivity granted herein.

The critical words here are "exclusive" — which prevents the contractor from licensing the same work to your competitors — and "sublicense to affiliates," which allows your marketing agency, printers, and other vendors to work with the files without your having to go back to the contractor for permission every time. Without that sublicense right, you can technically violate the license every time you send a file to a third party, even for internal purposes. A solid consulting agreement template will typically have a placeholder for this kind of license language that you can adapt to your specific use case.

The "Background IP" Problem: What the Contractor Keeps

Every experienced contractor comes to a project with pre-existing tools, frameworks, code libraries, design systems, or methodologies — collectively called "background IP." A blanket assignment clause that covers "all work product" can inadvertently sweep in this background IP, which creates problems for both sides: the contractor loses rights in tools they developed independently and need for other clients, and the client ends up with IP they did not intend to acquire and cannot practically maintain.

The standard solution is a background IP carve-out: a provision in the assignment clause that explicitly excludes the contractor's pre-existing materials from the assignment while granting the client a license to use those materials as embedded in the deliverables. Here is a sample carve-out:

Background IP. Notwithstanding the foregoing assignment, Contractor retains ownership of all intellectual property developed prior to or independently of this Agreement ("Background IP"), including but not limited to [list specific tools, frameworks, or libraries]. Contractor hereby grants Client a non-exclusive, perpetual, royalty-free license to use any Background IP embedded in or necessary to operate the Deliverables solely in connection with Client's use of such Deliverables. Client shall not acquire any other rights in Background IP by virtue of this Agreement.

The brackets in "list specific tools, frameworks, or libraries" are not decoration — fill them in. "Including but not limited to" without any specifics is weaker than a concrete list. If the developer uses a particular UI component library, name it. If the designer has a proprietary grid system, describe it. Precision now prevents argument later. An independent contractor agreement template that includes a background IP section will often have a table or exhibit where both parties list these pre-existing tools before the project begins.

Portfolio Rights, Moral Rights, and the Right of Attribution

One area that generates surprising friction in creative-service relationships is the contractor's desire to include completed work in their portfolio. Most designers and developers expect this as a matter of professional practice; many clients are uncomfortable with it, particularly when the work includes confidential business materials or unreleased products.

U.S. copyright law does not provide robust "moral rights" for most commercial work — the Visual Artists Rights Act (17 U.S.C. § 106A) protects attribution and integrity rights only for fine art, not for commercial graphic design or software. But portfolio use is a practical issue regardless of legal rights, and your contract should address it explicitly. A standard portfolio clause might read: "Contractor may display Deliverables in portfolio, in promotional materials, and on social media for the purpose of showcasing professional work, provided no confidential business information is disclosed and Client's prior written approval is obtained for any case study or detailed description of the project."

From the contractor's side, the draft contract often also includes a credit or attribution line — especially common in web development. If you are removing the contractor's credit from a website footer, confirm this is addressed in the agreement. Courts have occasionally treated removal of credit as a breach of an implied contractual term, even absent a moral rights statute.

Multiple-Client Trap: When Your "Exclusive" Work Is Reused Elsewhere

A license that does not say "exclusive" is non-exclusive by default — meaning the contractor is free to license the same work to other clients, including your competitors. This is the hidden risk in any contract that says "Client may use the deliverables" without specifying that no one else can. It also arises in assignment situations where the contractor assigned the final deliverable but kept ownership in the preliminary drafts, concept sketches, or underlying data structures.

The multiple-client problem is particularly acute in the software industry, where a developer builds a custom feature for your application, then builds a nearly identical feature for a competitor six months later — using the same logic, just reskinned. If your contract assigned only the final code and not the underlying architecture, the contractor may be legally free to do exactly that. The same issue arises with marketing agencies that develop a campaign "concept" for one client and reuse that concept with a different brand for another.

The fix is a combination of: (1) a broad assignment or exclusive license, (2) a non-compete or non-solicitation restriction specific to your industry for a defined period, and (3) a clear definition of what "deliverables" includes — final files, source files, preparatory materials, and preliminary concepts. Review your web development agreement template or any creative services contract to confirm the deliverables definition is broad enough to capture the underlying creative architecture, not just the polished output.

IP Provisions in Contractor vs. Employee Agreements: The Critical Differences

The rules change significantly when you move from an independent contractor relationship to an employment relationship. Employees who create copyrightable works within the scope of their employment produce "works made for hire" automatically under 17 U.S.C. § 101(1) — the employer owns the copyright from the moment of creation, no assignment clause required. Many states go further with "invention assignment" statutes that require employers to include written clauses assigning employee inventions to the company.

However, employment agreements should still include explicit IP assignment clauses for two reasons. First, not every employee creates works "within the scope of employment" — if an engineer writes code on their personal laptop at 11 p.m. for what they believe is a side project, ownership can be genuinely ambiguous. Second, several states — including California (Labor Code § 2870), Delaware, Illinois, Minnesota, North Carolina, and Washington — explicitly limit what an employer can claim in an employment IP agreement. These states allow employees to retain ownership of inventions developed entirely on their own time, without company resources, that do not relate to the company's business or anticipated business. A clause that purports to assign everything the employee ever creates may be unenforceable as to those excluded inventions.

If you are a small business onboarding full-time staff, confirm your employment contract template includes a state-compliant IP assignment provision — not just a blanket "all inventions belong to employer" sentence. The difference matters in jurisdictions like California where overbroad IP clauses carry their own legal risk.

Five Mistakes Small Businesses Make When Drafting IP Clauses

After reviewing hundreds of service contracts, the same errors appear with depressing regularity. Here is what to look for in your existing agreements — and avoid in the ones you create:

• Relying on the "work for hire" label alone without confirming the work falls into one of the nine statutory categories. If it does not, the label accomplishes nothing and may actually mislead both parties about who owns what.
• Using a generic NDA or service agreement that has no IP section at all. Online generators that produce minimalist one-page agreements often omit IP provisions entirely. You can visit the template catalog to find agreements that include comprehensive IP sections as a standard feature.
• Failing to define "deliverables" broadly enough to include source files, preparatory works, and underlying data. A contractor who delivers only "the final logo file" and not the source layers has technically complied with a vague deliverables clause while leaving your business unable to make modifications.
• Omitting a warranty that the work is original and does not infringe third-party rights. If the contractor used stock assets they did not license, or borrowed open-source code under a viral license, you may inherit the infringement problem without knowing it.
• Not addressing what happens to IP upon contract termination — especially in retainer or ongoing service relationships. If you stop paying and the contractor stops working, does the license survive? Does a partial assignment hold? Silence here creates real legal uncertainty in the most common type of dispute: the relationship that ends badly.

A well-structured non-disclosure agreement won't protect your IP in a service relationship — it protects confidential information you share with the contractor. These are related but distinct protections. Both are necessary; neither substitutes for the other.

What Courts Have Said About Ambiguous IP Clauses

Courts resolve ambiguous IP clauses consistently in favor of the creator, not the client. This is the "licensor's rule" — when a transfer of rights is unclear, courts presume the copyright owner intended to retain whatever rights were not explicitly granted. The principle appears in Cohen v. Paramount Pictures Corp., 845 F.2d 851 (9th Cir. 1988), where the court held that a license for "television" use did not include video cassette rights because the technology did not exist when the license was granted and was not explicitly covered.

More recently, in Design Basics, LLC v. Lexington Homes, Inc., 858 F.3d 1093 (7th Cir. 2017), the Seventh Circuit reaffirmed that copyright claims require a careful assessment of what was actually transferred and what was retained — vague "work product belongs to client" language in a construction contract was scrutinized for whether it amounted to a valid assignment under § 204(a) of the Copyright Act. The takeaway for contracts: specificity is always your friend. Courts will not generously interpret a broadly worded clause in the client's favor; they will narrowly construe it to protect whatever ownership interest the creator might have retained.

From a drafting standpoint, this means every assignment or license clause should be explicit about what is included, what is excluded, what rights are granted, and for what purposes. Do not leave the interpretation to a judge. The online standard for a well-drafted clause is not cleverness — it is precision. Any attorney reviewing the clause should be able to read it and answer "who owns this?" without guessing.

Final Checklist: IP Provisions That Protect Your Investment

Before signing any service contract — or auditing your existing ones — run through this list. If any item is unchecked, the contract has a gap worth addressing:

• Written and signed — the IP clause is in a signed written agreement, not a verbal understanding or an email chain.
• Assignment or license clearly stated — the clause uses one of these words explicitly, not vague language like "work product belongs to Client."
• Deliverables broadly defined — the definition covers final files, source files, preparatory materials, and underlying works.
• Background IP carve-out present — the contractor's pre-existing tools are excluded from assignment but licensed for use within the deliverables.
• Exclusivity addressed — if you are not getting an assignment, the license states whether it is exclusive and in what scope.
• Sublicense rights confirmed — you can share the work with affiliates, vendors, and service providers without needing separate contractor consent.
• Warranty of originality included — the contractor represents the work does not infringe third-party IP.
• Termination effects addressed — the contract states what happens to the license or assignment if the relationship ends early.
• Portfolio use clause negotiated — you and the contractor have agreed in writing whether and how the work may appear in their portfolio.
• State-specific compliance checked — if this is an employment agreement, the IP clause complies with any state limitations on invention assignment.

IP ownership disputes are expensive to litigate, difficult to prove after the fact, and nearly always avoidable with clear contract language drafted before the work begins. Whether you are commissioning a startup website or a full-scale software platform, the time to resolve ownership is at the contract stage — not after launch, and certainly not after the relationship ends. The goal of every well-drafted IP clause is simple: when you create something through your service partners, your business should own or control it in a way that matches your actual business needs, and both parties should understand exactly what those rights are from day one.

Article reviewed by: Jordan S. (Attorney)