Contracts
Identify the business moment
Requirements can appear late in procurement, in a master services agreement, or when a customer expands the scope. The deadline may be real, but speed should not replace a comparison of the underlying terms.
Start before signature whenever possible. If an insurance exhibit is left to the end of procurement, the team may have little time to distinguish a routine certificate request from a requirement that conflicts with the proposed policy.
Assign one owner to maintain a requirements tracker with the contract clause, legal entity, requested coverage, limit, endorsement, deadline, and status. This prevents a critical request from being lost in a general email thread.
Extract the specific asks
List required limits, policy types, additional-insured status, waiver language, primary wording, notice obligations, and any required endorsements. Keep the actual exhibit rather than relying on an email summary.
Separate mandatory wording from negotiable drafting. A request for a certificate may be administrative, while a request for notice, primary status, waiver, or additional-insured language may require a specific endorsement or a contractual revision.
Check whether the contract calls for ongoing evidence through renewal and whether it imposes a deadline for replacement coverage. Those operational requirements belong in the signing file as well as the insurance file.
Compare endorsement language
A certificate shows evidence of insurance; it does not change a policy. Compare the requested status and wording with available endorsements and the contract’s indemnity obligations. Note requirements that a policy cannot simply be made to promise.
Read the certificate description and the endorsement together. The certificate does not amend coverage, add an insured, waive a right, or create a notice obligation beyond the policy. Ask for the actual endorsement when the contract asks for changed terms.
Compare requested limits and retentions with the agreement’s indemnity, limitation-of-liability, and security commitments. The purpose is to identify mismatches for counsel, the broker, and the business—not to make a coverage determination from a checklist.
Keep a signing file
Save the executed agreement, certificate request, endorsements, and correspondence. Revisit them when the customer renews, the scope changes, or the contract is assigned. Policy wording, declarations, and endorsements control.
When an agreement is amended, assigned, or expanded, reopen the tracker. A changed legal entity, territory, project scope, or customer obligation can make a previously issued certificate stale.
Keep the issued certificate with the request that produced it and record the delivery date. That evidentiary trail is useful if a customer later asks what was furnished.
Separate insurance clauses from service promises
A SaaS agreement may mix insurance requirements with uptime, data security, privacy, indemnity, and limitations of liability. Treat them as related but distinct workstreams. Insurance can be one financial response to specified allegations or events; it does not automatically perform the service, erase a contractual promise, or convert a refund into insured damages. Identify the exact clause, the promise owner, and the policy question for each issue.
For example, an enterprise customer might ask for a cyber limit while also imposing a 24-hour incident notification obligation. The policy may have its own notice trigger and method, and the customer contract may have a different trigger. The security and legal teams need an incident process that can satisfy both applicable obligations; the presence of a cyber policy alone does not do that.
Work through an enterprise procurement example
Imagine a customer requires technology E&O, cyber, general liability, additional-insured status, and a certificate before production access. First, extract the clause into a tracker and verify the legal names of the customer, vendor, parent, and implementation entity. Second, compare requested policy types and limits with the proposed declarations. Third, examine each requested endorsement or special condition in the actual form. Fourth, record what is unavailable, pending, or requires a contract change. Do not tell procurement that a requirement is met because a proposal lists a similar headline.
The services schedule deserves equal attention. If the company will run data migration, custom integration, or managed support, check whether those services appear accurately in the application and technology E&O definitions. If the customer’s insurance exhibit is broader than the deliverables, clarify whether the clause can be tailored to the work actually performed.
Timing and negotiation options
Bring the insurance exhibit into review before signature and before a launch deadline. Some requests can be supported by existing declarations, some may require an endorsement and underwriting approval, and others may need the business to negotiate a contract exception. The review should identify who can make the decision, the time required, and what evidence the customer will accept. Avoid promising a document before the insurer has issued it.
When the contract calls for recurring certificates or notice of policy changes, put the obligation on a calendar with an accountable owner. A policy renewal, acquisition, assigned agreement, or material change in scope can make an older response stale. Preserve the executed clause, exceptions, delivered documents, and dated correspondence so the next review begins with a reliable record.
Contract-review checklist
The final check should answer six questions: Which entity is obligated? What services and data are in scope? Which policies and limits are required? Which endorsements or notice terms are requested? What is the deadline and delivery method? Who owns unresolved differences? If the team cannot answer one of these, leave it visibly open. This checklist organizes review; it does not interpret an issued policy or replace legal advice.
California Insurance Code section 384 makes the certificate distinction especially important: a certificate does not amend the insurance contract. The issued policy, declarations, endorsements, actual facts, and applicable law control.