IP Carve-out Agreements in the UK: When Businesses Need Them

IP carve-out agreements matter when a business deal includes intellectual property, but not all of it should transfer, be licensed, or be shared. Founders often get caught by three mistakes: assuming a broad assignment clause only covers the current project, relying on a side email about who keeps pre-existing IP, or signing standard terms without checking whether background materials, improvements, data, software code, or branding are excluded properly. Those mistakes can create expensive disputes later, especially when the business wants to scale, raise investment, appoint new suppliers, or end the relationship cleanly.

This guide explains when UK businesses usually need an IP carve-out agreement, what the carve-out should actually say, and the legal issues to check before you sign. It also covers where carve-outs commonly appear in commercial contracts, how they interact with ownership and licence rights, and the practical points to settle before you spend money on development, branding, or rollout.

Overview

An IP carve-out agreement separates the intellectual property that is included in a deal from the intellectual property that stays out of it. In practice, it helps businesses preserve ownership of pre-existing materials, ringfence reusable know-how, and avoid accidentally giving away rights they still need for other customers, products, or future growth.

• Identify exactly which IP is being transferred, licensed, or created under the deal.
• Define what is excluded, including background IP, templates, code libraries, trade marks, data sets, and confidential methods.
• Decide whether improvements, adaptations, and derivative works fall inside or outside the carve-out.
• Check the permitted use rights, duration, territory, exclusivity, and any restrictions on sublicensing.
• Make sure the carve-out matches the confidentiality, termination, and dispute clauses in the main contract.
• Confirm the agreement reflects what the parties actually intend before you rely on a verbal promise.

What IP Carve-out Agreements Mean For UK Businesses

An IP carve-out agreement is usually needed when one party is creating, supplying, transferring, or licensing IP, but wants to keep some rights outside the deal.

That issue comes up more often than many businesses expect. A software developer may build a custom platform for a client, but still need to retain ownership of its existing code base and reusable modules. A branding agency may assign the final logo files, but keep ownership of its design process, templates, and pitch concepts. A manufacturer may share technical drawings for a limited purpose, while excluding underlying know-how and production methods.

In each of those examples, the business relationship works because the commercial arrangement and the IP position are separated clearly. The client gets what it has paid for. The supplier keeps what it needs to continue trading.

What “carve-out” means in plain English

A carve-out is a specific exclusion from a broader legal promise. If a contract says “all intellectual property created or used under this agreement belongs to the customer”, a carve-out narrows that statement by saying certain categories are excluded.

Those excluded rights often include:

• pre-existing intellectual property owned before the contract starts
• general skills, know-how, and experience
• underlying software libraries, frameworks, or tools
• standard templates, forms, and internal methods
• trade marks, business names, and branding assets not commissioned under the project
• confidential processes and technical methods
• materials licensed from third parties

The wording matters because “excluded IP” can be narrow or wide. If it is drafted vaguely, the parties may still argue later about what was meant to stay out.

When businesses typically need one

UK businesses commonly need an IP carve-out agreement before they sign a contract that includes development work, creative work, technical collaboration, or any transfer of rights.

Common founder moments include:

• before you sign a software development agreement with a client who expects ownership of everything
• before you accept the provider's standard terms for bespoke design, branding, or content production
• before you commission a manufacturer to adapt an existing product or prototype
• before you enter a joint venture or collaboration where each side brings existing IP to the table
• before you buy a business asset and need to separate purchased IP from retained group IP
• before you engage a consultant who will use their own methods, templates, or tools
• before you rely on a verbal promise that “you can keep using your own materials”

Why this matters commercially

The main risk is not just legal wording, it is loss of control. If your contract accidentally assigns too much IP away, you may not be able to reuse your own materials, license your product elsewhere, or prove to investors that your business owns its core assets.

The opposite risk also matters. If the customer thought it was buying full ownership but the carve-out is too broad, the customer may find it cannot modify, maintain, or commercialise the deliverables as expected. That can damage the relationship quickly.

A good carve-out balances both sides. It should give the customer enough rights to use what it has bought, while preserving the supplier’s retained IP where that was always part of the deal.

Where carve-outs usually sit

You do not always need a standalone document. Many businesses deal with carve-outs inside a wider contract, usually in the intellectual property, licence, or definitions sections.

