Are Liability Waivers Enforceable in North Dakota?

A college hockey player ran a ten kilometre charity road race in Grand Forks as part of his team's preseason conditioning. He became severely dehydrated during the race, and the damage to his kidneys and liver eventually cost him one kidney transplant and two liver transplants. Before the start he had signed a registration form saying he entered the event at his own risk, assumed all responsibility for injuries incurred directly or indirectly through his participation, and agreed not to hold the participating sponsors responsible for any claims. North Dakota enforced it. The interesting part is how the state handled the fact that the form reached further than the law allows: rather than voiding it or calling it ambiguous, the court read the governing statute into the contract and treated the sweeping words as covering negligence only. That mechanism is unusual and it changes what a badly drafted release costs you here. The state by state picture is on the liability and waivers hub. Two statutes and one decision, summarised for working operators rather than lawyers.

Are liability waivers enforceable in North Dakota?

Yes, and broad wording survives better here than in most states.

The decision is Reed v. University of North Dakota, 1999 ND 25. The court began where nearly every state begins, acknowledging that the law does not favour contracts exonerating parties from liability for their own conduct and that such clauses are strictly construed against the party they benefit. Then it did something more useful for an operator than another recitation of disfavour: it held that where the language clearly and unambiguously evidences an intent to extinguish liability, the parties are bound by it. The release in front of it was broad, undefined in places and drafted for a charity fun run, and it still held.

The Wandering Angler, WY

The statute gets read into your form

North Dakota carries a provision, inherited from the same nineteenth century code that several western states adopted, declaring that any contract aimed, directly or by a longer route, at excusing somebody from answering for their own deceit, for deliberately harming another person or that person's property, or for breaking the law carelessly or on purpose, runs against what the law will allow. On its face that provision looks like it should have killed a release covering any claims and all responsibility. It did not, and the reason is stated in a footnote worth more than most opinions. Contracts are construed in light of existing statutes, which become part of and are read into the contract as if those provisions were included in it. So the statute governed the interpretation of the release, and the sweeping words were limited to negligent acts as a matter of law.

Why that mechanism matters to you

Compare it with what happens elsewhere. In some states a clause that reaches too far is treated as ambiguous and fails entirely. In others it is unenforceable to the extent of the overreach and the rest is trimmed away by a public policy balancing exercise. North Dakota simply assumes the statutory limit was written into your document from the start. The practical consequence is that overbreadth is a much cheaper mistake here than in most jurisdictions. That is not an argument for sloppiness, because the same court still requires clear and unambiguous language and still construes it against you. It is a reason to spend your effort on clarity rather than on hedging, and it explains why a plainly worded release drafted by a volunteer race committee did the job.

Single event beats season long

One line in the analysis deserves to be pinned above the desk of anyone who takes repeat customers. The court noted that this release was limited to a single event, and contrasted it with a Wisconsin case in which a release covering an entire season of ski shows was held unenforceable because it did not clearly identify what would be performed. The lesson translates directly. A form signed once and treated as covering every trip a guest takes with you over five years is doing more work than a court may allow it to do. A form signed for the trip in front of you, describing that water and that day, is standing on the ground the North Dakota court approved. Collect one per trip. It takes a minute, and it also solves the version control problem that catches operators who have quietly improved their paperwork since the customer first signed.

Consideration is easier to satisfy than people think

The runner argued the release failed for want of consideration, since he had paid nothing to the race organiser. The court disposed of that quickly. Consideration may be any benefit conferred or detriment suffered, the forbearance of a legal right is itself a detriment, and the organiser's agreement to let him run the course in exchange for his agreement not to sue supplied it. For a guide business that answers a question people worry about needlessly. A comped trip, a charity auction day, a familiarisation trip for a lodge, a friend's kid brought along at no charge: the release still has something to stand on, because being permitted to take part is the benefit and giving up the right to sue is the detriment. Get the form signed on the free trips too. The same question is answered on different reasoning in the South Dakota piece, which is worth a look for anyone working both sides of the line.

Vagueness arguments need more than an undefined term

He also argued the phrase participating sponsors was too vague, since the form never defined it. The court pointed out that the organiser was identified on the registration form as the entity to contact about the race and was plainly a participating sponsor, and rejected the argument. That is a reminder that an ambiguity claim has to bite on something real. It is also a reason to name yourself properly. If the release refers to the operator, the outfit, the sponsors or any other category, make sure a stranger reading the document could work out who that includes, and put your registered business name somewhere on the page rather than only your trading name.

Injuries nobody imagined are still inside plain words

The most sympathetic argument was that nobody contemplated a dehydration injury severe enough to require three transplants, or the allegedly inadequate medical response afterwards. The court accepted he may not have contemplated the severity, then held that the consequences of dehydration and the allegation of poor emergency care at the race site fell within the plain meaning of his assumption of all responsibility for injuries incurred directly or indirectly from participating. It added that the release would be rendered meaningless if construed otherwise, and pointed out that he conceded awareness of some risks inherent to running and that his own complaint treated dehydration as a foreseeable race injury. Severity, in other words, is not the same as unforeseeability. What matters is whether the type of harm sits within the words and within the risks of the activity.

Compulsion from a third party is not compulsion from you

This is the subtlest point in the case and it applies to a lot of guide work. He said he had no choice about signing, because running the race was a mandatory part of his team's conditioning programme and the coaches handed him the form. The court agreed there was compulsion and located it precisely: it came from his relationship with the hockey programme, not from the race organiser. He was under no economic or other pressure from the organiser to sign. Now think about corporate charters, tournament fields, lodge packages and school groups. A guest whose employer, team or tour operator told them to be there may feel they had no choice, but that pressure did not come from you. The two factor public policy inquiry the court described, which looks at bargaining power and at whether the service is a public or essential one, is set out at greater length in the Minnesota analysis, where it originated.

