--- title: "Restaurant certificates and additional-insured requests: what to verify" description: "Understand the difference between proof of insurance and policy changes." canonical: "https://spot.insure/research/guides/hayes-risk/restaurant-certificate-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/hayes-risk/restaurant-certificate-additional-insured) ## Agent Guide **What this page is:** Understand the difference between proof of insurance and policy changes. **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 # Restaurant certificates and additional-insured requests: what to verify Landlords, event venues, and vendors may ask for certificates on short timelines. The useful review begins with the contract requirement and the endorsement—not the certificate template. By Sanya Pillai. Originally published by Hayes Risk. ## Read the request behind the certificate Collect the insurance clause, legal names, party roles, requested policy types and limits, required endorsement wording, and delivery date. Confirm whether the request is from a landlord, property manager, venue, or customer. The entity named by a day-to-day contact may not be the entity required in the agreement. Use a request intake form that asks for the agreement, legal entity names, address, event or lease dates, requested coverage, exact wording, and recipient contact. It reduces the risk that a certificate is issued to a trade name while the contract requires a different legal party. Certificate workflows break down when the request arrives as an email with only a deadline. Require the agreement or insurance clause, legal entity names, property or event address, date range, policy type, required limits, requested status, and recipient details. This helps distinguish a routine evidence request from one that asks for an endorsement, altered notice language, or a policy term the restaurant does not have. Use a final document-control check: Do the legal names match the agreement? Does the policy period cover the request date? Is the recipient correctly identified? Does the certificate describe evidence only, while any requested endorsement is separately reviewed? Retain the outgoing version and the underlying request. ## Gather the current policy record Keep the declarations, applicable endorsements, lease or event contract, and prior certificates together. This shows what has already been issued and whether the request has changed. Do not rely on a prior certificate if the contract, location, or operation has changed. Certificates should be treated as controlled outgoing documents. Log the request date, policy period, person who reviewed the contract, any endorsements provided, delivery method, and expiration follow-up. A certificate copied from a previous file may not fit a new agreement. Treat every certificate request as a versioned record. Keep the requester’s original instructions, the policy period reviewed, the certificate issued, any endorsement supplied, delivery confirmation, and a renewal or expiration reminder. A document that was accurate for a prior event may not be accurate for a new location, counterparty, policy period, or service scope. ## Compare endorsement language A certificate generally provides evidence at a point in time; it does not add an insured or amend terms. Review the requested status and any notice, waiver, or primary wording against the available endorsement. If the policy cannot provide the requested wording, the insurance and contract teams should identify that difference before representing it as completed. Read an endorsement for its scope, trigger, named party, and relationship to the operations. If a request seeks notice, waiver, primary status, or additional insured status, identify the actual form and the wording available before telling a counterparty the request has been met. An additional-insured request should trigger a document comparison, not an assumption. Read the contract requirement, then identify the relevant policy and endorsement, the named entity, the operation or relationship addressed, and any conditions. If the requested status is unavailable or differs from the contract language, that difference belongs in a conversation with the appropriate commercial and insurance contacts before evidence is furnished. ## Preserve delivery evidence File the certificate, endorsements, contract request, and delivery correspondence with an expiration or renewal follow-up date. Revisit them when the agreement renews or a project changes. Policy wording, declarations, endorsements, contract terms, facts, and applicable law control. When a contract renews or is amended, reopen the record instead of sending the prior certificate automatically. Confirm the entities, premises, work, and policy term are still accurate and retain a copy of the updated agreement with the evidence supplied. Use a completion checklist before delivery: correct legal name, correct address and dates, current policy period, appropriate certificate holder, reviewed endorsement, and copy retained. If an agreement changes later, reopen the request rather than modifying the old certificate from memory. Certificates, endorsements, contracts, and facts each have different roles; none should be used as a substitute for the others. ## A document-control process for evidence requests Log every request before action: agreement name, requesting entity, contact, property or event, dates, policy requested, required wording, deadline, and document attached. If the agreement is missing, ask for it rather than inferring requirements from a certificate holder name. Review the request against current declarations and applicable endorsements. Distinguish evidence of an existing policy from a request that would require an endorsement or a change in contract language. Record exactly which document was reviewed and which wording was available. Before delivery, compare the certificate holder, entity names, address, effective dates, and policy term against the source documents. Retain a copy of the completed certificate, associated endorsement, and delivery correspondence in the same file as the original request. At renewal or amendment, reopen the request with fresh documents. A certificate is point-in-time evidence, and a prior certificate should not be treated as proof that the renewed policy or modified agreement has the same terms. ## A late event request example Suppose an event venue emails a certificate template two days before a catered reception. Ask for the signed agreement, the legal name of the venue and organizer, the date, the exact services, alcohol responsibilities, and the clause requiring insurance. Compare the requested additional-insured or waiver wording with the issued endorsement; do not assume the certificate template creates the requested status. California Insurance Code section 384 makes clear that certificate language cannot by itself change the insurance contract. If the policy cannot provide a requested term in time, record the difference for the contract owner and seek a documented decision. Keep the request, response, certificate, endorsement, and delivery proof together so the next event is not handled from memory. ## Sources - [California Insurance Code section 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/hayes-risk/restaurant-certificate-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)