An IP licence is a permission map, not a transfer of the asset

A Kenyan intellectual-property licence should answer one operational question without ambiguity: what may the licensee do that would otherwise require the rights holder’s permission? The owner normally retains the asset while granting defined rights of use. That makes a licence different from an assignment, even when the commercial payment is substantial or the licence is described as long-term.

Start by naming each asset. A brand deal may involve registered trade marks, unregistered get-up, artwork, product photographs, manuals, software, confidential recipes and domain names. A technology deal may combine patents, pending applications, know-how, source code, test data and improvements. One sentence granting “all IP needed for the business” cannot safely allocate this collection.

This guide concerns negotiated commercial licences. It does not replace the separate analysis for registering a trade mark, protecting a patent or industrial design, or proving copyright infringement. Those rights have different statutory rules, terms and recordal consequences, so the agreement needs an asset-by-asset schedule.

Run title and validity diligence before discussing royalties

For every registered right, obtain the registration or application number, owner, filing and renewal status, territory, classes or claims, security interests, recorded assignments, existing licences and pending challenges. Compare the register with the proposed licensor’s corporate name. If a group company, founder or contractor owns the right, a warranty from another entity does not create title.

Copyright diligence begins with authorship and first ownership. Collect employment terms, commission agreements, contributor releases, assignments, open-source notices and earlier distribution contracts. Section 33 of the Copyright Act governs assignments and licences; an assignment or exclusive licence must comply with the statutory writing and signature requirements. Define the works and rights rather than attaching a folder of mixed files without provenance.

For patents and industrial designs, read granted claims and representations instead of relying on a product description. Confirm maintenance, pending proceedings and whether the commercial process uses undisclosed know-how beyond the registered right. A patent licence may become commercially thin if the patent is revoked, expires or never covers the intended implementation, while the know-how may remain valuable under separate confidentiality controls.

Build a grant matrix before drafting the legal prose

Use a table with one row per asset and columns for permitted act, field of use, product, territory, channel, customer group, duration, exclusivity, sublicensing and reserved rights. For copyright, distinguish reproduction, adaptation, distribution, communication, public performance and translation where relevant. For software, specify users, instances, environments, hosting model, backup copies, interfaces, modification and access to source code.

A territory clause should address online use. “Kenya only” is unclear if a Kenyan platform can be viewed abroad, a cloud server sits in another country, or a distributor advertises across East Africa. State where the licensee may actively market, contract, deliver and appoint distributors, and whether passive online access outside the territory is permitted.

Reserved rights deserve their own clause. State what the licensor may continue doing, which customers or channels are retained, and whether affiliates or earlier licensees remain authorised. An exclusive licence should say whether exclusivity excludes only third parties or also the licensor. Section 65 of the Industrial Property Act supplies default rules for industrial-property licence contracts and distinguishes a contract that is exclusive from the ordinary position.

Exclusivity must be earned and measurable

Exclusivity can remove the owner’s ability to exploit a market, so connect it to performance. Minimum sales, launch milestones, distribution coverage, marketing spend, regulatory approvals or royalty floors can be measured on stated dates. The contract should say whether a failure ends the agreement, converts the grant to non-exclusive, narrows the territory, or triggers a cure process.

Do not describe several licensees as “exclusive” over the same field. Divide the fields precisely: for example, human veterinary products versus crop products, retail versus institutional supply, or named countries rather than an undefined region. Identify house accounts and existing contracts in a schedule instead of leaving them to later argument.

Competition compliance is a separate test. Section 21 of the Competition Act addresses agreements, decisions and concerted practices that prevent, distort or lessen competition, including use of intellectual property in a manner extending beyond the limits of legal protection. Territorial restraints, resale controls, tying, non-compete obligations, output limits and information exchange should be reviewed in their market context rather than copied from a foreign template.

Match formalities and recordal to the right being licensed

