Yes, that can be real - and it's exactly why these cases get nasty fast

If you were buried in a trench at a West Fargo jobsite and somebody is now saying, "Sorry, the policy might not cover this kind of accident," that is not automatically bullshit.

It also does not mean you're out of options.

A lot of workers hear a simple version from a buddy on break: if the contractor caused it, the contractor's insurance pays. Clean, neat, done. Real life is uglier. Especially with excavation work.

A trench collapse with no shoring in place is the kind of fact pattern that should make an insurer nervous. No shoring. No trench box. No proper protective system. Dirt gives way, a worker gets buried, and now everyone starts looking for a way to duck the bill.

That "coverage gap" language usually comes from one of three places.

First, the company may have a general liability policy that excludes part of the excavation risk, especially if the claim is framed as damage tied to earth movement, subsurface work, or a contractor's specialized operations.

Second, the contractor may have workers' comp for its own employees, but you may not be that company's employee at all. On a busy West Fargo commercial site, there may be a general contractor, a subcontractor, a staffing company, and a property owner all pointing fingers at each other.

Third, the insurer may not be denying coverage for the whole event. It may be denying coverage for one insured, one type of damage, or one part of the claim. That matters more than people realize.

No shoring is not just a safety screwup - it shapes the insurance fight

On a trench job, the absence of shoring is a giant red flag because it suggests the collapse was preventable.

That matters for liability.

It also matters for who gets dragged into the claim.

If Derek from a warehouse in West Fargo picks up weekend construction shifts because 12-hour warehouse runs don't cover the rent, and he gets buried in a trench with no protective system, the obvious target is the employer running the trench work. But obvious is not the same as complete.

The site owner may have exposure.

The general contractor may have exposure.

Another subcontractor may have created the unsafe condition or kept the trench open too long after rain, vibration, or nearby equipment movement.

Spring in North Dakota is its own problem. Freeze-thaw makes soil conditions less predictable. One day the ground feels locked in. Next day it's soft, sloughing, and unstable. Add heavy equipment nearby and the trench wall can fail in seconds.

That's why a weird insurance denial does not end the case. It usually expands it.

The big thing most injured workers miss: coverage and fault are different fights

A carrier can say, "Our policy doesn't cover this insured for this loss," while the injured worker still has a valid claim against somebody else on the job.

Those are two separate questions.

Was somebody negligent?

And if so, whose insurance, assets, or employment coverage responds?

People mash those together because insurance companies want them mashed together. It makes the denial sound final when it often isn't.

In a trench burial case, the paper trail matters like crazy. Not glamorous, but this is where the case turns:

• who controlled the trench, who was supposed to install shoring, what company employed each worker on site, what the contract required, and exactly what policy exclusions the carrier is relying on

If the at-fault contractor's commercial policy has a gap, the next question is whether another policy steps in. Additional insured coverage. Umbrella coverage. Another subcontractor's policy. Premises liability coverage from the property owner. Workers' comp through the direct employer if you were on that employer's payroll. Sometimes more than one.

West Fargo worksites are full of overlapping companies, and that's not an accident

Around West Fargo, from industrial builds near Main Avenue W and Sheyenne Street to warehouse and commercial expansion along I-94, job sites are rarely just one company doing one thing.

That's why the first version of the story you hear is usually incomplete.

"Company A caused it" may be true.

But if Company B supervised the site, Company C rented the excavation equipment, and Company D employed the worker, the money side gets complicated fast.

And insurers know exhausted workers won't always chase those layers down. A warehouse worker pulling 12s already has enough going on. Pain meds, missed checks, MRI appointments, maybe numbness in the legs or back spasms from the burial pressure. The carrier is counting on fatigue more than facts.

Workers' comp may exist, but that does not answer the whole insurance question

If you were doing the job as an employee, workers' comp may cover medical treatment and wage loss no matter who caused the collapse.

That still does not answer whether a third-party claim exists against a general contractor, subcontractor, site owner, or outside excavation company.

In North Dakota, personal injury claims generally have a six-year statute of limitations. That is unusually long. Longer than most states.

Do not mistake that for unlimited breathing room.

The legal deadline may be generous, but the evidence deadline is not. Trenches get filled. Sites get cleaned up. Photos vanish. Foremen "don't remember." Equipment logs get harder to track down. By the time six years passes, the useful facts can be dead as hell.

If the insurer says "earth movement exclusion," read that carefully

This is one of the favorite dodge moves in excavation cases.

An insurer may try to lump a trench wall failure into broader excluded earth movement language, as if this were some natural shifting ground event instead of a preventable excavation collapse on a controlled worksite.

Sometimes that argument sticks.

Sometimes it doesn't.

It depends on the exact policy wording and the exact facts: where the trench was, who excavated it, whether the collapse came from worksite activity, whether the exclusion applies to this insured, and whether another endorsement brings the claim back into coverage.

That's why "there's no coverage" is often just the opening punch, not the final one.

Out on US-2 you learn fast that North Dakota conditions can turn bad with no warning - brutal crosswinds, no wind breaks, nothing to stop a mess once it starts moving. Insurance fights after a West Fargo trench burial work the same way. One denial letter hits, and suddenly every company on the project starts drifting away from responsibility unless somebody pins down who controlled the trench and which policy actually has to pay.