Skip to content

Free Government Template

Free Inter-Agency MOU

MOU between [agencies]

Purpose & Authority Responsibilities Data Governance Security Requirements Funding & Resources Duration & Termination Amendment Process

Inter-Agency MOU

Use this template to mOU between [agencies].

Template Metadata

Field Details
Category Government
Owner [Team or owner]
Version [Version number]
Effective Date [Date]
Review Cycle [Monthly / Quarterly / Annual / Event-based]
Status [Draft / In Review / Approved]

Purpose & Authority

State the purpose of the MOU and the legal authority under which each party enters the agreement. Reference enabling statutes, executive orders, or agency mandates.

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Responsibilities

Create a table listing each agency's specific responsibilities, deliverables, and performance expectations. Clearly delineate which party does what.

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Data Governance

Define data sharing protocols, data ownership, permitted uses, retention periods, and destruction procedures. Reference applicable data privacy laws (HIPAA, CJIS, FERPA, etc.).

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Security Requirements

Specify technical and administrative security controls required for shared data and systems. Include encryption standards, access controls, audit logging, and breach notification obligations.

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Funding & Resources

Describe how costs are shared or borne. Specify whether the MOU involves transfer of funds, in-kind contributions, or shared infrastructure.

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Duration & Termination

State the effective date, duration, renewal provisions, and termination procedures including required notice period and obligations upon termination.

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Amendment Process

Describe how the MOU may be amended, who has authority to approve changes, and the required format for amendments. Use formal language. Include signature blocks placeholder at the end.

Item Details Owner Status
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]
[Item or requirement] [Describe the relevant detail, evidence, or decision] [Owner] [Open / Complete]

Notes

[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]

Review and Signoff

Document review conclusions, approvals, unresolved items, and next review date.

Role Name Date Notes
Preparer [Name] [Date] [Notes]
Reviewer [Name] [Date] [Notes]
Approver [Name] [Date] [Notes]

Template Structure

What the Inter-Agency MOU Includes

Use this government template as a starting point, then customize each section to match your internal workflow, evidence, and signoff needs.

1

Purpose & Authority

State the purpose of the MOU and the legal authority under which each party enters the agreement. Reference enabling statutes, executive orders, or agency mandates.

2

Responsibilities

Create a table listing each agency's specific responsibilities, deliverables, and performance expectations. Clearly delineate which party does what.

3

Data Governance

Define data sharing protocols, data ownership, permitted uses, retention periods, and destruction procedures. Reference applicable data privacy laws (HIPAA, CJIS, FERPA, etc.).

4

Security Requirements

Specify technical and administrative security controls required for shared data and systems. Include encryption standards, access controls, audit logging, and breach notification obligations.

5

Funding & Resources

Describe how costs are shared or borne. Specify whether the MOU involves transfer of funds, in-kind contributions, or shared infrastructure.

6

Duration & Termination

State the effective date, duration, renewal provisions, and termination procedures including required notice period and obligations upon termination.

7

Amendment Process

Describe how the MOU may be amended, who has authority to approve changes, and the required format for amendments. Use formal language. Include signature blocks placeholder at the end.

Recommended Structure

Write an Inter-Agency Memorandum of Understanding in a formal legal-governmental tone. Structure with:

Purpose & Authority

State the purpose of the MOU and the legal authority under which each party enters the agreement. Reference enabling statutes, executive orders, or agency mandates.

Responsibilities

Create a table listing each agency's specific responsibilities, deliverables, and performance expectations. Clearly delineate which party does what.

Data Governance

Define data sharing protocols, data ownership, permitted uses, retention periods, and destruction procedures. Reference applicable data privacy laws (HIPAA, CJIS, FERPA, etc.).

Security Requirements

Specify technical and administrative security controls required for shared data and systems. Include encryption standards, access controls, audit logging, and breach notification obligations.

Funding & Resources

Describe how costs are shared or borne. Specify whether the MOU involves transfer of funds, in-kind contributions, or shared infrastructure.

Duration & Termination

State the effective date, duration, renewal provisions, and termination procedures including required notice period and obligations upon termination.

Amendment Process

Describe how the MOU may be amended, who has authority to approve changes, and the required format for amendments.

Use formal language. Include signature blocks placeholder at the end.

Example Filled Template

Memorandum of Understanding — Data Sharing Between Health Department and Emergency Services

