--- title: "Certificates and additional-insured requests for distributors: what to verify" description: "Separate proof of insurance from policy changes when a customer, landlord, or vendor asks for a certificate or additional-insured status." canonical: "https://spot.insure/research/guides/embarcadero-risk/certificates-additional-insured-distributors" 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/embarcadero-risk/certificates-additional-insured-distributors) ## Agent Guide **What this page is:** Separate proof of insurance from policy changes when a customer, landlord, or vendor asks for a certificate or additional-insured status. **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 for distributors: what to verify A certificate request is often only the visible part of a larger contract requirement. By Divya Rajan. Originally published by Embarcadero Risk. ## Read the request before the deadline Start with the insurance clause, not a certificate template. Identify the requesting entity, its role, required limits, policy types, additional-insured language, waiver or primary wording, notice request, deadline, and the contract activity that produced the request. A same-day request is a reason to identify the contract owner, not to skip the contract review. The request may relate to a warehouse lease, product delivery, installation, or a customer’s vendor policy. Each has a different purpose, and the named entity on a certificate should be checked against the executed agreement. ## Gather the supporting documents Keep the executed agreement, request email, legal names of the parties, current declarations, endorsements, and any prior certificate. A parent company, property manager, customer, and vendor may each have different legal names and different reasons for requesting documentation. Keep the requested wording as received, including attachments or portal instructions. A generic request email can omit the actual insurance exhibit, while the exhibit may contain recurring certificate obligations or a deadline for replacement evidence after renewal. Save the request with the agreement rather than only with the certificate. ## Compare policy and endorsement language Check whether the proposed or issued policy includes the requested status, for what operations, and subject to what limitations. California law states that a certificate of insurance does not amend, extend, or alter the coverage provided by the policy; ask for the actual endorsement when the contract depends on changed terms. Where an endorsement is requested, identify its scope, trigger, and named party. The practical question is not merely whether an endorsement exists, but whether it is connected to the relevant operations and meets the language that the agreement requires. Any mismatch belongs in a documented business or contract discussion. ## Maintain the contract file Save what was requested, what was delivered, the delivery date, and any limitation noted. Reopen the file when the agreement renews, changes scope, or is assigned. Policy wording, declarations, and endorsements control. Maintain a simple certificate register with requester, agreement, entity name, policy period, issued endorsement, delivery date, and renewal reminder. It prevents a certificate prepared for an old contract or expired policy period from quietly becoming the working record for a current account. - Exact entity names and roles - Required policy and limit - Endorsement versus certificate - Deadline and renewal obligations ## Treat certificate work as a contract-control process A certificate request should enter a controlled queue with the agreement, legal entity names, deadline, and business owner. This keeps a facilities or procurement request from being handled as a standalone administrative task when it actually carries a continuing contractual obligation. Before issuing evidence, compare the requester’s role with the proposed recipient name and the policy or endorsement being referenced. If a property manager asks on behalf of an owner, for example, the required party and requested wording may not be the same. Confirm the relationship in the agreement rather than guessing from email signatures. At renewal, send the register to the business owners for confirmation. Close requests that are no longer tied to an active agreement and reopen any ongoing obligation early enough to review actual issued documents before the customer or landlord needs replacement evidence. ## Distinguish the certificate from the requested policy change A certificate normally reports information about a policy at a point in time. California Insurance Code section 384 addresses certificates and states that they do not amend, extend, or alter coverage. An agreement asking for additional-insured status, primary wording, or a waiver may require a separate endorsement or a contract-specific review. Do not mark the obligation complete merely because a portal accepted a certificate PDF. For each request, write the exact legal entity, its relationship to the business, the activity for which status is sought, and the contract clause that asks for it. A warehouse owner, property manager, shipper, retail customer, and delivery partner may each be asking about different operations. Compare the wording sought with the relevant form and endorsement, including any automatic or scheduled trigger, before describing the request as satisfied. ## Build a request matrix for freight and warehouse contracts Use one row per contract obligation: policy line, requested limit, certificate holder, additional-insured language, waiver, primary or noncontributory wording, notice request, effective date, and renewal deadline. Add columns for the document that supports each answer and the person who checked it. This makes it possible to distinguish a straightforward evidence request from a term that needs negotiation or a policy change. Include the operating scope beside the insurance clause. A distributor selling goods, storing customer inventory, arranging a shipment, and installing equipment could have different contract duties with the same customer. If an agreement expands from delivery to installation or from local storage to multiple facilities, revisit the insurance exhibit rather than reusing a certificate produced for the prior work. Do not assume a higher limit on a certificate answers a form-level issue. A schedule, territory restriction, excluded operation, or named-entity mismatch may be more material than the printed limit. Record the exact proposal or endorsement page that supports the conclusion, and keep unresolved questions visible until a written answer is received. ## Control delivery, renewal, and midterm changes Store the executed agreement, request email, final certificate, applicable endorsement, delivery confirmation, and correspondence in one contract folder. Record the policy period and the date a replacement document is due. When the account renews, compare the new issued forms and entity names before sending updated evidence. A certificate based on the old period should not silently become the working record for a current obligation. Give the business owner a clear escalation path for urgent requests. A same-day loading or warehouse access deadline may be commercially important, but it does not change what an issued policy says. If the request cannot be met as written, identify the precise difference and take it back to the contract decision-maker rather than altering a certificate description to imply a term that has not been confirmed. Policy wording, declarations, endorsements, actual contract terms, and facts control. A certificate process is useful because it produces a reliable trail of what was requested and delivered; it is not itself a coverage determination or a promise that every requested term is available. - Executed insurance clause and exact entity names - Policy line, limits, and applicable form - Endorsement or automatic-status trigger - Certificate holder and delivery record - Policy period and replacement deadline - Open differences requiring contract review ## Sources - [California Insurance Code § 384 — Certificates of insurance](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=INS§ionNum=384) - [California Department of Insurance — Commercial Insurance Guide](https://www.insurance.ca.gov/01-consumers/105-type/95-guides/09-comm/commercialguide.cfm) ## Agent and Developer Resources - [Markdown page](https://spot.insure/research/guides/embarcadero-risk/certificates-additional-insured-distributors.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)