You may see carve-out provisions in:

• software development agreements
• agency and creative services agreements
• consultancy agreements
• SaaS contracts with customisation work
• manufacturing and product development agreements
• distribution and white label arrangements
• business sale agreements
• research, collaboration, and innovation contracts

A standalone IP carve-out agreement can still be useful where the parties have already signed heads of terms, where there is a dispute about ownership wording, or where a transaction needs a separate schedule defining excluded assets in detail.

Legal Issues To Check Before You Sign

Before you sign, the contract needs to say exactly who owns what, who can use what, and what is excluded from the deal.

This is where founders often get caught because the broad commercial agreement sounds right, but the detail underneath is missing. If the contract only says “IP remains with the creator” or “all project IP belongs to the client”, that is rarely enough on its own.

1. Define the IP categories properly

The agreement should separate at least three categories of IP:

• background IP, meaning what a party already owned or controlled before the contract
• project IP or foreground IP, meaning what is created specifically under the contract
• excluded IP, meaning what is carved out from any transfer, assignment, or licence

If those categories overlap or are undefined, the carve-out can fail in practice. For example, if a developer updates existing source code during a custom project, the contract should deal clearly with the old code, the new code, and any merged output.

2. Check whether the clause is an assignment or a licence

An assignment transfers ownership. A licence gives permission to use IP without transferring ownership. Businesses often treat those as interchangeable, but they are not.

If your business wants to keep ownership but allow use, the carve-out should work alongside a licence back or retained-use clause. If the client needs permanent use rights, the licence may need to be irrevocable, transferable within its group, or broad enough for maintenance and future upgrades.

Before you sign, ask:

• Is ownership actually changing hands?
• If not, what licence rights are being granted instead?
• Can the customer modify, adapt, or integrate the deliverables?
• Can the supplier reuse the same methods or components elsewhere?
• Does anyone need sublicensing rights?

3. Deal with improvements and derivative works

Improvements are a common source of disputes. A supplier may retain its background IP, but what about changes made during the project? A customer may own the final deliverable, but what about the underlying enhanced framework used to produce it?

The contract should state whether improvements to excluded IP remain with the original owner, become project IP, or are licensed on agreed terms. Without that wording, both sides may claim the same development work.

4. Match the carve-out to third-party IP and open source use

A business cannot assign rights it does not own. If the work includes third-party software, stock assets, licensed fonts, external datasets, or open source components, the customer’s rights may be limited by those upstream terms.

This needs to be addressed explicitly. Otherwise, a customer may think it has full ownership when some parts can only be used under a separate licence or subject to compliance obligations.

The contract should identify:

• any third-party materials included in the deliverables
• whether those materials are excluded IP
• what licence terms apply to them
• who is responsible for obtaining permissions
• whether any open source conditions affect commercial use, disclosure, or distribution

5. Consider confidential information and know-how

Not every valuable asset is registered IP. Trade secrets, methods, formulas, internal workflows, customer selection criteria, and technical know-how may be some of the most important assets in the deal.

If you want those kept outside the transfer, the carve-out should sit alongside strong confidentiality wording. Otherwise, the parties may preserve ownership in theory but still disclose the material too widely in practice.

6. Check what happens on termination

Termination wording often exposes whether the IP position has really been thought through. If the relationship ends early, who can keep using the deliverables, and on what basis?

Before you sign, make sure the agreement covers:

• whether licences survive termination
• whether unpaid fees affect use rights
• whether confidential and excluded materials must be returned or deleted
• whether each party can keep archival copies for legal or compliance reasons
• whether transition assistance is needed so the customer can continue operating

7. Make sure the carve-out fits the commercial reality

The best drafting still fails if it does not reflect how the work will actually be done. If a supplier says it is creating something entirely bespoke, but really intends to build on an existing platform, the carve-out should say so plainly. If a customer expects exclusive control, that expectation must be matched by the IP clauses.

This is especially important before you invest in branding, before you register a trade mark, domain, or print packaging, or before you spend money on development that depends on ownership certainty.

Common Mistakes With IP Carve-out Agreements

The most common mistake is treating the carve-out as a drafting detail when it is really a commercial control issue.

Once the relationship sours, generic clauses rarely solve the problem. The contract needs to reflect the actual boundaries of ownership and use from the start.

