NDA Template Guide: How to Choose, Customize, and Sign a Non-Disclosure Agreement

Overview

A non-disclosure agreement, commonly called an NDA or confidentiality agreement, sets rules for handling information that one or more parties do not want shared or misused. Businesses often use NDAs during proposed partnerships, hiring discussions, product development, investments, sales negotiations, and work with contractors or professional advisers.

An NDA template is not automatically suitable simply because it looks complete. Templates differ in scope, governing law, definitions, exclusions, and enforcement terms. Start by identifying the commercial situation and then choose the document that reflects it.

Mutual NDA or one-way NDA?

Use a one-way NDA when only one party is expected to disclose confidential information. For example, a company may share product plans with a contractor, or a seller may provide financial information to a potential buyer.

Use a mutual NDA when both parties may disclose sensitive information. This is common in joint project discussions, strategic partnerships, acquisitions, and service relationships where each side will share non-public material.

The agreement should not describe the relationship as mutual if the operative clauses protect only one party. Compare the definition of confidential information, permitted uses, return obligations, and remedies on both sides.

What an NDA usually covers

A well-structured non-disclosure agreement typically identifies the parties, explains what counts as confidential information, states how the recipient may use that information, lists exclusions, sets confidentiality obligations, addresses disclosures required by law, and establishes the agreement's duration. It may also cover return or deletion of materials, ownership of intellectual property, notices, dispute provisions, and available remedies.

An NDA is not usually a substitute for a broader services agreement, employment agreement, intellectual property assignment, data processing agreement, or security schedule. If the relationship involves personal data, regulated information, ownership of work product, or access to systems, check whether additional documents are needed.

Checklist by scenario

Before sharing information with a contractor or freelancer

• Confirm the legal name and address of the business or individual receiving the information.
• Describe the project or permitted purpose precisely enough to prevent unrelated use.
• Identify whether the contractor may share information with employees, subcontractors, or professional advisers.
• Require those additional recipients to be bound by confidentiality duties that are at least as protective.
• Consider whether a separate intellectual property agreement is needed for work created during the engagement.
• Specify what happens to files, credentials, samples, and copies when the project ends.

Before a partnership, investment, or acquisition discussion

• Choose a mutual NDA if both sides will provide non-public information.
• Define the evaluation purpose, such as assessing a proposed transaction or collaboration.
• Check whether the document addresses representatives, advisers, financing sources, or affiliated companies.
• Review any restrictions on contacting customers, employees, suppliers, or other business relationships.
• Make sure the NDA does not accidentally create a commitment to complete the proposed transaction.
• Confirm that ownership of pre-existing materials remains with the party that supplied them.

Before sharing product, technical, or trade secret information

• List the categories of information that require protection, such as source code, designs, formulas, test results, specifications, or security details.
• Limit access to people who need the information for the stated purpose.
• Include reasonable handling requirements for electronic and physical materials.
• Check whether the recipient can use general knowledge, skills, or independently developed information without restriction.
• Coordinate the NDA with internal access controls, labeling practices, and document retention procedures.
• Consider whether the agreement should distinguish continuing protection for trade secrets from a shorter period for ordinary confidential information.

Before signing any NDA template

• Complete every blank, remove drafting notes, and resolve bracketed alternatives.
• Verify the signing authority of each organization and use consistent legal names throughout.
• Check the effective date, signature date, and any date on which disclosure may begin.
• Confirm that the governing law and dispute forum are appropriate for the parties and transaction.
• Ensure that the final signed version is stored where authorized users can retrieve it.

What to double-check

The definition of confidential information

The definition should be broad enough to protect the information that actually matters, but clear enough for the recipient to understand its obligations. Some agreements cover information marked confidential; others also cover information that should reasonably be understood as confidential based on its nature or the circumstances of disclosure. If oral disclosures are included, check whether the agreement requires written confirmation afterward.

Exclusions

Common exclusions may include information that was already known to the recipient, becomes public without a breach, is received lawfully from another source, is independently developed, or must be disclosed under legal process. Read these exclusions carefully. The agreement may require the recipient to prove that an exclusion applies, and that burden can affect how a dispute is handled.

Duration and continuing duties

Separate the duration of the agreement from the duration of confidentiality obligations. An NDA may stop accepting new disclosures after a set period while duties for information already received continue. The appropriate period depends on the information, the relationship, and applicable law. Avoid inserting a time period without considering whether the information could remain commercially sensitive longer.

Permitted use and compelled disclosure

The recipient should be allowed to use confidential information only for the stated purpose. Check the procedure for legally required disclosure: it may require prompt notice where legally permitted, cooperation in seeking protective treatment, and disclosure of only the required portion.

Remedies and practical controls

Review provisions about injunctive relief, damages, attorneys' fees, liability limits, and dispute resolution. The wording can have significant consequences and varies by jurisdiction. Also confirm that the contract's legal promises match the practical workflow. An NDA cannot replace sensible permission settings, secure transfer methods, employee training, or an offboarding process.

For a broader clause-by-clause review, use a contract review checklist alongside this NDA checklist. If the agreement will involve personal data, review the relevant GDPR compliance checklist as a separate exercise rather than assuming confidentiality terms address data protection requirements.

Common mistakes

• Using the wrong party name: A trading name, individual employee, or parent company may not be the intended contracting party.
• Relying on a vague purpose: Phrases such as “business discussions” may not clearly limit use. Describe the project or evaluation.
• Protecting only written material: Meetings, demonstrations, calls, prototypes, and verbal explanations may also contain sensitive information.
• Ignoring representatives: An agreement should explain who may access information and who is responsible if a permitted recipient mishandles it.
• Confusing confidentiality with ownership: Keeping information secret does not necessarily transfer or protect intellectual property rights.
• Signing after disclosure: Whenever possible, complete the NDA before sharing sensitive information and record when it becomes effective.
• Leaving template language unresolved: Unselected options, comments, placeholders, and inconsistent defined terms can create avoidable uncertainty.
• Assuming every NDA is enforceable everywhere: Enforceability depends on the wording, facts, and applicable jurisdiction. Obtain qualified legal advice for a high-value, cross-border, employment-related, or contentious situation.

When to revisit

Review your NDA process whenever the underlying transaction changes. Revisit the document before a new seasonal planning cycle, a product launch, a funding or acquisition discussion, a major contractor engagement, or a partnership involving new categories of information.

Update your workflow when your tools or access systems change. A move to a new file-sharing platform, customer relationship system, code repository, or document-signing tool may require changes to access permissions, approved representatives, retention practices, or return-and-deletion procedures.

Keep a simple record of the signed version, parties, effective date, permitted purpose, expiration or review date, and any related agreements. Before acting, run this final check:

1. Have the correct parties signed?
2. Does the NDA match a one-way or mutual disclosure?
3. Is the confidential information and permitted purpose clear?
4. Are exclusions, compelled disclosure, duration, and remedies understood?
5. Are practical security and offboarding steps in place?
6. Does the situation call for legal review rather than a generic template?

A reusable NDA template can streamline routine discussions, but it should be treated as a starting point. Customize it to the transaction, keep the final version accessible, and revisit both the contract and the workflow when the information, parties, or tools change.