Order Form vs MSA: How They Work Together

The short answer A master services agreement (MSA) and an order form are two parts of one deal. The MSA sets the legal terms that stay the same across every purchase: liability, indemnity, confidentiality, data protection, term and termination, dispute resolution. The order form sets the commercial terms that change with each purchase: what is being bought, how much of it, the price, the start date and the length of that specific subscription or engagement. Read together, the MSA is the rulebook and the order form is the scorecard for a single game. Neither is complete on its own. The order form points back to the MSA for all the legal protection, and the MSA relies on the order form to say what was actually sold. ## Why deals are split this way Splitting the contract lets a buyer and seller negotiate the hard legal points once, then transact many times without reopening them. This matters most for subscription and services businesses, where the same customer may add seats, modules or new projects several times a year. The benefits are practical: - Speed on repeat purchases. Once the MSA is signed, a follow-on order is a one or two page document. There is no need to renegotiate indemnity caps to add fifty more licences.

• Cleaner approvals. Legal reviews the MSA closely. Later order forms mostly need commercial sign-off on price and scope, which the deal desk or sales leadership can own.
• Consistency. Every order under the MSA inherits the same protections, so the company is not carrying ten different liability regimes for one customer. ## What belongs in the MSA The MSA holds the terms that should not change from one purchase to the next: - Definitions and the structure of the relationship
• Confidentiality and data protection or privacy terms
• Warranties and disclaimers
• Limitation of liability and indemnity
• Intellectual property ownership and licence grants
• Insurance, if required
• Term, termination and the effect of termination
• Governing law, jurisdiction and dispute resolution
• Boilerplate: assignment, notices, force majeure, entire agreement, order of precedence ## What belongs in the order form The order form holds the facts of one specific purchase: - The products, services or SKUs being bought
• Quantities, such as seats, units or named projects
• Fees, billing frequency and payment terms
• The subscription or service start date and the committed term for this order
• Any order specific commercial terms, such as a one time discount or a ramp schedule
• Reference to the governing MSA by name and date A good rule: if a term describes the shape of the relationship, it goes in the MSA. If it describes the size and price of this transaction, it goes in the order form. ## The order of precedence clause The single most important link between the two documents is the order of precedence clause. It tells a reader which document wins when they appear to conflict. There is no universal correct answer, and the two common choices lead to different behaviour: 1. MSA controls. The legal terms always govern, and an order form cannot quietly change liability or indemnity. This protects whichever party drafted the MSA and wants its legal terms locked.

2. Order form controls for the terms it addresses. This lets a specific deal vary a general term, for example a higher liability cap for a large order, without amending the MSA. Many MSAs use a hybrid: the MSA controls except where the order form expressly states that it overrides a named MSA clause. Express override language is the safe pattern, because it stops a stray price line from accidentally rewriting the indemnity. ## How the documents reference each other Each order form should name the MSA it sits under, including the MSA date and the parties, and state that it incorporates the MSA by reference. The MSA, in turn, should define what an order form is and say that each executed order form becomes part of the agreement. Watch for three common gaps: - Orphan order forms that do not name any MSA, leaving the legal terms unclear.

• Conflicting dates, where the order form points to an MSA version that was later amended.
• Silent renewals, where the order form sets a term but neither document says what happens at the end of it. ## Order form, MSA, SOW and SLA: who does what The MSA family often includes more than two documents: - Statement of work (SOW). Used in services deals to describe deliverables, milestones and acceptance for a project. An SOW is close to an order form in function but carries more operational detail.
• Service level agreement (SLA). Sets uptime, support response times and the remedies, often service credits, if those are missed. It can live inside the MSA or as an attachment.
• Data processing agreement (DPA). Required where personal data is processed, and usually attached to the MSA. In a typical software deal you will see an MSA, one or more order forms, a DPA and an SLA, all tied together by the MSA. ## A quick worked example A buyer signs an MSA in January that caps the vendor liability at the fees paid in the prior twelve months. In March the buyer signs an order form for 100 seats at a set annual price, pointing to the January MSA. In September the buyer adds 50 seats on a second order form. Both orders inherit the January liability cap, the confidentiality terms and the governing law. Only the seat count, price and dates differ. If the September order needs a higher liability cap for a sensitive workload, it says so expressly, overriding only that one MSA clause. ## Common mistakes to avoid - Burying legal terms in an order form where they will not get proper review.
• Leaving out the order of precedence clause, then arguing about it later.
• Using a new MSA for every order, which defeats the purpose of the structure.
• Forgetting to attach or reference the current DPA and SLA.
• Letting sales send order forms that do not name the governing MSA. ## Bringing drafting, review and tracking into one place The pair only works if the link between the MSA and every order form is accurate and visible. In practice that link breaks because the MSA lives in one system, the order forms live in a CRM, and no one can see at a glance which orders sit under which agreement. A single workspace helps here: a place to draft the MSA and each order form, review them against each other for conflicts, and track every executed order against its parent MSA, its renewal date and its obligations. Adira is built around that idea, with contracts modelled as structured documents so an order form and its MSA can be read as one connected agreement rather than two loose files. The point is not the tool but the discipline: one place where the rulebook and the scorecard stay in sync.