Same accident. Different state. Different answer.

A small example

Your car gets towed after an accident. It sits in a storage lot, running up a bill. At some point your insurer stops paying for that storage. How much warning do you get?

In Washington, five days. The insurer has to tell you by phone or in writing and note it in the file. In New Jersey, three working days, with a copy kept on file. In Florida, 72 hours. In California, "reasonable notice," with no number attached.

In Texas, New York, and Minnesota, we looked and could not find a state rule setting any notice period at all.

Seven states. Six different answers. One perfectly ordinary question.

Nothing on your paperwork tells you which of those situations you're in. That is the problem ClaimedUp exists to solve. Not that the rules are unfair, but that they're genuinely hard to find, and nobody has assembled them for the person they affect.

Where this came from

ClaimedUp grew out of firsthand professional experience in insurance claims, and out of watching, repeatedly, how confusing a claim becomes for an ordinary person when more than one policy, company, or set of rules might apply.

The information was never really missing. It was in statutes, regulations, policy documents, platform help pages. It just wasn't anywhere the person living through the claim would think to look, written in a way they could use.

They had a claim. What they didn't have was a map.

What we built

Coverage for a driver can change minute to minute. Your personal policy, the platform's policy, and your state's law all interact, and which one answers your question depends on details as specific as whether you'd tapped "accept" yet.

So instead of publishing articles, we built something you search the way your situation actually happened.

You get a plain-English answer, the source it came from, and the date we checked it.

How we know what we tell you

Every answer here traces back to a primary source. A statute, a state regulation, an official platform document. Not somebody's summary of somebody's summary.

Take Texas and storage again. We read the unfair claims settlement rules, the insurance code, and the department's own bulletins and consumer guides. We found no notice requirement anywhere in them, plus two bills that would have created one and never passed.

So this is what we publish: no Texas rule sets a specific notice period. And this is what we don't publish, even though it would be easier: that Texas insurers can cut you off without warning. We checked the state's rules, not every policy form and every court decision. That second sentence isn't ours to write.

Only one of those claims is ours. We make that one.

The standard is built into the site. Research we haven't finished doesn't appear at all. Research that's partway shows you exactly how far we got. And every answer carries the source and the date, so you never have to take our word for it. Open the link and check us.

Laws change, platform programs change, policies change. That's why the date is on every answer, and why we keep going back.

Why drivers first

Because this is where the gap is widest.

Most writing about rideshare accidents is aimed at injured passengers. The driver appears in it as a fact of the case, the person who was working, the person whose app status matters, but almost never as the reader.

Meanwhile the rules underneath are unusually fragmented. Minimum coverage while you're waiting for a request differs by state. New Jersey requires $1.5 million during a ride where most states require $1 million. Minnesota's rideshare insurance law is written around trips carrying a passenger, so delivery work falls outside it.

General advice can't reach any of that. It has to be specific to be worth anything.

What we're not

Straightforwardly:

• ✕ Not an insurance company or an adjuster.
• ✕ We don't represent you or negotiate for you.
• ✕ We don't decide what your policy covers.
• ✕ We don't give legal advice.
• ✕ We can't promise how your claim ends.

ClaimedUp doesn't replace a lawyer, a licensed insurance professional, your insurer, or your adjuster. It's meant to help you walk into those conversations knowing what's being discussed.

We're also independent. Not affiliated with, sponsored by, or endorsed by Uber, Lyft, DoorDash, Instacart, Amazon Flex, any insurer, or anyone else we write about, unless we say so directly. Those names appear here because explaining publicly available insurance information requires naming the companies it applies to.