Share Your Story | VictimsGuide.com
Share Your Story

Help Build the Public Record

Help document how Colorado auto insurance, medical billing, disclosure practices, claim conduct, and settlement systems affect real people after serious crashes. A well-organized story can help others understand the system more clearly.

Purpose Turn scattered private experiences into a clearer public record.
Best submission Factual, organized, and tied to dates, documents, entities, and sequence.
Main caution Do not send highly sensitive material casually or unnecessarily.
Public value Pattern evidence can support education, accountability, complaints, and reform.
Colorado auto-insurance focus Last reviewed: April 29, 2026 Spanish-version ready
Overview

Why submit a story

Most people experience the post-crash system in isolation. They do not know whether what happened to them was unusual, routine, preventable, or part of a larger pattern. Story submissions help change that. They help turn scattered private experiences into a clearer public record.

Why stories matter

Stories can show how the same kinds of problems repeat across different families, insurers, employers, hospitals, billing systems, tow yards, collection channels, and claim pathways.

Why structure matters

A story is most useful when it helps others see the timing, sequence, documents, entities, and pressure points that reveal a recurring public-interest issue.

Working principle: The strongest story is not the angriest story. It is the clearest, most factual, and most document-grounded story.
Useful Stories

What makes a story useful

Date of the crash or approximate time period Timing helps compare one story to another and identify patterns.
Main issue encountered Examples include low limits, delayed disclosure, MedPay trouble, work-vehicle confusion, hospital liens, claim delay, hidden coverage, or release pressure.
Sequence of what happened next The order of events often matters more than general conclusions.
Names or types of the entities involved Insurers, hospitals, tow yards, employers, contractors, billing companies, collection vendors, or others may reveal recurring system actors.
Written communications received Letters, emails, notices, claim documents, settlement offers, release drafts, and billing notices are often the strongest parts of the story.
Practical effect on the person or family What pressure followed, what changed, what deadlines appeared, and what consequences resulted.
Submission Structure

Suggested submission structure

A useful story can usually be organized in seven parts. The goal is to make the public pattern visible without requiring the reader to sort through an entire claim file.

1. What happened Describe the crash or event in general factual terms.
2. What issue became the problem Identify the main system problem that followed.
3. What you were told Summarize the explanations or positions given by insurers, providers, employers, billing entities, or collection vendors.
4. What documents or notices you received Name the letters, claim notices, bills, lien notices, emails, policy materials, release drafts, or complaint responses involved.
5. What pressure or obstacle followed Explain what practical problem came next: delay, billing pressure, settlement pressure, missing policy information, lien activity, collection activity, or other harm.
6. What outcome or current status exists now Explain what happened next or where the matter stands today.
7. What pattern this story may show Identify the larger public-interest issue the story may help document.
Story Submission Form

Submission area

Use the form on this page to submit a factual summary of your experience. Keep your submission focused on what happened, what issue arose, who was involved, what documents you received, and why the problem mattered.

Form placement area Place the live Squarespace form block or secure intake form directly below this section. The form should ask for organized facts first and should not request unnecessary sensitive documents at the initial submission stage.
Basic contact Name, email, and preferred contact method.
Crash setting Approximate date, county or city, and basic crash type.
Main issue category Low limits, disclosure failure, MedPay, liens, work-use, release pressure, complaint issue, or other pattern.
Factual summary What happened, what was said, what documents exist, and what pressure followed.
Consent preference Research only, anonymous public use, or identified public use only with separate written approval.
Privacy acknowledgment Do not upload highly sensitive documents unless specifically requested through a protected process.
Submission caution: Initial submissions should summarize the issue. Full records, claim files, medical files, or financial documents should not be sent casually.
After Submission

What happens after submission

What may happen

  • Submissions may be reviewed for clarity and relevance.
  • Some submissions may be grouped by issue category.
  • Some submissions may help shape pages, videos, complaint guides, reports, or white papers.
  • Some submissions may remain private and unpublished.
  • Some submissions may help identify recurring actors, timing issues, or structural patterns.

