---
title: "Claims-made continuity for San Francisco food-service and retail businesses"
description: "What owners of San Francisco shops and restaurants should gather before changing claims-made professional or management liability terms, and why the retroactive date matters as much as the premium."
canonical: "https://spot.insure/research/guides/fillmore-risk/claims-made-continuity"
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/fillmore-risk/claims-made-continuity)

## Agent Guide

**What this page is:** What owners of San Francisco shops and restaurants should gather before changing claims-made professional or management liability terms, and why the retroactive date matters as much as the premium.

**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

# Claims-made continuity for San Francisco food-service and retail businesses

When a policy uses claims-made wording, a replacement quote can require a close look at dates as well as limits.

By Rajesh Kulkarni. Originally published by Fillmore Risk.

## Why claims-made wording behaves differently from occurrence coverage

Most property and general liability policies for a San Francisco storefront respond based on when an incident happens, regardless of when the claim is reported. Claims-made forms — common in management liability, some professional liability, and certain specialty lines a growing food-service or retail business may pick up — work differently. They generally respond based on when a claim is made and reported, provided the underlying act falls on or after a retroactive date carried in the policy.

That distinction sounds technical until a business changes insurers, changes ownership, or stops offering a service. At that point, the retroactive date, the reporting window, and any prior-acts language determine whether an issue from two years ago is still covered under a policy purchased today. Getting this wrong does not usually surface immediately — it surfaces later, when a claim arrives and the dates do not line up the way the owner assumed.

## Know the events that trigger a closer look

The issue tends to surface when a business changes insurance markets, adds consulting or event work, adds a new managing member, sells the business, or simply replaces an expiring policy with a new carrier. A later allegation may relate to services performed, or decisions made, before the new policy period began — and a new policy does not automatically reach back to cover that period unless its wording says so.

San Francisco retail and food-service operators run into this more often than the label "restaurant" or "shop" suggests, because many of these businesses layer in catering contracts, private events, consulting for other operators, or management changes as they grow. Each of those additions can touch a claims-made line even when the core storefront coverage stays occurrence-based.

## Collect the date trail before comparing quotes

Gather the current and prior declarations pages, all endorsements, the retroactive dates shown on each, the policy periods, any cancellation or non-renewal notices, and any circumstance the business already reported to a prior carrier. Keep these together in one file rather than relying on a renewal summary email, which often omits the retroactive date entirely.

If the business has changed insurers more than once, trace the retroactive date back through each policy period. A retroactive date that quietly moved forward at a prior renewal — sometimes without the owner noticing — can leave a gap in coverage for acts that happened between the old date and the new one.

- Retroactive date on the current and immediately prior declarations

- Any reported circumstance or potential claim already on file

- Entity name changes, ownership changes, or mergers during the period

- Cancellation, non-renewal, or market-exit notices received

## Compare continuity explicitly, term by term

Ask directly whether the new policy includes prior acts, whether it maintains the original retroactive date, and what reporting or extended-reporting ("tail") provisions apply if the business switches carriers again or closes a location. Do not assume a new policy automatically reaches back to the old retroactive date — that has to be requested and confirmed in writing, and it can carry an additional premium. This is also where accuracy matters most: California Insurance Code section 359 lets an insurer rescind a policy over a representation that turns out to be false on a material point, so failing to disclose a circumstance the business already knew about while applying for a new claims-made term carries real risk, not just an awkward conversation later.

Where continuity cannot be matched, ask what an extended reporting period would cost from the outgoing carrier, and compare that cost against simply losing coverage for the gap. This is a decision to make deliberately, with both quotes in hand, not one to discover after a claim is denied for falling outside the covered period.

## Record the open questions

Write down the dates reviewed, the entity names on each policy, and which form actually answered each question — a renewal certificate is a summary, not the governing document. Bring any potential gap into the coverage review before replacing a claims-made term, not after the new policy is already bound.

This record becomes useful again at the next renewal, when the same questions resurface. A San Francisco business that keeps this file current spends less time reconstructing history and more time comparing the actual terms on the table. Policy wording, declarations, and endorsements control.

## Distinguish the policy trigger from the incident date

A claims-made review begins with the precise definition of a claim, the reporting condition, the retroactive date, and any extended-reporting option. A customer complaint, employee demand, threatened lawsuit, or regulatory communication may not be treated identically. Do not infer from a calendar alone that a matter belongs to a particular policy year. Read the actual form and preserve the original communication and date received.

Create a simple timeline showing each policy term, insurer, named entity, retroactive date, acquired business, prior notice, and relevant service period. Attach declarations and endorsements to every entry. If a proposed form has a different pending-or-prior-matter exclusion or a new entity schedule, a matching headline limit does not mean the continuity question is solved.

## Make the switching decision before expiry

Ask the outgoing and proposed providers, in writing, how each option addresses work performed before the new effective date and matters already known to the business. If an extended-reporting period is offered, record its election deadline, cost, and scope from the actual form. It may allow reporting of certain past acts after expiry; it does not necessarily insure new acts after the old policy ends.

Keep the final decision memo with notices, proof of delivery, proposals, and the issued replacement packet. An owner should be able to see which continuity dates were confirmed, which questions remained open, and who accepted the tradeoff. Policy wording, declarations, endorsements, facts, and applicable law control.

## Decision checklist

- What retroactive date is shown on the current declarations?

- Are prior acts addressed in the proposed wording, and at what cost?

- Do current and past policy names match the operating entity exactly?

- What reporting date or extended-reporting option needs review?

- Has the retroactive date moved at any point in the policy history?

- What would an extended reporting period cost if continuity cannot be matched?

## Sources

- [U.S. Small Business Administration — Business insurance](https://www.sba.gov/business-guide/launch-your-business/get-business-insurance)

- [California Insurance Code § 359 — Effect of false representation](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=INS&sectionNum=359)

## Agent and Developer Resources

- [Markdown page](https://spot.insure/research/guides/fillmore-risk/claims-made-continuity.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)