Writing a Memorandum of Understanding Template

SOP-TR-882: Generation of Memoranda of Understanding (MoU)

Document Control Block

• Document ID: SOP-TR-882
• Effective Date: 2023-10-27
• Version: 1.0.4
• Review Cadence: Biennial (Every 24 months)

1. Executive Summary & Purpose

This procedure defines the standardized workflow for drafting, reviewing, and finalizing an MoU. The purpose is to ensure that all non-binding collaborative agreements generated by Template Registry meet institutional legal standards, maintain terminological consistency, and clearly delineate the intent of participating parties.

2. Scope & Prerequisites

• Scope: Applies to all cross-departmental and inter-organizational agreements where "best effort" commitments are required. Does not apply to legally binding contracts or Service Level Agreements (SLAs).
• Prerequisites:
  • Access to the Standard Clause Repository (SCR).
  • Defined objective statement from project stakeholders.
  • Software: DocuSign (Signing), SharePoint/OneDrive (Versioning), Word/Google Docs (Drafting).
  • PPE: N/A.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Requirement Elicitation

• Define the specific "Non-Binding" intent (e.g., information sharing, research cooperation).
• Identify all participating entities and authorized representatives.
• Establish the expiration date or "trigger for termination" clause.

Phase II: Template Construction

• Open authorized TR_MOU_TEMPLATE_V1 file.
• Insert formal definitions from the SCR to prevent ambiguity.
• Draft the "Terms of Understanding" section—ensure the language is aspirational, not promissory (e.g., use "shall endeavor to" instead of "will").
• Include the "Non-Binding Clause" as a primary header to mitigate liability.

Phase III: Peer Review & Legal Scrub

• Route document to Legal Counsel for a "Binding-Language Audit."
• Verify that no financial penalties or liquidated damages are present.
• Cross-reference signatures with the current authorized signatory list.

Phase IV: Finalization & Distribution

• Convert finalized draft to PDF/A format.
• Initialize document workflow in DocuSign.
• File signed original in the Central Registry Archive.

5. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Time-to-Draft: Under 90 minutes for standard templates.
  • Legal Rejection Rate: Target < 5% per cycle.
• Pro-Tips:
  • The "Intent" Test: If an MoU reads like a contract, it is a liability. Replace "Must" with "Shall endeavor to" or "Intends to."
  • Formatting: Never use "shall" to describe a future event; use it only for obligation. In MoUs, avoid "shall" entirely.
• Common Pitfalls: Including "Indemnification" or "Choice of Law" clauses, which effectively convert the document into a binding contract.

6. Frequently Asked Questions

Q: Can we add a penalty clause to ensure performance? A: No. If a penalty clause is included, the document becomes a contract. Re-route the document through the Procurement/Legal team for formal contract processing.

Q: How do we handle changes in project leadership? A: The MoU is attached to the entity, not the individual. Ensure the "Successors and Assigns" section is included, or reference the specific project initiative rather than the specific department head.

Q: Does this require an internal audit? A: If the MoU involves data exchange (PII/PHI), it must be audited by the Data Protection Officer (DPO) prior to any signature.

Document Status: Authorized for immediate use. Author: Julian Vance, Chief Architect, Template Registry.