Enterprise customers often ask SaaS providers to prove insurance before a contract is signed. This guide explains how to track requested limits, certificates of insurance, additional-insured wording, notice provisions, and coverage clauses so your sales, legal, and risk teams can identify gaps before procurement becomes a delay.
Overview
Insurance requirements in SaaS contracts are not one-size-fits-all. A customer may request general liability, technology errors and omissions (tech E&O), cyber liability, professional liability, or a combination of these coverages. The requested limits and wording may reflect the customer’s industry, the services you provide, the data you process, the size of the relationship, and the customer’s own procurement standards.
For a SaaS company, the most important question is not simply, “Do we have insurance?” It is, “Does our current insurance respond to the risks and contract obligations we are accepting?” A certificate of insurance can demonstrate that a policy is in force, but it does not usually change the policy’s coverage. Contract language, exclusions, sublimits, deductibles, retroactive dates, and claims-made conditions still require review.
Use the requirements below as a contract-review framework rather than a substitute for advice from a qualified insurance professional or lawyer. Policy terms and legal requirements vary by jurisdiction, insurer, service model, and customer agreement.
What to track
1. Requested coverage and limits
Maintain a simple register for every material customer contract. Record the coverage type, requested limit, policy limit available, deductible or retention, policy period, and the person responsible for confirming compliance. A comparison table can make exceptions visible:
| Requirement | What the customer may ask for | What to verify |
|---|---|---|
| General liability | Coverage for specified third-party bodily injury, property damage, or related liability exposures | Limit structure, territory, exclusions, and whether the customer’s requested status can be issued |
| Technology E&O | Protection for alleged financial loss arising from errors, omissions, or failure in technology services | Service description, professional-services exclusions, retroactive date, and claims-made requirements |
| Cyber liability | Coverage associated with data incidents, network security events, privacy liability, or incident response | Covered data and systems, sublimits, waiting periods, ransomware conditions, and security-control requirements |
| Professional indemnity | A term used in some markets for professional liability, often including advice or service-related allegations | Whether the wording matches the SaaS services actually delivered and the governing jurisdiction |
| Contractual liability | Responsibility assumed under an agreement beyond ordinary legal liability | Whether the policy covers the specific assumption, indemnity, or hold-harmless language in the contract |
Do not assume that a high overall limit solves every requirement. A policy may contain separate sublimits, retentions, exclusions, or conditions that affect a particular loss. Compare the contract requirement with the declarations page and relevant endorsements, not only with a summary or certificate.
2. Certificate of insurance details
Track the customer’s certificate instructions, including the certificate holder’s legal name and address, required lines of insurance, expiration dates, and any requested description of operations. Confirm whether the customer wants evidence for a specific project, contract, subsidiary, or global entity.
A certificate should be accurate and consistent with the underlying policy. Avoid asking a certificate to state coverage that the policy does not provide. If the customer needs an endorsement, such as additional-insured status or a waiver of subrogation, identify that request separately and allow time for the broker or insurer to review it.
3. Additional-insured wording and other endorsements
Some customers request to be named as an additional insured on specified policies. Track the exact entity name, the applicable coverage, the required form or endorsement, and whether the request applies to ongoing operations, completed operations, or both. The scope of additional-insured status is controlled by the endorsement and policy terms; it is not created by a certificate alone.
Also record requests for primary and noncontributory wording, waiver of subrogation, or a separation-of-insureds provision. These provisions can have different effects and may not be available for every policy or relationship. Escalate nonstandard requests rather than accepting them as routine administrative language.
4. Notice, cancellation, and claims-made provisions
Customers sometimes request advance notice of cancellation, nonrenewal, material change, or reduction in coverage. Note whether the requested notice must come from the insurer, broker, or SaaS provider. A contract promise to provide notice may be broader than the notice the policy or insurer is able to provide, so this point deserves confirmation before signature.
For claims-made tech E&O or cyber policies, track the retroactive date, continuity date, extended reporting options, and how the contract treats claims first made after termination. Avoid agreeing to a policy period or reporting obligation that your insurance program cannot maintain.
5. Indemnity and coverage clauses
Compare the insurance section with the indemnity section. An indemnity may cover third-party claims related to intellectual property, confidentiality, privacy, security incidents, or service failures. Insurance may respond to some of these allegations, but not necessarily all of them, and coverage can depend on the precise facts and policy wording.
Flag unlimited indemnities, guarantees of legal compliance, obligations to cover a customer’s own negligence, and promises to pay losses that are not covered by insurance. The goal is not to reject every customer clause; it is to distinguish an insurable obligation from a contractual obligation that could remain with the company.
For a broader view of how coverage should align with systems and operations, see the insurance policy mapping guide for cloud businesses. For the distinction between general liability and professional liability, review general liability vs. professional liability for tech companies.
Cadence and checkpoints
Make contract insurance tracking a recurring operating process, not a one-time sales task. A practical cadence is:
- At opportunity qualification: Ask whether the prospect has minimum insurance requirements and request its standard security or vendor questionnaire early.
- Before legal review: Compare the proposed contract with current limits, policy terms, entities, territories, and service descriptions.
- Before signature: Confirm certificate wording, endorsements, indemnities, notice obligations, and any exceptions approved by both sides.
- Monthly or quarterly: Review open contracts, certificates approaching expiration, unresolved exceptions, and changes in customer requirements.
- Before renewal: Reconcile the contract register with the renewal submission and ask whether revenue, customer concentration, data types, services, or geographic reach have changed.
- After an operational change: Recheck requirements when launching a new product, adding professional services, using a new cloud architecture, processing sensitive data, or acquiring another business.
Keep the register with policy documents, certificates, endorsements, questionnaires, and approved contract exceptions. A policy management system or controlled shared workspace can help, provided ownership, version control, and access permissions are clear.
How to interpret changes
A new customer requirement is a risk signal, not automatically an instruction to buy the largest available limit. First identify what changed: the requested amount, the coverage type, the named entity, the endorsement, or the contractual promise. Then map that change to the actual exposure.
For example, a higher tech E&O limit may relate to the customer’s dependence on your platform, while a cyber requirement may reflect the data you access or the incident costs the customer expects you to manage. A request for additional-insured status may concern a particular liability exposure rather than every policy in your program.
When the requested terms exceed your program, document three options: negotiate a narrower obligation, obtain an endorsement or higher limit, or accept the gap with an informed internal approval. Do not describe a certificate as proof that every contract obligation is insured. Instead, identify the precise policy provision or insurer confirmation supporting the response.
Use the same discipline when a requirement decreases. Lower requested limits do not necessarily mean the business risk has decreased. Changes in customers, data, integrations, subcontractors, or product functionality may create new exposures that the contract does not mention.
When to revisit
Revisit this checklist at least quarterly and before each significant enterprise contract or renewal. Update it immediately when a customer introduces new procurement language, when your policy renews, or when your business changes in a way that affects technology E&O, professional liability, cyber liability, or contractual liability.
Before the next contract review, take these five actions:
- Export the current declarations pages, endorsements, certificates, and policy schedules.
- List every open customer requirement and mark it as confirmed, pending, negotiated, or outside current coverage.
- Compare indemnity and insurance clauses side by side, highlighting unlimited or unusual obligations.
- Ask your broker or insurance adviser to review any new service, data category, territory, limit, or endorsement request.
- Record the final decision, owner, expiry date, and next review date in your policy management process.
Requirements evolve as customers update procurement standards and SaaS companies expand their products. A maintained contract insurance register gives sales and legal teams a clearer answer, reduces last-minute certificate requests, and helps ensure that professional liability insurance and related coverage remain aligned with the promises the business makes.
For related planning, use the cyber insurance buyer’s checklist for SaaS startups and the small business insurance renewal checklist.