Vesting Is Not Delivery: What a Customer Actually Acquires in a Commissioned Deliverable
Photo: Scanning Dmitry Makeev, scan date - 2020 year., Public domain, via Wikimedia Commons
A bespoke platform. A six-figure budget. A clause that reads: all intellectual property rights in the deliverables shall vest in the Customer with effect from payment. Twelve months later the customer discovers that it cannot prevent the supplier from licensing the underlying engine to a competitor, cannot record the design it believed it owned, and has nothing signed to put in front of a funder's diligence team.
The clause is not unusual. It is simply doing considerably less work than either party assumed. Ownership of commissioned deliverables is one of the few corners of commercial drafting where the statute is unusually prescriptive and where a failure of formality produces a result that commercial intent cannot repair.
Two Piles of Rights, Not One
Commissioned work almost always involves two distinct bodies of rights. Background intellectual property is what the supplier brings to the engagement: frameworks, libraries, code modules, methodologies, tooling and the accumulated know-how of a specialist practice. Foreground intellectual property is what the engagement produces: the configured application, the drawing set, the report, the model, the dataset.
Suppliers rarely intend to part with background rights, and customers rarely intend to buy them. The difficulty is that in software and design work the two become entangled, and a contract that speaks only of the deliverables leaves the boundary to be argued about later, usually by two sets of lawyers billing against a project that has already gone live. The remedy is definitional rather than rhetorical: a deliverables schedule that identifies each item, a background schedule that identifies what is being carved out, and an express statement that anything not listed as background is foreground.
Vesting Is an Ambition; Assignment Is a Transaction
Under section 90(3) of the Copyright, Designs and Patents Act 1988, an assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor. A clause stating that rights shall vest may operate as an agreement to assign future copyright under section 91, which passes equitable title. It does not, of itself, transfer legal title. The distinction matters in diligence, in registration and above all in enforcement, where the claimant must prove the chain on which it sues.
Different rights carry different formalities, and a single vesting sentence is routinely expected to carry all of them:
- Copyright: assignment in writing signed by the assignor (section 90(3), CDPA 1988).
- Unregistered design right: assignment in writing signed by the assignor (section 222, CDPA 1988).
- Registered designs: assignment in writing signed by the assignor (Registered Designs Act 1949, section 19).
- Registered trade marks: assignment in writing signed by both parties (Trade Marks Act 1994, section 24(3)).
- Moral rights: not assignable at all. They may be waived, but only by an instrument in writing signed by the person waiving them (section 87, CDPA 1988), and a waiver may be limited or conditional. A waiver buried in a statement of work and unsigned by the individual author may achieve nothing at all.
- Performers' rights: separate consent requirements under Part II of the 1988 Act, which bite wherever commissioned content includes recorded performance.
A contract that addresses only the first of these has addressed perhaps a third of the asset.
The Chain of Title Is Only as Strong as Its Weakest Link
Where a work is made by an employee in the course of employment, the employer is the first owner of the copyright (section 11, CDPA 1988). The practical consequence is that a supplier's staff do not own what they write; the supplier does. Everything therefore turns on the customer obtaining an assignment from the correct entity, and on that entity having a complete chain behind it.
Two failures recur. The first is the subcontractor or freelancer engaged by the supplier without a back-to-back assignment, leaving the supplier unable to give the customer more than it holds. The second is the open-source component. A permissively licensed library may be incorporated without difficulty; a copyleft library incorporated into a proprietary deliverable may impose obligations on distribution that the customer never contemplated and cannot discharge.
The drafting answer is a combination rather than a single clause: a warranty that the supplier has and will maintain a complete chain of title, a schedule of third-party and open-source components with their licences, an obligation to refresh that schedule at each release, and an indemnity that is not limited to the supplier's negligence.
Licence-Back: The Clause That Keeps the Supplier Solvent
The supplier that assigns all foreground rights outright, with no reservation, may find itself unable to reuse its own tooling on the next engagement. That is a commercial problem, and suppliers frequently solve it by declining the assignment in the first place, or by refusing the engagement. A well-drafted licence-back is not a concession to the supplier; it is the mechanism that makes the assignment obtainable.
What the licence-back should specify:
- Scope: which background items, and whether the licence extends to foreground works that embed them.
- Permitted use: internal use only, or the right to sublicense and to transfer on a sale of the business or the relevant asset.
- Field and term: perpetual and irrevocable where the customer's operations depend on it, rather than terminable on expiry of the services.
- Reservations: whether the supplier may reuse know-how, techniques and generalised elements, and whether a residuals clause is acceptable.
- Improvements: who owns enhancements made during the term, and whether the customer receives a licence to them.
What the Deliverables Schedule Should Capture
Ownership is an abstraction until it is attached to an inventory. In our experience, disputes about commissioned IP are less often disputes about the legal rule than about what the parties thought was in scope. The schedule should list, item by item: source code and build instructions, design files in editable format, documentation, test assets, data models, and the credentials and accounts needed to operate what has been built. It should also state what is deliberately excluded.
A Practical Checklist
- Divide background from foreground expressly, with two schedules and a residual clause.
- Use assignment language, not vesting language, and require a signed instrument on delivery.
- Add a further assurance obligation with a power of attorney so that a missing signature can be cured without litigation.
- Obtain moral rights waivers signed by identifiable authors, including no-assertion wording, extending to successors in title.
- Address registered rights separately, including recordal at the UK Intellectual Property Office.
- Warrant the chain of title, including subcontractors and open-source components, with a components schedule.
- Grant a licence-back that is precise about scope, transferability and termination.
- Provide for delivery of everything needed to operate the asset, not merely to own it.
- Consider whether a source code deposit is needed, remembering that escrow is a licence contingent on an event, not a transfer of ownership.
- Reconcile the vesting trigger with the payment terms, and consider what happens on insolvency of either party.
None of this is exotic. It is simply the difference between owning something and being told that you do.