What submission does not do

  • It does not create attorney-client representation.
  • It does not create a legal-services relationship.
  • It does not guarantee publication.
  • It does not guarantee an investigation.
  • It does not guarantee an immediate response.
Important boundary: Submitting a story supports public-interest pattern review. It is not a request for legal representation and should not be treated as legal advice.
What We Are Looking For

Public-interest categories

Low policy limits after serious injury When the available bodily-injury limits are not remotely sufficient for the loss.
“Full coverage” confusion When the product sold does not match the consumer's reasonable understanding of actual protection.
Delayed or incomplete policy disclosure When the real policy picture remains hidden, arrives too late, or omits policies, endorsements, umbrella coverage, or policy copies.
Hidden or additional policies When umbrella, employer, owner, household, commercial, or other policies appear late or are not disclosed cleanly.
Work-vehicle or employer-responsibility issues When a personal-policy story hides a broader work-related claim structure.
Project-owner, contractor, or upstream-player issues When a driver-level crash may connect to a larger project, site, access route, contractor, owner, or insurance structure.
MedPay confusion, delay, or denial When early no-fault medical protection is misunderstood, delayed, underused, exhausted, or mishandled.
Hospital billing, liens, or collection pressure When medical billing systems destabilize the victim before the liability or coverage picture is clear.
Release pressure before the full loss is understood When finality is pushed before the facts, treatment, policy picture, lien picture, or UM/UIM posture are mature enough.
Claim-conduct or complaint-record problems When delay, vague explanations, under-investigation, missing documents, or repeated reassurance make the claim difficult to challenge without a disciplined record.
Do Not Send Casually

What not to send casually

Story submissions can contain sensitive information. The initial submission should identify the public-interest pattern without exposing unnecessary private data.

Avoid sending this casually

  • Full Social Security numbers.
  • Full driver’s license numbers.
  • Bank, credit card, or payment information.
  • Passwords or account credentials.
  • Full claim files without context.
  • Full medical records unless specifically requested later through a protected process.
  • Anything you would not want exposed if transmitted insecurely.

Safer first submission

  • Approximate date and location.
  • Type of issue encountered.
  • Names or types of entities involved.
  • General timeline.
  • Types of documents received.
  • What pressure followed.
  • What public pattern the story may show.
Privacy rule: Share only what the submission process specifically requests and what you are comfortable disclosing.
Workflow

Story-to-pattern workflow

The purpose of this workflow is to help contributors turn a confusing private experience into a structured public-interest submission.

1. Identify the problem

  • Low limits.
  • Hidden insurance.
  • Delayed disclosure.
  • MedPay problem.
  • Hospital lien or collection pressure.
  • Release or settlement pressure.

2. Identify the timeline

  • Crash date.
  • Claim report date.
  • Bill or lien dates.
  • Policy request date.
  • Offer or release date.
  • Complaint or denial date.

3. Identify the documents

  • Letters and emails.
  • Policy disclosures.
  • Settlement offers.
  • Release drafts.
  • Medical bills and lien notices.
  • Complaint records.
Submission preparation sheet
Before submitting, write down: Crash date: County or city: Type of crash: Main issue: Insurance companies involved: Medical-billing entities involved: Employer or work-use issue: Policy-disclosure issue: MedPay issue: UM/UIM issue: Hospital lien or collection issue: Settlement or release pressure: Key dates: Key documents: What pattern this story may show: What should remain private: What can be safely summarized publicly: Consent preference:
Guidance: A structured story is safer for the person sharing it and more useful for public reform.
Public Understanding

From private experience to public understanding

A serious crash often leaves people feeling isolated and pressured. But repeated experiences can become pattern evidence, and pattern evidence can support education, accountability, complaint strategy, and reform. That is why this page exists.

Core idea
A single story can explain harm. Repeated stories can reveal structure. Documented structure can support reform.
Authorities

