How to build a clause extraction table for SaaS Subscription Agreements

Build a customer-side SaaS clause extraction table by assembling the operative contract package, assigning stable source references, and recording material provisions against consistent topics. Keep source wording separate from interpretation, and capture the responsible party, trigger, exceptions, remedy, and unresolved dependencies. Reconcile orders, product terms, and amendments before treating an extraction as definitive. The resulting deliverable is a source-linked table that lets legal, procurement, finance, privacy, and technical teams answer contract questions without repeatedly rereading the package.

When to use this workflow

Use this workflow when reviewing a proposed subscription, preparing for renewal, comparing suppliers, or answering diligence questions about existing commitments. It is particularly useful when pricing sits in an order while operational obligations appear in an SLA, DPA, security schedule, or incorporated policy.

The task is extraction and verification, not a complete negotiation or implementation process. The table should distinguish contractual evidence, interpretation, and recommended action.

This guide assumes U.S.-oriented commercial review. Governing law, processing roles, service characteristics, and customer location affect the analysis. Assess California privacy requirements and EU switching rules only where relevant. The legal-source discussion uses an October 13, 2026 cutoff; the practical workflow checks are recommendations, not independent legal requirements.

What you need

Collect these inputs before substantive extraction:

• Contract package: master subscription agreement, orders, amendments, DPA, security schedule, SLA, acceptable-use policy, and incorporated product or online terms.
• Version evidence: execution status, effective dates, amendment history, and dated copies of linked terms. Distinguish current website text from the version relevant to the transaction.
• Subscription facts: service tier, licensed entities, users, usage units, committed volumes, currency, billing period, term dates, and deployment locations.
• Customer context: critical workflows, data categories, integrations, export needs, and business owners.
• Review instructions: the customer’s own checklist of required topics, preferred positions, fallbacks, and escalation authority—not an assumed software feature.

Assign document IDs such as MSA-01 and ORD-01. List unavailable schedules separately rather than assuming the master supplies their terms. Identify whether the deliverable describes proposed terms or an executed commitment.

Use the template

SaaS Subscription Agreements — Clause extraction table

Copy this table into your working document or spreadsheet. Use one row per distinct rule, splitting a clause when its triggers or consequences differ.

Source / version identifies the document, date or version, and execution status. Locator / excerpt contains the section, page, and short source passage; cite spreadsheet sheet names and cells where relevant. Pagination alone may not distinguish versions.

Rule / definitions contains the normalized interpretation, preserving consequential terms such as whether “Customer Data” includes metadata. Owner / trigger identifies the obligated party and event requiring performance. Exceptions / remedy preserves qualifications and consequences; distinguish “not located” from “none.”

Use Dependencies / status for linked rows, missing evidence, and verification status: verified, provisional, conflict, or not located. Add confidence with a reason, not an unexplained score. Action / reviewer names the follow-up owner. Record commercial approval separately from extraction verification, even if both appear in this cell.

Step by step

1. Define the questions and row topics

Agree on the questions the table must answer. For business-critical SaaS, include licensed use, fees and overages, renewal, suspension, service levels, security, data processing, liability, indemnities, termination, and exit.

Separate provisions supporting different decisions. “Term” should not absorb renewal notice, price changes, and post-termination retrieval. Likewise, uptime targets and credit-claim procedures deserve separate rows.

Assign stable row IDs before substantive review. Add rows as needed rather than forcing every provision into the original list.

Record: topic, row ID, review scope, and the customer decision each material row supports.

2. Establish document identity and precedence

Read incorporation, amendment, and precedence clauses before extracting substantive rules. Determine whether an order overrides the master generally or only for specified conflicts. Check whether an amendment changes one order, one product, or the entire relationship.

For example, § 12.3 of an SEC-filed Salesforce agreement ranks the applicable order above the master and the master above Documentation, while rejecting customer purchase-order terms. This illustrates contractual wording, not a universal SaaS hierarchy or enforceability conclusion.

Preserve both sides of apparent conflicts. Do not silently select the more customer-friendly text.

Record: precedence rule, document versions, conflict references, and the reviewer’s resolution or assigned question. Mark unavailable incorporated terms as missing evidence.

3. Extract source wording before normalizing meaning

Capture a short passage and exact locator, then write a plain-language rule. Read surrounding language, definitions, provisos, and referenced schedules before completing the row. Preserve qualifiers such as reasonable efforts, materiality, knowledge, and exclusions.

Distinguish vendor commitments from customer duties. Service availability and a customer’s obligation to submit a supported credit claim require different entries. An export right does not necessarily establish assistance or continued access.

For missing language, state the search boundary: “No export-assistance commitment located in MSA-01 and DPA-01; product schedule outstanding.” Absence is neither a prohibition nor an affirmative right.

Record: excerpt, interpretation, defined terms, obligated party, and evidence status.

4. Preserve commercial units and timing mechanics

Extract quantities with their measurement basis: per user or pooled, monthly or annual, calendar or rolling period, and committed or actual usage. Preserve currency, rounding, unused-unit expiry, overage rates, and usage-dispute rights where stated.

The utilization notice in the SEC-filed order forms illustrates non-rollover, Central Standard Time measurement, monthly arrears billing, and contractual rather than technical limits. These historical product-specific terms are not current pricing or market evidence.

For notices, capture the event, interval, recipient, delivery method, receipt rule, and time zone where specified. Calculate dates only after verifying the underlying inputs; label calculations as derived, not quoted terms.

Record: units, timing mechanics, calculation assumptions, and missing inputs. Link pricing rows to usage definitions.

