---
name: saas-agreement-checklist
description: "Gives a customer-side checklist for reviewing a SaaS agreement, focused on SLA targets and data governance for your regions and data sensitivity. Use when a buyer is reviewing a SaaS contract and needs a checklist of SLA and data governance terms to check. Do not use for negotiating the agreement or drafting a provider's terms. Related topics: legal, compliance, saas."
---

# SaaS Agreement Checklist

Gives a customer-side checklist for reviewing a SaaS agreement, focused on SLA targets and data governance for your regions and data sensitivity.

## When to use

Use this skill when a buyer is reviewing a SaaS contract and needs a checklist of SLA and data governance terms to check. Do not use it for negotiating the agreement or drafting a provider's terms.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Set the review depth from the data sensitivity and the two regions involved.
3. List SLA items with what good looks like, the red flag and the clause to find.
4. List data governance items covering ownership, subprocessors, breach notice, location, retention and exit.
5. If clause text is supplied, mark each item as found, weak or missing.
6. Close with the items to raise with counsel first.

## Inputs

- **Customer location** (free text, e.g. "EU")
- **Provider location** (free text, e.g. "US")
- **Data sensitivity** (choose one: High, Medium, Low)
- **Agreement text or key clauses** (longer free text)

## Output

Two checklists, SLA and data governance, with good, red flag and clause location per item, then a short priority list.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### SaaS Agreement Checklist

Build a customer-side review checklist for a SaaS agreement.

- Customer location: {{Customer location}}
- Provider location: {{Provider location}}
- Data sensitivity: {{Data sensitivity}}
- Agreement text or key clauses: {{Agreement text or key clauses}}

Cover two areas. First, SLA: uptime target and how it is measured, exclusions, service credits and the claim process, support response times, and termination rights for repeated failure. Second, data governance: data ownership, processing purposes, subprocessors, security measures and certifications, breach notification time, data location and transfer mechanisms between the customer and provider regions, retention, deletion and return on exit.

For each item give what good looks like, the red flag, and the line to look for in the agreement. Raise the bar as sensitivity goes up. If text was supplied, mark each item found, weak or missing. State that this is a checklist for discussion with counsel, not legal advice.

## Pitfalls

- Accepting a headline uptime figure without checking how it is measured and what is excluded.
- Missing cross-border transfer rules when customer and provider are in different regions.
- Treating the checklist as legal advice instead of input for counsel.
