A product name, a registration number and interest in a territory are useful starting points. They do not answer every question about a proposed in-licensing relationship. Before discussing a transaction as if its scope were settled, build a short evidence map linking each statement to its source, date and responsible party.
1. Separate product status from the proposed rights
WIPO distinguishes a licence, which permits use under agreed terms, from an assignment of ownership. Its biotechnology licensing primer also identifies territory, exclusivity, field of use and sublicensing as matters to define. A product record therefore belongs in one evidence line; the proposed contractual grant belongs in another. [1] [2]
For example, if a team shares a registration record and describes an opportunity as “exclusive,” do not combine those statements into one verified conclusion. Identify the exact product and market behind the record, then ask what the exclusivity claim covers and which evidence can confirm it. This is a discussion method, not a finding about any particular product.
2. Prepare a non-confidential first review
The following questions are an initial business-screening framework. They are not a complete legal or regulatory diligence list.
Record the product, dosage form or presentation, relevant market, current stage and dated public reference. Mark a mismatch or missing identifier explicitly.
Describe the organisation’s role and relationship to the product or rights holder. Keep a claimed role separate from a confirmed authority to negotiate.
State the intended territory and activities. Note open questions on exclusivity, sublicensing, data access and any limits of the proposed grant.
List the public source or controlled document that would answer each open question, its owner and the appropriate route for review. Do not upload confidential agreements or dossiers through a public inquiry.
3. Treat the regulatory handover as a separate workstream
In the EU centralised system, EMA describes a marketing-authorisation transfer as a change to a different holder. Its guidance calls for product-specific transfer information and confirmation that the complete, current product file is available to the transferee. These are defined regulatory steps, not something to infer merely from a commercial discussion. [3]
Use that example to ask a practical question: what information, responsibilities and implementation decisions would have to move for this particular project? Confirm the applicable pathway with the responsible regulatory specialists for the actual market. Do not apply the EMA procedure automatically to national authorisations or other jurisdictions.
4. Leave the meeting with a usable evidence map
A first meeting should produce three short lists:
- Known: statements linked to an identified source and a date checked.
- To confirm: claims or missing information, written without treating them as agreed facts.
- Next action: the question, responsible party and document or discussion needed to resolve it.
The next step may be to clarify the product, establish the participant’s role, arrange controlled document review or ask the relevant specialists to define the regulatory route. It should not be a promise of rights, supply, registration success or transaction completion.
Frequently asked questions
Does a product registration record establish the scope of a licence?
It provides a regulatory reference for the identified product and market. The proposed territory, exclusivity, sublicensing and data access still need their own contractual evidence and review.
Should an in-licensing discussion be treated as a marketing-authorisation transfer?
Do not assume that. EMA describes a specific transfer procedure for changing the holder of a centrally authorised product. The actual market, authorisation and proposed transaction determine which specialist questions need to be resolved.