Chapter 4: The Long Silence
How American Courts and Regulators Turned “We’ll Get Back to You” into a Legal Obligation
There was a time when an insurance company could accept your claim, promise to look into it, and simply disappear. No call. No letter. No explanation. Just silence – weeks of it, sometimes months – while the policyholder waited, repaired nothing, paid for temporary housing out of pocket, or watched a lawsuit barrel toward a judgment that would exceed their policy limits. The insurer was under no affirmative obligation to pick up the phone.
That era is over, though its end came unevenly, state by state, decade by decade, in a patchwork of court decisions, regulatory adoptions, and statutory mandates that still has not fully settled. The story of how the status update became a regulated document is, at its core, a story about the consequences of silence – and about how long it took the American legal system to decide that silence itself could be actionable.
The Status Update Obligation Takes Shape
The Origin Story: When Silence Became Actionable
The earliest cases in our dataset do not use the phrase “status update.” They do not contemplate a letter mailed every thirty or forty-five days with a form paragraph explaining why the investigation is still pending. What they establish, instead, is something more fundamental: that an insurer who takes control of a claim – particularly a third-party liability claim, where the insurer literally directs the defense – cannot simply go dark on the person whose financial future hangs in the balance.
The 1933 South Carolina decision in Tyger River Pine Co. v. Maryland Casualty Co. is, chronologically, the first case in our dataset tagged to the status update obligation. It established that a liability insurer owes its insured a duty to defend and settle actions in good faith, giving equal consideration to the insured’s interests. The opinion does not prescribe a letter or a timeline. But it plants the seed: if you owe good faith, you owe communication, because good faith without information is a contradiction.
The idea germinated slowly. In 1956, the Oregon Supreme Court decided Radcliffe v. Franklin National Insurance Co., and the seed broke ground. In Radcliffe, the insurer failed to notify its insureds of a settlement offer within the policy limits. The case proceeded to trial, producing a judgment that far exceeded those limits, leaving the insureds personally liable for the excess. The court ruled that the insurer’s failure to communicate the settlement offer constituted bad faith. This was not a status update in the regulatory sense. It was something more visceral: a court telling an insurer that when you hold the keys to someone else’s financial survival, you do not get to keep them in the dark about the offers on the table.
California formalized the principle in 1958 with Comunale v. Traders & General Insurance Co. The case arose from an automobile accident in which Comunale’s insured struck a pedestrian. The injured pedestrian offered to settle within the policy limits — a deal that would have ended the matter. Traders & General refused, betting that a trial would produce a lower verdict. It did not. The jury returned a judgment that far exceeded the policy limits, and the insured — a person who had purchased liability insurance precisely to avoid this kind of financial ruin — was left personally exposed for the excess. The California Supreme Court held that the insurer had breached the implied covenant of good faith and fair dealing, embedding the duty to settle – and by extension, the duty to communicate about settlement – into the insurer-insured relationship. Two decades later, Davis v. Blue Cross of Northern California (1979) took the next step, holding that the implied covenant includes the duty to reasonably inform an insured of their rights and obligations under the policy, particularly when the insured’s ignorance could result in a loss of benefits. The court was explicit: the insurer cannot passively assume the insured knows what they are entitled to.
By 1982, Iowa had produced one of the starkest illustrations of what happens when communication fails. In Kooyman v. Farm Bureau Mutual Insurance Co., the insurer failed to inform the insured that the underlying plaintiff had made a settlement demand. Nor did it explain that the insured could be personally financially ruined by an impending verdict on a policy with significantly lower limits. The Iowa Supreme Court held this silence actionable. As the court later elaborated in Loudon v. State Farm Mutual Auto. Insurance Co. (1984), if a claim has the potential to exceed policy limits, the status update must contain an explicit warning about the expected financial consequences for the insured.
These early cases share a common thread: they arise in the third-party liability context, where the insurer controls the defense and the insured is, functionally, a passenger. The communication duty was born not from a regulatory mandate but from the fiduciary-like relationship created when one party hands another the power to settle – or refuse to settle – claims that could bankrupt them.
From Fiduciary Duty to Regulatory Mandate: The NAIC Model Act
The transition from common-law communication duties to the regulatory status update we recognize today happened through the National Association of Insurance Commissioners. The NAIC Model Unfair Claims Settlement Practices Act, adopted in the late 1970s, did not invent the status update. What it did was codify a baseline expectation that had been percolating through court decisions for decades: that insurers must act with “reasonable promptness” in communicating with claimants and must not fail to affirm or deny coverage within a reasonable time after receiving proof of loss.
The Model Act’s language was deliberately elastic. It spoke of “reasonable” timeframes rather than specific day counts, giving states room to adapt the standard to their own regulatory cultures. And adapt they did – though not uniformly, not quickly, and not always in the same direction.
The states that adopted the Model Act most faithfully kept the “reasonable” standard and left it to courts and regulators to define what reasonable meant in practice. Connecticut, Massachusetts, Idaho, and Mississippi, among others, still operate under this framework today. In these states, the frequency of status updates is not prescribed by a number on a calendar. Instead, it is measured against the totality of the circumstances: the complexity of the claim, the information available, the insured’s vulnerability, and the insurer’s conduct.
The problem with “reasonable,” of course, is that it invites litigation. An insurer who waits sixty days to send an update on a straightforward auto claim may argue that the delay was reasonable given staffing constraints. The policyholder – who has been without a car for two months – may see it differently. Courts in “reasonable” states have spent decades refining the standard, case by case, without ever producing the clean bright line that claims departments crave.
The Spread: How States Picked Their Numbers
The dissatisfaction with “reasonable” drove states toward specificity. Beginning in the 1980s and accelerating through the 1990s and 2000s, state insurance departments began adopting regulations that translated the Model Act’s aspirational language into concrete deadlines.
The most common number is forty-five calendar days. Fifteen states – Alabama, Arizona, Arkansas, Iowa, Kansas, Kentucky, Maryland, Missouri, Ohio, Oregon, Rhode Island, Texas, Utah, Virginia, and Washington – have adopted some version of a 45-day status update cycle for at least their primary personal lines (auto and homeowners). The logic behind 45 days is pragmatic rather than principled: it is long enough to accommodate a genuine investigation cycle while short enough to prevent the kind of open-ended silence that generates complaints and lawsuits.
Eight states opted for a more aggressive thirty calendar days: California, Colorado, Hawaii, Nebraska, Nevada, New Hampshire, New Jersey (for auto physical damage), and Pennsylvania (after an initial 30-day notice, then 45 days thereafter). These states tend to have more activist regulatory environments and, not coincidentally, more robust bad faith jurisprudence. California’s 30-day requirement, codified in 10 CCR Section 2695.7(c)(1), is among the most detailed in the nation, requiring the insurer to specify any additional information needed, state the continuing reasons for the inability to make a determination, and provide an estimate of when a determination can be made.
At the other end of the spectrum, New York stands alone with a 90-calendar-day status update cycle for most claim types – and an extraordinary 180-day cycle for workers’ compensation claims. Tennessee requires updates every 60 calendar days. These longer intervals reflect a different regulatory philosophy: that the state’s role is to prevent abandonment rather than to micromanage the cadence of insurer communication.
Seven states use business days rather than calendar days for at least some lines of business, adding another layer of complexity. Alaska requires updates every 45 business days. Vermont mandates 30 business days. West Virginia prescribes 15 business days after the initial investigation period. Georgia requires updates every 5 business days after the initial acknowledgment period for auto claims – the most aggressive frequency in the nation, and one that effectively mandates near-continuous communication.
And then there are the states with no specific frequency requirement at all. Delaware, Indiana, Louisiana, Maine, Montana, North Carolina (for personal lines), and Wyoming have not adopted a numeric standard for status update frequency. In these states, the obligation exists only to the extent that courts have recognized a common-law duty of good faith communication – which, as the case law demonstrates, is a real but unpredictable obligation.
The Divergence: What Counts as an Update?
The frequency question – how often must you write? – is only half the puzzle. The content question – what must you say? – is where the real divergence lies.
At one extreme, some states require little more than an explanation of why the investigation remains open. Virginia’s regulation (14 VAC 5-400-60) requires a “written notice setting forth the reasons additional time is needed for the investigation.” That is the entirety of the content mandate. Kansas, under K.A.R. 40-1-34, requires the insurer to “set forth the specific reasons additional time is needed for the investigation.” Simple, clean, and relatively easy to comply with using a form letter.
At the other extreme, states like California, Florida, Iowa, and Washington have layered case law requirements on top of their regulatory frameworks, creating content obligations that extend far beyond the statutory text. California requires the insurer to affirmatively disclose available coverages the insured may not have claimed, per the 1991 decision in Ramirez v. USAA Casualty Insurance Co. Florida, following Harvey v. GEICO (2018), requires the insurer to proactively initiate settlement negotiations when liability is clear and to act with what the court called “haste and precision” – as if the insurer were in the insured’s shoes.
Iowa’s content requirements are particularly demanding. Building on Kooyman (1982) and Loudon (1984), the state requires that status updates in claims with excess exposure must contain an explicit warning regarding the expected financial consequences for the insured. The Iowa Supreme Court in Bellville v. Farm Bureau Mutual Insurance Co. (2005) articulated specific factors for evaluating bad faith, explicitly including an insurer’s failure to keep the insured fully informed of all developments that could reasonably affect their interests.
Arkansas illustrates another dimension of the content question: specificity. Under the Arkansas Insurance Department’s bulletin interpreting the state’s unfair claims practices regulation, stating “still investigating” in a status update is not specific enough and is considered equivalent to failing to send the notice at all. The update must explain why the investigation remains open and what the insurer is still examining.
New Hampshire adds a formal dimension: second and subsequent delay letters must include the verbatim Department of Insurance complaint notice in at least 12-point bold type. New Jersey requires the update to include the address of the office handling the claim, the policy number, the claim number, and a telephone number providing direct access to the claims office. These formatting requirements transform the status update from a communication into a regulated document with prescribed elements.
The third-party context introduces yet another layer. In states like Ohio, Oregon, Pennsylvania, and Wisconsin, courts have imposed content requirements for liability claims that go well beyond what the statute prescribes for first-party claims. The insurer must communicate settlement offers, explain excess exposure, and advise the insured of the potential for a judgment beyond policy limits. In Wisconsin, Warren v. American Family Mutual Insurance Co. (1984) upheld a bad faith verdict where the insurer failed to keep its insured informed of developments. In Ohio, Unklesbay v. Fenwick (2006) held that an insurer’s “foot-dragging in the claims-handling process” – including communication delays – itself constitutes bad faith, independent of whether the claim was ultimately paid.
The Workers’ Compensation Exception
Workers’ compensation claims occupy a peculiar space in the status update landscape. In most states, the workers’ compensation act’s exclusive remedy provision bars tort actions against insurers for claims handling failures, which removes the common-law bad faith lever that has driven communication requirements in other lines of business.
The result is a patchwork within the patchwork. Twenty-three states in our dataset have no specific statutory or regulatory status update frequency requirement for workers’ compensation claims. The states that do impose requirements show enormous variation: Missouri requires updates every 30 calendar days, New York every 180 calendar days, South Carolina every 180 calendar days, and Texas every 5 business days.
Georgia’s experience in Bright v. Nimmo (1984) illustrates the tension. The Georgia Supreme Court ruled that the intentional delay of workers’ compensation payments does not give rise to an independent cause of action against the insurer because the Workers’ Compensation Act already contains specific statutory provisions and penalties for delayed payments. In Kentucky, Zurich Insurance Co. v. Mitchell (1986) closed the door entirely on supplemental civil remedies. In Connecticut, DeOliveira v. Liberty Mutual Insurance Co. (2005) similarly prohibited independent civil tort actions for bad faith processing of workers’ compensation claims.
The practical consequence is stark: a claims department handling a homeowners claim in California must send a detailed status update every 30 calendar days with specific content elements prescribed by regulation and case law. That same claims department, handling a workers’ compensation claim in the same state, operates under an entirely different framework – or, in many states, under no status update framework at all.
The Modern Enforcement Landscape
The question of what happens when an insurer fails to send a status update has evolved as dramatically as the update requirement itself. In the early decades, the consequence was indirect: silence was one factor among many that a court might consider in evaluating a bad faith claim. A missed update, standing alone, rarely established liability.
That began to change as courts recognized that communication failures have compound effects. In Illinois, Buais v. Safeway Insurance Co. (1995) demonstrated the point: the insurer completely refused to discuss, evaluate, or investigate a claim for an astonishing period despite there being no legitimate dispute regarding coverage. In Louisiana, Zydeco’s II, LLC v. Certain Underwriters at Lloyd’s, London (2019), a commercial property insurer was found in bad faith specifically for ignoring an insured’s emails requesting a status update over an 89-day period.
The 2021 federal case Lee v. Berkshire Hathaway Guard Insurance Co. in Washington may represent the high-water mark of this trend. The court imposed bad faith liability based almost entirely on the insurer’s failure to provide status updates and communicate proactively during a property insurance claim. The case did not involve a fraudulent denial or a coverage dispute. It involved silence – and the court found that silence, by itself, was enough.
Pennsylvania offers an instructive counterpoint. In Ridolfi v. State Farm Mutual Auto. Insurance Co. (2017), the plaintiff alleged bad faith specifically because the insurer failed to provide the mandated 45-day written status updates. The federal court held that while regulatory violations can be considered when examining a bad faith claim, a violation of the Unfair Insurance Practices Act or the Unfair Claims Settlement Practices regulation is not, on its own, a per se violation of the bad faith statute. The regulatory violation is evidence, not proof. Similarly, Greene v. United Services Automobile Association (2007) determined that an adjuster’s failure to respond to a specific letter or a few phone calls constitutes “inadvertence” rather than the motive of self-interest or ill will required for bad faith.
The distinction matters enormously. In states like Arizona, where Zilisch established that deliberately forcing the insured through “needless adversarial hoops” is bad faith regardless of the outcome, the status update obligation has real teeth. In states like Pennsylvania, where the plaintiff must demonstrate clear and convincing evidence of the insurer’s knowing or reckless disregard, a missed update is a data point, not a verdict.
The Practical Impact: Building the Status Update Workflow
For a claims department operating across multiple states today, the status update obligation creates a compliance challenge that is simultaneously simple in concept and maddeningly complex in execution.
The concept is simple: do not go dark on your policyholders. Tell them what you are doing, what you still need, and when they can expect a decision. The execution is complex because the answer to “how often?” and “what must you say?” varies by state, by line of business, and sometimes by the type of claim within a line of business.
A national carrier must maintain at minimum four distinct status update cadences: 30-day cycles for California, Colorado, Hawaii, and their peers; 45-day cycles for the plurality of states; 60-day cycles for Tennessee; and 90-day cycles for New York. It must track whether each state counts business days or calendar days. It must determine whether a workers’ compensation claim in a given state even requires a status update at all, or whether the exclusive remedy provision has effectively silenced the obligation.
Content requirements add another dimension. A status update letter that satisfies Virginia’s minimal requirements – a written notice setting forth the reasons for the delay – would be woefully insufficient in California, where the letter must specify additional information needed, state continuing reasons for the inability to decide, and provide an estimate of when a determination will be made. In New Hampshire, the letter must include the verbatim Department of Insurance complaint notice in 12-point bold type. In New Jersey, it must include the claims office address and a direct telephone number.
The smartest claims operations have responded by building to the most demanding standard and then tailoring downward. A status update letter that satisfies California’s content requirements will, with minor modifications, satisfy the requirements of every other state. The challenge is not writing the letter – it is knowing when to send it, tracking the cadence state by state, and ensuring that the content reflects the actual status of the actual investigation rather than the boilerplate that Arkansas has specifically held to be equivalent to no notice at all.
But there is a counterargument that the industry raises with increasing frequency, and it deserves an honest hearing. When a thirty-day status update mandate produces a letter that says, in substance, “we are continuing to investigate your claim and will contact you when we have additional information,” has the regulation produced communication – or has it produced paper? Claims managers point to stacks of nearly identical form letters, generated on schedule, containing no new information, serving no purpose except to satisfy a compliance checkbox. The policyholder who receives the same anodyne paragraph every thirty days is not being kept informed. They are being kept on a mailing list. The mandate was designed to prevent silence, but in practice it has sometimes produced something worse: the appearance of communication without the substance. A thoughtful status update sent when there is actually something to report – a new piece of evidence, a coverage question resolved, a timeline revised – would serve the policyholder far better than a calendared obligation to say nothing on schedule. Arkansas got at this truth when it held that “still investigating” is equivalent to no notice at all. The question the industry presses is whether the regulatory framework, with its fixed day counts and compliance calendars, has made the Arkansas standard the exception or the rule.
The deeper lesson of the case law is not about deadlines or form paragraphs. It is about the relationship between insurer and insured. From Tyger River in 1933 to Lee v. Berkshire Hathaway in 2021, the courts have been saying the same thing in different ways: when a policyholder entrusts a carrier with their claim – their roof, their car, their business, their financial future – the absence of communication carries consequences. The claims operations that handle this well are the ones that treat the status update not as a compliance checkbox but as a genuine touchpoint with the person on the other end of the file.
The Modern Status Update
The status update that satisfies the most demanding jurisdictions is no longer a form letter. It is a substantive communication that tells the policyholder not just that the claim remains open, but why, what happens next, and what they should know. The carrier that builds to California’s standard – the most prescriptive in the nation – will satisfy nearly every other state with minor tailoring.
A compliant multi-state status update should include:
- Specific reasons the investigation remains open – not “still investigating” (which Arkansas has held equivalent to no notice at all), but an explanation of what the insurer is still examining and why a determination cannot yet be made (virtually universal; California, Arkansas, Kansas, New Hampshire, and others require specificity)
- Identification of any additional information still needed from the claimant, with enough detail for the claimant to act on the request (California, North Carolina, Mississippi)
- An estimated date or timeframe for when the insurer expects to reach a determination (California, Georgia, Colorado, Pennsylvania)
- Disclosure of settlement demands and offers, including any demands within policy limits (Alaska, Arizona, Florida, Illinois, Iowa, Minnesota, Missouri, Nevada, Tennessee, Vermont, Washington, Wisconsin – primarily in third-party/liability contexts)
- Warning of excess exposure if damages sought exceed policy limits, including a plain-language explanation of potential financial consequences for the insured (Iowa, Illinois, Florida, Louisiana, Minnesota, Missouri, Nevada, Wisconsin)
- Disclosure of available coverages and benefits the insured may not have claimed (California, Hawaii, Iowa, Wyoming)
- Notification of conflicts of interest and the insured’s right to independent counsel, where applicable (Illinois, Mississippi, New York, South Carolina, Tennessee)
- The address of the claims office handling the file, the policy number, the claim number, and a telephone number providing direct access to the claims office (New Jersey)
- A verbatim Department of Insurance complaint notice in at least 12-point bold type on second and subsequent delay letters (New Hampshire)
- An honest, non-misleading explanation reflecting a reasonable and fair evaluation of the claim – not boilerplate (Arkansas, Ohio, Pennsylvania, Wisconsin, Utah)
The cadence varies from five business days in Georgia (auto, after the initial period) to ninety calendar days in New York, but the plurality of states cluster at thirty or forty-five calendar days. The safest national approach is a thirty-day cycle – the shortest common interval – with content built to California’s standard and formatting that includes New Hampshire’s DOI notice and New Jersey’s contact details. The compliance challenge is not writing the letter – it is tracking fifty different cadences, distinguishing business days from calendar days, and ensuring that the content reflects the actual status of the actual investigation rather than the boilerplate that courts have held insufficient.
The status update is the letter most likely to be written by a system rather than a person — and at most carriers, it already is. The thirty-day cycle, the form paragraph, the compliance checkbox: this is rules-engine territory, a letter generated on schedule without human intervention unless the claim’s status has actually changed. The mandate created communication; it did not necessarily create information. An automated letter that says nothing is worse than no letter at all: it satisfies a calendar trigger while violating the substantive obligation that Arkansas, Iowa, and a growing number of courts have held the letter must actually fulfill.
50-State Snapshot: Status Update Requirements
The table below summarizes the status update frequency and content requirements across all fifty states, drawn from regulatory data across five lines of business (Auto, Homeowners, Commercial Property, Workers’ Compensation, and General Liability). Where requirements differ by LOB, the Auto/Homeowners standard is shown as the primary entry, with notable LOB-specific variations noted.
The range is extraordinary. At one extreme, Georgia requires auto status updates every five business days after the initial period — a pace that essentially demands continuous communication. At the other, New York allows ninety calendar days between updates (one hundred eighty for workers’ compensation), and states like Delaware, Indiana, Louisiana, Maine, and Montana impose no specific frequency at all. The plurality of states cluster around a thirty-to-forty-five-day cycle, but even within that band, the content standards diverge sharply. California demands the most comprehensive update in the country: specific reasons the investigation remains open, an estimated decision date, identification of information still needed, and disclosure of all available coverages. Most states ask only for a “reason additional time is needed.” Workers’ compensation is the wild card — the majority of states exempt it from general status update requirements or apply separate (often longer) timelines, making it the least uniform line of business in the table.
| State | Frequency (Primary) | Day Type | Content Standard | Notable Variations |
|---|---|---|---|---|
| Alabama | 45 days | Calendar | Reasons additional time needed | WC: No specific requirement |
| Alaska | 45 days | Business | Reasons for delay; settlement offers; excess exposure | Consistent across LOBs |
| Arizona | 45 days | Calendar | Reasons for delay; must disclose settlement offers | CP: B15; WC: Reasonable (case law) |
| Arkansas | 45 days | Calendar | Specific reasons required; “still investigating” is insufficient | WC: No specific requirement |
| California | 30 days | Calendar | Specify info needed; reasons for delay; estimated decision date; disclose available coverages | WC: Exempt from Fair Claims Settlement Practices |
| Colorado | 30 days | Calendar | Reasons for delay; must convey necessary claim handling info | WC: Reasonable (case law) |
| Connecticut | Reasonable | N/A | Communications must not be false, misleading, or deceptive | WC: No specific requirement |
| Delaware | No specific requirement | N/A | Third-party: Proactive communication of settlement offers | Consistent across LOBs |
| Florida | Reasonable / 30 days (HO) | Calendar | Coverage status; adjuster name/license; substantive and honest | WC: No specific requirement |
| Georgia | 5 days (Auto, after initial period) | Business | Reason for delay; estimated additional time needed | HO/WC: No specific requirement |
| Hawaii | 30 days | Calendar | Reasonable written explanation for delay; disclose all benefits | Consistent across LOBs |
| Idaho | Reasonable | N/A | Investigation results; settlement demands (case law) | No specific statutory requirement |
| Illinois | 40 days (Auto PD) / 75 days (HO/CP) | Calendar | Reasonable written explanation; DOI notice | WC: No specific requirement |
| Indiana | No specific requirement | N/A | Case law only in limited contexts | Consistent across LOBs |
| Iowa | 45 days | Calendar | Reasons for delay; financial consequences warning if excess exposure | WC: Contemporaneous (case law) |
| Kansas | 45 days | Calendar | Specific reasons additional time needed | WC: No specific requirement |
| Kentucky | 45 days (30 initial for HO) | Calendar | Specific reasons additional time needed | WC: No specific requirement |
| Louisiana | No specific requirement | N/A | Must communicate pertinent facts (case law) | Case law: “regularly” |
| Maine | No specific requirement | N/A | No specific requirement | Consistent across LOBs |
| Maryland | 45 days | Calendar | Actual reason additional time necessary | WC: No specific requirement |
| Massachusetts | Reasonable | N/A | Material facts; settlement offers; coverage disputes | WC: No specific requirement |
| Michigan | Reasonable | N/A | All developments affecting insured’s interests (case law) | Limited statutory framework |
| Minnesota | Reasonable / B45 (CP) | Mixed | Reasons for delay; expected completion date; settlement info | WC: No specific requirement |
| Mississippi | Reasonable | N/A | Must articulate legitimate reason for delay | WC: Reasonable (case law) |
| Missouri | 45 days (Auto/HO/CP/GL) / 30 days (WC) | Calendar | Reasons for delay; settlement offers; excess judgment risk | WC has shorter cycle |
| Montana | No specific requirement | N/A | Must notify of reasons for failure to pay (statute, 60-day trigger) | Case law only |
| Nebraska | 30 days | Calendar / Business | Reasons for delay; settlement demands (third-party) | CP: B15 initial |
| Nevada | 30 days | Calendar | Reasons for delay; settlement opportunities; excess exposure risk | WC: Reasonable (case law) |
| New Hampshire | 30 days | Calendar | Factual/legal reasons for delay; DOI complaint notice in 12-pt bold | WC: No specific requirement |
| New Jersey | 30 days (Auto PD) / 45 days (other) | Calendar | Reasons for delay; office address; policy/claim numbers; phone number | WC: No specific requirement |
| New Mexico | Reasonable / Promptly (CP) | N/A | Crucial developments; settlement offers; excess exposure | Case law driven |
| New York | 90 days | Calendar | Reasons additional time needed | WC: 180 days |
| North Carolina | No specific requirement (personal) / 45 days (CP/GL) | Calendar | Explain why investigation open; what info still needed | WC: No specific requirement |
| North Dakota | Reasonable | N/A | Must explain denials; proactive on settlement offers | GL: No specific requirement |
| Ohio | 45 days | Calendar | Status of investigation; time needed; settlement offers (case law) | WC: Reasonable (case law) |
| Oklahoma | Reasonable (Auto/HO) / 45-60 days (CP/GL) | Calendar | Honest explanation; must not ignore insured’s evidence | WC: No specific requirement |
| Oregon | 45 days | Calendar | Reason additional time needed; significant developments (Moody) | CP: C30 initial, then C45 |
| Pennsylvania | 30 days initial, then 45 days | Calendar | Reasonable written explanation; expected decision date; settlement info | WC: No specific requirement |
| Rhode Island | 45 days | Calendar | Reasons additional time needed | WC: No specific requirement |
| South Carolina | Promptly (Auto) / Reasonable (GL) | N/A | Coverage disputes: Specific policy provisions; conflicts of interest | WC: 180 days |
| South Dakota | Reasonable / 30 days (CP/GL) | Calendar | Basis of evaluations; settlement offers; excess risk | WC: No specific requirement |
| Tennessee | 60 days | Calendar | Settlement offers; demands; coverage limits status; conflicts | WC: No specific requirement |
| Texas | 45 days | Calendar | Specific reasons for delay | WC: B5 |
| Utah | 45 days | Calendar | Reasons for delay; reasonable explanation of basis for position | WC: No specific requirement |
| Vermont | 30 days | Business | Reasons for delay; coverage status; settlement offers | WC: Reasonable (case law) |
| Virginia | 45 days | Calendar | Reasons additional time needed | Consistent across LOBs |
| Washington | 45 days initial, then 30 days | Calendar | Reason claim unresolved; material developments; settlement info | WC: C30 general |
| West Virginia | 15 days (after initial period) | Business | Specific reasons additional time needed | WC: No specific requirement |
| Wisconsin | Reasonable | N/A | Fair evaluation; reasonable explanation for delay/denial | Limited statutory framework |
| Wyoming | No specific requirement (Auto) / Reasonable (other) | N/A | Specific basis for denial; insured’s right to benefits info | WC: No specific requirement |
The table’s most important lesson is not about the states that regulate heavily but about the ones that do not. Delaware, Indiana, Louisiana, Maine, and Montana impose no specific status update frequency — and yet claims in those states are no less likely to stall in investigative limbo. The absence of a mandate does not mean the absence of a need; it means the policyholder has no regulatory lever to pull when the phone stops ringing. For carriers operating nationally, the thirty-day cycle built to California’s content standard is the only approach that satisfies every state with a numeric deadline while providing genuine substance in the states that have none. The alternative — calibrating update frequency state by state — is a compliance exercise that produces fifty different schedules and no better communication.
What Ended It?
Status updates kept the claim alive in the policyholder’s mind – a periodic signal that someone, somewhere, was still working. But every claim eventually ends, and for decades, many ended the same way: in silence. The adjuster stopped calling. The file was closed internally. No letter was sent. The policyholder was left to guess whether the absence of news meant the claim had been paid, denied, or simply forgotten. The obligation to say “it’s over” – and to say it clearly, in writing, with specific content – would prove to be the newest and most unevenly adopted requirement in all of claims correspondence.