Document Automation
Product features
By practice area
By company size
Contract Review
PRODUCT FEATURES
Resources
LearN
Case Studies
Pricing
Gavel Exec reviews and redlines contracts inside Microsoft Word, checked against your own playbook. Start with 25 free queries, no credit card required.
To review a software as a service (SaaS) agreement for the customer, test what the vendor controls after signing: how usage is counted, what uptime it promises, whether online terms can change, when it can cut off access, how its artificial intelligence (AI) features use your data, and how you leave.
Last reviewed November 16, 2026. This playbook is general information for lawyers, not legal advice for a specific matter. Gavel publishes it and makes Gavel Exec.
Every row assumes your company is buying a hosted application on the vendor's paper: an order form, subscription terms and linked policies. For general liability, indemnity and insurance terms, use the master services agreement (MSA) playbook. Personal data terms belong in the data processing agreement (DPA), covered in the DPA playbook. Other contract types are on the contract playbooks hub.
Acting for the provider, flip the table: commercially reasonable uptime efforts, capped credits as the downtime remedy, policy updates on notice, suspension for security threats, and no open-ended free export help.
Open with the preferred position, give the fallback without sign-off, and escalate the rest to the lawyer who owns the contract.
| Issue | Preferred position | Acceptable fallback | Escalate or walk away if | Why it matters |
|---|---|---|---|---|
| Authorized users | Employees, contractors and outsourcers of the customer and its affiliates. Seats reassignable at any time; integrations use no seats. | Reassignment once every 30 days. Affiliates named in the order form. | License limited to the signing entity, or integrations billed as users. | The user definition moves spend more than seat price. |
| Usage metrics and overages | Each metered unit (application programming interface (API) calls, records, storage, AI credits) defined, with a live dashboard. Overage triggers notice and 30 days to buy more at the contracted rate or reduce use. | Annual true-up in arrears at the contracted rate plus up to 10%. | Overage at list price, automatic tier upgrades, or throttling without notice. | Metered plans can double cost without a new signature. |
| Renewal and seat reductions | 12-month renewals. Price notice 60 days before the non-renewal deadline. Seats and modules reducible at renewal. Added seats at the current contracted unit rate. | 30-day non-renewal deadline. Seat reductions up to 20% per renewal. Added seats at list price less the original discount. | Then-current list price, multi-year automatic renewal, or a deadline over 90 days out. | Common Paper reports a 30-day notice window in about 70% of its cloud agreements. |
| Uptime and exclusions | 99.9% per calendar month for core production functions, measured each minute. Maintenance up to 4 hours a month in a fixed window on 5 business days' notice. Hosting and subprocessor outages count. | 99.5% per month. Up to 8 hours of maintenance on 72 hours' notice. | No number, quarterly or annual measurement, or exclusions for any third-party provider. | 99.9% allows about 43 minutes of downtime in a 30-day month; exclusions decide whether that holds. |
| Service credits and sole remedy | Automatic credits of 10%, 25% and 50% of monthly fees below 99.9%, 99.5% and 99.0%. Sole remedy for unavailability only. Termination with refund after misses in 2 of 3 consecutive months. | Credits on request within 30 days. Termination after 3 misses in any 12 months. | Credits are the exclusive remedy for every failure, including data loss. | Common Paper's SLA standard caps credits at 8% per subscription period, so the exit right matters more. |
| Online terms and service changes | Linked policies fixed at the version attached at signing. No material cut to functionality, security or support. Click-through terms do not bind the customer. | Updates on 30 days' notice. Termination with refund of unused fees if a change is materially adverse. | Changes by posting, with continued use as acceptance. | The terms you reviewed may not be the terms in force at the dispute. |
| Suspension | Only for an imminent security threat, limited to affected users or components, or undisputed fees 30 days late after 10 business days' notice. | Whole-account suspension for an active threat, with same-day notice. | Discretionary suspension without notice, or of the whole tenant for one user's conduct. | Suspension is self-help that stops operations the day it is used. |
| Customer data and usage data | Customer owns its data and outputs; the vendor uses data only to provide the service. Usage data is telemetry, excludes content, and is shared only in aggregate. | Aggregated, de-identified data for product improvement and benchmarking, with no re-identification. | Perpetual license to customer data, or usage data defined to include content. | Common Paper's CSA lets the provider freely use usage data, so the definition decides its reach. |
| Export and deletion | Free export of data, metadata, audit logs and configuration at any time in a documented format. 60 days of read-only access after termination. Certified deletion within 30 days after the customer confirms export or the access period ends. | 30 days of access after termination. Export help at hourly rates in the order form. | Proprietary export format, export fees, or deletion on the termination date. | For European Union (EU) customers, the Data Act requires at least 30 days to retrieve data. |
| Security evidence and subprocessors | Current System and Organization Controls (SOC) 2 Type 2 report covering the product. Subprocessors, including hosting and AI model providers, listed with locations. Hosting region fixed. | SOC 2 Type 1 now and Type 2 within 12 months. Subprocessor changes on 30 days' notice. | No third-party report, or region changes without notice. | A Type 2 report tests whether controls operated over a period. |
| AI features | No training or fine-tuning on customer data, prompts or outputs. New AI features off until an administrator enables them. | Training only on aggregated metrics with no customer content. Administrators can disable AI features at any time. | Data use for "service improvement" that does not carve out model training, or AI enabled by update. | Common Paper reports vendor training rights in about 3% of its 2026 cloud agreements. |
| Liability cap base | Fees payable for the current 12-month subscription period, whenever invoiced, with a dollar floor. Credits do not reduce the base. A dollar cap during pilots using real data. | Fees paid and payable in the 12 months before the claim, with a floor. | Fees paid in the prior 1, 3 or 6 months, or fees net of credits. | With monthly billing, a cap on fees paid in the prior 12 months equals one month's fees in month two. |
| Escrow and continuity | Critical systems only: SaaS escrow with code, deployment documentation and current data, released on insolvency or prolonged SLA failure. | Scheduled data export to customer storage and a business continuity plan tested yearly. | Vendor holds the only copy of critical data with no tested plan. | Code alone does not restore a hosted service. |
The contract clause checker tests one vendor clause against a row.
Named-user plans break when affiliates or contractors need access, and metered plans break when overages default to list price.
Preferred: "Authorized Users" means employees, contractors and outsourcing providers of Customer and its Affiliates who access the Service on Customer's behalf. Subscriptions may be reassigned at any time. Access through an integration or service account does not consume a subscription. If usage exceeds a quantity in the Order Form, Provider will notify Customer in writing, and Customer will have 30 days to buy additional quantity at the Order Form unit price or reduce usage.
Fallback: "Customer may reassign a subscription no more than once every 30 days. Excess usage not resolved within 30 days after notice will be invoiced annually in arrears at the Order Form unit price plus 10%."
Vendors say free reassignment lets one seat serve a team; the 30-day limit answers that, and an annual true-up pays them for real growth.
Common Paper's 2026 contract benchmark, based on agreements signed on its platform, reports a 30-day non-renewal window in about 70% of its cloud service agreements. Ask for a vendor renewal notice stating the new price and a right to reduce seats at each renewal; the MSA playbook covers the price cap.
California's automatic renewal law defines a consumer as an individual buying "for personal, family, or household purposes" (Cal. Bus. & Prof. Code 17601), so it does not reach a company buying software for its business. Wis. Stat. 134.49 is written for business contracts: it covers contracts "for providing business services" to a customer that conducts business in Wisconsin, "but only if the contract is for the direct benefit of the end user."
If a covered contract renews for more than one month, the seller must disclose the renewal terms on a form the customer signs or conspicuously in a contract the customer initials, or the automatic renewal provision "is not enforceable." If the initial and renewal terms each exceed one year, the seller must also give written notice "at least 15 days but not more than 60 days before the deadline" to decline. "Business services" is undefined, so whether a SaaS subscription qualifies is open, and usage-based contracts with a predetermined minimum payment of $250,000 or more in a 12-month period are excluded. The MSA playbook covers New York's rule.
Common Paper reports that only 26% of the agreements in its 2026 data included an SLA. Amazon's compute SLA excludes unavailability "caused by factors outside of our reasonable control." Common Paper's SLA standard terms, version 2.0, cap credits at 8% in a subscription period, call the SLA "Customer's exclusive remedy," and allow termination after misses in two of any three consecutive months.
Preferred: "Availability means the percentage of minutes in a calendar month in which the production core functions listed in the Order Form operate, excluding only Scheduled Maintenance of up to four hours per month within [window] on five business days' notice. Outages of Provider's Subprocessors are not excluded. Below 99.9% Availability, Provider will credit [10]% of that month's fees, [25]% below 99.5%, and [50]% below 99.0%, without a request. If Availability falls below 99.9% in any two of three consecutive months, Customer may terminate the affected subscription for a refund of prepaid fees for the remaining term. Apart from that termination right and refund, service credits are Customer's sole monetary remedy for unavailability and do not limit remedies for data loss, security incidents or other breaches."
Fallback: "...Availability of at least 99.5%... Customer must request credits within 30 days after month end... Customer may terminate after three missed months in any rolling twelve months."
Vendors resist automatic credits and the carve-out. Concede the request window and keep the carve-out: a few percent of monthly fees cannot answer lost data.
Vendors post the acceptable use policy, support terms and security description online, reserve the right to update them, and can cut features mid-term.
In Stover v. Experian Holdings, Inc. (9th Cir. 2020), a consumer case, the Ninth Circuit repeated that "[p]arties to a contract have no obligation to check the terms on a periodic basis to learn whether they have been changed by the other side." Write that rule into the contract. Common Paper's Cloud Service Agreement (CSA), version 3.0, offers a benchmark: the provider warrants it "will not materially reduce the general functionality of the Cloud Service during the Subscription Period."
Preferred: "Each policy referenced by web address in this Agreement applies in the version in effect on the Effective Date, attached as Exhibit [x]. Provider may update a policy only in ways that do not reduce Customer's rights or Provider's obligations, and will not materially reduce the functionality, security or support levels of the Service during a Subscription Term. Click-through, browser or in-product terms do not bind Customer or modify this Agreement."
Fallback: "Provider may update a referenced policy on 30 days' written notice. If an update is materially adverse, Customer may terminate the affected subscription within 30 days after the notice for a refund of unused prepaid fees."
Vendors cannot keep a policy version per customer, so the fallback accepts one version and prices the exit at unused fees.
Common Paper's CSA lets the provider "temporarily suspend Customer's access to the Product with or without notice" for undisputed balances more than 30 days late, breach of use restrictions, or harmful misuse. Narrow the grounds, require notice, and confine the suspension to the problem.
Preferred: "Provider may suspend access only (a) as reasonably necessary to prevent an imminent threat to the security of the Service, limited to the affected Authorized Users or components, or (b) for undisputed fees more than 30 days past due, after 10 business days' written notice. Provider will give notice before a suspension under clause (a) or, if impracticable, within 24 hours after it, and will restore access once the cause is resolved. Provider will not delete Customer Data during a suspension, and fees abate for any suspension this section does not permit."
Fallback: "Provider may suspend the entire account to address an active security threat, with notice the same day, and will restore access within one business day after the threat is resolved."
Vendors want discretion for abuse and legal process. Agree to a court-order carve-out and to suspending the one user who breached the acceptable use policy.
Common Paper finds AI language in 53% of its 2026 cloud service agreements. Staff of the Federal Trade Commission (FTC) wrote in February 2024 that it may be unfair or deceptive to start "using that data for AI training" and disclose the change only "through a surreptitious, retroactive amendment" to the terms. That guidance protects consumers, so a business customer needs its own clause.
Preferred: "Provider will not use Customer Data, prompts or outputs to train, fine-tune or otherwise improve any artificial intelligence model, whether operated by Provider or a third party. Any new feature that sends Customer Data to such a model will remain disabled until a Customer administrator enables it. Each third-party model provider is a Subprocessor, and Provider will ensure that it retains Customer Data only as long as needed to return the output. As between the parties, Customer owns outputs generated from Customer Data."
Fallback: "Provider may use aggregated usage metrics containing no Customer Data, prompts or outputs to improve its features. Customer administrators may disable artificial intelligence features at any time without losing other functionality."
Vendors say default-off features hurt adoption and that model providers promise not to train. Ask for the model provider's name and retention term in writing, and hold default-off if the vendor will not flow them down.
Read the usage data definition with the exit terms: Common Paper's CSA lets the provider "freely use Usage Data" to improve and promote its products. For EU customers, the Data Act, Regulation (EU) 2023/2854, applies to providers serving customers in the Union "irrespective of their place of establishment," and Recital 81 names SaaS. Article 25 requires a switching notice period that "shall not exceed two months," a transition of no more than 30 calendar days, data retrieval "of at least 30 calendar days," and erasure; Article 29 bars switching charges "from 12 January 2027." The Regulation has applied since September 12, 2025.
Preferred: "Customer may export all Customer Data, including attachments, metadata, audit logs and configuration, at any time through the Service or Provider's API in [CSV/JSON] with documented schemas, at no additional charge. For 60 days after termination, Provider will keep read-only access available for export, and will delete Customer Data within 30 days after the earlier of Customer's confirmation that its export is complete or the end of that 60-day period, and certify the deletion in writing."
Fallback: "...for 30 days after termination... Provider will provide reasonable export assistance at the hourly rates in the Order Form."
Escrow fits SaaS poorly. Writing in Law360, Mark P. Kesslen of Lowenstein Sandler concluded that "a traditional source code escrow agreement is of little or no use to the customer" in a SaaS outage. For a critical system, ask for SaaS escrow with deployment documentation and current data, released on prolonged SLA failure as well as insolvency.
If you use escrow, grant an express license to the released materials. 11 U.S.C. 365(n) protects a licensee's rights under "any agreement supplementary to such contract" when a bankrupt licensor rejects a license, and an access-only subscription fits that language less clearly.
A SOC 2 report is an auditor's examination of controls relevant to "security, availability, processing integrity, confidentiality, or privacy." A Type 1 report speaks "as of a specified date"; a Type 2 report covers "a specified period." Confirm it covers your product, read the exceptions, and compare out-of-scope providers with the subprocessor list.
| Segment | What changes in the SaaS agreement | Why |
|---|---|---|
| Healthcare provider or health tech | A vendor holding electronic protected health information (ePHI) signs a business associate agreement (BAA) and must flow Security Rule duties down to its hosting provider and other subcontractors by contract. | 45 C.F.R. 164.314(a)(2)(i) requires Security Rule compliance, subcontractor agreement and incident reporting. |
| Financial services (New York regulated) | Add multi-factor authentication, encryption in transit and at rest, cybersecurity event notice, and security representations. | 23 NYCRR 500.11(b) requires third-party service provider policies to address these items where applicable. |
| Customer in the EU | Switching notice of two months or less, transition within 30 calendar days, 30 days to retrieve data, erasure, and no switching charges from January 12, 2027. | Data Act Articles 25 and 29. Article 31 exempts time-limited test versions and lifts the charge ban for mostly custom-built services. |
| System of record vs departmental tool | System of record: 99.9% or better, chronic failure exit, 90 days of post-termination access, escrow considered. Departmental tool: accept the vendor SLA and focus on export, renewal and AI terms. | Leverage and harm scale with how long the business can run without the system. |
| Startup buyer vs enterprise buyer | A startup on click-through terms screens renewal, export, AI training, suspension and term changes, and switches tools if they fail. An enterprise attaches an addendum that overrides online terms. | Click-through forms are fixed at low spend; enterprise volume buys an override. |
Sources: 45 C.F.R. 164.314, 23 NYCRR 500.11 and the Data Act.
Gavel Exec is AI contract review and drafting software that works in Microsoft Word. It generates playbook rules from a checklist, a spreadsheet playbook or signed agreements (.docx, PDF or .csv), so this page's table can serve as your SaaS rule set. See how playbooks work in Gavel Exec.
Open a vendor's subscription agreement or order form in Word, and Gavel Exec applies the rules as priority-ranked tracked changes with the reasoning for each change. In the web app, benchmarking labels each provision on-market, off-market or missing. Pricing is $160 per user per month or $1,740 per user per year, with 25 free queries per user and no credit card required.
What is a SaaS agreement?
A SaaS agreement is the contract under which a customer subscribes to software the vendor hosts and runs, usually an order form, subscription terms and linked policies.
What should a SaaS contract review checklist include?
Check the usage metric and overage pricing, the renewal deadline, the SLA and its exclusions, any right to change online terms, suspension, data and AI use, the SOC 2 report, and export at termination.
Are service credits the only remedy for SaaS downtime?
Only if the contract says so, as Amazon's compute SLA and Common Paper's SLA standard terms do. Limit the exclusive remedy language to unavailability, keep ordinary remedies for data loss and security incidents, and add a termination right for repeated SLA failures.
Can a SaaS vendor change its terms during the subscription?
Only as the contract allows, and some vendor forms allow changes by posting. The Ninth Circuit has said parties need not check posted terms periodically, but a business customer should negotiate fixed policy versions, notice, and a refund-backed exit for materially adverse changes.
Who owns customer data in a SaaS agreement?
The customer should own its data and outputs generated from it, and the vendor should use that data only to provide the service. Check the usage data definition, because Common Paper's standard form lets the provider use it freely.
Do automatic renewal laws apply to business SaaS contracts?
It depends on the state. California's law protects only individuals buying for personal, family or household purposes. Wisconsin's statute, Wis. Stat. 134.49, covers some contracts for business services with customers that conduct business in Wisconsin, and a covered automatic renewal provision is not enforceable if the seller skips the required disclosure or notice.
Related reading: the MSA playbook for general vendor terms, the DPA playbook for personal data terms, and redlining contracts with AI.
AI contract review and redlining in Microsoft Word, checked against your own playbook, with the reasoning behind each change.