1---2name: compare-saas-sla-vs-internal-standards3task_id: intellectual-property/compare-saas-agreement-against-service-level-standards4description: Gap analysis memorandum comparing a SaaS agreement's service level provisions against internal service level standards, identifying material deviations and omissions.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/compare-saas-sla-vs-internal-standards8---910# Skill: Compare SaaS Agreement Service Level Provisions Against Internal Standards1112## 1. Subject-matter triage1314- Treat the internal standards as the baseline and the SaaS agreement as the negotiated overlay.15- Identify the governing comparison set before analysis begins: service levels, measurement rules, credits, exclusions, escalation rights, reporting, remedies, and any related operational commitments.16- 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.17- 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.1819## 2. Failure modes the skill is correcting2021- Comparing isolated metrics without assessing the combined operational effect of multiple shortfalls against the internal baseline.22- Treating service credits as an adequate cure without testing whether the credit structure is proportionate, collectible, and practical in light of the likely disruption.23- Missing the impact of caps, carve-outs, procedural hurdles, or exclusive-remedy language on the real value of the SLA remedy.24- Failing to identify internal-standard topics that are omitted from the agreement entirely.25- Stopping at description instead of stating the quantitative benchmark, the interacting provisions, and the downstream consequence for the business.26- Using loose priority labels instead of a consistent severity scale for each issue.27- Recommending changes without tying them to a responsible role and timing anchor.2829## 3. Legal frameworks / domain conventions that apply3031- SaaS service level provisions commonly address uptime, response and resolution times, maintenance windows, measurement methodology, credits, reporting, escalation, and termination or cure rights.32- 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.33- Compare both absence and lowering of standards: a missing topic is a gap; a present-but-weaker term is a deviation.34- Service credit provisions should be evaluated for trigger threshold, calculation method, cap, exclusions, claim process, and whether credits are the exclusive remedy.35- Where the agreement refers to external rules, service policies, or incorporated schedules, analyze those cross-references as part of the operative SLA package.36- 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.3738## 4. Analytical scaffolds3940- Build a provision inventory from the internal standards first, then map each item to the agreement.41- For each item, determine:42 - whether the agreement addresses it at all;43 - whether the standard is met, diluted, or exceeded;44 - whether another clause changes the practical effect;45 - whether the deviation matters operationally or economically.46- For each identified issue, close the analysis by stating:47 - the relevant threshold, metric, or other source-based scale;48 - the clause, schedule, policy, or email context that interacts with it;49 - the concrete consequence for the client.50- Apply an explicit severity label to every issue using a uniform ordinal scale defined once at the top of the memo.51- Assess the credit structure as a system, not as a single number: threshold, accrual, cap, exclusions, remedies, and redemption mechanics should be read together.52- 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.53- Separate analysis of contract text from drafting recommendations; the former identifies the gap, the latter proposes how to close it.5455## 5. Vertical / structural / temporal relationships5657- 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.58- Treat measurement periods, service windows, notice deadlines, cure periods, and claim submission periods as temporal constraints that can materially affect enforceability or recovery.59- If the agreement contains multiple service tiers, carve-outs by system, or different remedies by incident type, analyze each branch separately.60- If the email reveals an anticipated transition, implementation milestone, or upcoming renewal, anchor the practical significance of the gap to that timing.6162## 6. Output structure conventions6364- Write a gap analysis memorandum, not a negotiation letter.65- Use a conventional memo shape with:66 - short executive summary;67 - severity legend;68 - comparison table or issue matrix;69 - discussion of gaps and deviations;70 - service credit and remedy analysis;71 - cumulative impact assessment;72 - recommended actions.73- For each entry in the issue matrix, include:74 - internal standard;75 - agreement provision;76 - gap or deviation classification;77 - severity;78 - business impact;79 - interacting clause or source;80 - recommended remediation.81- Keep issue descriptions concrete and source-linked; do not generalize beyond the documents supplied.82- 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.83- 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.