How can I let a potential investor, buyer or licensee examine confidential know-how while limiting disclosure?

Start with the decision the reviewer needs to make

A potential investor may need confidence that a process works and that the company controls the relevant know-how. A prospective licensee may also need to establish whether it can reproduce the result with its own equipment. Those questions require different levels of access.

Ask the reviewer to identify the uncertainty they need to resolve before requesting a complete technical folder. Record the question, the proposed evidence and any further examination that may be necessary. This turns disclosure into a sequence of specific assessments.

WIPO’s trade-secret guidance recognises that a licensee may need access to confidential information to assess its utility or value. Confidentiality measures must allow a meaningful examination while controlling how that information is used.

Reveal evidence in stages

Consider a fictional manufacturer licensing a confidential calibration method. The method improves production consistency, but its parameter tables and operating sequence would let a competitor reproduce it. A possible review sequence is:

Agree what triggers the next stage, such as completion of an initial technical assessment and agreement on the recipients and terms for deeper review. An investor examining an early opportunity may not need the same access as a buyer completing an acquisition.

A demonstration supports what happened under the conditions shown. It does not necessarily establish that the method will work at another scale, with other inputs or without the original operator. Record those limits so the next stage addresses the remaining question.

Use an independent reviewer where direct disclosure is too sensitive

The parties may agree that a suitably qualified expert examines the detailed know-how and reports on specified questions. For the calibration method, the expert could inspect the settings, witness trials and assess compatibility without passing the full parameter tables to the commercial team.

Agree who appoints the expert and check their qualifications and any conflicts of interest. Define which material they can access, the tests they will perform, their confidentiality obligations and what their report may disclose. The receiving party must accept the scope and limitations of the report if it is to serve the intended review.

Identify the exact technical package examined and preserve the report with that reference. “The technology was independently reviewed” is too vague if the expert saw only selected results or an earlier version. Expert review can reduce direct disclosure, but it cannot answer questions excluded from its scope.

Define the terms and people before granting access

Specify the permitted purpose, such as evaluating a licence for the identified method. Identify the receiving organisation and the employees or advisers allowed to examine the material, including how further disclosure is authorised. Address copying, testing, retention and use of the information as appropriate to the review.

The UK Intellectual Property Office’s NDA guidance recommends defining the permitted purpose precisely and considering disclosures to employees and professional advisers. Check the applicable agreement before granting access. If a potential investor will not accept confidentiality terms at the introductory stage, use material suitable for that exchange and leave the sensitive technical examination for a separately agreed process.

For the detailed mechanics, see how to identify information covered by an NDA. An NDA does not determine which files a person needs to see; that decision still comes from the review scope.

Preserve the package before disclosing it

Prepare a separate package for each stage, containing only the material intended for those recipients. Check that redacted files do not expose hidden text, comments, spreadsheet formulas or attachments. Preserve the original material separately, with a record of how the disclosure copy relates to it.

Timestamp the exact package before release and retain the matching files and verification data. This gives the disclosure a verifiable content reference that can also appear in an annex or review report. It does not require revealing the underlying know-how publicly. See what a digital timestamp establishes.

For the calibration example, certify the initial test report as its own package. If a technical expert later receives the settings and operating instructions, preserve and certify that separate package too. A certificate for the complete internal project does not, by itself, identify which subset the investor received.

Timestamping supports the dated existence and integrity of the package. It does not demonstrate that the process works, that the company owns the know-how or that the recipient kept it confidential. Those questions rely on the technical assessment, rights documents and handling records.

Record the examination as well as the file exchange

Keep the package reference, recipients, applicable terms and available delivery or access records together. For a demonstration or technical call, record who attended, what was shown and what additional detail was explained. A follow-up answer revealing a parameter or process step is another disclosure even if no new file was uploaded.

Ask the reviewer to distinguish in their report between material examined directly, conclusions based on summaries, and matters left unverified. This prevents a limited review from being presented later as a complete technical assessment. See how to document recipients and accepted terms.

When the review ends, close access and follow the agreed retention, return or deletion arrangements. Preserve the disclosure history and any confirmations received. Access restrictions can control future retrieval, but cannot erase downloaded copies or knowledge already acquired. Decide how much to disclose with that practical limit in mind.