The ugly part first: your boss not carrying workers' comp does not erase the fact that you got hurt on the job.

In North Dakota, employers are generally supposed to have coverage through Workforce Safety & Insurance, the state system people still call workers' comp. If your employer didn't buy it, that is their violation. It is not supposed to become your eviction problem.

And if this happened on I-94 near Dickinson because an 18-wheeler drifted out of its lane and clipped you, you may be dealing with two separate claims at the same time. That's where people get lost.

The truck crash claim and the work injury claim are not the same thing

If a semi sideswiped you, the trucking company's insurer is one lane of recovery.

Your work injury benefits are another lane.

Normally, if the employer has proper North Dakota coverage, WSI handles wage loss and medical while the liability claim against the truck gets sorted out later. But when the employer has no coverage, the whole thing gets messier fast.

Messy does not mean hopeless.

It means you need to stop waiting for the boss to "figure it out," because the boss is already breaking the law and probably trying to buy time.

Money first: the fastest possible source may be auto no-fault, not the truck company

Here's what most people in Dickinson don't realize after an interstate sideswipe: North Dakota is a no-fault auto state.

That matters because no-fault benefits can pay medical bills and some lost wages without waiting for the trucking insurer to admit fault. If you were driving your own car, start with your own auto policy's no-fault coverage. If you were in a farm or company vehicle, look at the policy on that vehicle.

That can be the quickest path to money while everything else drags.

The trucking insurer is not in a hurry. Not on I-94. Not when there's lane drift, speed questions, road spray, or the usual garbage about "sudden wind." Out west, around Dickinson, crosswinds can absolutely push a trailer, and truck insurers love using weather as a smokescreen. North Dakota roads are open enough for that argument. US-2 across the top of the state is notorious for brutal crosswinds with no wind breaks, and insurers try the same excuse on the interstate whenever they can.

But "the wind did it" is not some magic defense if the driver failed to control the rig.

Your employer being uninsured opens a different fight

If the crash happened while you were working - driving between fields, hauling supplies, moving crews, whatever the job was - report the injury to the employer in writing immediately if you haven't already.

Do not keep this verbal.

Text, email, screenshot, save it.

North Dakota's WSI system has procedures for uninsured employers. The state can come after the employer for failing to carry coverage, and injured workers may still be able to seek benefits through that route instead of being left with nothing. At the same time, because the employer was uninsured, the usual shield that protects covered employers can crack. That can expose the employer directly.

That's a big damn difference.

An insured employer usually points at WSI and says, "That's the system." An uninsured employer may end up facing direct financial exposure because they ignored a legal requirement.

If rent is due now, move in this order

• Open the no-fault claim on the vehicle policy immediately
• Get the crash report number from Stark County or the North Dakota Highway Patrol
• Report the work injury to the employer in writing today, not tomorrow
• Ask WSI specifically about an injury involving an uninsured employer
• Keep every wage record, schedule, text, and proof you were on the job

That last piece matters more than people think.

Seasonal agricultural workers get jerked around on paperwork all the time. Cash payments. Shifting schedules. "You weren't really working yet." "You were just heading over there." "You were off the clock." Same song every season.

If you were traveling for the employer's work purpose, the boss doesn't get to rewrite the trip after the crash.

The second injury problem is real, but it doesn't kill the claim

Your headline issue is brutal: this is not the first time you got hurt doing seasonal work.

Insurance companies and shady employers love that.

They'll say your neck already hurt. Your back already hurt. Your shoulder was already bad from the last season. They'll act like a second crash means no one owes you because you were not perfectly healthy before.

That's nonsense.

A new crash that makes an old condition worse is still a real injury claim. In fact, the medical records from the first injury can end up proving the change. If you were functioning, working, lifting, driving, and then after this I-94 sideswipe you couldn't turn your head, missed two weeks, needed new treatment, or your pain shot up, that difference matters.

The ER record from Dickinson, ambulance notes, urgent care follow-up, missed-shift texts, and pharmacy receipts can do more for you than a long argument ever will.

Don't let the landlord timeline force a bad insurance decision

When rent is late and an eviction notice is starting, people sign garbage fast.

The trucking adjuster knows that.

So does an uninsured employer who suddenly gets sweet and offers "a little help" if you don't make trouble.

If they hand you a release in exchange for a quick check, read the damn thing like your next three months depend on it, because they do. A sideswipe can look minor at the scene and turn into weeks of neck, back, rib, or shoulder trouble. If the truck shoved your vehicle into the lane edge, median, or rumble strip, symptoms often get worse after the adrenaline burns off.

In Dickinson, with long drives, rough spring thaw conditions, and work that doesn't forgive lifting limits, a "small" crash can wreck your ability to earn by the end of the week.

That's why the immediate goal is not just proving fault. It's finding the fastest legitimate source of benefits, locking down proof that you were working, and not letting an employer who skipped required coverage pretend your injury is somehow your fault.