Standard Operating Procedure: Processing Mutual Non-Disclosure Agreements (MNDA)

This document outlines the standardized workflow for selecting, customizing, and executing a Mutual Non-Disclosure Agreement (MNDA) using a standard Word template. The primary objective is to ensure that proprietary information shared between organizations is adequately protected, legally binding, and consistent with company risk management policies. Adherence to this SOP minimizes legal exposure and streamlines the onboarding of new business partnerships.

Phase 1: Preparation and Template Selection

• Locate the "Approved MNDA Master Template" on the secure internal shared drive. Never use an unvetted document from an external web source.
• Confirm the scope of the potential partnership to ensure an MNDA is the correct instrument (as opposed to a Unilateral NDA or a Master Services Agreement).
• Verify that the counterparty is a registered entity.
• Assign a unique tracking ID to the draft file (e.g., MNDA_YYYYMMDD_CounterpartyName).

Phase 2: Drafting and Customization

• Open the Word template and enable "Track Changes" to maintain an audit trail.
• Populate the "Effective Date" field to align with the commencement of discussions.
• Define the "Purpose" clause clearly; narrow scopes are often more enforceable than broad, vague descriptions.
• Specify the "Term" of the agreement (typically 1–3 years) and the "Survival Period" for confidentiality obligations (usually 2–5 years post-termination).
• Identify the designated "Authorized Representatives" from both organizations who are permitted to receive confidential information.
• Insert the correct legal jurisdiction and governing law clause as advised by your internal legal department.

Phase 3: Review and Internal Approval

• Submit the draft to the department head for a business-case review.
• Flag any deviations from the master template for Legal Department review.
• Once internal approval is secured, save the document as a non-editable PDF to prevent unauthorized alterations before sending.

Phase 4: Execution and Archiving

• Send the PDF to the counterparty for review via a secure email channel.
• Facilitate any necessary negotiations; once terms are finalized, route the document through your organization’s e-signature platform (e.g., DocuSign or Adobe Sign).
• Once fully executed, save the final document in the Centralized Contracts Repository.
• Notify the relevant stakeholders of the agreement’s execution and any specific expiry dates.

Pro Tips & Pitfalls

• Pro Tip: Use defined terms (e.g., "Confidential Information," "Disclosing Party") consistently throughout the document to avoid ambiguity.
• Pro Tip: Include an "Injunctive Relief" clause to ensure you have the right to seek a court order to stop a breach immediately, rather than waiting for monetary damages.
• Pitfall: Over-broad definitions of confidential information can lead to court challenges. Keep the definition specific to the business project at hand.
• Pitfall: Forgetting to define the return or destruction of materials after the relationship ends. Always include a clause requiring the counterparty to certify the destruction of sensitive data upon request.

Frequently Asked Questions (FAQ)

1. Can we modify the standard MNDA template for every client? Minor modifications to names, dates, and purpose descriptions are standard. However, any substantive changes to liability, indemnification, or governing law require mandatory sign-off from the Legal Department.

2. What should I do if the other party insists on using their own MNDA template? Politely explain that your organization has a standardized, pre-approved template to maintain compliance. If they refuse, you must forward their template to Legal for a redline review, which will add time to the process.

3. Does an MNDA expire automatically? Yes, an MNDA typically has two timeframes: the term during which information can be exchanged, and the survival period during which the received information must remain confidential. Ensure both are clearly defined in the final document.