MOU’s, by definition, must develop organically. When that happens, MOU’s are comforting and provide a level of reassurance because they bring some specificity to a situation with too much uncertainty. They must reflect our interdependent relationship and convey that both parties stand to gain or lose – an element necessary to true collaboration.
The act of grabbing an MOU template and using it as a blank form for the other party to fill out will instantly change the dynamics of a budding collaborative relationship to one of customer / service provider. Consequently, do NOT treat this document as a template. This is a training document whose purposes is to illustrate some common elements found useful in past situations.
Note that there are relationships that are more aptly described as customer / service provider. In these situations, an SLA (Service Level Agreement) may be more useful than an MOU. An MOU reflects a snapshot in time and usually includes a date when it will be reviewed and optionally renewed. An SLA, on the other hand, enumerates services a customer should expect to receive from a provider over a specified timespan.
MOU’s should be used only when they are useful. They are situation-specific and should be as simple or as complicated as needed to preempt future misunderstanding. An MOU can range from a two-sentence email exchange to a signed and countersigned multipage document.
Memorandum of Understanding (MOU) By and Between
______& University of Iowa Libraries
{Date}
Introduction
Open with something here about what this document is and does, such as: The purpose of this MOU is to define the parameters of an ongoing partnership between ___ and the University of Iowa Libraries (the Libraries) to provide ___. The shared goal of the project is to ___.
If some background context would be helpful, add it here.
Project Implementation
In order to meet the project goals, the parties agree as follows:
The Libraries will:
·
·
·
·
___ will:
·
·
Add sections to address key issues
Consider: design issues, rights and ownership, release forms, access restrictions, conservation issues, metadata plan, preservation plan, long-term digital preservation.
Also list any important contingencies that might interfere with getting the project completed on time and on budget.
Target Dates
Add a few milestones and target date for each.
· Date 1: Milestone 1
· Date 2: Milestone 2
· Date 3: Milestone 3
Post-Production. Something about launch and wrap up.
Contacts
Technical contacts. Administrative contacts. Financial contacts if needed.
Term
This agreement begins on August 25, 2014, and is expected to be in effect for one year. The agreement may be amended or renewed by mutual agreement at the initiation of either party.
Signatures
Signature Signature
Date: Date: