Free companion page
Free to print: The Reading Checklist: Forty Questions for Any SaaS Subscription Agreement, from How to Read a SaaS Subscription Agreement.
This page is free and needs no sign-up. It reproduces material from How to Read a SaaS Subscription Agreement by Julian R. Sterling so you can print it or keep it open while you work.
To print it, use your browser's print button. Figures are as stated in the book; check the official source before relying on any of them.
The last thing to read before signing an order form, or before letting one renew, is not the contract. It is a list of questions about the contract. The forty below follow the order of this book, so each one points back to the chapter that explains it.
They are written for the business buyer: the finance team that will pay the invoices, procurement that will manage the vendor, in-house counsel who will negotiate, and IT who will live with the platform. Fernmoor Logistics, the customer in the case, faced most of them when it signed with Quillbrook Analytics in Year 1 and again when it chose to leave at the end of Year 5. Each question takes one line, followed by one sentence on why it matters. None of them tells a reader what to sign; they tell a reader what to find.
The first six questions establish what the contract is made of, which Chapters 1 and 2 cover. A reader who cannot answer them does not yet know what document is being signed.
Which documents make up the contract, and which one wins if they conflict?
The order of precedence decides whether a negotiated order form can be overridden by online terms or a policy (Chapter 2).
Are the master terms attached as a fixed text, or incorporated by a link the vendor can update?
Terms that change on a web page can shift the bargain after signature without a new negotiation (Chapter 2).
Which policies (acceptable use, security, support, service levels) are incorporated, and can the vendor change them alone?
A policy incorporated by link is part of the contract, and its later changes may be too (Chapter 2).
Is there a data processing addendum, and does it prevail over the master terms on personal data?
For a customer with people in the European Union, the addendum is where most data protection commitments live (Chapters 2 and 7).
Does the order form state the product, the unit of subscription, the quantity, the fees, the term and the renewal mechanism?
These are the commercial terms the finance team will budget against for years (Chapters 1 and 3).
Who inside the organization signs, who owns the budget, and who will manage the vendor day to day?
A SaaS contract is a multi-year financial commitment, and someone must be responsible for each of its dates (Chapter 1).
The next seven questions turn the order form into a forecast. Chapter 3 treats fees, and Chapter 4 the renewal mechanics.
How is a unit defined (named user, active user, transaction, location), and who counts it?
A loose definition makes usage, and therefore cost, hard to predict and easy to dispute (Chapter 3).
At what rate are units above the contracted quantity charged: the contract rate or list price?
In the case, overage at list price cost more per user than the contract rate (Chapter 3).
Can the customer reduce units at renewal, or only add them?
A one-way ratchet turns a temporary peak into a permanent cost (Chapter 3).
Is the price increase at renewal capped, and at what rate?
Over several renewals, the uplift cap is often the largest single negotiated saving (Chapters 3 and 11).
Are fees invoiced in advance, and what are the payment terms?
Advance invoicing affects cash flow and what is at stake if the customer later terminates (Chapter 3).
Does the contract renew automatically, and how many days before the end must notice be given?
A missed notice date commits the customer to another full period of fees (Chapter 4).
Where and in what form must a non-renewal notice be sent?
A notice sent to the wrong address or in the wrong form may not count (Chapter 4).
Five questions on how the contract can end before its time, the ground of Chapter 4.
What is the initial subscription term, and what is each renewal period?
The term fixes the total commitment the customer cannot leave without a right to do so (Chapter 4).
Can either party terminate for cause, after what notice and what cure period?
The cure period decides how long the customer must live with a breach before it can act (Chapter 4).
Does the customer have a right to terminate for convenience, from when, and at what fee?
A paid exit right puts a known price on leaving early, as it did in the case (Chapter 4).
Can the customer terminate if the vendor becomes insolvent?
That right lets the customer start its exit before its data and access are tied up in a proceeding (Chapters 4 and 10).
On termination for the vendor's breach, does the customer get a refund of prepaid fees?
Without it, the customer may pay for a service it can no longer use (Chapter 4).
Seven questions on what the vendor promises about availability and help, treated in Chapters 5 and 6.
What is the monthly availability target, and how is downtime measured?
The difference between targets that look close can be several hours of downtime a month (Chapter 5).
What is excluded from downtime: scheduled maintenance, emergency maintenance, third-party failures?
Broad exclusions can empty a high target of most of its meaning (Chapter 5).
What credit is paid at each level, and is it paid in cash or only against future invoices?
Credits earned in the last months may be worth nothing to a customer that is leaving (Chapter 5).
Must the customer request credits, within what time, and is there a total cap on credits?
A short claim window and a low cap shrink the credits actually received (Chapter 5).
Are credits the sole remedy, and is there a right to terminate for chronic failure?
In the case, the chronic failure right gave the customer leverage that credits alone could not (Chapter 5).
What does the vendor warrant about the service, and what is the remedy if the warranty fails?
A narrow warranty with a narrow remedy leaves the customer little to stand on when the product disappoints (Chapter 6).
What support hours, response times and channels are promised, and can the vendor remove features?
Support levels and product changes shape what the customer actually receives over the term (Chapter 6).
Six questions on the customer's data, the ground of Chapter 7.
Does the customer keep all rights in its content and in the output the service produces from it?
Ownership is the base on which every later data clause, including exit, depends (Chapter 7).
For what purposes may the vendor use customer data, including de-identified or aggregated data?
A broad license to improve products can reach further than the customer expects (Chapter 7).
What security commitment does the vendor make: efforts, a named policy, or annual reports and certifications?
The rung on that ladder decides how easy a security breach is to establish (Chapter 7).
How are subprocessors listed, how are changes notified, and can the customer object?
In the case, the incident happened at a subprocessor the customer had never contracted with (Chapter 7).
Within how many hours must the vendor notify a security incident, and does the clock start when a subprocessor becomes aware?
In the case, notice came 5 days after the vendor learned of the incident (Chapter 7).
What insurance must the vendor carry, for how long after the term, and will it provide a certificate?
Insurance gives the vendor a source of funds to meet its promises after a loss (Chapter 7).
Five questions on who pays when things go wrong, covered in Chapters 8 and 9.
Does the vendor indemnify against third-party intellectual property claims, and is that indemnity capped?
In the case, the vendor's infringement indemnity sat outside every cap (Chapter 8).
What exclusions apply to the vendor's indemnity, especially for combination with other systems?
The combination exclusion can remove protection exactly where a connected platform is most exposed (Chapter 8).
What is the general cap, how is it measured, and does the look-back include fees payable as well as paid?
The cap in money changes over the term, and early or late claims may meet a thin ceiling (Chapter 9).
Is there a supercap for data and security breaches, at what level, and what triggers it?
In the case, the supercap decided whether a data incident was fully recovered or not at all (Chapter 9).
Does the waiver of indirect damages exclude data breach costs, or are those costs named as direct damages?
A waiver that sweeps in breach costs can reduce a high supercap to nothing (Chapter 9).
Four final questions on how the customer leaves, the subject of Chapter 10.
How long is the retrieval window after termination, and is the service accessible during it?
A short window turns a planned migration into a rush (Chapter 10).
In what format is the data exported, and is there a fee?
A documented machine-readable format at no charge is what makes a move to another platform practical (Chapter 10).
Is transition help an obligation, at a fixed rate, with staff who know the account, whatever the reason for exit?
In the case, transition help was the whole exit cost under the signed contract and most of it under the vendor's draft (Chapter 10).
When is the data deleted, is deletion certified, and does the customer need escrow or rather regular exports?
For a hosted service, a recent copy of the data held by the customer often protects more than source code it could not run (Chapter 10).
A reader rarely gets a clean answer to all forty. Some answers sit in the order form, some in the master terms, some in a policy behind a link, and some are simply missing. The missing ones are the most useful: they mark the points where the contract is silent and common practice, or the vendor's later choices, will fill the gap.
The case shows that the forty do not carry equal weight. For Fernmoor, the questions on renewal uplift, the supercap and the waiver of indirect damages, and the exit format and fee decided the largest sums; the questions on credits decided small ones. A finance team usually ranks the answers by the money at stake before taking them into a negotiation.
Key Takeaway: Forty questions, in the order of the contract stack, fees, termination, service levels, data, liability and exit, turn a SaaS agreement into a list of answers and silences a buyer can act on. In the case, the answers that mattered most were the renewal uplift cap, the supercap with its treatment of breach costs, and a free, documented export. Ask them before signing and again before every renewal.