Standard Operating Procedure: Mutual Non-Disclosure Agreement (MNDA) Execution

This Standard Operating Procedure (SOP) outlines the standardized process for initiating, reviewing, and executing a Mutual Non-Disclosure Agreement (MNDA). The objective is to ensure that all proprietary information exchanged between our organization and external parties is legally protected, risks are mitigated, and institutional knowledge remains confidential throughout the duration of any partnership or business inquiry. This SOP must be followed for every instance where two parties intend to exchange sensitive data.

Phase 1: Initiation and Template Selection

• Confirm the business need for an MNDA (e.g., potential partnership, joint venture, or vendor evaluation).
• Retrieve the current, Legal-approved MNDA master template from the internal document repository.
• Verify that the "Mutual" nature is appropriate; if only one party is disclosing information, utilize a Unilateral NDA instead.
• Identify the legal entities involved (ensure full legal names and jurisdictions are accurate).

Phase 2: Drafting and Customization

• Enter the legal names and addresses of both parties in the preamble.
• Define the "Purpose" of the disclosure specifically—avoid overly broad language to ensure enforceability.
• Specify the "Confidential Information" scope (include technical, financial, and strategic data).
• Set the "Term of Agreement" (e.g., 2 years) and the "Survival Period" for confidentiality obligations (e.g., 3–5 years post-termination).
• Ensure the "Governing Law and Jurisdiction" clause aligns with company preference (typically the state of incorporation).
• Review the "Return or Destruction of Materials" clause to confirm compliance with internal data management policies.

Phase 3: Review and Internal Approval

• Submit the drafted MNDA to the Legal Department or designated contract manager for review via the tracking system.
• Highlight any deviations from the standard template (e.g., non-standard indemnity or non-solicitation clauses).
• Obtain sign-off from the Department Head who owns the relationship with the counterparty.
• Finalize the document in PDF format to prevent unauthorized edits.

Phase 4: Execution and Archiving

• Send the final PDF to the counterparty using the designated e-signature platform (e.g., DocuSign, Adobe Sign).
• Monitor the e-signature workflow and send reminders if the document remains unsigned beyond 48 hours.
• Once fully executed, save the MNDA in the centralized contract management database.
• Notify the relevant project leads that the agreement is active and that information sharing may commence.

Pro Tips & Pitfalls

• Pro Tip: Always include a "Residuals Clause" if possible, which allows employees to use the general knowledge retained in their minds, provided they do not consciously misuse confidential information.
• Pitfall: Avoid "Perpetual" terms. Many courts view indefinite confidentiality obligations as unreasonable and unenforceable; always attach a clear expiration date.
• Pro Tip: Clearly define "Confidential" to include oral disclosures, provided they are summarized in writing within 30 days of the meeting.
• Pitfall: Do not use an MNDA as a substitute for a full Commercial Agreement; MNDAs protect data, not business outcomes or revenue models.

Frequently Asked Questions (FAQ)

Q: Can we change the jurisdiction clause? A: Changes to governing law should be avoided. If a counterparty insists on their home jurisdiction, it must be escalated to the Legal Department for a risk assessment, as it increases our legal costs in the event of a dispute.

Q: Does an MNDA protect us from a patent being stolen? A: An MNDA provides contractual recourse if the other party breaches confidentiality, but it is not a substitute for formal intellectual property (IP) protection. Always file for provisional patents prior to sharing core technical IP.

Q: What happens if the counterparty refuses to sign our template? A: If they provide their own template, do not sign it immediately. Submit their version to the Legal Department for a "redline" comparison against our standard terms to identify unfavorable clauses.