Explain a coverage in plain language

Act as an agent explaining a coverage to somebody who keeps mishearing it. Explain the coverage below so it sticks.

Coverage: [WHAT, e.g. UMBRELLA / REPLACEMENT COST VS ACTUAL CASH VALUE / ORDINANCE OR LAW]
Who I am explaining it to: [HOMEOWNER / BUSINESS OWNER / LANDLORD / OTHER]
What they currently believe: [THEIR WORDS, OR "UNSURE"]
Why it is coming up now: [RENEWAL / CLAIM / QUOTE / THEY ASKED]
Format: [EMAIL / CALL SCRIPT / ONE-PAGER]

Produce, in order:
0. ASSUMPTIONS. Any bracket I left unfilled, anything ambiguous, and what you assumed instead. Write "none" if there were none
1. The coverage in one sentence, no insurance words
2. One concrete scenario where it pays. Real numbers, an ordinary situation
3. The same scenario without the coverage. Same numbers. Then one ordinary situation where this coverage does not pay, in one sentence
4. The misunderstanding people have about it, named directly
5. What it costs, roughly, and what moves that number
6. One question that tells me whether they actually understood
7. WHAT YOU SHOULD CHECK AGAINST THEIR ACTUAL POLICY. Every inferred or unsourced claim, listed plainly, so it does not end up in what you send

Rules:
- Anything you inferred rather than were told goes in "WHAT YOU SHOULD CHECK AGAINST THEIR ACTUAL POLICY" instead, never in both places
- No insurance term appears without being defined in the same sentence
- The scenario is ordinary, not dramatic. A burst pipe, not a hurricane
- Never state a real price. Describe what moves it and put any figure in the verify section
- After section 6, add one line for the client: this is a plain-language summary, and the policy wording decides what is covered
- Hard limit: 450 words for the whole response. If you cannot fit it, cut the least useful section and say which one you cut

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response, every section filled in, nothing deferred to a follow-up. If a required input is missing, ask for it once before starting; otherwise proceed and record the assumption in section 0.

Notes: R42 build; insurance set. Tuned to vendor prompting guidance.