Order of precedence: reviewing the master agreement against the statement of work
Reconciling conflicting terms across an MSA and its schedules is a structural problem. How to configure Review to catch precedence inversions before they are signed.
Master Services Agreements (MSAs) are negotiated by counsel. Statements of Work (SOWs) are drafted by the commercial team. The two documents meet at the order of precedence clause. This clause is a mechanical fix for a human problem: the business wants to move fast, and lawyers cannot read every operational schedule.
When a dispute arises, the conflict is rarely about the master terms alone. It is usually a collision between a carefully negotiated limitation of liability in the MSA and a rogue indemnity buried in an SOW appendix. We built Review 4.2 to read across document boundaries. Here is how to configure your playbook to catch these inversions before signature.
The anatomy of a precedence inversion
A precedence inversion happens when a subordinate document attempts to override a core legal protection in the master agreement, either explicitly or accidentally.
Consider a standard technology deployment. The MSA caps liability at twelve months of fees. The SOW, copied from a vendor’s old template, contains a single sentence under a ‘Deliverables’ heading stating that the vendor is fully responsible for all data loss.
If the MSA states that it controls in the event of a conflict, the SOW provision is technically void. But ‘technically void’ still requires a phone call between opposing counsel to resolve, and often a concession elsewhere. If the MSA permits the SOW to override it—provided the SOW explicitly references the overridden clause—the risk is worse. The rogue sentence might survive a strict reading.
To handle this, Review evaluates the precedence clause first. It maps the hierarchy of the transaction suite. When it reads the SOW, it does not evaluate it in isolation. It evaluates the SOW against the established boundaries of the MSA. If an SOW introduces a new warranty, Review flags it as a High severity issue, noting exactly how it conflicts with the master terms.
Configuring the playbook for operational schedules
You do not review an SOW the same way you review an MSA. Applying a master playbook to a commercial schedule generates false positives. The system will flag missing boilerplates, missing governing law clauses, and absent survival provisions.
In ZAAN, playbooks are modular. When reviewing a transaction suite, you assign the master playbook to the MSA and a subordinate playbook to the SOWs, Service Level Agreements (SLAs), and Data Processing Agreements (DPAs).
A subordinate playbook is essentially a negative filter. It ignores commercial terms, project milestones, and pricing tables. It looks exclusively for legal terms that have migrated into the business document.
We recommend configuring the SOW playbook to flag five specific triggers:
- New indemnities or warranties.
- Attempts to redefine terms already defined in the MSA (for example, redefining ‘Confidential Information’ to exclude certain deliverables).
- Rogue termination rights (such as a clause allowing the client to terminate the SOW for convenience, when the MSA requires thirty days’ notice for cause).
- Intellectual property assignments that contradict the master licence.
- Any sentence beginning with ‘Notwithstanding anything to the contrary in the Master Agreement’.
Drafting subordinate documents safely
The safest way to resolve a precedence conflict is to prevent it during drafting. Draft 3.9 allows you to generate SOWs from the context of an executed MSA.
When a user opens Draft to create a new SOW, the system requires the MSA as the base context. This does two things. First, it imports the exact defined terms. If the MSA defines ‘Customer Data’, Draft will ensure the SOW uses the same capitalisation and definition, preventing accidental ambiguity.
Second, it enforces the firm’s house style on the precedence mechanism. If the business team needs to alter a legal term for a specific project—for example, extending the payment terms from net-30 to net-60 for one SOW—Draft will automatically insert the correct override language required by the MSA. It will cite the specific section being amended, rather than relying on a vague ‘notwithstanding’ clause. Every clause generated includes a citation to the firm’s precedent library, proving it has been used in this exact configuration before.
The limits of mechanical conflict resolution
A precedence clause is a fallback. It is not a drafting strategy. Relying on it to resolve sloppy drafting guarantees friction during a dispute.
Identifying explicit conflicts is a basic text-matching problem. Identifying functional conflicts requires reasoning. This is why we deploy ZAAN-7B Counsel for cross-document review. A functional conflict occurs when the SOW does not explicitly contradict the MSA, but creates a situation where the MSA’s protections are impossible to enforce.
For example, the MSA might require the client to provide written notice of a defect within ten days of delivery. The SOW might include a convoluted acceptance-testing protocol that takes thirty days to complete. There is no direct textual conflict between ‘notice’ and ‘testing’, but the operational timeline breaks the legal requirement. ZAAN-7B Counsel identifies these timeline collisions, flagging them as Note severity issues for counsel to review.
An order of precedence clause will not save a transaction if the business operates on the terms of the schedule.