Intellectual Property MOU Template

Purpose & Relationship Overview

Opens by naming both parties and describing the collaboration, partnership, pilot, or evaluation the MOU relates to: what the two sides are discussing, why intellectual property is likely to be created or shared, and the general timeline. This section states plainly that the MOU is meant to establish a shared understanding ahead of, or instead of, a fully negotiated IP agreement, and that it is not intended to replace legal counsel where one is later needed. It also identifies the anticipated next step, whether that's a formal licensing agreement, an assignment agreement, a joint development agreement, or simply a decision not to proceed, so both sides know what this document is a placeholder for. Include the date discussions began and, if relevant, reference any prior correspondence, proposal, or pitch deck that led to this MOU being drafted, so the paper trail is unambiguous if either party later needs to reconstruct the timeline of who knew what and when.

Intellectual Property Covered

Defines exactly what counts as intellectual property under this MOU: copyrights (written content, code, designs, media), trademarks (names, logos, brand marks), patents and patentable inventions, trade secrets and confidential know-how, and any data sets, methodologies, or proprietary processes either party may reference or create. Being specific here matters more than it seems: a generic 'all intellectual property' clause leaves room for disputes later about whether a shared spreadsheet template or an internal process document was ever meant to be covered. This section should list concrete examples relevant to the collaboration rather than relying on a single blanket definition. Where the collaboration spans multiple jurisdictions, note that IP definitions and default ownership rules can vary by country, and that this MOU does not override any statutory registration requirements for trademarks or patents in the relevant territories.

Background IP vs. Foreground (Newly Created) IP

This is the distinction most generic MOU and NDA templates skip entirely, and it's the single biggest source of IP disputes between agencies, freelancers, and their clients or partners. Background IP is anything either party already owned before this collaboration started: a designer's existing font library, an agency's proprietary campaign framework, a SaaS company's core codebase, or a startup founder's pre-existing product concept. Foreground IP (sometimes called 'new IP' or 'arising IP') is anything created during the collaboration itself: a co-developed feature, a jointly written proposal, a new logo concept, or code built specifically for the project. This section should list each party's background IP explicitly before work starts, state that background IP remains owned by whoever brought it in, and set a default rule for foreground IP (sole ownership by the creating party, joint ownership, or ownership assigned to one party on payment) so there's no ambiguity about which category a given deliverable falls into once work is underway. A practical way to apply this: keep a running two-column list as the collaboration progresses, background IP on one side and foreground IP on the other, and update it whenever a new deliverable is discussed. Agencies in particular should list their existing frameworks, proprietary research, and past-project templates as background IP before a single pitch deck goes out, since 'we already had that' is a much weaker argument after a client has seen it inside a shared workspace than before. The same logic applies in reverse for clients: if a client shares proprietary brand data, customer research, or existing creative assets to brief the agency, those should be listed as the client's background IP so the agency's later work product isn't mistaken for something the agency is entitled to reuse for other clients.

Ownership & Assignment of New IP

Once foreground IP is defined, this section states who will own it and under what conditions ownership transfers. Common structures include: the hiring party owns all new IP upon full payment (typical for client-agency and client-freelancer work), each party owns the IP it individually authored while jointly-authored elements are co-owned, or ownership is assigned entirely to one party with the other receiving a license back. It should also flag the difference between employee-created IP (often automatically owned by the employer under work-for-hire principles) and contractor-created IP (which usually requires an explicit written assignment to transfer, since default legal rules in many jurisdictions favor the contractor absent that clause). Tie the transfer moment to something concrete and verifiable, such as full and final payment clearing, rather than a vague reference to 'completion of the project,' since disputes over ownership almost always surface exactly when a payment is late or a project ends ambiguously. For joint ownership, spell out whether either party can license the jointly owned IP to third parties without the other's consent, since most jurisdictions default to allowing this unless the agreement says otherwise, which surprises a lot of first-time joint venture partners. It's also worth noting who is responsible for filing and maintaining any resulting patent or trademark registrations, and how the cost of that filing is split, since ownership on paper means little if nobody actually completes the registration.