Using vague terms like “pre-existing materials” without examples

That phrase sounds sensible, but it often creates arguments. Does it include updated templates, modified code libraries, partially reused concepts, or material created during the early proposal stage?

Concrete definitions work better. If certain assets matter, identify them by category, schedule, or specific description.

Assuming payment means full ownership

Many customers assume that if they paid for the work, they own everything connected to it. Many suppliers assume the opposite, especially where they used their own tools and know-how. Both assumptions can be wrong.

Payment terms and IP ownership are separate issues. The contract needs to spell out whether the deal is for an assignment, a limited licence, or a hybrid structure with carve-outs.

Leaving improvements unaddressed

This is where disputes often become technical and expensive. If an existing platform is adapted for one customer, each side may later claim the updated components. The supplier may say the enhancements are part of its core product. The customer may say the enhancements were funded under the project and belong to it.

A simple clause on improvements can prevent a much larger disagreement later.

Forgetting practical use rights

A business may successfully preserve its excluded IP, but still draft the customer’s use rights too narrowly. That can leave the customer unable to operate, maintain, edit, or migrate what it has paid for.

The reverse also happens. A customer may negotiate broad rights for internal use, but the wording accidentally allows wider reuse, sublicensing, or disclosure than the supplier intended.

Relying on proposal documents and email chains

Founders often think a proposal, statement of work, or negotiation email is enough to protect background IP. It usually is not, especially where the signed contract contains an entire agreement clause or broad IP assignment wording.

Before you sign, make sure the final agreement includes the carve-out in the operative clauses, not just in commercial notes or side correspondence.

Ignoring group company and contractor issues

The party signing the contract may not be the only entity involved in creating or owning the IP. A group company may own the software platform. Freelancers may have produced some of the design assets. External developers may have written parts of the code.

If your business does not control those rights properly, the carve-out may promise more than you can legally give. This is where internal IP ownership documents, contractor agreements, and assignment clauses matter.

Using one-size-fits-all precedent wording

An IP carve-out for a branding project should not look identical to one for software, manufacturing, or a business asset sale. The categories of IP, the use rights, and the termination risks are different.

Generic templates often miss what matters most in the actual transaction. That is why founders should pressure-test the wording against the real deliverables, the real workflow, and what each side needs after the deal ends.

FAQs

Do all service agreements need an IP carve-out?

No. Some contracts are simple enough that a basic ownership clause works. A carve-out is usually needed where one party brings valuable existing IP into the work, or where broad assignment wording could accidentally capture more than the parties intended.

Can an IP carve-out sit inside a main contract instead of a separate agreement?

Yes. Many carve-outs appear inside the main commercial contract. A separate agreement is more useful where excluded assets need detailed schedules, where negotiations are sensitive, or where the parties need to amend an existing deal.

Does a carve-out mean the customer gets no rights to use the excluded IP?

No. A carve-out only means the excluded IP is not transferred outright. The customer may still receive a licence to use it, and the scope of that licence should be stated clearly.

What is the difference between background IP and project IP?

Background IP is what a party already owns or controls before the deal, or develops independently outside it. Project IP is the material created specifically under the contract. The agreement should define both, especially if they will be combined.

Can a business rely on a verbal promise about keeping its own IP?

That is risky. If the written contract says something broader, the written terms usually carry much more weight. Before you sign, make sure the carve-out and any licence terms are in the final signed document.

Key Takeaways

• An IP carve-out agreement helps separate the IP included in a deal from the IP that stays with its original owner.
• UK businesses often need carve-outs in software, design, consultancy, manufacturing, collaboration, and asset sale contracts.
• The agreement should define background IP, project IP, excluded IP, use rights, improvements, and third-party materials clearly.
• Broad ownership clauses can create real commercial problems if they accidentally transfer reusable code, know-how, templates, branding assets, or confidential methods.
• The wording should match how the work is actually delivered, especially before you sign a contract, before you spend money on development, or before you rely on a verbal promise.
• Termination, confidentiality, licences, and contractor ownership all need to fit the carve-out so the arrangement works in practice.
• If you are reviewing or negotiating IP carve-out agreements and want help with contract drafting, ownership and licence clauses, supplier negotiations, or IP risk reviews, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.