Compare Saas Agreement Against Service Level Standards

---
name: compare-saas-sla-vs-internal-standards
task_id: intellectual-property/compare-saas-agreement-against-service-level-standards
description: Gap analysis memorandum comparing a SaaS agreement's service level provisions against internal service level standards, identifying material deviations and omissions.
activates_for: [planner, solver, checker]
---

# Skill: Compare SaaS Agreement Service Level Provisions Against Internal Standards

## 1. Subject-matter triage

- Treat the internal standards as the baseline and the SaaS agreement as the negotiated overlay.
- Identify the governing comparison set before analysis begins: service levels, measurement rules, credits, exclusions, escalation rights, reporting, remedies, and any related operational commitments.
- If the source set contains multiple service-level dimensions or time periods, enumerate each one explicitly before comparing them; do not collapse distinct metrics into one blended assessment.
- If the email supplies context about urgency, business criticality, or negotiation posture, use it to frame materiality and recommended follow-up, not to replace clause-by-clause comparison.

## 2. Failure modes the skill is correcting

- Comparing isolated metrics without assessing the combined operational effect of multiple shortfalls against the internal baseline.
- Treating service credits as an adequate cure without testing whether the credit structure is proportionate, collectible, and practical in light of the likely disruption.
- Missing the impact of caps, carve-outs, procedural hurdles, or exclusive-remedy language on the real value of the SLA remedy.
- Failing to identify internal-standard topics that are omitted from the agreement entirely.
- Stopping at description instead of stating the quantitative benchmark, the interacting provisions, and the downstream consequence for the business.
- Using loose priority labels instead of a consistent severity scale for each issue.
- Recommending changes without tying them to a responsible role and timing anchor.

## 3. Legal frameworks / domain conventions that apply

- SaaS service level provisions commonly address uptime, response and resolution times, maintenance windows, measurement methodology, credits, reporting, escalation, and termination or cure rights.
- Internal service level standards represent the organization’s minimum acceptable performance; deviations create operational risk even when they do not breach the agreement on their face.
- Compare both absence and lowering of standards: a missing topic is a gap; a present-but-weaker term is a deviation.
- Service credit provisions should be evaluated for trigger threshold, calculation method, cap, exclusions, claim process, and whether credits are the exclusive remedy.
- Where the agreement refers to external rules, service policies, or incorporated schedules, analyze those cross-references as part of the operative SLA package.
- When stating a legal proposition, tie it to the controlling authority named in the source materials or to the operative contractual text being compared; do not state conclusions in the abstract.

## 4. Analytical scaffolds

- Build a provision inventory from the internal standards first, then map each item to the agreement.
- For each item, determine:
  - whether the agreement addresses it at all;
  - whether the standard is met, diluted, or exceeded;
  - whether another clause changes the practical effect;
  - whether the deviation matters operationally or economically.
- For each identified issue, close the analysis by stating:
  - the relevant threshold, metric, or other source-based scale;
  - the clause, schedule, policy, or email context that interacts with it;
  - the concrete consequence for the client.
- Apply an explicit severity label to every issue using a uniform ordinal scale defined once at the top of the memo.
- Assess the credit structure as a system, not as a single number: threshold, accrual, cap, exclusions, remedies, and redemption mechanics should be read together.
- Test cumulative impact across all deviations; a cluster of moderate shortfalls may create a material overall risk even if each item looks manageable in isolation.
- Separate analysis of contract text from drafting recommendations; the former identifies the gap, the latter proposes how to close it.

## 5. Vertical / structural / temporal relationships

- Compare the internal standard, the agreement language, and any incorporated documents as a layered stack; later or more specific terms may narrow earlier general promises.
- Treat measurement periods, service windows, notice deadlines, cure periods, and claim submission periods as temporal constraints that can materially affect enforceability or recovery.
- If the agreement contains multiple service tiers, carve-outs by system, or different remedies by incident type, analyze each branch separately.
- If the email reveals an anticipated transition, implementation milestone, or upcoming renewal, anchor the practical significance of the gap to that timing.

## 6. Output structure conventions

- Write a gap analysis memorandum, not a negotiation letter.
- Use a conventional memo shape with:
  - short executive summary;
  - severity legend;
  - comparison table or issue matrix;
  - discussion of gaps and deviations;
  - service credit and remedy analysis;
  - cumulative impact assessment;
  - recommended actions.
- For each entry in the issue matrix, include:
  - internal standard;
  - agreement provision;
  - gap or deviation classification;
  - severity;
  - business impact;
  - interacting clause or source;
  - recommended remediation.
- Keep issue descriptions concrete and source-linked; do not generalize beyond the documents supplied.
- End with an explicit Recommended Actions section that assigns each action to a role and ties it to a deadline or near-term milestone from the source set, or to the most urgent available business milestone if no deadline is stated.
- If no deliverable artifact other than the memo is required, produce the memo directly; do not add an extraneous cover page or standalone summary file.