Letter of Intent vs Memorandum of Understanding (2026)

Letter of intent vs memorandum of understanding: what is the difference? A letter of intent (LOI) and a memorandum of understanding (MOU) are both preliminary documents that record where parties have got to before a full contract is signed. In everyday use the two terms overlap heavily, and people often use them interchangeably. There are, however, some typical differences in form and use: - A letter of intent is usually written as a letter, from one party to another, setting out that party's intention to proceed toward a deal on broadly agreed terms. It is common in acquisitions, real-estate deals, financing and large purchases.

• A memorandum of understanding is usually written as a mutual document, signed by two or more parties, recording a shared understanding and the framework for how they will work together. It is common between organisations, in collaborations, joint ventures and public-sector partnerships, and in multi-party arrangements. The far more important question than the label is: is it binding? This is general guidance, not legal advice. ## Is an LOI or MOU legally binding? Neither name decides the answer. Whether a document is binding depends on what it says and what the parties intended, judged by its wording, not its title. The key points: - A document can be wholly non-binding (a statement of intent only), wholly binding (a contract in all but name), or, most commonly, partly binding (some clauses bind, others do not).
• In most LOIs and MOUs, the commercial heart (the price, the final deal) is expressly non-binding and "subject to contract" and due diligence, while certain protective clauses are binding, typically confidentiality, exclusivity or a no-shop period, costs, and governing law.
• Courts look for the intention to create legal relations, certainty of terms, and (in common-law systems) consideration. A document that is specific, signed and acted upon looks binding, whatever it is called; a vague "we hope to work together" does not. The practical risk is accidental bindingness: a document meant as a friendly understanding that a court later reads as an enforceable contract, or a binding obligation the parties thought was just talk. ## How to make it binding, or non-binding, on purpose Decide clause by clause, and say so. To keep the commercial terms non-binding: - State clearly, near the top, that the document is a statement of intent, is not legally binding, and is "subject to a formal written agreement".
• Avoid definite contractual language ("shall pay", "agrees to buy") for the parts you do not want to bind.
• Make completion conditional on signing a definitive agreement, board approval, due diligence and any regulatory consents. To make specific clauses binding: - Add a clause that expressly identifies which provisions are binding (for example confidentiality, exclusivity, costs, governing law and dispute resolution) and states that the rest is not.
• Use clear obligation language in those clauses only.
• Have it signed and dated by authorised signatories. A well drafted LOI or MOU usually contains both: a non-binding commercial outline and a short, binding "legal effect" section that names the exceptions. ## Typical contents | Element | Usually in an LOI | Usually in an MOU | |---|---|---| | Form | A letter, one party to another | A mutual document, two or more parties | | Common use | M&A, real estate, financing, purchases | Collaborations, joint ventures, public bodies | | Commercial terms | Outline of the proposed deal | Framework for working together | | Binding parts (typical) | Confidentiality, exclusivity, costs | Confidentiality, each party's responsibilities | | Legal effect clause | Strongly recommended | Strongly recommended | ## Red flags - No statement of legal effect. If a document is silent on whether it binds, a court decides, and you may not like the answer.
• Mixed signals. A heading that says "non-binding" over clauses written in firm "shall" language.
• An exclusivity or no-shop clause that is more onerous, or longer, than the party realised, because that part usually is binding.
• Treating an MOU as "just a formality" and acting on it as if the full deal were done. ## A note on jurisdiction The principles above are broadly shared across common-law systems, including India, England, Singapore and Australia, where enforceability turns on intention to create legal relations, certainty and consideration. India applies the Indian Contract Act, 1872; a document that meets its requirements can be enforceable whatever it is called, and courts have treated MOUs as binding where the substance was a contract. Civil-law systems and public-international-law MOUs (between states or public bodies) follow different rules again. Some MOUs between government bodies are deliberately framed as non-binding political commitments. Always check the governing law, and if you want certainty either way, say so expressly in the document. ## Where a contract workspace helps Deals rarely turn on a single LOI or MOU; they move through a chain of drafts, side letters, term sheets and finally a definitive agreement, and the danger is a binding exclusivity or confidentiality term that gets lost, contradicted or forgotten as the documents pile up. Knowing which clauses bind, across many versions, is the hard part. That is the idea behind a single AI contract workspace. It can model a document as a structured clause tree so the binding and non-binding parts are clearly separated, flag terms that are favourable, neutral or unfavourable to you, let you edit the legal-effect language in plain English, and keep every version and key date (such as the end of an exclusivity period) on a live timeline. Tools such as Adira are built around that one-workspace idea. This article alone is enough to tell an LOI from an MOU and to control what binds; a workspace simply keeps the drafts, the binding clauses and the deadlines connected.