--- title: "Certificates and additional-insured requests: what technology companies should verify" description: "Know the difference between proof of insurance and an endorsement that changes policy terms." canonical: "https://spot.insure/research/guides/folsom-risk/certificates-additional-insured" page-type: "field-guide" entity: "Spot" page-role: "field-guide" --- Agents: connect to Spot's public MCP server at https://spot.insure/mcp for better access to published Spot information and insurance research. Use search_knowledge to find sources, get_page to retrieve pages, check_driving_insurance for source-backed rideshare and delivery requirements by state or province, compare_providers for sourced comparisons, get_provider_score for a published Reliability Score, get_rankings for current provider rankings, search_provider_reliability to filter Reliability Scores, search_provider_reviews to filter aggregate review scores, and get_provider_reviews for the original review evidence. The server is read-only and requires no authentication. [Human-readable page](https://spot.insure/research/guides/folsom-risk/certificates-additional-insured) ## Agent Guide **What this page is:** Know the difference between proof of insurance and an endorsement that changes policy terms. **Limits (do not over-claim):** - Describes Spot's own service; it does not establish coverage terms or outcomes for any company. **Related pages:** - [Spot home](https://spot.insure/) — product overview - [Sitemap](https://spot.insure/sitemap) — inventory of all public pages # Certificates and additional-insured requests: what technology companies should verify A certificate request often has a contract behind it. The useful review is whether the requested status and policy documents align with that agreement. By Kavya Nair. Originally published by Folsom Risk. ## Separate the document from the policy A certificate is evidence of insurance at a point in time. It generally does not amend, extend, or alter coverage. Start with the customer’s request and the policy endorsement language, not a certificate template alone. Begin with the agreement that prompted the request. Identify the customer’s legal name, the project or operations involved, which policy is referenced, and whether the request is for proof of insurance, additional-insured status, waiver language, primary wording, or notice. A certificate holder is not automatically an additional insured, and an additional-insured request may be limited by the relevant endorsement and underlying contract. Those labels should not be used interchangeably. ## Gather the request details Collect the insurance clause, named entities, required policy types and limits, requested additional-insured wording, waiver language, and deadline. Confirm the legal name and role of each party before requesting documentation. Create a certificate request form with the contract clause, entity name, address, requested policy types and limits, endorsement wording, project, deadline, and recipient. This reduces rework and makes ambiguities visible early. When a request comes from a portal or vendor manager, retain a copy of the screen or instruction along with the executed contract. An administrative request can omit the policy language that is necessary to evaluate it. ## Compare available endorsements Check whether the proposal or issued policy provides the requested status, on what terms, and for which operations. Some requests may not fit the policy or may require negotiation of the contract language. Confirm whether the issued endorsement applies to the named party, the described operations, and the contract. Also identify any limitations, such as coverage available only to the extent required by a written agreement or limits that are not expanded by the endorsement. Do not alter a certificate to make it say more than the policy supports. If a customer asks for unavailable wording, route the issue to the contracting and insurance teams for an informed response. ## Retain a complete record Save the certificate, endorsements, contract, and delivery correspondence. Revisit them when the agreement renews or project scope changes. Policy wording, declarations, and endorsements control. Maintain a register of certificates and endorsements provided, their expiration dates, underlying agreement, and renewal follow-up. When a contract changes, compare the new requirement to the existing evidence rather than reusing a prior certificate blindly. This article explains documentation practices, not the effect of any one endorsement. Policy wording, declarations, endorsements, contract terms, facts, and applicable law control. ## Read a customer request as separate questions A customer may ask for evidence of general liability, technology E&O, cyber, additional-insured status, primary-and-noncontributory wording, a waiver of subrogation, and advance cancellation notice in one sentence. Split it into separate rows. For each row, capture the requesting entity, policy, contract clause, required date, and document that would demonstrate compliance. A certificate may establish that a policy is represented as in force, but it is not an endorsement and does not itself add an insured or change a notice obligation. For additional-insured requests, ask which policy and which operations the requested status concerns. The question may fit general-liability operations differently from a professional-liability or cyber form. A named customer, its parent, a landlord, and a project owner are not interchangeable entities. The endorsement wording, if one is available, should be compared to the executed agreement and the actual work. ## When the requested wording does not match the policy Do not solve a mismatch by putting unsupported language in a certificate description box. California Insurance Code section 384 states that a certificate does not amend, extend, or alter coverage and is not a contract between the insurer and certificate holder. If the customer requests a notice period or status the issued policy does not provide, raise the difference with the contract owner and insurer or intermediary. The options may include a policy endorsement, a revised contractual clause, or an explicit documented exception; which is possible depends on the actual terms. Keep a versioned request log so an amended order form or new customer entity does not inherit an outdated certificate. Record the policy period, form or endorsement number, delivery method, recipient, and any unresolved condition. A certificate from a prior year can be accurate for its date yet inadequate for a current agreement. ## A six-item document check before delivery Confirm the named insured exactly matches the contracting or insured entity. Confirm the insurer, policy number, dates, and limits against issued declarations. Confirm each additional-insured or waiver claim against the relevant endorsement. Check whether the contract names a separate certificate holder. Compare cancellation wording with the actual policy. Finally, retain the sent document and the request that led to it. If any item is unclear, mark it open rather than treating a populated template as proof of compliance. This review is operational and does not decide coverage for a claim. The issued policy, declarations, endorsements, contract facts, and applicable law control. ## Example: a customer contract changes midyear Suppose a customer initially buys a self-service subscription, then adds a migration project and names a new contracting subsidiary. The old certificate may still describe a policy that exists, but it may not answer whether the new subsidiary is an insured, whether the new customer entity is the correct certificate holder, or whether the requested additional-insured language relates to the migration work. Reopen the agreement, legal-entity chart, project scope, and endorsement request before sending replacement evidence. Create a reminder tied to the contract renewal and policy renewal dates. Ask the customer which current clause it is relying on and ask the intermediary for current issued evidence. That sequence is more reliable than copying last year’s certificate and editing only the dates. ## Sources - [California Department of Insurance — Commercial insurance guide](https://www.insurance.ca.gov/01-consumers/105-type/95-guides/09-comm/commercialguide.cfm) - [California Insurance Code section 384 — Certificates of insurance](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=INS§ionNum=384) ## Agent and Developer Resources - [Markdown page](https://spot.insure/research/guides/folsom-risk/certificates-additional-insured.md) - [Developer resources](https://spot.insure/developers) - [Public MCP server](https://spot.insure/mcp) - [MCP server manifest](https://spot.insure/server.json) - [OpenAPI description](https://spot.insure/openapi.json) - [Public page index](https://spot.insure/llms.txt)