Section 67 of the Industrial Property Act requires industrial-property licence contracts to be in writing and signed by the parties. Sections 68 and 69 create a registration and review framework for those contracts, including scrutiny of terms that impose unjustified restrictions on the licensee or harm Kenya’s economic interests. The official KIPI commercialisation guidelines explain the commercialisation process and the relevance of section 69.

For registered trade marks, section 31 of the Trade Marks Act provides for registration of a proposed user. The application materials address the relationship between proprietor and user, the goods or services, conditions or restrictions, duration and the proprietor’s degree of control. A contract can impose obligations between the parties, but the parties should separately decide what must be filed or recorded and who is responsible for completing it.

Do not use one closing condition for every right. Create a completion checklist identifying signatures, board approvals, stamped or certified copies where required, registry forms, supporting affidavits, fees, recordal receipts and deadlines. State whether commercial use may begin on signature, on payment, on regulatory approval or only after a required recordal.

Turn the royalty clause into an auditable calculation

Define the royalty base with an example. “Net sales” should state whether it excludes VAT, genuine returns, separately invoiced delivery, approved rebates, bad debt and related-party transfers. It should also say when a sale is recognised and how bundled products, free samples, foreign currency and non-cash consideration are treated. A percentage without these rules invites a dispute even where both parties report honestly.

Set the reporting period, currency, exchange-rate source, payment date, invoice requirements and interest or other consequence for late payment. Address Kenyan tax treatment in a tax schedule after current advice, including responsibility for withholding, evidence of remittance, gross-up if negotiated and treatment of indirect tax. Do not hard-code a tax rate from an earlier transaction into a long licence.

Audit provisions should identify record retention, notice, auditor independence, confidentiality, frequency, material discrepancy threshold and who bears audit cost. The licensee’s systems must be able to separate licensed products and territories. If sales occur through affiliates or distributors, the agreement should specify whether reporting is based on the licensee’s transfer price or the downstream arm’s-length sale.

Quality control protects the trade mark and the customer

A brand licence needs an objective approval system. Attach brand standards and product specifications; identify who approves packaging, advertising, local translations, suppliers and material changes; and set realistic response times. Silence should not be deemed approval unless the owner can accept that risk. Keep approval records in a shared register.

Inspection rights should fit the product. They may include sample testing, factory access on notice, batch records, complaint reports, recall cooperation and evidence of regulatory compliance. State who pays for failed tests, rework, withdrawal and corrective notices. The licensor should not reserve unlimited control over the licensee’s entire business when only use of the licensed brand or technology is relevant.

Customer complaints can affect both parties. Define notification thresholds, adverse-event or safety escalation, control of public statements and preservation of suspect units. If the licensee can appoint manufacturers or distributors, flow down the relevant quality and brand rules and keep the primary licensee responsible for monitoring compliance.

Separate background IP, improvements and project output

List what each party brings into the relationship as background IP. Then decide who owns improvements, adaptations, local content, tooling, data sets, documentation and feedback created during performance. “All improvements belong to the licensor” can capture the licensee’s independent technology; “developer owns everything it creates” can deprive the paying customer of essential product changes. Draw the boundary by reference to the licensed asset and the contribution made.

If new work is commissioned, include contributor and employee paperwork in the delivery process. Payment and possession of source files do not alone resolve copyright ownership. Acceptance criteria should cover technical performance, documentation, security testing, third-party components and the evidence needed to show that promised rights can be granted.

For software and data, maintain a third-party dependency schedule. Record open-source licences, commercial libraries, model or data licences, hosting services and export or use restrictions. The licensor should disclose components that prevent the promised sublicensing, closed distribution or field of use. The licensee should avoid combining the licensed asset with material that forces an unintended disclosure or licensing obligation.

Confidential know-how needs controls that survive the licence

Define confidential information by substance and context, not only by a marking requirement. Set permitted recipients, security measures, copying limits, compelled-disclosure procedure and return or deletion rules. Exclude information already public, lawfully known, independently developed or received without duty. A patent may be public; the manufacturing tolerances, source code or customer implementation around it may not be.

