To write a memorandum of agreement, start by deciding whether you want the document to be legally binding, collect the identifying and operational information for every party involved, then draft clauses covering purpose, roles, timeline, money, intellectual property, confidentiality, disputes, and termination before anyone signs. The work that matters happens before you open a template. Vague inputs produce vague agreements, and vague agreements produce arguments.
Decide First Whether the MOA Will Be Binding
The most misunderstood thing about an MOA is whether it carries legal weight, and the answer depends on what the document says rather than what it’s titled. An MOA that lays out specific obligations, deliverables, timelines, and resource commitments can look like a contract to a court. If both parties exchanged something of value and intended to be bound, a judge can treat the MOA as enforceable.
If you want the document to remain non-binding, say so in plain language. Effective disclaimer wording states that the MOA expresses intent only and that no legally enforceable obligations arise from it. Even then, you can carve out specific sections that stay binding. Confidentiality and non-disclosure provisions are the common carve-outs, because information shared during the collaboration needs protection whether or not the partnership itself creates enforceable duties.
Make this call at the outset. If the collaboration involves real money, shared staff, or deliverables one party depends on, draft it as a binding agreement. If it’s a framework meant to lead to a formal contract later, say so in the opening paragraph and again in a standalone non-binding clause.
Information to Collect Before You Draft
Trying to fill blanks as you go is where the ambiguity creeps in. Pull everything together first.
Parties and Signing Authority
Record the full legal name of every participating entity. If an organization operates under a trade name or DBA, include both so there’s no confusion about who is actually bound.1U.S. Small Business Administration. Choose Your Business Name Collect current mailing addresses, primary email contacts, and the name and title of each person who will sign.
The signer must have actual authority to bind the organization. For corporations, that’s typically an officer designated in the bylaws, such as a CEO, president, or secretary. For LLCs, it’s usually a managing member or someone authorized in the operating agreement. If someone without signing authority executes the document, the whole agreement can be challenged. Ask each party to confirm its signatory’s authority in writing before the signing date.
Purpose, Roles, and Deliverables
Write a statement of purpose specific enough that a reader a year from now would immediately understand the scope. “The parties will collaborate on community health initiatives” is too vague. “The parties will jointly develop and distribute a diabetes screening program in three counties during the 2026–2027 fiscal year” gives everyone something to measure against.
Then list each party’s roles and responsibilities. Be concrete about who provides what: staff time, equipment, office space, data access, funding. If Party A supplies the lab space and Party B supplies the researchers, write that down. Ambiguity on this point is the top source of friction in MOA-governed partnerships, because each side walks away with a different understanding of who owes what.
Timeline and Money
Set a specific start date and end date. If the collaboration is tied to milestones rather than calendar dates, define the milestones and state what ends the agreement: completion of the final deliverable, exhaustion of allocated funds, or a written determination by both parties that the objectives have been met.
Document the financial dimensions even when no cash changes hands. Allocate shared costs for equipment, travel, printing, or software to a specific party. If one party contributes in-kind resources, like free use of a facility, assign a reasonable value so both sides understand the scale of the commitment. Leaving financial expectations unstated invites one party to feel shortchanged six months in.
Clauses the Document Needs
A bare-bones MOA that names the parties and states a purpose leaves everyone exposed. The clauses below address the risks that actually materialize. Not every MOA needs all of them, but skipping one should be a deliberate choice.
Indemnification and Liability
An indemnification clause decides who pays when something goes wrong. Under mutual indemnification, each party covers losses caused by its own negligence or breach, and that is the common structure between organizations of roughly equal bargaining power. One-sided indemnification, where only one party assumes the risk, is more typical when one entity is significantly larger or is funding the collaboration.
Specify what’s covered (legal fees, third-party claims, property damage) and include a cap on total exposure where possible. Without a cap, one party’s liability could dwarf the value of the entire collaboration. Also decide whether the clause survives termination. Liability for something that happened during the partnership doesn’t disappear just because the agreement ended.
Intellectual Property
Collaborations produce things: reports, data sets, software, designs, curricula. State who owns what before the work begins. Sole ownership gives one party everything created under the MOA, which fits when one entity is essentially hiring the other to produce work product. Joint ownership lets both parties use, license, or build on the work independently, though it needs careful language on sublicensing without consent. Split ownership gives each party the specific deliverables it produces, with a separate rule for jointly created materials; it’s more administratively complex but can be the fairest arrangement.
Add a clause protecting pre-existing IP. Each party should retain full ownership of anything it brought into the relationship. Without that language, a party sharing proprietary methods or data during the collaboration risks an argument that those assets became shared property.
Confidentiality
Define confidential information broadly enough to cover oral disclosures, not just written documents. State how long the obligation lasts and list the exceptions: information already public, information the receiving party independently developed, or disclosures compelled by a court order. If the work involves trade secrets, use a standalone non-disclosure agreement rather than relying on a paragraph.
Dispute Resolution
Decide how disagreements get handled before anyone is angry. A tiered approach works well: direct negotiation between designated representatives first, formal mediation if that fails, and binding arbitration or litigation as the final step. Mediation and arbitration tend to be faster and cheaper than court and preserve the working relationship better. If you choose arbitration, name the administering organization and state whether the decision is final and binding. If you want to keep the courthouse door open, say so explicitly, because a broadly worded arbitration clause can be read as mandatory.
Termination
Cover two exit paths. Termination for convenience lets either party walk away without proving fault, typically with written notice of 30, 60, or 90 days. Termination for cause allows immediate or accelerated exit when the other party breaches a material term, fails to perform, or becomes insolvent. Address what happens to work in progress, shared resources, and confidential information after the agreement ends. A half-finished database or a partially built training curriculum needs a wind-down plan.
Governing Law, Jurisdiction, and Amendments
When parties sit in different states, pick which state’s law governs and which courts have jurisdiction. If one party is a state agency, that state’s law will almost certainly control. For private organizations, the choice is negotiable, but pick one and stick with it.
Include a clause requiring that any changes to the MOA be in writing and signed by authorized representatives. Without it, someone can argue a verbal agreement or an email exchange modified the terms.
Filling in a Template Without Creating Problems
Several federal agencies publish MOA templates for interagency partnerships and public-private collaborations. The Department of Defense’s Civilian Personnel Advisory Service maintains a sample MOA reflecting standard federal formatting. State government portals and university administrative offices also publish templates tailored to academic or nonprofit partnerships. Pick one that matches the nature of your collaboration; a joint research agreement calls for different provisions than a shared facilities arrangement.
Map the information you gathered into the corresponding sections. The statement of purpose goes in the opening recitals, usually introduced with “WHEREAS” clauses. Roles and responsibilities fill the operative body. Timeline information populates the term and renewal provisions. Financial allocations go into a resources or budget section. Resist the urge to leave “to be determined” in the final draft. Every blank is a future argument.
After populating the template, read the document end to end as a single narrative. Check that defined terms are used consistently; if you call one party “the Provider” in Section 2, don’t switch to “the Contractor” in Section 5. Confirm cross-references point to the correct section numbers, especially if you added or removed provisions. A five-minute consistency check catches errors that would otherwise take months of correspondence to untangle.
If Federal Grant Money Is Involved
When the collaboration involves federal award funds, the MOA has to satisfy the Uniform Guidance at 2 CFR Part 200.2eCFR. Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards A pass-through entity issuing a subaward through an MOA must include the subrecipient’s legal name and unique entity identifier, the Federal Award Identification Number, the subaward period of performance, the amount of federal funds obligated, the applicable Assistance Listings title and number, and whether the award is for research and development.3eCFR. 2 CFR 200.332 – Requirements for Pass-Through Entities
The pass-through entity must also negotiate or assign an indirect cost rate for the subrecipient. If the subrecipient has a federally negotiated rate, the pass-through entity cannot require use of the de minimis rate instead.3eCFR. 2 CFR 200.332 – Requirements for Pass-Through Entities The MOA also has to incorporate applicable federal requirements such as conflict-of-interest disclosures, mandatory disclosure of fraud or criminal violations, and federal procurement standards.2eCFR. Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards Omitting any of these from an MOA governing federal funds can jeopardize the award and trigger audit findings.
Signing and Storing the Agreement
The document can be signed with ink or through an electronic signature platform. Federal law prohibits denying a signature legal effect solely because it’s electronic, so e-signatures are valid for MOAs involving interstate or foreign commerce.4Office of the Law Revision Counsel. 15 USC 7001 – General Rule of Validity Electronic platforms generate audit trails recording when each party signed and from what device, which is useful if someone later disputes execution.
You can also have signatures notarized. The notary confirms that the signer is who they claim to be and is signing voluntarily. Notary fees for a simple acknowledgment vary by state but generally run $5 to $15 per signature. Notarization isn’t legally required for most MOAs, but it’s worth considering when the agreement involves substantial resources or when the parties don’t have an established relationship.
Once everyone signs, deliver the executed document through a method that creates a delivery record: certified mail, a courier with tracking, or a secure digital transmission. Each party keeps an identical, fully executed copy. Scan the signed document into a central digital repository where operational staff and legal counsel can both find it without hunting through email. Set a calendar reminder for the expiration date so you can start renewal or close-out well before the term ends. An agreement that expires without anyone noticing creates an awkward gap where the parties are still collaborating but no longer have a governing document, and that’s exactly where disputes thrive.