This page lists three turns, the messages you send to the AI one after another in the same chat, and then a check of the answer. Keep it open next to your chat. Each turn shows the next thing to paste, with the values you entered already filled in. Nothing is sent from this page, and your conversation stays in the AI tool you are using.
Paste the full SOW including every schedule, exhibit, and addendum attached to it.
Quote the MSA clauses on precedence, IP, liability, payment, acceptance, change orders, and data.
The work, the price, the duration, and the deadline pressure on signature.
Determines whether a conflict with the MSA is a threat to catch or a position to defend.
What the MSA says governs, and whether the SOW tries to say something different.
Watch for these throughout
Vendors staple new exhibits to SOWs: security addenda, AI-use terms, updated support policies. Read every attachment, because an addendum can amend the MSA by reference.
Some MSAs expressly allow an SOW to override numbered sections. If yours does, the vendor's language may be effective rather than merely aggressive. Check before you call it a conflict.
A not-to-exceed cap is worthless if the vendor can issue change orders unilaterally. Confirm the change-order right, not just the number.
If the SOW expands data access or brings a new environment into scope, your DPA, security exhibit, and vendor risk assessment may all need to be updated before signature.
The model only sees the MSA excerpts you paste. If you omit the survival, insurance, or subcontracting clause, it cannot tell you the SOW just contradicted it.