Start with the transaction, not a downloaded form
A one-way supplier quotation, a mutual development project and a potential license evaluation involve different information flows. Before reviewing clauses, draw who will disclose what to whom and for what purpose. The contract should fit that exchange rather than force the project into a generic template.
WIPO: Trade secret management identifies important confidentiality-contract topics, including scope and permitted use. WIPO: How to protect trade secrets places agreements within a broader protection program. The checklist here is a briefing tool for legal review, not a ready-to-sign contract or advice that a particular clause is enforceable.
Prepare the factual briefing
- Parties. Identify the actual legal entities and whether affiliates or subcontractors need access.
- Information. List drawings, samples, process settings, test data and verbal explanations that may be shared.
- Purpose. Define the intended evaluation or work precisely enough to distinguish permitted use from unrelated use.
- Recipients. Identify roles that need access and how onward sharing will be controlled.
- Timing. Explain when sharing starts, how long the project may last and what should happen afterward.
- Jurisdictions. State where the parties and work are located so counsel can assess practical issues.
Include previous disclosures. A lawyer cannot evaluate a prospective agreement accurately if important files were already sent without the expected arrangement. Be factual about what happened rather than describing it as “probably confidential.”
A hypothetical evaluation project
An inventor wants a design consultancy to evaluate a mechanism. The consultancy plans to use an outside simulation specialist. A generic NDA names only the consultancy and says information is confidential, but the inventor has not discussed the specialist or the intended use of the simulation results.
The briefing should identify the specialist's role, the files needed, whether onward sharing is allowed, and how obligations flow to recipients. It should also separate the confidentiality question from ownership of the new simulation work and any design improvements. Those may require additional engagement terms.
The inventor does not need to draft complex legal language alone. The useful work is to expose the operational facts so counsel can prepare or review terms that fit them. A clear process often prevents more confusion than adding severe-sounding penalties to an unsuitable form.
Topics to discuss with counsel
| Topic | Practical question |
|---|---|
| Definition | Can both sides identify the covered information, including oral disclosures? |
| Permitted use | Is the information limited to the agreed evaluation or work? |
| Exclusions | How are public, previously known or independently developed information handled? |
| Recipients | Who may receive it and under what obligations? |
| End of project | What return, deletion, retention and continuing duties are appropriate? |
| Disputes | Are governing law and remedies practical for the relationship? |
Read beyond the title
A document called “NDA” may contain other provisions, such as feedback rights, licenses, residual-knowledge language, restrictions on competition or dispute terms. Do not assume those are standard or harmless. Ask counsel to explain their practical effect on the invention and future business.
Conversely, not every exclusion is a loophole. Legitimate recipients may already know information or develop something independently. The goal is a workable agreement reflecting the exchange, not a promise that no similar idea can ever exist elsewhere.
Make the agreement operational
After signing, use consistent labels, named recipients and a disclosure register. Train anyone presenting the invention on what may be shared. Save the signed version and confirm the correct party signed it. If the project's purpose changes, review whether the existing arrangement still fits.
Plan for the end of the relationship. Samples, backup copies and legally required records may need specific treatment. An unrealistic deletion demand can be difficult to verify or perform. Discuss a practical process rather than assuming a final email makes all copies disappear.
Diagnose false confidence
- The agreement is signed, but files are sent to an unrelated entity.
- The permitted purpose is unclear or broader than the intended evaluation.
- No one knows which version of the agreement applies.
- The inventor assumes confidentiality also transfers ownership.
- Public presentations continue to reveal the same information.
- The contract's requirements do not match the supplier's actual workflow.
The deliverable for review
Prepare the information-flow map, party details, planned file package, previous disclosures and questions about unusual terms. Ask the lawyer to distinguish confidentiality obligations from ownership, licensing and development terms. Then implement the agreed process in day-to-day sharing.
This is educational guidance, not legal advice or a contract template. Enforceability and suitable drafting depend on the facts and applicable law.