Authorities and public-record anchors

These references support the public-interest framing of this page. They do not replace private legal advice, claim analysis, complaint strategy, policy review, or representation by a qualified attorney.

Colorado Division of Insurance — consumer protection and complaint role Colorado DORA resource explaining that the Division of Insurance regulates the insurance industry, answers consumer questions, investigates complaints, and helps consumers understand insurance. Visit DORA insurance consumer protection
DORA — File a complaint Colorado Department of Regulatory Agencies complaint resource for identifying the applicable DORA division or regulatory area and submitting complaints or reports. Visit DORA complaint resource
C.R.S. § 10-3-1104 — Unfair methods of competition and unfair or deceptive acts or practices Colorado statute defining unfair and deceptive insurance practices, including unfair claim-settlement practices, misrepresentations, unreasonable communication failures, and claim-investigation problems. Read C.R.S. § 10-3-1104
C.R.S. § 10-3-1117 — Required automobile liability policy disclosures Colorado statute requiring disclosure of known relevant auto liability policies, including excess or umbrella insurance, after a proper written request sent to the insurer’s registered agent. Read C.R.S. § 10-3-1117
DOI Complaints Guide VictimsGuide companion page explaining how to use Colorado’s insurance complaint system as a document-based administrative tool when claim handling becomes unclear or unreasonable. Open the DOI Complaints Guide
Stories and Reform VictimsGuide companion page explaining how organized stories can reveal recurring patterns and support public education, oversight, and legislative reform. Open Stories and Reform
The 20 Illusions of Auto Insurance VictimsGuide series explaining recurring claim patterns, including low limits, hidden insurance, work-use disputes, hospital-billing pressure, release problems, and finality risks. Open the 20 Illusions series
Policy Disclosures Guide VictimsGuide companion page explaining how to request policies, limits, endorsements, umbrella coverage, deadline tracking, and incomplete-production issues before settlement. Open the Policy Disclosures Guide
Crash Victim Workflow VictimsGuide companion workflow for preserving evidence, organizing treatment and billing records, tracking coverage, reviewing releases, and avoiding premature finality. Open the Crash Victim Workflow

Short glossary

Story submission
A factual account shared to help identify recurring insurance, billing, lien, disclosure, claim-conduct, or settlement patterns.
Pattern evidence
Repeated facts, documents, timing, actors, or pressure points that suggest a broader public-interest issue beyond one private dispute.
Complaint record
A dated, document-supported record that can be used in an insurance complaint, regulatory submission, public report, or reform analysis.
Policy disclosure
The process of obtaining relevant insurance information, including insurer identity, insured names, limits, policy copies, and umbrella or excess coverage.
Public-interest use
Use of a story to educate, identify patterns, support reform, inform videos or white papers, or help explain how systems operate in practice.
Anonymous or de-identified use
Use of a story without identifying the person, family, claim number, policy number, or unnecessary private details.
Privacy filter
The discipline of removing unnecessary medical, financial, personal, and identifying details before a story is shared publicly.
Release pressure
Pressure to sign settlement or release documents before medical, billing, policy, lien, UM/UIM, or responsibility issues are mature enough for finality.
Important Notice

Project notice

VictimsGuide.com is a public-interest educational project focused on Colorado auto insurance, crash recovery systems, transparency, accountability, and reform. Its purpose is to help citizens understand how these systems work in practice.

Important notice

This page provides public-interest educational information and commentary. It is not legal advice, does not create an attorney-client relationship, and is not a substitute for advice from a qualified attorney. Submitting information through this site, sending a story, using a contact form, or communicating with the project does not create an attorney-client relationship.

Bottom line

Story submissions matter when they are organized well enough to show that what felt private and isolated may actually be part of a larger public pattern. That is how private experience begins to support public understanding.

Stories and Reform Start Here 20 Illusions Policy Disclosures Contact
VictimsGuide.com