When a consulting project ends, who owns what was made? The strategy document, the software tool, the designs, the training materials. Most people assume the client does because the client paid for them. Under the law of England and Wales that assumption is often wrong, and the contract is where the answer is actually settled.
The default position: the contractor usually owns it
Under the Copyright, Designs and Patents Act 1988 the author of a work is the first owner of the copyright in it. There is an exception for employees: where an employee creates a work in the course of their employment, the employer owns the copyright unless they have agreed otherwise. A consultant working through their own business is not an employee, so that exception doesn’t apply. Copyright in a report, code or design a consultant creates starts with the consultant (or the consultant’s company, if the individual is its employee).
Paying for the work doesn’t change that. An assignment of copyright only takes effect if it is in writing and signed by or on behalf of the person transferring it. If the contract says nothing, or only says the client “will own” the work without a proper assignment, the client may end up with no more than an implied licence to use the work for the purpose it was commissioned. How wide that licence is depends on the facts, which is exactly the kind of argument both sides would rather avoid. Inventions and designs have their own statutory rules, which is another reason a good contract deals with all intellectual property expressly rather than relying on the default.
So if you are the client, you want a clear written assignment. If you are the consultant, you should know that you start from a stronger position than many clients realise, and that giving up ownership is something you can price.
Why ownership matters to both sides
If the client owns everything you create, you can’t reuse those elements for other clients, build a product from tools you developed on the job, or publish the work as a case study without permission. For a management consultant whose deliverable is a one-off report, that may not matter much. For a developer or designer whose code, components and templates have lasting value, it matters a great deal.
Clients have their own concerns. They want to use, change and build on what they paid for without coming back to you, and they may need to show a buyer or investor that the business owns its key assets. Those interests can pull against yours, which is why IP clauses get negotiated.
The main approaches to ownership
Client owns all IP. A typical clause reads: “All intellectual property created by the consultant in the course of the services is assigned to the client.” This is what most client-drafted contracts say. If you accept it, factor it into your price.
Consultant keeps ownership and grants a licence. For example: “The consultant retains all intellectual property in the deliverables and grants the client a perpetual, royalty-free, non-exclusive licence to use them for its own business.” This is less common but makes sense where you are building on reusable tools or processes.
A split. Most well-drafted agreements land in between: the client owns the bespoke deliverables and the consultant keeps its pre-existing materials and general know-how, with a licence to the client to use anything of the consultant’s that is built into the deliverables.
The types of IP a clause should separate
Deliverables. The main output, such as a report, design, strategy document or software. This is usually what the client expects to own.
Background IP. What you owned before the engagement started: frameworks, templates, methods, code libraries. You would normally keep this even if the client owns the deliverables.
Adaptations. Changes you make to your background IP for this client. A common compromise is that the client owns (or has a licence to) the client-specific configuration, and you keep the underlying tool.
Third-party material. Open-source software, stock images, licensed data or fonts. Neither you nor the client owns these. The contract should say they are used under their own licence terms and that you are not assigning something you don’t own.
If the contract doesn’t distinguish between these, a broad “client owns everything” clause can sweep in your background IP. That is the single most common problem in consultancy IP terms.
Clauses to look for
Background IP. The contract should say plainly that anything you bring to the engagement stays yours. This is rarely controversial and avoids arguments later.
A clear definition of “deliverables”. Is it only the final report, or does it also cover raw data, working papers, drafts and presentations? The narrower the definition, the more you keep.
Licence back and portfolio use. Even where the client owns the deliverables, you may want a right to use anonymised versions in your portfolio or to describe the type of work you did. Ask for it expressly.
Residual knowledge. The law generally doesn’t prevent you from using the general skill and experience you build up on a job. The risk comes from wide confidentiality and IP clauses that blur the line between that and the client’s confidential information. A residual knowledge clause confirms you can keep using general know-how in future work, provided you don’t use the client’s confidential information or copy its deliverables.
Moral rights. Authors have moral rights, such as the right to be identified as the author and to object to derogatory treatment of the work. They can’t be assigned but can be waived in writing, and client contracts often ask for a waiver. Check whether that matters to you before agreeing.
What to negotiate
Anonymised case studies. If the client is to own everything, ask for permission to describe the project and results without naming the client. Many clients will agree if they can see the text before it is published.
Separate the deliverables from your tools. For example: “The client owns the customised reports and configuration produced for it. The consultant retains ownership of its analytics framework and grants the client a perpetual, royalty-free, non-transferable licence to use the framework as part of the deliverables for its own business.”
Ownership tied to payment. Consultants often ask for the assignment to take effect only once the relevant fees have been paid. If the project is cancelled halfway, the contract should say who owns the work in progress. A common approach is that the client gets what it has paid for and nothing more.
Software specifics. If you write code, the contract should list or describe your pre-existing libraries and tools, confirm they are licensed rather than assigned, and deal with open-source components and their licence terms.
Warning signs
“The client owns all IP created during the term, whether or not it relates to the services.” That is far too wide. It could catch unrelated work you do for other clients or on your own products while the contract is running. Limit it to work created in performing the services.
An assignment of background IP. Watch for wording such as “all intellectual property used or created in connection with the services”. “Used” can capture your existing tools. Ask for background IP to be carved out and licensed instead.
A right for the client to commercialise your work. If the client can sell or license what you build to others, that may be fine, but it is worth more than a deliverable used only in-house. Price it accordingly or limit the licence.
Wide confidentiality combined with client ownership. Together these can stop you even saying what kind of work you did. Ask for confidentiality to be limited to genuinely confidential information and for general know-how to be excluded.
Getting it right before you sign
IP terms shape what you can do with your work long after the project ends, so they are worth reading carefully before you sign. QuickLegalCheck reviews consultancy agreements, including the IP and confidentiality clauses, and explains in plain English what you would be agreeing to and what you might ask to change. If the IP is central to the value of your business, or the client wants to buy your platform outright, that is a point to speak to a solicitor.
You can get started with a free first look at your contract.
Related: what the consultancy agreement review covers, and a complete sample report.