Memorandum of Understanding Ngo Sample

SOP: Drafting and Execution of Memorandum of Understanding (MOU) for NGOs

Document ID: TR-LEG-MOU-001
Effective Date: 2023-10-27
Version: 1.0
Review Cadence: Annual

1. Executive Summary & Purpose

This SOP establishes the standardized workflow for drafting, reviewing, and executing a Memorandum of Understanding (MOU) between Template Registry and external NGO partners. The purpose is to define non-binding collaborative frameworks, resource sharing, and operational expectations while mitigating legal risk and ensuring alignment with organizational mission.

2. Scope & Prerequisites

• Scope: Applies to all cross-sector partnerships where intent is established but legal obligation of funding is not yet defined.
• Prerequisites:
  • Validated NGO Tax-Exempt Status (IRS 501(c)(3) or equivalent).
  • Document Management System (DMS) access (e.g., DocuSign, SharePoint).
  • Legal Counsel approval (required for all external agreements).

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase I: Preparation and Drafting

• Conduct preliminary due diligence on the partner NGO.
• Define project scope, deliverables, and timeline.
• Draft MOU using the standard Template Registry MOU boilerplate.
• Insert specific project milestones in the "Scope of Collaboration" clause.

Phase II: Internal Review and Negotiation

• Submit draft to Legal Counsel for risk assessment.
• Conduct collaborative redlining via track-changes in shared workspace.
• Finalize the "Financial Implications" clause (explicitly stating non-binding nature).
• Secure internal executive signature.

Phase III: External Execution

• Transmit finalized MOU to the NGO authorized signatory.
• Utilize secure e-signature platform (DocuSign/Adobe Sign).
• Verify NGO signatory authority matches their corporate bylaws.
• File finalized, countersigned PDF in the central Document Repository.

5. Quality Assurance & Pro-Tips

• Best Practice: Always include an "Exit Clause." Partnerships must be terminable with 30-day written notice to avoid indefinite liability.
• Common Pitfall: Drafting language that implies a "Contract" rather than an "MOU." Avoid "shall" or "must" regarding payment; use "intent to provide" or "aims to collaborate."
• Metric Thresholds:
  • Legal review cycle time: < 72 hours.
  • Execution turnaround: < 5 business days from final draft.

6. Frequently Asked Questions (FAQ)

Q: Is an MOU legally binding?
A: Generally, no. An MOU is a statement of intent. However, specific clauses within an MOU (such as Confidentiality, Data Privacy, or Intellectual Property) can be made legally binding if explicitly drafted as such. Consult Legal for specific language.

Q: What if the NGO does not have a formal MOU template?
A: Do not accept external templates without a comprehensive review by the Chief Architect office. Utilize the internal Template Registry MOU boilerplate to maintain version control and risk parity.

Q: How do we handle changes to the project scope after signing?
A: Do not rely on verbal agreements. Execute an "Addendum to MOU" signed by both parties to maintain the audit trail.

End of Document. Unauthorized distribution is prohibited.