Parties: County Department of Public Health ("Health") and County Department of Emergency Services ("EMS") | MOU Number: MOU-2026-IA-0015 | Effective Date: March 1, 2026

Purpose & Authority

This Memorandum of Understanding establishes the framework for sharing protected health information (PHI) and emergency response data between Health and EMS to improve coordinated response to public health emergencies, disease outbreaks, and mass casualty incidents.

Authority: - Health: State Health and Safety Code § 101000 et seq.; County Code Chapter 4.60 - EMS: State Government Code § 8550 et seq. (Emergency Services Act); County Code Chapter 2.68 - Data sharing: HIPAA 45 CFR § 164.512(b) (public health activities) and (j) (law enforcement)

Responsibilities

Responsibility Health Department Emergency Services
Disease surveillance data Provide de-identified outbreak data within 4 hours of confirmed cluster Integrate data into EOC situational awareness dashboard
EMS patient care reports N/A Provide patient care reports for syndromic surveillance within 24 hours
Joint training exercises Co-develop annual tabletop exercise scenarios Provide EOC facilities and ICS staffing for exercises
Epidemiological support Deploy epidemiologist to EOC during Level 1/2 activations Provide EOC workstation and communications access
Public messaging Draft health advisories and clinical guidance Disseminate via emergency alert systems and PIO channels
After-action reviews Co-author public health sections of AAR Coordinate AAR process and corrective action tracking

Data Governance

  • Permitted Uses: Shared data may be used solely for emergency preparedness, disease surveillance, and coordinated incident response. Secondary use for research requires separate IRB approval.
  • Data Ownership: Each agency retains ownership of data it originates. Derived datasets are jointly owned.
  • Retention: Shared data retained for 7 years per state records retention schedule, then securely destroyed.
  • Privacy Compliance: All data sharing complies with HIPAA Privacy Rule, state health information privacy statutes, and CJIS Security Policy where criminal justice data is involved.

Security Requirements

Control Requirement
Encryption in transit TLS 1.2 or higher for all data transmissions
Encryption at rest AES-256 for stored PHI
Access control Role-based access; minimum necessary principle; multi-factor authentication
Audit logging All access to shared data logged with user ID, timestamp, and action
Background checks All personnel with PHI access must pass criminal background check
Breach notification Notify the other party within 24 hours of a suspected data breach
Annual security review Joint security review conducted annually; findings shared within 30 days

Funding & Resources

This MOU does not involve the transfer of funds. Each party bears its own costs for implementation. Shared infrastructure (secure file transfer server) is hosted by EMS and maintained at EMS expense. Health reimburses EMS $12,000 annually for server hosting costs via inter-departmental transfer.

Duration & Termination

  • Duration: Three (3) years from the effective date.
  • Renewal: Automatically renews for successive one-year terms unless either party provides written notice of non-renewal at least 90 days before expiration.
  • Termination: Either party may terminate with 60 days written notice to the other party's designated representative. Upon termination, each party shall return or securely destroy all shared data within 30 days and provide written certification of destruction.

Amendment Process

Amendments require written agreement signed by authorized representatives of both parties (Division Director level or above). Amendments are documented using Form IA-200 and appended to this MOU. Administrative changes (contact information, designated representatives) may be made by written notice without formal amendment.


Authorized Signatures:

Health Department: ______ Date: ____

Emergency Services: ______ Date: ____

Skip Manual Drafting

Generate a Inter-Agency MOU from a Video

Record a walkthrough, training session, or process demonstration. Docsie AI turns it into structured documentation using this template as the starting framework.

Use the template manually, or let Docsie generate the first draft from source footage.

DOCX, PDF, and Markdown downloads
Works with process and training videos

Template FAQ

Inter-Agency MOU FAQ

Common questions about using and generating a inter-Agency MOU.

Using This Template

Q: What is a inter-Agency MOU?

A: A inter-Agency MOU is a structured document for mou between [agencies].

Q: Can I download this inter-Agency MOU as Word or PDF?

A: Yes. This page includes free downloads in DOCX, PDF, and Markdown formats so you can edit, share, or import the template into your documentation system.

Q: Can Docsie generate this from a video?

A: Yes. Upload a process walkthrough, training recording, or screen capture to Docsie, then use this template structure to generate a first draft automatically.