Memorandum of understanding: agreeing to work together before agreeing terms

A memorandum of understanding — an MOU — is a document in which two or more organisations write down what they have agreed to do together before, or instead of, a contract. Universities sign them with industry, charities with local authorities, companies with prospective partners in new markets. Its defining feature is that it is usually not intended to be legally binding, and its defining risk is that "usually" does a great deal of work in that sentence.

What a memorandum of understanding should contain

• The parties, and who within each is accountable — an MOU signed by people who leave is an MOU nobody owns.
• The shared purpose, stated concretely enough that an outsider could tell whether it is being met.
• What each side will actually do, separated by party rather than written as a joint aspiration.
• What each side will not do, where exclusivity or restraint is part of the understanding.
• Resources: money, people, facilities, data — including the honest answer where the answer is none.
• Duration, review points and how either side ends it.
• An explicit statement of legal effect: which clauses are binding and which are not.

The parts that bind you whatever the heading says

Calling a document non-binding does not make all of it non-binding. Courts look at substance and at how the parties behaved.

1. Confidentiality is normally intended to bind, and should be stated as binding rather than left inside the general disclaimer.
2. Data protection obligations apply by law regardless of what the document says about enforceability.
3. Exclusivity and standstill undertakings — an agreement not to talk to others — are commonly held binding even in a non-binding document.
4. Any provision about costs, liability or governing law should be explicitly carved out as binding, or you have a dispute-resolution gap.
5. Conduct matters: if the parties act for two years as though the MOU is a contract, arguing later that it never was is a difficult position.

The failure mode is the opposite of what people expect. Most trouble comes not from an MOU accidentally binding someone, but from an MOU that binds nobody being relied on as though it did — budgets allocated, staff hired, a launch announced, on the strength of a document that carries no obligation to perform. If the plan depends on the other side doing something, that part needs to be a contract.

When to write something else instead

• Money changing hands: that is a services or grant agreement, not a memorandum.
• One side building something the other will use: define acceptance and ownership, which means a real contract with a statement of work underneath.
• Sharing personal data: a data processing agreement or a controller-to-controller arrangement is required, and an MOU does not substitute.
• A commercial relationship expected to repeat: a master service agreement makes the second and third engagement trivial.
• A short-lived commercial negotiation: heads of terms serve the same purpose with a clearer expectation that a contract follows.

Where the memorandum lives

Ettex Docs keeps the memorandum with its version history and, more usefully, with the review dates that most MOUs quietly miss — these documents tend to have an eighteen-month horizon and no owner watching it. Record who signed and when, because the common question later is whether a given activity was covered by the understanding in force at the time. Ettex does not draft agreements and cannot tell you whether a clause binds you; where the arrangement matters commercially, the boundary between binding and non-binding is exactly the part worth a lawyer.