Memorandum of Understanding Navy Template

Standard Operating Procedure: Memorandum of Understanding (MOU) Generation

Template Registry Engineering Division

---

1. Document Control Block

---

2. Executive Summary & Purpose

This SOP establishes the standardized workflow for drafting a Memorandum of Understanding (MOU) within Department of the Navy (DoN) administrative frameworks. The purpose is to ensure all inter-agency or intra-departmental agreements adhere to SECNAVINST 5000.x series standards, minimizing legal ambiguity and ensuring structural uniformity across the Registry.

---

3. Scope & Prerequisites

• Scope: Applies to all personnel drafting non-binding agreements between DoN entities and external stakeholders.
• Prerequisites:
  • Access to DON Correspondence Manual (SECNAV M-5216.5).
  • Valid Common Access Card (CAC) for digital signing.
  • Hardware: Enterprise workstation with Adobe Acrobat Pro DC.
  • Software: Microsoft Word (Template: NAV_MOU_STND_V1.dotx).

---

4. Roles & Responsibilities (RACI)

---

5. Step-by-Step Procedure

Phase I: Drafting

• Initialize document using the authorized NAV_MOU_STND_V1.dotx template.
• Define the "Purpose" section with specific reference to statutory authority.
• Establish "Responsibilities" using clear, actionable verbs (e.g., "shall provide," "will coordinate").
• Ensure "Terms of Agreement" include effective date and termination clauses.

Phase II: Routing and Legal Review

• Route draft through local Office of General Counsel (OGC) via official correspondence tracking system.
• Address all redline comments from OGC within 48 business hours.
• Update document version control metadata in the footer.

Phase III: Finalization & Execution

• Perform a final sanity check against the SECNAV M-5216.5 formatting standards (margins, font: Courier New 12pt).
• Obtain signature via DoD SAFE or local digital workflow tool.
• Upload signed PDF/A to the Template Registry repository.

---

6. Quality Assurance & Pro-Tips

• Metric Thresholds: All MOUs must undergo a minimum of two peer reviews before OGC submission. Any document returned for "major revision" triggers a reset of the QA counter.
• Pro-Tip 1: Always verify the specific signatory authority. If the MOU commits funds, it is technically a Memorandum of Agreement (MOA); ensure the document title matches its financial nature.
• Pro-Tip 2: Keep paragraphs numbered at the decimal level (1.1, 1.2) for easy reference during legal mediation.
• Common Pitfall: Drafting a binding commitment for resource allocation when no statutory authority exists. Avoid phrases like "will guarantee funding."

---

7. Frequently Asked Questions (FAQ)

Q: Can I use boilerplate language for the "Termination" clause? A: Yes. Use the standard "Termination for Convenience" clause provided in the NAV_MOU_STND_V1.dotx boilerplate to ensure consistency with DoN policy.

Q: Does an MOU require an expiration date if it is an ongoing partnership? A: Yes. Best practice dictates a maximum term of 5 years with an automatic review trigger at the 4-year mark to prevent "agreement rot."

Q: What is the primary indicator that an MOU needs to be converted to an MOA? A: The presence of an exchange of value (funds, personnel transfers, or hardware). If resources are shifting, it is an MOA and requires a fiscal review.

---

End of SOP Authorized by: Julian Vance, Chief Architect, Template Registry