What the statute still keeps out of reach

Reading the provision into the contract cuts both ways. It saved the release from being struck down for overreaching, and it also means no form in this state gets anywhere near deceit, deliberate harm, or lawbreaking of either kind. The court noted the release before it was not limited to negligent conduct on its face, but that the claims were negligence claims and nobody argued the point. An operator should draft to the line anyway. Say the release covers ordinary negligence in conducting the trip and the risks that come with the activity, and leave the rest alone. You gain nothing by reaching past a boundary the statute will impose on your document regardless.

Silver Sea Adventures, AK

Strictly construed still means what it says

It would be a mistake to read this case as North Dakota going easy on operators. The court repeated the standard rule that these clauses are construed strictly against whoever benefits from them, and the only reason the race form survived is that its central sentence was clear. Everything the runner attacked was at the margins: an undefined category, an unanticipated severity, an absent fee. Had the operative sentence itself been muddled, the outcome would likely have gone the other way, as it did in the states covered in the New Hampshire analysis and the Missouri analysis, where clear wording was the whole test. The safe reading is that North Dakota will not punish you for reaching too far, and will absolutely punish you for writing badly.

Photographs and the other clauses in the same form

The registration form the runner signed did two jobs at once. Alongside the assumption of risk language it granted permission for the free use of his name and picture in any broadcast or account of the event. That is worth noticing, because guide operations depend on photographs and most collect them without ever asking. If you post client pictures, put a short permission line in the same document, describing where images may appear and giving the guest a way to decline. It costs one sentence, it removes an argument that has nothing to do with injuries, and it sits naturally beside the rest of the paperwork. Keep it clearly separate from the release clause so that a question about one does not become a question about the other.

When two businesses run the same day

The runner also argued the race organiser and the university had acted in concert, which would have made the organiser jointly liable for the university's share of fault. He lost. The court held that knowledge of each other's activities, presence at the site, failure to object, and even asking in advance about water and emergency care did not amount to the common plan or design that joint liability requires. Concurrent carelessness by two parties is not the same thing as acting together. For guides that matters whenever a trip involves more than one business: a lodge and a guide, a mothership and a skiff operator, a tournament committee and the boats fishing it. Each is answerable for its own share, and each needs its own paperwork, its own briefing and its own insurance rather than an assumption that somebody else's arrangements will cover the day.

The recreational land chapter is unusually well drafted

North Dakota's landowner provisions are worth reading even if you own nothing, because the definitions are sharper than most states manage. Under the chapter published by the North Dakota Legislative Branch, an owner of land owes no duty to keep premises safe for recreational use, and no duty to warn of a dangerous condition, use, structure or activity. Land takes in public and private ground, roads, water, watercourses and anything built or installed on them. Owner includes tenants, lessees, occupiers and whoever is in control. And recreational purposes is defined about as broadly as language allows, covering any activity engaged in for exercise, relaxation, pleasure or education.

Two definitions a guide should read twice

The chapter defines charge as money asked in return for an invitation to come onto the land, and then defines commercial purpose in terms that reach much further than a fee. A commercial purpose includes a deliberate decision to invite or permit use of the property for normal business transactions, and expressly covers inviting the public onto the premises for recreation as a means of encouraging business or directly improving the owner's commercial activities other than through good will. Read that against your access arrangements. A landowner who lets your clients cross because it might bring them customers has made a commercial decision. A landowner who does it out of pure neighbourliness has not. The distinction matters to them rather than to you, which is exactly why you should raise it before the season instead of after a claim.

Drafting for this state

Six things, most of them cheap. One form per trip rather than one per customer. Name the registered entity, its owners, captains, crew and agents, and any vessel used. Describe the specific water and the specific day. Set the hazards down the way you would describe them on the dock, serious outcomes included. Say the release covers negligence in conducting the trip, and stop there. And collect it from every adult who steps aboard, since the release only protects you against people who signed something. Anyone building this from scratch will get more from reading the introduction to these documents first than from copying a competitor's page.

What the case says about running the operation

Strip away the contract law and the underlying complaint was about water stations and medical cover at an event on a hot day. Those are operational decisions, and they are the kind a guide makes constantly: how much water is aboard, what is in the first aid kit, whether anybody on the boat can use it, how long it takes to get help from the far end of the run, whether a guest who has stopped sweating gets noticed. A release that holds up is worth having and it is not a substitute for any of that. Keep a short trip log with the weather, the briefing and anything unusual about a guest's condition, since that record is what tells the story if the paperwork is ever tested. Cancellations and weather calls belong in the same habit and the contingency notes lay out a routine for them.

Getting ready for the season

Print a fresh release for every trip on the calendar. Check that your entity name and your trading name both appear. Ask a North Dakota lawyer whether anything in your form reaches past ordinary negligence, since the statute will limit it anyway and clarity is worth more here than coverage. Talk to any landowner whose ground you cross about the commercial purpose definition, because it may put them outside a shield they assume they have. Then look at coverage, since the claims a release cannot touch are the ones that end businesses, and how these policies are structured is explained in the captain insurance breakdown. Federal guidance on business insurance is a fair starting point for a first purchase. Confirm licensing and permit requirements with the agency that issues them before you take money. Water specific detail for the state sits in the North Dakota guide hub, and the recurring drafting failures worth avoiding are gathered in the review of waivers that fell over.