Licensing & Permitted Use

Covers any license being granted rather than IP being fully transferred, most often when one party needs to use the other's background IP to complete the work: an agency licensing a client's brand assets to build a campaign, or a vendor licensing an API to build an integration. This section should specify the scope of the license (which specific assets, and for what purpose), whether it's exclusive or non-exclusive, how long it lasts, whether it can be sublicensed to subcontractors, and whether it survives if the broader collaboration ends. Leaving license scope undefined is a common cause of scope-creep disputes once a project is underway. Also address geographic scope and medium: a license to use a client's logo in a single social campaign is not the same as a license to use it across every future marketing channel, and a template that doesn't force this distinction tends to get stretched well past what either side originally intended. If subcontractors, freelancers, or a fulfillment partner will touch the licensed IP, name that explicitly here rather than leaving it implied, since sublicensing without permission is one of the more common accidental breaches in agency-vendor chains.

Confidentiality & Non-Disclosure

Sets expectations for how each party will handle the other's confidential and proprietary information encountered during the collaboration, including unreleased product plans, pricing, methodologies, and any IP disclosed before a formal agreement exists. This typically mirrors standard NDA language: information marked or reasonably understood as confidential may not be shared with third parties or used outside the scope of the collaboration, standard carve-outs apply (information already public, independently developed, or required to be disclosed by law), and the obligation survives for a defined period after the MOU ends. If the parties already have a separate NDA in place, this section should reference it directly rather than duplicating conflicting terms. Specify a practical confidentiality period, commonly two to five years for general business information and indefinitely for trade secrets, since an obligation with no stated end date is harder to enforce and one that expires too quickly leaves genuinely sensitive IP unprotected right when it matters most, such as during a later acquisition or licensing negotiation.

If This MOU Doesn't Convert Into a Formal Agreement

Most templates assume the collaboration goes ahead; this section plans for when it doesn't, which is exactly the scenario agencies and freelancers hit most often during pitches, vendor evaluations, and early partnership talks that stall. It should state explicitly that no license or ownership transfer is created by simply discussing or sharing IP during this evaluation period, that each party must return or destroy the other's confidential materials and any shared background IP on request, that confidentiality obligations continue regardless of whether the deal proceeds, and that neither party may use ideas, concepts, or work samples exchanged during this period without a separate written agreement. Spelling this out up front prevents the common dispute where a prospect walks away from a pitch and later builds something suspiciously similar to the concept an agency shared for free. This matters just as much for freelancers submitting speculative design concepts, for startups discussing a potential technical partnership that stalls at due diligence, and for product teams evaluating a vendor's prototype and then building the same feature in-house. Naming this scenario explicitly, instead of hoping it never comes up, is what turns an MOU from a formality into an actual piece of leverage if a dispute happens six months later.

Term, Termination & Survival of Obligations

States how long the MOU stays in effect (commonly 30 to 90 days, or until superseded by a formal agreement), how either party can end it early (typically with written notice), and which obligations survive termination. Confidentiality duties, the return-of-materials requirement, and ownership of any IP that has already vested under this MOU should all explicitly survive; the general intent to collaborate does not need to. This section removes ambiguity about whether protections quietly expire the moment either side decides not to move forward. It's worth setting a specific expiration date rather than an open-ended term, since an MOU that never technically expires can create confusion months or years later about whether it's still the operative document or has been superseded by a signed contract nobody bothered to formally reference back to it. If the collaboration is renewed or extended past the original term without a new agreement, note whether the same background IP and confidentiality terms automatically continue or need to be re-confirmed in writing.

Signatures

The signature block: authorized representatives from both parties sign and date the MOU, confirming they understand and agree to how background IP, new IP, licensing, and confidentiality are handled for the duration of this collaboration and its evaluation period. Include each signatory's full name, title, and the entity they're signing on behalf of, since a signature from someone without authority to bind the company is one of the more common (and avoidable) ways an otherwise solid MOU gets challenged later. Sending the finished document for e-signature, rather than a scanned or photographed wet signature, also creates a timestamped audit trail of exactly when each party reviewed and agreed to these terms.