Security enforcement: documents to prepare
Security enforcement over a licensed intellectual property right moves fast once the secured party issues a formal notice. The documents you assemble in the first days determine whether the licensee, the collateral agent and any registry keep pace with the timetable, or whether the file stalls on a missing signature. This page sets out what to prepare, in what order, and who signs off at each stage.
The material below sits in the Licensing, transfers and IP structures overview explained cluster and assumes a security interest already registered against a licence, a portfolio, or transfer rights.
Practical consequence
Once a default notice is served, the clock on cure periods, registry updates and third-party notifications starts running in parallel, not in sequence. A licensor who waits for one document before starting the next typically loses days that cannot be recovered later in the process. Preparing the full set before service, rather than reacting document by document, is what keeps the enforcement window intact.
The practical effect for a licensee is different: once notice is validly served, continued use of the licensed right without the secured party's consent becomes a breach in its own right, separate from the original default. This is the point after which negotiation options narrow sharply.
What to do
- Confirm the security instrument and its scope. The person handling enforcement pulls the original security agreement and checks which rights, which territories and which licence agreements it actually covers. Enforcement outside the registered scope is void from the start.
- Obtain a current registry extract. Whoever administers the relevant IP register issues an extract showing the security interest as recorded, including any prior-ranking entries. This extract accompanies every later filing.
- Draft the default notice. Counsel for the secured party sets out the trigger event, the cure period if one applies, and the consequence of non-cure, addressed to the licensee and any guarantor named in the agreement.
- Serve the notice through the method fixed in the agreement. Courier, registered post or the specified electronic channel — whichever the contract names, not whichever is convenient. Service through the wrong channel restarts the clock.
- Prepare the enforcement notice for the registry. Once the cure period expires without remedy, the secured party files an enforcement notice with the register to update the entry and, where applicable, to record a transfer or a new licence in its own favour.
- Notify sub-licensees and dependent contract parties. Anyone whose rights derive from the affected licence needs written notice before enforcement affects their position, not after.
Where the underlying asset is source code rather than a registered mark, the sequence above still applies, but the register that confirms authorship and assignment history looks different in practice — see Industrial manufacturing a contractor claims ownership of the code for how that record is checked before enforcement proceeds.
Who decides
| Question | Who decides | Typical timing |
|---|---|---|
| Is the trigger event valid | Secured party's counsel, subject to challenge by the licensee | Before notice is drafted |
| Has the cure period lapsed | Fixed by the contract; no discretion once dates are set | Runs from valid service |
| Is the registry entry updated | Registry administrator, on a compliant filing | Days to weeks depending on register |
| Is enforcement disputed | Court or arbitral tribunal named in the agreement | Opens once a challenge is filed |
The registry administrator does not assess the merits of the default. Its role is limited to checking that the filing is complete and consistent with the existing entry. Substantive disputes go to the forum the agreement names, most often arbitration or the courts of the licence's governing law.
Forks
If the licensee disputes that a trigger event occurred, enforcement does not stop automatically — the secured party can proceed unless the agreement or an interim order says otherwise, though contesting the underlying right at this stage resembles the kind of dispute resolved in How opposition settlement trade mark what the decision maker looks at, where the decision maker weighs competing claims rather than procedural compliance.
If the licensed asset is a tokenised right recorded off-chain and on-chain in parallel, enforcement documents must reconcile both records before filing — the same reconciliation problem covered in When an off-chain agreement contradicts metadata: what to do first, applied here to a security context rather than a sale.
If the licensee has already sub-licensed the right to a third party who is not in default, that third party's position does not disappear on enforcement; it is preserved or terminated depending on how the original licence and the security agreement address sub-licences, which is why sub-licensee notice sits inside the core document set rather than as an afterthought.
Limit
This page covers the documents needed to open and progress enforcement. It does not cover the substantive question of what a court or tribunal will decide once enforcement is challenged, and it does not cover the personal data notices that may be required when serving notice on individuals connected to the licensee — that assessment follows its own logic, set out in Legitimate interest assessment: summary and who decides, and needs to be run separately before any notice referencing an individual is sent.
It also does not address what happens once enforcement concludes and the secured party takes over the licensed portfolio — that stage, including how staff, contracts and registrations are folded into the acquiring structure, is covered separately in Post-closing integration step by step.
Verified
Reviewed by Marge Ojasalu. The procedural sequence above reflects standard security enforcement practice for intellectual property licences and does not reference a specific national statute; document requirements vary by governing law and by the register in question, and should be confirmed against the applicable security agreement and the relevant register's current filing rules before service.
FAQ
How long does security enforcement take in practice?
Timing depends on the cure period fixed in the agreement and on how quickly the registry processes the enforcement filing. A file with no dispute and a compliant notice moves through registry steps in days to a few weeks; a contested trigger event adds the time needed for the named forum to rule.
Which documents are needed to start?
At minimum: the security agreement, a current registry extract, and a default notice drafted to match the contract's own notice provisions. Sub-licensee notices and the registry's own enforcement filing follow once the cure period lapses without remedy.
What happens if the other side does not respond?
Non-response does not pause enforcement. If the cure period has run and no remedy has been provided, the secured party proceeds to file the enforcement notice with the registry and, where the agreement allows, takes over or reassigns the licensed right without further consent from the licensee.