Review Msa Playbook Deviation Review

Skill: Review MSA Playbook Deviation Review

1. Subject-matter triage

When the source set includes a redlined MSA, a clean template, internal contracting playbook guidance, and deal summary or DDQ materials, treat the clean template as the baseline form, the playbook as the approval standard, and the deal materials as context that can confirm, qualify, or contradict the redlines.

Before analysis, confirm whether there is one agreement or multiple related versions; if more than one, enumerate each version and compare them separately rather than collapsing them into one pass.

Use the template to catch both explicit edits and silent changes. Use the playbook to determine whether each deviation is acceptable, acceptable only with fallback, or outside authority. Use the deal summary and DDQ to test whether the agreement tracks the commercial and factual record.

2. Failure modes the skill is correcting

• Comparing the redline only to the playbook and missing changes that appear only when set against the clean template
• Missing silent deletions, moved clauses, reordered definitions, and structural edits that are not obvious from tracked changes alone
• Treating playbook “preferred” and “fallback” positions as interchangeable instead of classifying where the redline lands relative to each
• Failing to tie each issue to the agreement section, the template baseline, and the specific playbook position that controls it
• Ignoring deal summary terms or DDQ facts that should be reflected in the MSA or that expose inconsistency with the draft
• Writing a narrative summary that does not end in concrete disposition, priority, and next-step guidance

3. Legal frameworks / domain conventions that apply

• Contract review is clause-level and version-aware: tracked changes identify overt edits, but side-by-side comparison against the clean form is necessary to detect deletions, substitutions, and structural reshuffling
• Internal playbooks usually encode an approval hierarchy, with a preferred position, an acceptable fallback, and a point at which escalation is required
• Agreement review in this setting is not only legal issue-spotting; it is also deviation classification against internal drafting authority and business deal alignment
• DDQ and deal summary materials may function as interpretive context for operational scope, data handling, service levels, risk allocation, and commercial assumptions
• Where the source set states a governing rule, internal policy, or approval condition, cite that controlling source explicitly in the deviation analysis rather than implying it

4. Analytical scaffolds

1. Build the comparison set: clean template, redlined MSA, playbook, deal summary, and DDQ.
2. Identify every deviation from the template, including:
   • textual additions, deletions, and substitutions
   • silent deletions
   • moved provisions
   • reordered defined terms
   • changed cross-references
   • structural changes that alter meaning or allocation of risk
3. For each deviation, compare the redlined position against the playbook hierarchy:
   • within preferred position
   • outside preferred but within fallback
   • outside fallback and requiring escalation
4. For each deviation, test whether it also conflicts with or is supported by the deal summary or DDQ.
5. For each deviation, state the operational or transactional consequence for the client if the change is accepted.
6. If the same issue is repeated across multiple sections, treat each impacted clause as a separate entry while noting the common root issue.
7. Prioritize the report by disposition:
   • escalation-required items first
   • negotiation items next
   • within-bounds confirmations last

5. Vertical / structural / temporal relationships

When a change in one clause affects another provision, capture the relationship explicitly. Typical dependencies include:

• definition changes that alter multiple operative clauses
• indemnity, limitation of liability, and insurance provisions that allocate the same risk in different places
• order-of-precedence or incorporation language that changes how the template and exhibits interact
• service, security, confidentiality, data-processing, and audit clauses that rely on one another
• survival, termination, and suspension language that changes remedies over time

If the redline changes timing, notice, cure, renewal, payment, or termination mechanics, assess the downstream effect across the agreement lifecycle rather than as a standalone edit.

6. Output structure conventions

• Produce a full deviation report in a conventional issues-report format, not a simple checklist.
• Define an ordinal severity scale once at the top and apply it uniformly to every entry.
• For each deviation entry include, at minimum:
  • severity
  • agreement section
  • template position
  • redlined position
  • playbook position reached or exceeded
  • classification / disposition
  • deal summary or DDQ status
  • practical consequence
  • recommended response
• Use robust change notation in the written report so each change is legible even outside tracked formatting, such as explicit deletion, insertion, or replacement markers where needed.
• Include a separate section for silent changes and structural deviations not visible from tracked changes.
• If a deviation relies on a governing policy or legal principle identified in the source materials, cite that authority by name and section or other controlling reference as stated in the materials.
• End with a concise Recommended Actions section that assigns each action to a responsible role and gives a timing anchor tied to the deal process or an expressed deadline.
• The report should read as an actionable disposition memo: it should explain what changed, why it matters, where it sits relative to playbook authority, and what should happen next.