5. Connect provisions that change each other’s effect

Link liability caps to fee basis, measurement period, exclusions, and affected claims. Connect indemnities to defense control and settlement restrictions. Link suspension to notice, cure, disputed payments, and restoration. Connect SLA credits to exclusions, claim windows, and exclusive-remedy wording.

For covered California service-provider or contractor relationships, 11 CCR § 7051(a)–(b) specifies contractual use restrictions, processing-purpose specificity, oversight, inability-to-comply notification, remediation rights, and subcontractor arrangements. These provisions do not establish a universal requirement for unrestricted audits or a particular certification.

Extract relevant privacy commitments separately. “DPA attached” does not establish its contents or applicability.

Record: linked row IDs, qualifications, and an assigned applicability question where privacy roles or coverage remain uncertain.

6. Check exit provisions against technical dependencies

Extract data scope, formats, retrieval window, assistance, transition access, deletion timing, and charges. Ask technical owners whether metadata, attachments, and configuration are needed. Record their assessment separately from contractual promises; do not turn extraction into a full migration project.

For covered services, Data Act Articles 25–26 address written switching terms and information about procedures, formats, and limitations. Article 25’s generally maximum 30-calendar-day transition follows the notice period and allows extensions. Assess territorial coverage, service qualification, and Article 31’s special treatment before applying these provisions.

At the October 13, 2026 cutoff, Article 29 permits reduced switching charges within its cost limit; the prohibition begins January 12, 2027. Distinguish switching charges from ordinary service fees and early-termination penalties.

Record: exit commitments, technical dependencies, legal applicability, and an owner for each gap.

7. Verify the table against the complete package

Have a reviewer trace material rows to operative sources. Check numerical transcription, definitions, cross-references, and whether amendments displace extracted rules. Revisit provisional rows when missing documents arrive.

Reconcile competing extractions through the precedence analysis. For supplier comparisons, normalize units without erasing differences in service tier, product scope, or contract date. Check that normalized figures remain traceable to original values.

Record: reviewer, verification status, corrections, and assigned open issues. Preserve a dated table tied to the reviewed package; it does not automatically update when online terms change.

Worked example

Fictional scenario: Alder Quay Analytics is reviewing Northstar Ledger Cloud. All parties, documents, amounts, and clause wording below are fictional.

The proposed package contains draft MSA-01 v2, ORD-01 v3, and SLA-01 v1. The order provides 80,000 processing events monthly for $96,000 annually. MSA § 2 gives conflicting order terms priority. A referenced product schedule is missing, and the commencement date remains unsettled.

Procurement describes the deal as a fixed annual subscription with 30-day nonrenewal notice. Extraction reveals three qualifications:

The table changes the decision. The order’s longer notice interval requires a verified expiry date before deadline calculation. If 100,000 countable events occur in one month, the stated allowance and rate produce $800 in overages. That is conditional arithmetic, not a forecast: counting rules remain missing. The export wording alone cannot establish a workable migration path. These gaps should remain assigned issues, not become assumed protections.

Common mistakes

• Treating the master as the whole agreement. Extract precedence first, then check orders, amendments, and product schedules against material topics.
• Reducing economics to annual price. Retain counting definitions, measurement windows, expiry, and overage mechanics so variable exposure stays visible.
• Recording only vendor duties. Include customer credit claims, account administration, usage compliance, and nonrenewal requirements.
• Writing “silent” without boundaries. Identify searched documents and missing sources; absence in one file does not establish package-wide absence.
• Equating accurate extraction with approval. Keep evidence verification separate from commercial acceptance and legal applicability.

Final quality check

• Every material row identifies a source version and precise locator.
• Excerpts support interpretations, including definitions and qualifications.
• Precedence conflicts have reasoned resolutions or named reviewers.
• Fees retain currency, units, periods, and calculation assumptions.
• Notice and claim rows capture stated delivery and trigger mechanics.
• Privacy and switching-law conclusions include applicability assessments.
• Missing language and missing documents are distinguished; open issues have owners.
• The dated table matches the reviewed package and is checked by the responsible lawyer before reliance.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities support work across SaaS documents. In Word, reviewers can select the customer as represented party and give deal-specific instructions. Findings quote clauses, locate text, rank severity, and identify missing language as not present. Lawyers retain responsibility for precedence, interpretation, and verification. To discuss this workflow for your subscription package, book a demo.

Frequently asked questions

Should each clause have one row?

Not necessarily. Split independently actionable rules, such as renewal, price adjustment, and notice delivery. Link related rows so readers can reconstruct their combined effect without duplicated excerpts.

How should incorporated online terms be recorded?

Record the referenced URL, preserve a dated copy, and identify the incorporated version. If that version cannot be established, mark the extraction provisional rather than substituting current website text without explanation.

Can one table compare several SaaS suppliers?

Yes. Identify suppliers and documents clearly. Normalize currency, usage units, fee bases, and term lengths while preserving original values. Service-tier differences or missing schedules may explain apparent deviations.

Is the extraction table an obligations tracker?

It can supply one, but extraction alone is insufficient. An operational tracker also needs performance steps, trigger evidence, completion records, and maintained dates. Transfer verified rows rather than treating provisional interpretations as settled duties.

Sources

• SEC Exhibit 10.12: Salesforce Master Subscription Agreement and Order Forms — §§ 12.3 and NOTICE—Utilization; contractual examples only.
• California CCPA regulations effective January 1, 2026 — § 7051, covered service-provider and contractor contracts.
• Regulation (EU) 2023/2854 — Articles 25, 26, 29, and 31; conditional switching-law overlay.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.