Specify how knowledge will be transferred: named personnel, training sessions, manuals, test environment, acceptance date and support response. If the licence cannot be used without continuing technical assistance, price and service obligations belong in the contract rather than in an informal promise.

On termination, the licensee may need enough retained information to handle warranty claims, legal retention and regulator inquiries. Permit a secured archival copy for defined purposes while ending operational use. For source code essential to continuity, consider escrow triggers such as insolvency, permanent support failure or specified discontinuation, with release terms that grant enough rights to maintain the system.

Allocate infringement response before the first complaint arrives

The agreement should distinguish third-party infringement of the licensed right from a third-party allegation that licensed use infringes someone else’s right. For enforcement, decide who monitors, who may send notices or sue, who controls strategy, who pays, how settlement is approved and how recoveries are shared. An exclusive licensee’s statutory position may differ by right, so do not assume a single enforcement clause answers standing.

For incoming claims, require prompt notice, evidence preservation and cooperation. Define control of defence and settlement, especially where an injunction could shut down the licensee while the licensor prefers to litigate. Possible business responses include obtaining additional rights, modifying the product, replacing the component, pausing a territory or refunding defined amounts. Indemnity is only useful if its scope, exclusions, procedure and financial support are credible.

Coordinate a serious dispute through the IP enforcement guide. The licence file should already contain ownership evidence, approval records, sales reports, specimens and technical schedules. Those records help prove authorised use, identify conduct outside scope and calculate the commercial effect of infringement.

Design termination around an operational exit

List termination events separately: non-payment, material out-of-scope use, quality failure, missed minimums, confidentiality breach, insolvency, loss of the licensed right and uncured ordinary breach. Give each an appropriate notice and cure route. A ten-day cure may make sense for an unpaid invoice but not for a product recall or deliberate source-code disclosure.

The exit schedule should cover final orders, sell-off stock, removal of marks, domain and account transfer, destruction or return, continuing customer support, accrued royalties, final audit, warranties, confidentiality, data handling and public announcements. A sell-off right should identify products, quantities, territories, period, quality requirements and reporting; otherwise it can become an indefinite extension.

Also plan for expiry of a patent, cancellation of a mark or loss of exclusivity. Decide whether the remaining know-how, support and other rights justify continued payments. Avoid a clause that treats every validity challenge as an automatic material breach without competition and enforceability review.

Close only when the schedules can be used by the operating team

A signing set should include the rights schedule, grant matrix, territory and channels, technical specification, brand manual, minimum performance plan, royalty example, reporting form, approved subcontractors, third-party components, recordal checklist and exit plan. Assign an owner inside each business for approvals, renewals, reports and disputes. Calendar renewal dates and performance reviews rather than relying on the legal department to rediscover them.

Request a Kenyan IP licence review with the draft, registry extracts, ownership chain, asset list, proposed products and territory, financial model, technical dependencies, existing licences, quality standards and intended subcontractors. The review should test the grant against actual title, complete the relevant statutory formalities, model the royalty, identify competition risk and produce an exit that the business can perform.

Frequently asked questions

What should be listed in a Kenyan IP licence agreement?

List each registered right, application, work, software component, item of know-how and brand asset, then state the permitted acts, products, field, territory, channels, term, exclusivity, sublicensing and reserved rights. Attach registry details and technical schedules so the grant can be matched to the licensor’s actual title.

Must an IP licence be registered in Kenya?

The answer depends on the right. Industrial Property Act sections 67–69 impose writing and registration-related requirements for industrial-property licence contracts, while Trade Marks Act section 31 provides the registered-user framework. Copyright, trade mark and patent formalities should be checked separately and assigned to a party in the closing checklist.

How should royalties be defined to avoid a dispute?

Define the royalty base, permitted deductions, recognition date, bundles, affiliate sales, currency, exchange-rate source, reporting period, payment date, tax handling and audit process. Include a worked calculation using the expected transaction so both finance teams can test the same result before signature.