How to Review a Technology Transfer Agreement (2026 Checklist)

A technology transfer agreement moves the right to use technology from one party to another. The technology can be patents, trade secrets and know-how, software, designs, data or a mix, and the transfer often comes with documentation, training and support so the receiving party can put it to use. Reviewing one well means being precise about what technology and which IP rights are actually covered, how wide the licence is, who owns improvements, how the transferor is paid, and what warranties and protections sit around a deal whose whole value is intangible. This is general guidance, not legal advice. ## The fast answer: what to check first Check four things first. Exactly what technology and IP rights are transferred (and whether it is an assignment or a licence). The scope of the licence (exclusive or not, field, territory, duration). Who owns improvements made by each side. How the transferor is paid and what warranties protect you. If the technology and IP are not clearly defined, nothing else in the agreement is safe. ## Clause-by-clause review checklist ### The technology and IP defined The agreement should define the transferred technology precisely: the specific patents (by number), patent applications, trade secrets and know-how, software, designs, data and documentation. A schedule listing the IP is essential. Vague definitions ("all technology relating to the product") create disputes about what was actually transferred. Confirm the transferor owns or controls what it is purporting to transfer. ### Assignment or licence Decide whether ownership is being assigned or whether rights are licensed. For a licence, this clause is the core of the deal. For an assignment, check that it is a full transfer with the right to record it at the relevant IP offices. ### Licence scope For a licence, check each dimension: exclusive, sole or non-exclusive; the field of use (which products or applications); the territory; the duration; and whether it includes the right to make, use, sell, sublicense and modify. A licence that is narrower than your business needs can leave you unable to use the technology as intended; one that is broader than the transferor intended will be resisted. ### Know-how and technology transfer mechanics Patents alone rarely let you use a technology. Check what practical transfer happens: documentation, source code, specifications, training, technical support, and a defined handover period with acceptance. For many deals this is where the real value lives, so confirm the transferor must actually enable you to use the technology, not just grant paper rights. ### Improvements and grant-back Technology evolves, so the agreement must say who owns improvements each party develops and whether they must be shared. Watch broad grant-back clauses that require you to assign or license all your improvements back to the transferor, often for free; these can erode the deal's value and, in some jurisdictions, raise competition-law concerns. Aim for balanced, reciprocal and reasonable improvement terms. ### Payment: fees, royalties and milestones Identify how the transferor is paid: an upfront fee, running royalties (on net sales, with the base clearly defined), minimum royalties, milestone payments, or a combination. Check the royalty base and rate, audit rights over royalty reports, and what happens if the underlying patents expire or are invalidated. Ambiguity in the royalty base is a common source of later disputes. ### Field of use, territory and exclusivity conditions If the licence is exclusive, check for performance conditions (minimum sales or development milestones) that let the transferor convert it to non-exclusive or terminate if you do not exploit the technology. If non-exclusive, understand who else may hold rights in your field or territory. ### Warranties and IP infringement Check what the transferor warrants: that it owns the IP, that it has the right to transfer, and ideally that the technology does not infringe third-party rights, with an indemnity if it does. Transferors often resist strong non-infringement warranties, so understand what protection you actually have and how liability is capped. ### Confidentiality Know-how and trade secrets lose value if disclosed. Expect strong confidentiality terms, surviving termination, covering the transferred know-how and any of your information shared during the transfer. ### Regulatory, export and competition compliance Technology transfer can trigger export controls, foreign-investment rules and competition law, which vary by country. Check which laws apply and who is responsible for approvals and filings. In some jurisdictions certain licence restrictions are regulated, so local advice is important. ### Term, termination and consequences Check the term, termination rights, and what happens on termination: whether the licence ends, whether you may keep using technology already deployed, what happens to confidential materials, and whether any rights survive. For an exclusive licence, understand what triggers reversion of rights to the transferor. ## Red flags to push back on Vaguely defined technology or an IP schedule that is missing. A licence narrower than your business needs. A broad, free grant-back of your improvements. An unclear royalty base. No obligation to actually transfer know-how and support, just paper rights. No IP warranty or indemnity, with the whole infringement risk on you. Export or competition-law issues left unaddressed. ## How the law changes by jurisdiction Contract law is national, so the same words do not behave the same everywhere. In common-law systems (India, the UK, Singapore, Australia, the US) courts lean on the written terms and read ambiguity against the drafter. Governing-law and jurisdiction clauses decide which country's rules apply and where disputes are heard; check they match where the parties and the assets actually are. In India, stamp duty and, for many instruments, registration are live concerns, and the Indian Contract Act 1872 governs formation. In the US, state law varies and the Uniform Commercial Code may apply where goods are involved. Across the EU and UK, data and consumer rules add mandatory terms you cannot contract out of. When in doubt, take local advice; this page is general information, not legal advice. ## A simple review workflow Nail down the defined technology and IP first, then the licence scope and improvement terms, then payment, then warranties and compliance, then termination. Get a patent or IP specialist to confirm the schedule and the ownership chain, and check export and competition rules for the relevant countries. Keep an issues list with clause reference, risk and proposed change. ## One workspace for drafting, review and tracking Everything above is work you can do by hand: read the draft, mark the risky positions, line up your redlines, remember the dates. The friction is rarely the reading. It is that the draft, the comments, the versions, the signed copy and the renewal date usually live in five different places. The simple idea behind an AI contract workspace is to keep that work together: draft from your own catalogue, see each clause flagged favourable, neutral or unfavourable to you, edit clauses in plain English and get a clean diff, keep a live activity timeline so every version is traceable, and track key dates and obligations so renewals and notices do not slip. Adira is one such workspace, built on Anthropic's Claude and tuned to how your company contracts. It is India-first today; deeper support for other jurisdictions and a single legal health pane (the Company Command Centre) are on the roadmap. None of that replaces legal advice on a specific deal. It just means the review you ran once does not have to be rebuilt from scratch next quarter.