Memorandum of understanding (MOU) template for Word (free download)
Memorandum of understanding (MOU) template for Word (free download)
Every serious business relationship starts with a conversation, not with a contract. Two companies meet, see that they could do something together — distribute a product, provide a service, share a warehouse, develop a project — and spend weeks exploring the idea without having signed anything yet. In that middle stretch, when there is real interest but no obligations on either side, a memorandum of understanding is more useful than any other document.
A memorandum of understanding, usually shortened to MOU, is a short document in which two parties write down what they understand their collaboration to be: what they are looking for, what each one contributes, when they plan to review it and how much notice either side needs to step away. It is not a contract and does not try to be one; its value lies in organising the conversation, aligning expectations and leaving a record of what was discussed before anything becomes enforceable.
This memorandum of understanding template for Word already carries the full structure: letterhead, city and date, centred title, the details of both parties, the purpose, the commitments table, the term and termination section, the clause on the status of the document, the signatures, the copy line and the legal notice. You only have to replace the bracketed fields, adapt it to your company and have it reviewed before signing.
⬇ Download memorandum of understanding (.docx)
What a memorandum of understanding is
A memorandum of understanding is a statement of intent: it describes the general framework of a relationship that has not been formalised yet. It is written in plain language, with numbered sections and visible headings, and it is signed like any other company document. Its job is not to bind anyone but to put a shared starting point on paper, with names, dates and responsible people attached.
The difference from a contract is fundamental and worth being clear about before signing either one. A contract creates enforceable obligations: it states what is delivered, by when, at what price and what happens if someone fails to deliver. A memorandum, by contrast, declares an intention and a working route. In this template that difference appears explicitly in section five, which states that each obligation becomes binding only when the corresponding contract or definitive document is signed.
From an organisational point of view, the memorandum does three things that become obvious when a negotiation cools down or when the person handling it changes jobs. First, it forces both sides to write down what they believe they agreed, and that exercise tends to surface the disagreements the conversation had glossed over. Second, it supports internal work: whoever has to request budget approval, reserve staff or commit warehouse space can show the document and explain where the idea came from and how far it goes. Third, it leaves an orderly record, with a date, a version and a filed copy for each party, so nobody has to rebuild from memory months later what was said at the beginning.
It is just as useful to know what not to expect from it. A memorandum of understanding does not set prices, quantities, warranties or liability for damages, and it is not the document you use to demand a delivery. If the relationship needs those things from day one, the right document is a contract, not a memorandum, and forcing the memorandum to do that job only produces arguments about what was really promised.
What it is for in practice
- Recording the start of an alliance or a possible joint venture between two companies, before prices, volumes and responsibilities are discussed.
- Setting the general scope of a shared project: what it is about, in which area, with which product or service, and what is left out at this stage.
- Putting on paper what each party contributes — technical information, staff, premises, commercial contacts or production capacity — so that nobody takes for granted what was never promised.
- Ordering the previous steps: who prepares the technical proposal, who checks the numbers, by when each side replies and who the contact is inside each company.
- Supporting the internal case for whoever must request budget approval, hire staff or commit warehouse space to an idea that is not yet a contract.
- Providing an orderly exit: if the negotiation does not move forward, the closing date and the way to end it with written notice are already on record, so nobody has to give awkward explanations.
What the template includes
The file follows the classic order of a document signed between two companies and comes with the fields already marked between brackets so that you only replace them with real data. This is the structure, section by section:
| Section of the document | What is written there |
|---|---|
| Letterhead | Company name, company ID, address, city, phone, email and website. It is the same header used on the company's letters and invoices. |
| City and date | Place and date of signature, written in full and without abbreviations. |
| Title | Centred and in capitals: MEMORANDUM OF UNDERSTANDING. |
| 1. Parties | Details of both parties: legal name, company ID, representative and position of the signatory. If more than two take part, one block is added for each. |
| 2. Purpose | One paragraph describing the shared interest: the collaboration, project or business relationship, in general terms. |
| 3. Commitments of the parties | A three-row table: what the first party undertakes to do, what the second one does, and what both contribute jointly. |
| 4. Term and termination | Start date, end date, notice period to terminate and the date of that notice. |
| 5. Status of this document | The clause stating that the memorandum expresses an intention and does not bind the parties until the corresponding contract or definitive document is signed, and that either party may end it by giving written notice. |
| 6. Signatures | Space for the signature of both parties, with name, company ID and position under each one. |
| Copy | Final line stating which file each copy of the document goes to. |
| Legal notice | Closing note: this is a statement of intent and not a contract, and it should be reviewed with the company's adviser before signing. |
How to use the template, step by step
- Download the Word file and save it with a name that identifies the project and the year, for example mou-alliance-2026. That way you find it later without opening folders at random.
- Replace the letterhead and the footer details: company name, company ID, address, city, phone, email and website. Delete every bracket and check that no other company's name is still in the file.
- Write the city and the full date of signature, the way a formal letter is dated.
- Fill in the parties section with the legal name, company ID, representative and position of each side. Check that the person signing actually holds the authority the company grants for this kind of document.
- Write the purpose in a single paragraph that answers three questions: what relationship is intended, how far it reaches and what is left out at this stage.
- Complete the commitments table with its three rows: first party, second party and joint contribution. Write concrete commitments with a verb and a result, not good intentions.
- Define term and termination: start date, end date, how many days of notice either party must give and the date of that notice. If the number of days is left blank, the argument arrives exactly when you most need it settled.
- Check the copy line and prepare the signatures; print two copies, sign both and hand one to the other party. File yours where company documents belong, not on someone's desktop.
What to check before signing
- That the purpose describes a concrete relationship and not a generic wish to collaborate in the future.
- That no commitment is left vague: phrases like supporting whatever is required say nothing and will later be read in two different ways.
- That the dates are coherent with each other: the end date after the start date, and a notice period the company can realistically meet.
- That section five remains intact, with no wording that accidentally turns the memorandum into an enforceable commitment. It is the heart of the document.
- That the person signing for each party has the authority to do so and that their name and position match the parties block.
- That the legal notice stays in place and that the review with the company's adviser happens before signing, not after. Adapting the text to each party's operation and country is part of the work, not paperwork.
What goes in the bracketed fields
The brackets in the file are not decoration: they mark the points that have to be decided. There go the names or legal names, the company ID and the position of each representative, the shared interest described in the purpose, the commitment of each party, and the start, end and notice dates. Also the number of days of notice required to terminate the memorandum.
That last point deserves a pause. The notice period is the only piece of the memorandum that resembles an operating rule, so it should be set according to how long each company needs to dismantle what has already started: gathering the shared information, closing the open fronts, telling the people who were already working on it. Too short a period leaves the other party without room to move; too long a period keeps alive a relationship that is no longer going anywhere. Neither value is copied from another document: it is agreed in the conversation and written down in plain words and clear numbers.
When to move to a system
The memorandum of understanding brings order to the stage of intention, but it falls short once the relationship really starts and there is stock, orders, deliveries and dates running. At that point the questions stop being about what we agreed and become how many units are in the warehouse, what is still pending with each supplier and which documents are past their date with nobody watching them. A shared folder does not answer that. When a company reaches that point, it is worth moving to an inventory and document system that keeps versions, warns about due dates and lets you rebuild the history of every open front. Kardex Tauro is built for that transition: keeping everything written in a stable format, with names and dates that do not depend on who was in the meeting. Kardex Tauro does not replace the judgement of the parties or the work of the adviser; it is the part of the operation worth automating so that the conversation does not get lost in memory.
Notice: a general model, not legal advice
This template and this article are a general model for internal use. They are not legal advice and do not replace a professional review: before signing a memorandum of understanding, go over the text with your company's adviser, adapt it to your operation and to the rules of your country, and confirm who is allowed to sign on behalf of each party. The Word file already carries this notice at the end; it is worth keeping even when the document is adapted.
