When a pledge over rights is enforced: what to do first

A pledge over intellectual property rights turns from a paper clause into an active process the moment the secured creditor declares an event of default. The first task is not negotiation. It is establishing exactly which right is pledged, where — if anywhere — the security interest is recorded, and which enforcement route the security agreement actually permits. Everything else, including licence survival and register updates, follows from that.

The legal basis: it depends on what was pledged

Intellectual property rights are not a single category for security purposes. Some carry a dedicated EU-level register; others rely entirely on national law or on the mechanics of a private agreement.

An EU trade mark is treated by Regulation (EU) 2017/1001 (EUTMR) as an object of property in its own right, separate from the business that owns it. That treatment is what allows a trade mark to be pledged at all, and it is why the pledge, once created, should be reflected in the EU trade mark register rather than left as a private arrangement between creditor and debtor.

A unitary patent sits under a different instrument. Regulation (EU) No 1257/2012 treats a unitary patent, for property purposes, in line with the national patent law of the participating state where the proprietor has its seat or residence. This matters directly for enforcement: it tells you whose national foreclosure rules apply to the pledge, even though the patent itself is a single unitary right across the participating states.

Software copyright and database rights sit outside both frameworks. Neither Directive 2009/24/EC nor Directive 96/9/EC addresses security interests, and neither creates a register in which a pledge could be recorded. A pledge over a database right or over software copyright is governed by the general national law applicable to the security agreement, with no EU-level recordal to check.

What changes once enforcement starts

Once the creditor moves to enforce, three things happen at once, and they do not wait for each other. The register entry, if one exists, may need updating to reflect the change of control over the right. Any licences already granted over that right come under pressure, because an enforcement sale can raise the question of whether the licence survives a change of proprietor. Deadlines tied to the underlying right — renewal dates, opposition windows, notice periods in the licence itself — keep running regardless of who is enforcing what.

Ignoring any one of these three does not pause it. A licence notice period that expires during enforcement still expires. A renewal deadline that falls due still falls due.

What to do first

1. Identify the exact right pledged. The debtor or its counsel should confirm whether the pledge covers a specific registered right, a portfolio, or rights arising under a licence — these are not interchangeable for enforcement purposes.
2. Check the register, if one exists. Whoever holds the register-facing role should pull the current entry for the right and confirm whether the security interest itself was ever recorded there.
3. Locate every licence tied to the right. The licensing team should list every current licensee and check each licence's change-of-control and termination clauses before enforcement proceeds further.
4. Confirm the deadline calendar. Someone with authority over the portfolio should list renewal dates, opposition windows, and licence notice periods that are running independently of the enforcement process.
5. Establish the enforcement route agreed in the security document. The creditor's counsel should confirm whether the agreement calls for a court process, an arbitral process, or a private sale, since this determines who decides next.
6. Notify affected licensees only once the route is confirmed. Premature notice before the route is settled tends to create disputes about what was actually communicated.

Who decides, and on what evidence

The forum is set by the security agreement, not by the registry. It may be a court with jurisdiction over the debtor, an arbitral tribunal named in the agreement, or a private sale process supervised by the creditor under terms the debtor already accepted. Whichever forum applies, the evidence it works from is the same core set: the security agreement itself, the register entry if one exists, and proof that the default triggering enforcement actually occurred and remains uncured.

For an EU trade mark or a unitary patent, the register entry carries weight because it is the public record third parties rely on. For a database right or software copyright, there is no equivalent public record, so the security agreement and the licence documents carry correspondingly more weight in any dispute.

Different scenarios, depending on the right pledged

If the pledged right is a registered trade mark and a third party is already contesting the mark's own scope — a colour, a shape, or a similar sign — the enforcement process and the scope dispute need to be tracked as two separate files with two separate timelines. What to do first in this situation and its sets out the separate steps for that dispute.

If the pledged asset is a database that a supplier built under contract, ownership itself may still be unsettled at the point enforcement starts, which changes what the creditor is actually entitled to seize. When the database was built by a supplier: what covers how to establish that ownership before enforcement proceeds on a contested basis.

If the right pledged is represented through a platform — a tokenised licence position or a custody arrangement rather than a direct register entry — enforcement depends on the platform's own custody terms as much as on the underlying IP right. When custody is held by a platform in practice addresses that layer separately.

What this page does not cover

This page does not value the pledged right, does not draft the security agreement, and does not resolve a dispute over who validly created the pledge in the first place. It also does not cover the data protection questions that can arise when a creditor requests access to licensing records held about identifiable individuals during enforcement; that assessment is a separate exercise. Legitimate interest assessment overview and the deadline sets out how that assessment is structured.

Verified

Checked against: Regulation (EU) 2017/1001 (EUTMR); Regulation (EU) No 1257/2012; Directive 2009/24/EC; Directive 96/9/EC. Where the underlying right has no EU-level register — database rights, software copyright, most national trade marks and patents — the applicable rule is the national law governing the security agreement and the relevant national register, which is not itself covered by the sources above.

Related publications

A pledge enforced against rights under a licence often exposes gaps between what the term sheet promised and what the licence itself actually grants. What to do first in this situation in practice covers that gap directly.

FAQ

What is the first step when a pledge over rights is enforced?
Identify exactly which right is pledged and check whether a register entry exists for it. That single check determines whether the enforcement route runs through a public register or through the security agreement alone.

Which deadline is already running?
Renewal dates for the underlying right, opposition or appeal windows tied to it, and any notice period in a licence granted over it. None of these pause because enforcement has started.

Who decides, and on what evidence?
The forum named in the security agreement — a court, an arbitral tribunal, or a private sale process — decides on the agreement itself, the register entry where one exists, and proof that the default remains uncured.

— Marge Ojasalu, AURELIS