Master Service Agreement Template and How to Draft One (2026)

What is a master service agreement and when do you need one? A master service agreement (MSA) is a contract that sets the general terms between two companies, usually a service provider and a customer, so that future work can be added quickly through short statements of work (SOWs) without renegotiating the legal terms each time. You need an MSA when you expect an ongoing relationship with repeated projects: an agency and a client, a software vendor and a customer, a consultancy and a company. The MSA holds the terms that rarely change (payment, liability, IP, confidentiality), and each SOW holds the details that do (scope, deliverables, timeline, price). Think of it as a two-layer structure: - MSA: the stable legal framework, signed once.

• SOW: the project-specific order, signed for each piece of work, incorporating the MSA by reference. This is a general template, not legal advice. Have a qualified lawyer in your jurisdiction review the final document for a significant engagement. ## MSA vs SOW: what goes where | Belongs in the MSA | Belongs in the SOW | |--------------------|--------------------| | Payment terms and invoicing | Scope and deliverables | | Liability and indemnity | Timeline and milestones | | Intellectual property ownership | Fees for that project | | Confidentiality | Named contacts | | Term and termination | Acceptance criteria | | Governing law and disputes | Any project-specific terms | The golden rule: if a term is true for the whole relationship, it goes in the MSA; if it is true only for one project, it goes in the SOW. ## Master service agreement template ``` MASTER SERVICE AGREEMENT This Agreement is made on [date] between: (1) [Provider legal name], of [address] (the "Provider"); and (2) [Customer legal name], of [address] (the "Customer"). 1. STRUCTURE This Agreement sets the general terms for services. Specific services are described in Statements of Work ("SOWs") that reference this Agreement. If an SOW conflicts with this Agreement, this Agreement prevails unless the SOW expressly says otherwise. 2. SERVICES The Provider will perform the services described in each SOW with reasonable skill and care. 3. FEES AND PAYMENT The Customer will pay the fees in each SOW. Invoices are due within [e.g. 30] days. Late amounts may carry interest at [rate] as permitted by law. Fees are exclusive of applicable taxes. 4. TERM AND TERMINATION This Agreement starts on the date above and continues until terminated. Either party may terminate for convenience on [e.g. 30] days' written notice, or immediately for material breach not cured within [e.g. 15] days of notice. Active SOWs continue unless also terminated. 5. CONFIDENTIALITY Each party will protect the other's confidential information, use it only for this Agreement, and not disclose it except to those who need to know and are bound by similar duties. This survives for [e.g. 3] years after termination. 6. INTELLECTUAL PROPERTY Each party keeps the IP it owned before. Ownership of deliverables created under an SOW is [assigned to the Customer on full payment / as stated in the SOW]. Each party grants the other any licence needed to perform the services. 7. WARRANTIES The Provider warrants it will perform with reasonable skill and care and has the right to enter this Agreement. Except as stated, services are provided without other warranties to the extent permitted by law. 8. LIMITATION OF LIABILITY Neither party is liable for indirect or consequential loss. Each party's total liability under this Agreement is capped at [e.g. the fees paid in the prior 12 months], except for breaches of confidentiality, indemnified claims, or liability that cannot be limited by law. 9. INDEMNITY Each party will indemnify the other against third-party claims arising from its own breach, negligence, or infringement, subject to prompt notice and cooperation. 10. INSURANCE The Provider will maintain reasonable insurance appropriate to the services. [Specify types and amounts if required.] 11. DISPUTE RESOLUTION The parties will first try to resolve disputes in good faith. Unresolved disputes are subject to [courts / arbitration] in [place]. 12. GOVERNING LAW This Agreement is governed by the laws of [jurisdiction]. 13. GENERAL Neither party may assign without consent (not unreasonably withheld). Notices must be in writing. This Agreement and its SOWs are the entire agreement and may be amended only in writing. If any term is unenforceable, the rest remains in force. Signed for the Provider: ____________ Customer: ____________ Name / title / date Name / title / date

2. **Precedence (clause 1).** Decide whether the MSA or an SOW wins in a conflict. Most MSAs let the MSA prevail except where an SOW expressly overrides it, so one project can vary a term without rewriting the framework.
3. **Payment (clause 3).** Set the payment window, any late interest (within legal limits), and how taxes are handled.
4. **Term and termination (clause 4).** Choose the notice period for termination for convenience and the cure period for breach. Decide what happens to active SOWs when the MSA ends.
5. **IP (clause 6).** The most negotiated clause. Customers usually want to own the deliverables; providers want to keep their pre-existing tools and know-how. A common middle ground assigns deliverables to the customer on full payment while the provider keeps its background IP.
6. **Liability cap (clause 8).** Set a cap both sides can live with, often tied to fees paid, with carve-outs for confidentiality, indemnities, and liabilities that cannot be limited by law.
7. **Disputes and governing law (clauses 11 to 12).** Choose a forum and law both sides can realistically use. For cross-border deals this needs care, because enforceability and procedure vary by jurisdiction. ## A simple SOW to pair with it Each SOW should name the project, describe the scope and deliverables, set the timeline and milestones, state the fees and payment schedule, give acceptance criteria, and reference the MSA so its terms apply. Keep SOWs short; the heavy legal terms live in the MSA. ## Common mistakes to avoid - **Putting project details in the MSA.** Scope and price belong in the SOW, so you do not reopen the MSA for every job.
- **No precedence clause.** Without one, an MSA and SOW conflict is hard to resolve.
- **An uncapped liability.** Few providers should accept unlimited liability; few customers should grant it without carve-outs.
- **Vague IP ownership.** Decide clearly who owns deliverables and when, and separate background IP.
- **Forgetting termination of SOWs.** Say what happens to live work when the MSA ends.
- **Ignoring jurisdiction.** Stamp duty, execution formalities, and the enforceability of liability caps and arbitration clauses vary. In India, stamping rules differ by state; elsewhere, notarisation and formalities differ. This varies by jurisdiction. ## Where a contract workspace helps Drafting the MSA once is the easy part; spinning up each SOW, keeping versions straight, tracking renewals and termination notice windows, and checking that every new SOW matches the master terms is the ongoing work, and it is exactly what an AI contract workspace can carry. Instead of copying last quarter's SOW and hoping it still fits the MSA, you generate documents from a brief, see each clause marked favourable, neutral, or unfavourable to your company, edit a term in plain English, and let the workspace link each SOW to its MSA and remember the key dates. [Adira](https://adiralaw.com) is one such workspace, keeping drafting, per-clause risk, version history, e-signing, and renewal tracking together and tuned to how your company contracts. The template above works on its own; a workspace just makes running an MSA and its SOWs over time far less manual. Put the stable terms in the MSA, the project details in each SOW, and set precedence, IP, and the liability cap with care.