Before you share pricing, product plans, customer information, source code, or other sensitive business material, use this NDA checklist to confirm that the agreement identifies the right parties, defines confidentiality clearly, sets workable limits, and explains what happens at the end. An NDA can support a sensible information-sharing process, but it should match the specific relationship and the law governing the agreement.
Overview
A non-disclosure agreement (NDA), also called a confidentiality agreement, sets rules for handling information that one or more parties share. Small businesses commonly use NDAs when speaking with contractors, employees, potential investors, manufacturers, strategic partners, software developers, or prospective buyers.
A useful NDA is not simply a document containing the word “confidential.” It should answer practical questions: Who is bound? What information is covered? What may the recipient do with it? How long do the obligations last? What information is excluded? What happens if disclosure is legally required? What must happen to documents and copies when the relationship ends?
Use the following checklist before signing an NDA template or accepting an agreement supplied by another party. If the information is especially valuable, the transaction is cross-border, or the agreement includes restrictive provisions beyond confidentiality, consider obtaining advice from a qualified lawyer in the relevant jurisdiction.
Mutual versus one-way NDA
| Type | When it fits | Points to check |
|---|---|---|
| One-way NDA | One party mainly discloses information to the other, such as when hiring a contractor to review internal materials. | Confirm that the disclosing party is accurately identified and that the recipient’s permitted use is narrow enough. |
| Mutual NDA | Both parties expect to exchange confidential information, such as during a partnership discussion or joint project. | Check that confidentiality duties apply fairly to both parties and that each party’s information receives comparable protection. |
Checklist by scenario
1. Identify the parties and the business purpose
- Use the complete legal names of the parties, including the correct company entity and any relevant trading name.
- Confirm addresses or notice details where the agreement requires formal notices.
- State the relationship or project that explains why information is being shared.
- Check whether affiliates, employees, officers, contractors, advisers, or subcontractors may receive the information.
- Make sure each party has authority to sign and disclose the information covered by the agreement.
A vague purpose can make it harder to decide whether a later use was permitted. For example, “business discussions” may be less useful than a description of the proposed product evaluation, supplier relationship, or investment review.
2. Define confidential information
- Include the categories that matter to the business: designs, formulas, source code, product roadmaps, pricing, forecasts, customer lists, supplier terms, security information, processes, and business plans.
- Cover information shared orally, visually, electronically, and in physical documents if those formats will be used.
- Explain whether information must be marked confidential or whether its nature and the circumstances of disclosure are enough.
- Address information disclosed before the signing date if the parties intend to protect it.
- Consider whether notes, analyses, summaries, models, or other materials created from the original information are also covered.
The definition should be broad enough to reflect how the business actually operates, but not so unclear that the recipient cannot tell what obligations apply. A practical NDA protects identifiable business information rather than attempting to label every communication confidential without distinction.
3. Include sensible exclusions
Most confidentiality agreements exclude information that the recipient can show:
- was already publicly available without a breach of the agreement;
- was lawfully known before disclosure;
- was received lawfully from another source without a confidentiality duty;
- was independently developed without using the protected information; or
- must be disclosed under law, regulation, or a valid legal process.
Check who carries the burden of proving an exclusion and what records may be used to prove it. The agreement should also explain whether legally required disclosure requires advance notice, where notice is legally permitted, and whether the recipient must disclose only the required portion.
4. Set permitted use and access controls
- Limit use to the stated business purpose.
- Require reasonable care, or a clearly stated standard of protection, for storing and handling the information.
- Limit access to people who need the information for the permitted purpose.
- Require those recipients to be subject to confidentiality duties appropriate to the situation.
- Decide whether copying, reverse engineering, testing, or data extraction is prohibited or permitted for the project.
For a software or product review, the agreement may need more detail about testing environments, screenshots, credentials, demonstrations, or technical access. For an employee or contractor, the NDA should work alongside employment, intellectual property, security, and data protection documents rather than contradicting them.
5. Choose the term carefully
Separate the agreement’s duration from the period during which particular information must remain confidential. Some information may need protection only during negotiations, while trade secrets or similarly sensitive material may require protection for as long as they remain legally protectable and confidential. Avoid inserting a standard term without checking the type of information, the project timeline, and the governing law.
6. Cover return, deletion, and retention
- State when the disclosing party may request return or destruction.
- Include electronic files, backups, extracts, notes, and copies where appropriate.
- Explain whether the recipient must certify deletion or destruction.
- Address records that must be retained for legal, regulatory, accounting, security, or backup purposes.
- Clarify that retained material remains subject to confidentiality duties.
7. Review remedies and surrounding clauses
Look for provisions concerning injunctive or other equitable relief, liability, indemnity, dispute resolution, governing law, jurisdiction, notices, assignment, amendments, and entire agreement language. An NDA may also contain non-solicitation, non-compete, intellectual property, or publicity restrictions. These are separate issues and deserve separate review; do not assume they are ordinary confidentiality terms.
What to double-check
- Entity details: Confirm spelling, company status, signatory authority, and whether the correct parent or subsidiary is named.
- Information flow: Map what will be shared, by whom, through which systems, and with which advisers or subcontractors.
- Personal data: If the information includes customer, employee, or other personal data, review the separate data protection obligations. An NDA does not replace a data processing agreement, privacy notice, security assessment, or other required documentation.
- Intellectual property: Confirm that confidentiality is not being confused with ownership. An NDA may protect information without transferring or assigning intellectual property rights.
- Cross-border issues: Check governing law, dispute location, language, transfer restrictions, and practical enforcement concerns when parties operate in different countries.
- Conflict between documents: Compare the NDA with employment agreements, contractor terms, master services agreements, procurement terms, and project statements of work.
- Operational fit: Make sure the business can actually follow the storage, access, deletion, marking, and notice requirements.
Keep a short signing record: the final version, signing date, parties, project name, information categories, permitted recipients, and any negotiated exceptions. That record can make later contract review and offboarding more reliable.
Common mistakes
- Using a generic NDA without editing it: Placeholder names, wrong entities, unsuitable jurisdictions, and irrelevant clauses can create avoidable uncertainty.
- Defining everything as confidential: Overbroad wording may be difficult to administer and may not reflect what the parties reasonably intended to protect.
- Ignoring prior disclosures: If discussions have already begun, decide whether earlier information is covered and document that choice.
- Allowing unrestricted internal sharing: A recipient should not automatically be able to distribute information to every employee, affiliate, consultant, or vendor.
- Assuming an NDA protects trade secrets by itself: Confidentiality language works best with sensible access controls, security practices, employee training, and documented handling procedures.
- Adding unrelated restrictions without review: Non-compete, non-solicitation, exclusivity, and ownership terms can have different legal and commercial consequences.
- Failing to plan the end of the relationship: Decide who will retrieve materials, close access, delete files, and preserve records before the project ends.
When to revisit
Recheck an NDA before each new disclosure relationship, not only when a business adopts a new template. Revisit it when the project scope changes, a new class of information will be shared, a contractor or subcontractor is added, the parties begin exchanging personal data, or the business moves into another country or legal entity.
Use seasonal planning cycles to review active agreements and identify NDAs approaching their end dates or information-destruction deadlines. Also review the workflow when your file-storage, collaboration, customer relationship, or access-management tools change. The document should match actual information handling.
As a final action, complete this short pre-signing check: identify the parties; write the business purpose; list the information categories; select mutual or one-way protection; confirm exclusions; set permitted access and use; choose the confidentiality term; address legally required disclosure; plan return or deletion; compare related contracts; and record the final signed version. If any answer is unclear or the NDA includes significant restrictions beyond confidentiality, pause before sharing sensitive information and seek jurisdiction-appropriate legal advice.