Skip to content

How to Write an MOU for Grants (Template + Checklist)

Updated 24 official sources

Quick Answer: A memorandum of understanding (MOU) for a grant application is a signed document between two or more organizations that spells out each party's roles, responsibilities, resource commitments, and timeline for a proposed project.

Full answer and how we checked it

Strong MOUs include 8 sections: purpose, scope, roles, resources, governance, communication, duration, and signatures. For nonprofit grant leads, the rule that matters most: of 16 FY2026 federal notices Grantsights checked, 10 required a signed MOU or signed letter of commitment from named partners, and only 4 accepted a letter of support for any partner.

Data note: Amounts may shift with annual appropriations.

Source review by Grantsights, October 18, 2026: Grantsights checked the partner-documentation rules in 16 FY2026 federal funding notices (10 from DOJ's Office on Violence Against Women, 3 from HRSA, and 3 from DOL), plus OVW's MOU and letter-of-support instructions and the 2 CFR 200 subaward rules. The full count and the rule quoted from each notice are in the 16-notice table below. The short version: when a partner controls referrals, data, facilities, services, or match, most of these notices want a signed MOU or a signed letter of commitment that names the partner's role, not a general endorsement. A school district providing student records and counseling space, for example, belongs in an MOU with FERPA-aware roles, not a one-paragraph support letter.

In this guide

A memorandum of understanding is one of the highest-value documents in a grant application, and it's one of the most frequently botched. A common pattern: applicants invest weeks in their project narrative and budget, then throw together a vague one-page MOU the night before the deadline.

Whether you're a grant writer coordinating with partner organizations, a PI formalizing a multi-site collaboration, or a nonprofit director documenting community partnerships for a federal application, this guide covers how to write an effective MOU.

That's a scoring problem. When your NOFO requires an MOU, reviewers are evaluating whether your partnership is real and operational. A thin MOU signals a partnership that exists on paper only. A detailed MOU with specific commitments, named staff, dollar amounts, and governance structures tells reviewers that both organizations have thought through the collaboration and are ready to execute.

At a minimum, an MOU should explain the need, name the organizations involved, and say why they need to work together. That's the floor. This guide will show you how to build an MOU that goes well beyond that floor and actually strengthens your application score.

What an MOU Is and Why It Matters to Reviewers

An MOU is a formal document that establishes a working relationship between two or more organizations for a specific purpose. In the context of grant applications, that purpose is your proposed project. The MOU tells reviewers three things they can't learn from your project narrative alone:

Both parties agree on the scope. Your narrative describes what you plan to do. The MOU confirms that your partner organization has read that plan and agrees to their part in it. That's a fundamentally different level of evidence.

Resources are actually committed. Anyone can claim a partnership in a narrative. An MOU signed by an authorized official puts that claim in writing with specific deliverables attached. Reviewers treat signed MOUs as documentary evidence of organizational commitment.

Governance is defined. When two organizations work together, questions will arise about decision-making authority, data ownership, communication protocols, and conflict resolution. An MOU that addresses these questions tells reviewers the partnership has been thought through, not just promised.

At agencies that use point-based scoring (SAMHSA, HRSA, ACF, DOJ), partnership documentation typically falls under "Organizational Capacity" or "Collaboration" criteria. Point weights vary by NOFO, so check the scoring table in your notice. A strong MOU directly supports those points. A weak one leaves them on the table.


Looking for your next grant?

About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.

No spam. Unsubscribe anytime.

MOU vs. Letter of Support vs. Subaward Agreement

These three documents serve different purposes, and using the wrong one is a compliance error that reviewers will catch.

MOU (Memorandum of Understanding)

An MOU documents a collaborative partnership where both organizations contribute resources and effort toward a shared project goal. It outlines roles, responsibilities, resource commitments, and how the organizations will work together. MOUs are generally non-binding but carry significant weight as evidence of partnership intent.

Use when: A partner organization has a defined operational role in your project but won't receive federal funds directly through your grant.

Letter of Support

A letter of support expresses endorsement of your project. It describes the writer's relationship to the work and may include general statements about the project's importance. It does not commit the writer to specific deliverables or resource contributions.

Use when: An organization supports your project's goals but won't be involved in day-to-day implementation. Community leaders, elected officials, and organizations that will refer clients but don't have operational roles typically provide letters of support.

Subaward Agreement

A subaward agreement is a formal funding mechanism governed by 2 CFR 200 (opens in a new tab). When your grant passes federal funds to another organization to carry out a portion of the project scope, that's a subaward. Subaward agreements include detailed budgets, compliance requirements, monitoring provisions, and reporting obligations. Subrecipient monitoring under 2 CFR 200.332 (opens in a new tab) applies to every subaward, whatever its size, and FFATA subaward reporting starts at $30,000. The $50,000 figure you may have heard about only caps how much of each subaward counts in your modified total direct cost (MTDC) base for indirect costs under 2 CFR 200.1 (opens in a new tab).

Use when: A partner organization will receive a portion of your federal award to perform a defined scope of work.

The key distinction: Letters of support say "we believe in this project." MOUs say "here's exactly how we'll work together." Subaward agreements say "here's the federal funding being passed through and the compliance terms attached to it."

MOU ElementPurposeExample Language
PartiesIdentify organizations"Between [Org A] and [Org B]"
PurposeDefine the collaboration"To support [Project Name] funded by [Agency]"
RolesSpecify each party's responsibilities"[Org B] will provide 150 hours of counseling services"
DurationSet timeline"Effective [date] through [project end date]"
ResourcesQuantify contributions"Office space valued at $15,000 annually"
TerminationDefine exit terms"Either party may terminate with 60 days written notice"

When MOUs Are Required in Grant Applications

Not every grant application needs an MOU. Here's how to figure out whether yours does.

Check your NOFO first. The Notice of Funding Opportunity will specify whether MOUs are required, encouraged, or optional. Search the document for "memorandum of understanding," "MOU," "partnership agreement," and "collaboration agreement." Some NOFOs use these terms interchangeably.

Programs that required MOUs in FY2026 (from the notices Grantsights checked):

  • DOJ Office on Violence Against Women programs with required partners, such as Justice for Families, the Criminal Justice Response program, Abuse in Later Life, and the Disability Grant Program
  • HRSA network programs, such as the Delta States Rural Development Network Program (a signed MOU/A from each network participant)
  • DOL training programs with required partners, such as RESTART, WORC Round 7, and Strengthening Community Colleges Round 6 (a signed MOU or letter of commitment)
  • Other agencies, including SAMHSA, ACF, and the Department of Education, use partnership documents in some notices; the rule changes from notice to notice, so read yours

MOUs are typically required when:

  • Your project involves two or more organizations sharing implementation responsibilities
  • Partners will provide staff, facilities, data, or services to the project
  • The NOFO includes scoring criteria related to partnerships, collaborations, or organizational capacity
  • Your project operates across multiple sites or jurisdictions

MOUs are typically not needed when:

  • A partner is simply endorsing your project (use a letter of support)
  • A partner will receive federal funds through your grant (use a subaward agreement)
  • The NOFO doesn't mention partnership documentation

What 16 FY2026 Federal Notices Require From Partners

Grantsights checked 16 FY2026 federal funding notices on October 18, 2026 to see what each one asks applicants to submit for their partners. The sample: 10 of the 21 FY2026 solicitations on the DOJ Office on Violence Against Women solicitations page (opens in a new tab) (skipping formula, tribal-only, coalition, technical-assistance, and pilot notices), plus 3 HRSA and 3 DOL notices on Grants.gov (opens in a new tab) whose programs are built on networks or required partners. For each notice, Grantsights read the eligibility and attachment sections and recorded the partner-document rule in the notice's own words.

Notice (FY2026)What partners must submitLetter of support accepted?
OVW Justice for Families (opens in a new tab) (O-OVW-2026-172608)"Partnerships must be documented in a signed memorandum of understanding (MOU)" with a victim service provider and a courtNo. A court that can't sign may send a letter of commitment
OVW Criminal Justice Response (opens in a new tab) (O-OVW-2026-172633)"These partnerships must be documented in a memorandum of understanding (MOU)"No. Courts and tribal governments may send letters of commitment
OVW Consolidated Youth (opens in a new tab) (O-OVW-2026-172652)Applicants must "document partnerships in a memorandum of understanding"No
OVW Abuse in Later Life (opens in a new tab) (O-OVW-2026-172663)MOU "signed by the Authorized Representative of each of the four required MOU partners"No. Tribal governments may send letters of commitment
OVW Disability Grant Program (opens in a new tab) (O-OVW-2026-172670)"An MOU is required to document the required partnership(s)"No
OVW Abby Honold program (opens in a new tab) (O-OVW-2026-172637)Partnership with a victim service provider documented via "a signed Memorandum of Understanding or Letter of Commitment"No, commitment letters only
HRSA Delta States Rural Development Network (opens in a new tab) (HRSA-26-045)"a scanned, signed copy of the MOU/A from each network participant"No. Letters of commitment are a stopgap; the signed MOU/A is due within 60 days of the project start
DOL RESTART (opens in a new tab) (FOA-ETA-26-17)A signed and dated letter of commitment or MOU with each required partnerNo: "general Letters of Support are not acceptable"
DOL WORC Round 7 (opens in a new tab) (FOA-ETA-26-23)Letters of commitment, partnership agreements, or MOUs from all required employer partnersNo: "Letters of support are not sufficient"
DOL Strengthening Community Colleges Round 6 (opens in a new tab) (FOA-ETA-26-40)Signed letters of commitment or MOUs "dated no earlier than six months prior to the closing date"Not for service partners (separate state-official support letters are required)
OVW Rural program (opens in a new tab) (O-OVW-2026-172579)"a memorandum of understanding (MOU) among the applicant and project partners or letter(s) of support" when more than one entity is involvedYes
OVW Legal Assistance for Victims (opens in a new tab) (O-OVW-2026-172580)MOU or memorandum of exemption required; for multi-entity projects, "a memorandum of understanding (MOU) among the applicant and project partners or letter(s) of support"Yes
OVW Cybercrimes program (opens in a new tab) (O-OVW-2026-172629)MOU with a victim services provider for purpose 1; other partners by MOU or letterYes, except for the purpose 1 partner
HRSA Small Health Care Provider Quality Improvement (opens in a new tab) (HRSA-26-046)A letter of support from each partner, plus signed and dated letters of agreement for working relationshipsYes
OVW Transitional Housing (opens in a new tab) (O-OVW-2026-172624)MOU "required if the lead applicant is a state, territory, or local government"Not addressed for nonprofit leads
HRSA Telehealth Nutrition Services Network (opens in a new tab) (HRSA-26-076)A site-commitment table at application; MOAs signed by "an authorized official" after awardNot addressed

Grantsights analysis of these 16 notices found that 10 required a signed MOU or a signed letter of commitment from required partners at application, 4 accepted a letter of support for at least some partners, 1 required an MOU only from government-led applicants, and 1 required memoranda of agreement after award. In the 5 OVW notices that required an MOU outright, the only partners allowed to send a letter of commitment instead were courts or tribal governments. Two DOL notices went further and said general letters of support don't count at all. A sample of 16 isn't every federal program, and SAMHSA, ACF, and Education notices weren't in it, so treat the split as a pattern to check against your own notice, not a rule.

According to DOJ's Office on Violence Against Women, an MOU must be "dated within 12 months before the date the application is submitted," signed by the authorized representative of each partner, and it "is not a substitute for a subaward agreement." OVW's MOU and letters of support instructions (opens in a new tab) present letters of support as the fallback for cases when, "for legal reasons, an applicant cannot enter into an MOU," and each letter must cover the same six criteria an MOU would. According to DOL's WORC Round 7 notice, applicants that don't document commitment from all required employer partners "will receive zero points for this rating factor."

The practical read: a red flag in any partnership notice is the phrase "required partner." When it appears, plan on a signed MOU or a signed letter of commitment that names the partner's role, and check the notice's dating window. OVW allows 12 months; Strengthening Community Colleges allowed six. To find open programs with partnership rules like these, start with the Grantsights grant search, then read the full notice before you draft the MOU.


The 8 Sections Every Grant MOU Should Include

A complete MOU follows a consistent structure. Here's each section with guidance on what reviewers look for.

Section 1: Purpose and Background

State why the MOU exists. Identify the grant opportunity by name and funding opportunity number. Describe the problem both organizations are addressing and why collaboration is necessary.

Example: "This Memorandum of Understanding establishes the terms of collaboration between Riverdale Community Health Center and Metro County School District for the proposed School-Based Mental Health Integration Program, submitted in response to SAMHSA Funding Opportunity SM-26-001. Both organizations have identified a documented gap in adolescent mental health services in Metro County, where only 23% of students who need counseling receive it within the school setting."

Section 2: Scope of the Partnership

Define what the partnership covers and, equally important, what it does not cover. This section prevents misunderstandings later about what each organization agreed to.

Example: "This MOU covers the collaborative delivery of school-based mental health screening, assessment, and counseling services in four Metro County middle schools during the 36-month project period. This MOU does not cover clinical services outside of school settings, inpatient treatment, or medication management."

Section 3: Roles and Responsibilities

This is the most important section. For each partner organization, list specific duties, deliverables, and the named staff or positions responsible. Use quantifiable language wherever possible.

For the lead applicant, specify:

  • Project management and fiscal oversight
  • Federal reporting responsibilities
  • Staffing commitments (by position title and FTE)
  • Facilities and equipment provided

For the partner organization, specify:

  • Services or expertise contributed (with volume or frequency)
  • Staff positions committed (by title, FTE, and dollar value)
  • Data, referrals, or access provided
  • Facilities, equipment, or materials contributed

Example: "Metro County School District agrees to: (1) designate a School-Community Liaison (0.25 FTE, valued at $17,500 annually) to coordinate screening schedules and parent communication; (2) provide dedicated counseling space in each of the four participating schools, including private offices with soundproofing, valued at $14,400 annually; (3) support access to student health records with appropriate FERPA-compliant consent procedures; and (4) include project staff in quarterly school safety team meetings."

Section 4: Resource Contributions and Budget Alignment

Quantify every resource each partner will contribute. This section should align directly with your grant budget justification. If a partner's in-kind contribution appears in your budget, the MOU should document the same dollar amount.

Include:

  • Staff time (position, FTE, annual value, total project value)
  • Facilities (description, estimated annual value)
  • Equipment (items over $10,000 should be listed individually per federal guidelines)
  • Data access or intellectual property
  • Cash contributions or cost sharing

Section 5: Governance and Decision-Making

Describe how the partnership will be managed. Reviewers look for evidence that you've thought about operational logistics, not just the big picture.

Address:

  • Who has final decision-making authority for the project?
  • How often will partners meet? (Monthly meetings are standard.)
  • Who represents each organization on the project steering committee?
  • How will disagreements be resolved?
  • What happens if one party can't fulfill their obligations?

Example: "The Project Director (Riverdale Community Health Center) and School-Community Liaison (Metro County School District) will meet biweekly during Year 1 and monthly during Years 2 and 3. A Joint Advisory Committee comprising two representatives from each organization and two parent representatives will meet quarterly to review project progress and address implementation challenges. Disagreements will be escalated first to the executive leadership of both organizations and, if unresolved, to a mutually agreed-upon mediator."

Section 6: Communication and Reporting

Specify how partners will communicate about project activities, data, and outcomes. This section is especially important for multi-site projects.

Include:

  • Regular meeting schedule and format (in-person vs. virtual)
  • Shared reporting responsibilities
  • Data sharing protocols and privacy protections
  • Who receives copies of federal progress reports

Section 7: Duration, Amendment, and Termination

State the start and end dates of the MOU, typically matching the grant's project period. Include provisions for:

  • Amendments: How can the MOU be modified? (Usually requires written agreement from both parties.)
  • Termination: Under what circumstances can either party end the agreement? What notice period is required? (30 to 60 days is standard.)
  • Renewal: Will the MOU automatically renew if the grant is continued or extended?

Section 8: Signatures

Both organizations must sign the MOU. The signer should be someone with the authority to commit their organization's resources. That means executive directors, department heads, or vice presidents. A program coordinator or case manager generally doesn't have the authority to commit FTE, facility access, or financial contributions.

Each signature block should include:

  • Full name and title
  • Organization name
  • Date
  • Contact information

MOU Template for Grant Applications

Use this template as a starting point. Customize every section for your specific project and partner.


MEMORANDUM OF UNDERSTANDING

Between [Lead Organization] and [Partner Organization]

Regarding [Project Name]

In Response to [Funding Opportunity Number / Program Name]

I. Purpose

This Memorandum of Understanding establishes the framework for collaboration between [Lead Organization] and [Partner Organization] for the [Project Name], submitted in response to [Funding Opportunity Number]. The purpose of this collaboration is to [one sentence describing the shared goal].

II. Background

[2-3 sentences describing the problem both organizations are addressing and why collaboration is needed. Include a specific data point if possible.]

III. Scope

This MOU covers [specific services, activities, or functions included]. This MOU does not cover [anything explicitly excluded].

IV. Roles and Responsibilities

[Lead Organization] agrees to:

  • [Specific responsibility #1 with FTE, timeline, or deliverable]
  • [Specific responsibility #2]
  • [Specific responsibility #3]

[Partner Organization] agrees to:

  • [Specific responsibility #1 with FTE, dollar value, or deliverable]
  • [Specific responsibility #2]
  • [Specific responsibility #3]

V. Resource Contributions

[Lead Organization] will contribute: [List with dollar values]

[Partner Organization] will contribute: [List with dollar values]

Total estimated value of partner contributions: $[amount] over the [X]-year project period.

VI. Governance

[Describe meeting schedule, decision-making authority, and dispute resolution process.]

VII. Communication

[Describe meeting frequency, reporting protocols, data sharing agreements.]

VIII. Duration and Termination

This MOU is effective from [start date] through [end date], corresponding to the [X]-year project period. Either party may terminate this MOU with [30/60] days written notice. Amendments require written agreement from both parties.

IX. Signatures


[Name], [Title] [Lead Organization] Date: __


[Name], [Title] [Partner Organization] Date: __


MOU vs. MOA: When to Use Each

The terms "memorandum of understanding" and "memorandum of agreement" get used interchangeably in grant writing, but they have different legal weight.

MOU (Memorandum of Understanding): Generally non-binding. Expresses mutual intent to collaborate and outlines how the partnership will work. Most grant applications call for MOUs because they document partnerships without creating legal obligations that might complicate the relationship if the grant isn't funded.

MOA (Memorandum of Agreement): Generally considered more binding. An MOA typically includes more formal contract language, specifies enforceable obligations, and may include consequences for non-performance. According to the University of Alaska Southeast's guidance on MOUs and MOAs (opens in a new tab), MOUs are generally not legally binding, while MOAs set common legal terms for a conditional agreement where a transfer of funds for services is anticipated.

For most grant applications, use an MOU. Unless your NOFO specifically requests a memorandum of agreement or your partnership involves binding financial commitments that extend beyond the grant period, an MOU is the standard document type. If you're unsure, check with your agency's program officer before submission.


Whether an MOU is legally binding depends on its language, not its title. Here's what to watch for.

Language that creates binding obligations:

  • "Shall" instead of "will"
  • Specific financial penalties for non-performance
  • Clauses requiring arbitration or litigation for disputes
  • Terms like "agreement," "contract," or "covenant"

Language that preserves non-binding intent:

  • "Will endeavor to" or "intends to"
  • "Subject to the availability of funding"
  • An explicit statement that the MOU is non-binding
  • A clause stating that neither party incurs financial liability

Best practice: Include a clause stating: "This MOU is not a legally binding agreement and does not create any enforceable obligations. It expresses the mutual intent of both parties to collaborate on the described project, subject to the availability of grant funding."

Have your organization's legal counsel review the MOU, especially if it involves data sharing, intellectual property, or financial contributions exceeding $25,000.


How Reviewers Evaluate MOUs

Understanding the reviewer's perspective will help you write a stronger MOU. Here's what they're looking for.

Specificity of commitments. Reviewers compare MOU language against your project narrative. If your narrative claims a partner will provide 500 patient referrals per year, the MOU should confirm that exact number. Vague commitments like "will assist with recruitment as needed" don't give reviewers the evidence they need to award points.

Authority of signers. A reviewer will check whether the person who signed the MOU has the organizational authority to deliver the promised resources. An MOU committing 0.50 FTE of a clinician signed by the organization's executive director is credible. The same commitment signed by an intern is not.

Alignment with budget. If your partner's in-kind contribution appears as cost sharing in your budget, the MOU should document the same dollar amounts. Inconsistencies between MOUs and budgets are a common flag in reviewer critiques.

Completeness. MOUs that cover roles, resources, governance, and termination signal a mature partnership. MOUs that only list general intentions signal a partnership that hasn't been fully developed.

Realistic commitments. Reviewers are experienced enough to spot over-promising. If a small nonprofit MOU commits $200,000 in staff time to your project, reviewers will question whether that organization has the capacity. Keep commitments proportional to the partner's size and realistic given their existing workload.


Getting Partner Signatures on Time

The signature process is where most MOU problems start. Here's a timeline that works.

8 weeks before deadline: Identify all partners who need MOUs. Contact each partner to confirm their willingness and discuss their role.

6 weeks before deadline: Send the draft MOU to each partner with a one-page project summary. Ask them to review the roles, responsibilities, and resource commitments described.

4 weeks before deadline: Collect feedback and finalize the MOU language. Make sure both organizations agree on every commitment.

3 weeks before deadline: Route the MOU through each organization's internal approval process. For universities, hospitals, and government agencies, this step can take 2 to 3 weeks because the document may need review by legal counsel, sponsored programs, and executive leadership.

1 week before deadline: All MOUs should be signed and in your hands. Convert to the required file format (usually PDF) and include in the correct attachment section of your application.

A common mistake: Waiting until the last week to start the MOU process. Large institutions like universities and hospitals can't turn around legal documents in 3 days. Their sponsored programs offices, legal departments, and authorized signatories have review queues. Build your timeline around the slowest partner, not the fastest.


Common Mistakes That Cost Points

Mistake 1: Vague Roles With No Deliverables

"Partner Organization will support the project as needed" is not a commitment. It's a gesture. Every role in your MOU should include a specific deliverable, a timeline, and a responsible person or position. Compare "will assist with outreach" to "will conduct 12 community presentations per year in [Geographic Area], reaching approximately 300 residents annually, led by their Community Health Worker (0.15 FTE)."

Mistake 2: Missing Dollar Values for In-Kind Contributions

If your partner is providing staff time, space, or equipment, calculate the dollar value and include it in the MOU. This does two things: it demonstrates the partnership's financial substance to reviewers, and it ensures alignment with your budget justification. Staff time should be calculated as FTE multiplied by annual salary and fringe. Facility space should be estimated at fair market rental value.

Mistake 3: No Governance Structure

An MOU that lists roles but doesn't explain how the partnership will be managed leaves reviewers wondering how decisions will get made when things don't go as planned. Include meeting frequency, decision-making authority, and a dispute resolution process. It doesn't need to be elaborate, but it needs to exist.

Mistake 4: MOU Doesn't Match the Narrative

If your project narrative describes a partner providing clinical supervision and the MOU says they'll provide data analysis, reviewers will flag the inconsistency. Write your MOU and narrative in parallel, and cross-check every partner commitment across both documents and your grant budget justification.

Mistake 5: Wrong Signer

An MOU signed by someone without authority to commit resources isn't credible. Program coordinators, case managers, and project staff typically can't bind their organization to specific FTE commitments or facility access. Get signatures from executive directors, department heads, or authorized institutional officials.

Mistake 6: No Termination Clause

What happens if the grant isn't funded? What if a partner can't fulfill their commitments? A termination clause protects both organizations and shows reviewers you've planned for contingencies. Include the notice period (typically 30 to 60 days) and what happens to shared resources or data if the partnership ends.

Mistake 7: Submitting an Unsigned MOU When Signatures Are Available

Some applicants submit unsigned MOUs out of convenience or because they ran out of time. If you had time to get signatures and didn't, reviewers will notice. An unsigned MOU is significantly weaker than a signed one because it doesn't confirm that the partner's authorized official has actually approved the commitments described.


How Many MOUs to Include

The right number depends on your project design, not an arbitrary target.

Include an MOU from every organization with a defined operational role. If an organization appears in your project narrative as responsible for specific activities, services, or resource contributions, they need an MOU.

Don't create MOUs for peripheral supporters. Organizations that will refer clients, endorse your project, or participate in an advisory capacity but don't have operational responsibilities should provide letters of support instead.

How the count usually works: there's no standard number. Plan one MOU (or one multi-party MOU, if the NOFO allows it) for each organization with an operational role, one per site for multi-site projects, and check whether the NOFO caps partnership attachments.

Watch your page limits. Some NOFOs cap the total pages for partnership documentation. If you have 8 partners and a 20-page limit, you'll need concise MOUs (2 to 3 pages each). Prioritize the partners with the largest roles and combine smaller commitments where possible.


Tips for Multi-Partner MOUs

For projects with three or more partner organizations, you have two options.

Option 1: Individual MOUs. Write a separate MOU between the lead applicant and each partner. This is the standard approach and works well when each partner has a distinct role.

Option 2: Omnibus MOU. Create a single MOU that all partners sign. This works for consortium projects where partners have overlapping roles or shared governance. The omnibus MOU should include a section for each partner's specific commitments plus shared sections on governance and communication.

For most applications, individual MOUs are cleaner and easier for reviewers to evaluate. They can flip to the specific partner's MOU without reading through commitments from six other organizations. But if your NOFO emphasizes a consortium model, an omnibus MOU better demonstrates the collaborative structure.



The MOU Problems That Show Up in Reviewer Critiques

Reviewers don't just evaluate whether an MOU exists. They evaluate whether the MOU's commitments are believable given what they know about organizations of the partner's size and type. A community health center in a rural county committing 0.75 FTE of a licensed clinical supervisor to a project, valued at $65,000 annually, is a credible commitment. The same organization committing 1.5 FTE of clinical staff when their whole organization has eight employees is not. Reviewers with program experience catch this immediately, and a commitment that looks inflated damages your application's credibility beyond just the partnership section.

Some agencies put a shelf life on MOUs. The DOJ Office on Violence Against Women (opens in a new tab) says an MOU must be current, meaning dated within 12 months before the application is submitted, and signed by the authorized representative of each partner (electronic signatures are fine; missing signatures can lower the score or remove the application from consideration). The age rule trips up applicants who submit to multiple NOFOs across a grant season. An MOU signed in January for an April submission is fine. The same MOU reused for a submission the next February is stale. Check your own NOFO for any dating or signature rule before reusing an MOU.

A partner's authorized official can leave, or the position can be eliminated, between signing and award. Post-award negotiations can then require a new MOU and a change of the designated organizational representative in JustGrants, and the partner's new leadership may need weeks to review the commitment before re-signing. That can push back the award start date. None of this is visible during application review, which is why governance language and a current contact name in Section 5 of the MOU matter more than applicants think.

In DOJ/OJP applications, the MOU-versus-subaward distinction is often misunderstood. When a partner organization will perform discrete tasks and receive a portion of the award budget to do so, that isn't an MOU relationship. That's a subaward, which requires a formal subaward agreement with a budget attachment, compliance flow-down provisions under 2 CFR 200, and monitoring requirements on the prime recipient's part. Some applicants submit MOUs for what are clearly subaward relationships, identifying named partners as "providing services" with dollar values that match line items in the budget. OJP's grants management staff flag this during award negotiation. Fixing it post-award takes time, and it can delay your first draw while the subaward agreements are drafted, reviewed, and executed. Draft your MOU and your budget side by side, and if money is moving to a partner, you need a subaward agreement, not an MOU.

What Federal Funding Notices Don't Tell You About Memoranda of Understanding for Grants

Most of the 16 FY2026 notices in the table above say which partners must sign and when the document has to be dated, but none of them tells you how binding the MOU language should be. The OVW solicitations point applicants to a separate OVW instructions page (opens in a new tab) for content, and HRSA's Delta States notice lists four topics each MOU/A should cover. The legal weight of the wording is left to you and your partners.

An MOU is not a legally binding contract in most jurisdictions unless it contains specific elements of a contract (offer, acceptance, consideration). Federal reviewers know this. If your NOFO requires a 'binding commitment' from partners, an MOU may not be sufficient. Check whether the agency wants an MOU, a Memorandum of Agreement (MOA), or a formal subcontract. The terms are not interchangeable.

The strongest MOUs in grant applications describe specific deliverables, timelines, and named personnel. An MOU that says 'Organization X will collaborate with the project' adds nothing. One that says 'Organization X will provide 200 hours of bilingual case management per year, supervised by [Name], at no cost to the project' directly addresses reviewer questions about partnership authenticity.

Many grant applicants draft MOUs too late in the application process, resulting in generic language that doesn't match the project narrative. Draft your MOUs at the same time you write your project description. The partner commitments in your MOU should mirror the activities described in your work plan. Reviewers cross-reference these documents and flag inconsistencies.


Sources

Frequently Asked Questions

Is an MOU legally binding?

In most cases, no. An MOU expresses mutual intent and outlines roles and responsibilities, but it's generally not enforceable in court unless it contains specific contract elements like consideration, offer, and acceptance. However, some agencies and legal jurisdictions treat MOUs with binding language as enforceable agreements. If your MOU includes phrases like 'shall' instead of 'will' or specifies financial penalties for non-performance, a court could interpret it as a binding contract. Have your organization's legal counsel review the MOU before signing, especially when the document involves financial commitments, data sharing, or intellectual property.

How many MOUs should I include in a grant application?

Include one MOU for each organization that has a defined, substantive role in your project. Some notices fix the count: OVW's FY2026 Abuse in Later Life solicitation requires an MOU signed by four required partners (law enforcement, a prosecutor's office, a victim service provider, and an organization serving people 50 and older). Don't create MOUs for organizations that are simply endorsing your project with no operational role. Those partners should provide letters of support instead. Your NOFO will specify whether MOUs are required and who the required partners are. HRSA's FY2026 Delta States Rural Development Network notice, for example, asks for a separate signed MOU/A from each network participant.

What is the difference between an MOU and a subaward agreement?

An MOU documents a partnership where organizations agree to collaborate and share resources toward a common goal. A subaward agreement is a formal funding mechanism where the prime grantee passes a portion of the federal award to another organization to carry out part of the project scope. Subaward agreements trigger compliance requirements under 2 CFR 200, including risk review and subrecipient monitoring under 2 CFR 200.332 for every subaward regardless of size, plus FFATA subaward reporting once a subaward reaches $30,000. The $50,000 figure in the Uniform Guidance only caps how much of each subaward counts in the prime's modified total direct cost (MTDC) base for indirect costs. If your partner will receive federal funds through your grant, you need a subaward agreement, not just an MOU.

Can I submit an unsigned MOU with my grant application?

Some agencies accept draft or unsigned MOUs, but a signed MOU is always stronger. An unsigned MOU tells reviewers that the partnership hasn't been finalized, which raises questions about whether the collaboration will actually happen. DOJ's Office on Violence Against Women says missing signatures may reduce the score or remove the application from consideration. Some notices build in a fallback instead: HRSA's FY2026 Delta States notice accepts letters of commitment when signed MOUs aren't ready, then requires the signed MOU/A within 60 days of the project start. Read your notice before submitting anything unsigned, and don't assume a fallback exists.

When should I use an MOU instead of a letter of support?

Use an MOU when a partner has a defined operational role in your project, including providing staff, facilities, data, referrals, or services. Use a letter of support when an organization endorses your project but won't be directly involved in implementation. The key test is whether the partner needs to do something specific for your project to succeed. If yes, you need an MOU that spells out what they'll do, when, and with what resources. If they're simply affirming the project's value, a letter of support may be enough. Check your NOFO first: in a Grantsights review of 16 FY2026 federal notices, only 4 accepted a letter of support for any project partner, and two DOL notices said general letters of support don't count.

Last updated October 18, 2026. Corrected October 18, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.