Review Enterprise Saas Agreement Against Company Playbook

---
name: review-enterprise-saas-agreement-company-playbook
task_id: intellectual-property/review-enterprise-saas-agreement-against-company-playbook
description: Reviewing a SaaS agreement against a contracting playbook and related deal context to produce a prioritized deviation and risk memorandum with recommended redline positions.
activates_for: [planner, solver, checker]
---

# Skill: Review Enterprise SaaS Agreement Against Company Playbook

## 1. Subject-matter triage (only if applicable)

- Treat the company playbook as the primary negotiation baseline; review the SaaS agreement against that baseline first, then use the deal-team email chain to adjust priority, urgency, and fallback positions.
- Identify the agreement version actually in scope, any incorporated order form, addenda, exhibits, policies, security terms, and any linked email commitments that may override or refine the main text.
- If the source set contains multiple drafts, revisions, or counterparties' markups, enumerate them before analysis and compare each against the same playbook baseline rather than mixing versions.
- If a provision is absent from the playbook, assess it as a novel risk item and explain why it matters in this deal context.

## 2. Failure modes the skill is correcting

- Using a generic SaaS checklist instead of the company’s approved playbook positions, which misses negotiated “must-have” baseline terms and false positives on acceptable deviations.
- Failing to incorporate the deal-team email chain, which can change the practical risk ranking, reveal commercial constraints, or preserve fallback positions.
- Identifying a deviation without tying it to the governing clause set, related schedules or policies, and the client consequence, leaving the issue descriptively incomplete.
- Treating all deviations as equal; issue memoranda must distinguish material risk from routine cleanup and separate escalation items from negotiable items.
- Overlooking internal inconsistency across the main agreement, attachments, referenced policies, and email-driven commitments.
- Recommending changes without a concrete redline position and fallback language, which leaves the memo advisory but not actionable.

## 3. Legal frameworks / domain conventions that apply

- A contracting playbook is the controlling internal authority for acceptable SaaS terms; deviations should be measured against the stated baseline, not against market custom alone.
- SaaS agreement review typically centers on data rights, permitted use, confidentiality, security, service levels, support, business continuity, termination, liability allocation, indemnity, audit/compliance rights, subcontracting, changes to service or terms, and dispute mechanics.
- Data use and ownership analysis should distinguish customer data, derived data, usage data, and vendor improvements; review whether the vendor’s processing is limited to service delivery or expands into broader operational or commercial use.
- Liability analysis should compare the cap structure, exclusions, and any uncapped carve-outs against the playbook baseline and the deal’s exposure profile.
- Security and compliance terms should be checked for specific obligations, incident notice mechanics, remediation commitments, audit/reporting rights, and flow-down obligations to subprocessors or affiliates.
- Termination and transition provisions should be tested for practical exit rights, data return/deletion, transition assistance, and any fees or impediments that could trap the customer.
- Governing law, venue, dispute escalation, and injunctive relief provisions should be checked for alignment with the company’s standard positions where they affect enforcement leverage.

## 4. Analytical scaffolds

1. Map each playbook position to the corresponding agreement provision and flag every departure from the baseline.
2. For each departure, assess severity using a uniform ordinal scale defined once at the top of the memo, then explain the rating in one line.
3. For each issue, close the analysis by tying it to a concrete source-document anchor, the interacting clause or schedule, and the downstream consequence for the client.
4. Use the deal-team emails to refine priority, identify business constraints, and surface any requested exceptions or fallback positions.
5. For each issue, state the recommended redline position in operational terms, and provide a fallback where the point is negotiable.
6. If the agreement contains a provision not addressed by the playbook, evaluate it independently for legal, operational, or commercial risk and add it to the memo as a novel issue.
7. Check for internal consistency across the main form, attachments, incorporated policies, and any email commitments; flag conflicts even if each clause is individually acceptable.
8. Identify any point that requires a business or legal decision before positions can be finalized, and mark it explicitly.
9. Where the source documents contain controlling authority, quote or cite that authority as presented; where they do not, identify the governing contract principle or standard drafting convention that supports the position.

## 5. Vertical / structural / temporal relationships (only if applicable)

- Review the agreement as a layered package: master terms, order forms, exhibits, addenda, security schedules, privacy terms, support policies, and any incorporated website or reference documents.
- Give priority to provisions that override or qualify others, such as precedence clauses, order-of-precedence language, unilateral update rights, incorporation by reference, and amendment mechanics.
- Track whether obligations apply at signing, during the service term, upon incident, at termination, or after termination; timing affects both severity and redline strategy.
- If the deal-team emails narrow or expand a concept in time or scope, reconcile that change against the written draft and note the mismatch.
- When a provision references another document or policy, analyze the referenced document only to the extent needed to understand the operative obligation and its practical effect.

## 6. Output structure conventions

- Produce a prioritized issue memorandum, with the most significant deviations first.
- State the severity scale once at the top and apply it consistently to every issue.
- For each issue, include: agreement section or provision, playbook baseline, deviation, severity, deal-context adjustment if any, and recommended redline position with fallback.
- Each issue entry must make the consequence clear: why the deviation matters to the client in economic, operational, regulatory, litigation, or transaction terms.
- Include a separate section for novel provisions not addressed by the playbook.
- Include a short conflict-check section if the draft, exhibits, or incorporated materials pull in different directions.
- End with a Recommended Actions block that assigns the next step to the appropriate role and ties it to a practical timing anchor from the deal posture.
- Use plain-text change language for any proposed redline positions so the reader can understand the operative edit without relying on formatting alone.
- Do not reproduce internal document language verbatim unless the task specifically requires quoting; summarize the operative point instead.