Compare Saas Renewal Proposal Against Current Agreement

---
name: compare-saas-renewal-proposal-current
task_id: intellectual-property/compare-saas-renewal-proposal-against-current-agreement
description: Deviation report evaluating a SaaS renewal proposal against the current agreement and amendments, with issue characterization and negotiation guidance for internal presentation.
activates_for: [planner, solver, checker]
---

# Skill: Compare SaaS Renewal Proposal Against Current Agreement

## 1. Subject-matter triage

Treat the current agreement, amendments, and any incorporated schedules or exhibits as one operative contract set. Establish the baseline from the latest integrated terms before comparing the renewal proposal.

If more than one current document, amendment, service schedule, security exhibit, or ordering document is in scope, enumerate each source set first and note how it fits into the operative baseline. If only one operative set exists, say so explicitly.

## 2. Failure modes the skill is correcting

- Comparing the renewal proposal to an obsolete base agreement instead of the integrated current agreement
- Missing amendment-driven changes that silently override earlier terms
- Reviewing commercial terms in isolation from security, privacy, continuity, and data-handling obligations
- Treating internal stakeholder concerns as background rather than as negotiation inputs
- Failing to identify provisions the current agreement expects to carry forward or refresh at renewal
- Stopping at issue spotting without translating the deviation into risk, business impact, and negotiation posture

## 3. Legal frameworks / domain conventions that apply

- Contract interpretation starts with the operative agreement as amended; later-dated provisions control to the extent they conflict with earlier text
- Renewal proposals are negotiation documents, not automatic renewals; compare each proposed change against the currently binding term
- SaaS renewal analysis should cover pricing, term, renewal mechanics, service levels, support, data use, security, audit/right-to-review, confidentiality, indemnity, liability allocation, termination, portability, deletion, and transition assistance
- Security and privacy terms should be tested against the vendor’s stated controls and any existing assessment findings
- Issue characterization should distinguish legal deviation, operational deviation, commercial deviation, and risk-transfer deviation
- Where a legal conclusion depends on a rule, identify the governing contract principle, statute, regulation, or other controlling authority by name or section as reflected in the source set or standard governing framework

## 4. Analytical scaffolds

- Baseline construction: read the full current contract stack and map which provisions are operative, superseded, or supplemented
- Term-by-term comparison: compare the proposal to the operative baseline for each material provision and record the exact deviation
- Interaction check: test each deviation against related clauses elsewhere in the agreement set, including cross-referenced schedules and exhibits
- Security integration: cross-check data protection and security commitments against any existing assessment, audit findings, or internal risk notes
- Business context integration: factor in internal feedback from legal, procurement, finance, IT, security, or the business owner when rating risk and recommending posture
- Consequence analysis: for each deviation, state the practical downstream effect on cost, control, compliance, continuity, or dispute exposure
- Negotiation posture: convert each issue into a recommended internal position, distinguishing must-have edits from preferred asks and acceptable trade-offs

## 5. Vertical / structural / temporal relationships

When the source set contains multiple versions over time, analyze them in chronological order and identify which terms survive, which are replaced, and which are newly introduced at renewal. If a proposal changes a term that is linked to another clause’s operation, analyze the linked provisions together rather than separately.

For each issue, state the scale or magnitude using the figures or thresholds found in the source documents or internal materials, then tie the issue to the interacting clause set and the business consequence. Do not use placeholder arithmetic; use the actual document numbers and commercial context available in the file set.

## 6. Output structure conventions

Produce a GC-ready deviation report in a professional memorandum format. Use conventional sections such as executive summary, assumptions/baseline, issue analysis, risk assessment, and negotiation recommendations.

Include a compact issue table with these fields for each deviation:
- Current operative term
- Proposed renewal term
- Nature of deviation
- Severity
- Risk / business impact
- Recommended negotiation position

Define the severity scale once near the top using a simple ordinal framework such as Critical / High / Medium / Low, and apply it consistently.

Make the report issue-driven: each entry should end with three explicit moves:
- the scale or threshold implicated
- the related clause, schedule, exhibit, or source document it interacts with
- the resulting consequence for the client

End with a clearly labeled Recommended Actions section that assigns each action to the relevant internal role and anchors timing to a milestone, meeting, signing target, or other practical deadline. Use imperative verbs.

If the deliverable is to be exported to a file, ensure the primary report file is created and populated first, and do not treat a summary or cover note as a substitute for the report itself.