Start saving proof before the story changes

No, you're not screwed.

But you do need to move fast, because an uninsured driver crash in Layton goes bad in a hurry once the evidence starts evaporating.

Rear-end wrecks on I-15 near Layton Hills Mall, Antelope Drive, Hill Field Road, or the on-ramps by Exit 330 happen in that miserable stop-and-go stretch where everybody swears traffic was "barely moving." That's exactly why the other side starts playing games. The uninsured driver may suddenly claim you stopped short, cut lanes, or were on your phone.

Here's the ugly part: if you were glancing at Slack, Teams, or a work text while remote-working your way through a lunch errand, that does not automatically hand them the case. Utah is a comparative fault state. Blame can be split. And in a basic rear-end collision, the driver behind you still has a big problem.

The first fight is proof.

Photograph the boring stuff, not just the smashed bumper

Most people take three dramatic photos and call it good. That's not enough.

You need the whole scene.

Get wide shots showing lane position, traffic backup, skid marks if there are any, the shoulder, nearby exits, and street signs. In Layton, that means grabbing markers that pin the location down: the Hill Field Road interchange, a FrontRunner overpass, the Lagoon exit area, whatever is actually there. Location matters because traffic flow matters.

Then get close-ups of damage on both vehicles.

Not just yours.

If their front end is crumpled and your rear damage lines up, that helps kill the "you backed into me" nonsense before it starts. Photograph license plates, the VIN sticker if visible through the windshield or door jamb, and the other driver's face if the situation is safe and not escalating. If they're acting squirrelly because they have no insurance, document that too by recording audio or video from a safe distance.

Utah weather can mess with the scene fast. Spring means rain, glare, and wind. Evidence on the roadway does not stick around for your convenience.

Witnesses disappear almost immediately

On I-15, witnesses don't hang around because nobody wants to spend their day at a crash scene in Davis County traffic.

If somebody saw it, get their name, phone number, and email right there. Ask them to text you so you have their number saved correctly. If they'll do it, record a short video of them saying what they saw while it's fresh.

Don't ask, "It was his fault, right?"

Ask, "What did you see?"

That answer is cleaner and more useful later.

If a Utah Highway Patrol trooper or Layton police officer responds, tell them there were witnesses and make sure those names get noted. Weeks later, "there was a lady in an SUV who saw everything" is worthless.

Dashcam footage is gold, and it gets overwritten

This is where people blow it.

If you have a dashcam, pull the file immediately and save it in at least two places. Don't trust the memory card. Don't trust the app. Don't assume it will still be there tomorrow.

If the other driver had a dashcam, ask for that footage on the spot. They probably won't hand it over, especially if they're uninsured, but ask anyway and record that you asked. If there were nearby vehicles with dashcams, ask those drivers too.

Save the footage with the date, time, and exact location in the file name. Screenshot the metadata if your camera app shows it.

And don't forget nearby business cameras. A gas station off Antelope Drive or a retail lot near the interchange may have caught part of the lead-up or aftermath. Those systems often overwrite in days, sometimes faster.

Get the police report, then read it like a hawk

You want the report number before you leave the scene if possible.

In Utah, crash reports can come from the investigating agency, often Layton City Police or Utah Highway Patrol depending on where the wreck happened. Get the officer's name, badge number, agency, and report number. Then request the report as soon as it's available.

When it arrives, don't just skim it.

Read every line.

Wrong vehicle direction, wrong lane, wrong insurance status, wrong witness name, wrong time - those mistakes turn into insurance headaches fast. And since the other driver has no insurance, you may be dealing with your own uninsured motorist coverage, which means your insurer is not automatically your friend here no matter how nice the adjuster sounds.

Utah doesn't cap pain-and-suffering damages in regular car wreck cases. The med-mal cap you hear about - $450,000 in non-economic damages - is a different lane entirely. For a rear-end injury claim, the real issue is proving the crash and the harm, not some made-up cap.

Save your phone records before the carrier makes it hard

If you were using your phone around the time of the crash, preserve the truth now.

That means screenshots of call logs, text timestamps, app notifications, and your phone's screen-time or activity history for that hour. If your work chat shows you got a message at 2:14 p.m. but you didn't open it until 2:19 p.m., save that. It may matter.

Also save your location history if it's enabled.

Don't edit. Don't crop in a way that looks shady. Save full screenshots.

Phone carriers do not keep everything forever in an easy, consumer-friendly format. App data can be even worse. If there's any chance your distracted-driving issue becomes part of the blame argument, preserving the actual timeline early is smarter than trying to reconstruct it months later.

Save these records this week, not "eventually"

If the crash left you hurt, keep a tight evidence file:

• tow and storage receipts
• repair estimate and photos before repairs
• ER, urgent care, or chiropractor records
• wage-loss proof, even if you work remote and used PTO
• screenshots of missed meetings, canceled calls, or reduced work output
• your insurance policy pages for uninsured motorist coverage
• every text, email, or voicemail with the other driver and your insurer

Remote workers miss this one all the time: lost income is not only "I couldn't clock in." If neck pain from a rear-end hit means you can't sit through coding sessions, client demos, or sprint planning without breaks, document that in plain English. Your calendar, Git commits, project notes, and manager messages can tell the story better than vague complaints do.

Utah has plenty of workers' comp fights through the Labor Commission when injuries happen on the job, but this is not that system unless you were driving for work duties. For a regular highway rear-end in Layton, your proof file is the whole damn game.