MOU against contract

Why an understanding is worth writing at all

If a document cannot be enforced, the reasonable question is why anybody spends an afternoon drafting one. The answer is that most collaborations fail on misunderstanding rather than on bad faith, and the act of writing forces the awkward questions early: who pays for what, who is in charge on the day, whose insurance covers the volunteers, what happens when one side wants out. A memorandum that surfaces those questions has already earned its keep, even though nobody could sue on it. It also gives a board, a funder or an auditor something to look at, which for community organisations and public bodies is often the actual reason it exists. Treat it as governance rather than as law and it stops being a weak contract and becomes a good record.

How a memorandum turns into a contract without anybody deciding to

Courts look at substance. A document that names precise sums, fixed dates, deliverables and a payment schedule, and that both sides then perform, is very hard to describe as an understanding. Add language such as will pay, must provide or agrees to supply and the intention test starts to swing as well, because commercial parties dealing at arm's length are presumed to mean what promises sound like. The disclaimer helps but does not settle it, particularly where the conduct that followed looks like performance of a contract. The practical rule is that if a page could be handed to a stranger who could then run the arrangement from it, it is probably a contract and should be drafted as one.

Marking the clauses that are meant to bind

Most memoranda need a small binding core. Confidentiality over what each side sees. Insurance and indemnity, because somebody has to carry the risk of an injury in the shared workshop. Sometimes intellectual property, where a collaboration produces something. The clean pattern is one clause near the front listing the numbered paragraphs that have legal effect and stating that the remainder is a statement of intention only. Do not scatter the binding provisions through the document, and do not rely on the reader inferring which is which from tone. A person reading it in two years, after everybody who wrote it has moved on, should be able to see the split in five seconds.

What each party should insist on before signing

A term and an exit. Twelve months with a review point beats an open ended arrangement that nobody revisits until it has quietly become a habit. A named contact on each side, by role rather than by person, so the document survives staff turnover. Insurance stated as a fact, with the type of cover and the minimum sum, since this is the clause that matters if anything goes wrong. And a short paragraph on what happens to shared property, data or equipment when the arrangement ends, because that is the conversation nobody wants to have at the point of ending it.

When to stop writing memoranda and write a contract

Three signals. Money is now moving between the parties rather than each bearing their own costs. One side is relying on the other in a way that would hurt if it stopped, such as staffing a service or holding a lease. Or a third party, a funder, an insurer or a regulator, has started to ask what the arrangement actually is. Any one of those means the relationship has outgrown a statement of intent. The replacement does not have to be long: a services agreement of four pages with scope, price, term, liability and termination will do more work than fifteen pages of understanding. Making the change is easier than most people fear, because the memorandum has already done the hard thinking. The scope, the parties and the practical arrangements are written down; what the contract adds is price, liability, term and a way out, which is a short conversation between people who already trust each other.

Questions people ask