Are Liability Waivers Enforceable in Ohio?

A woman rented a horse and tack from a livery stable in Vinton County, went out on the trail and was thrown. She sued over the choice of horse, the equipment she was given and the trail she was sent down. The form she had signed at the counter never used the word negligence, never said plainly who was being released, and was described by the Court of Appeals as poorly drafted. It worked anyway for the negligence claims. What it could not touch was her allegation of willful and wanton misconduct, and that claim went back for trial even though she had put forward no evidence to support it. Ohio therefore hands operators a reasonably forgiving standard on wording and a hard ceiling on what any wording can achieve. Where the other states land is mapped on the liability and waivers hub. One appellate decision and one statute, read for people who run trips rather than for lawyers.

Are liability waivers enforceable in Ohio?

Yes, and the bar for wording is lower than most states set it.

The decision is Swartzentruber v. Wee-K Corp., 117 Ohio App.3d 420 (4th Dist. 1997). It states the general position cleanly. Exculpatory contracts that clearly and unequivocally relieve a party from the results of its own negligence are generally not contrary to public policy in Ohio, and it is settled that a participant in a recreational activity is free to contract with the proprietor of that activity so as to relieve the proprietor of responsibility for injuries caused by the proprietor's negligence. Then comes the limit. A proprietor may not contract away responsibility for willful or wanton misconduct, and no release, however well written, changes that.

Two Rivers Fishing Co, WY

The word negligence is not required, but use it anyway

The plaintiff asked the court to hold the release unenforceable purely because the word negligence never appeared. The court declined, and the passage is worth an operator's attention. The better practice, it said, would certainly be to expressly state the word somewhere in the exculpatory provision, but the absence of that term does not automatically render the provision fatally flawed. The test it applied instead asks whether it is clear from the general terms of the entire contract, considered in light of what an ordinarily prudent and knowledgeable party of the same class would understand, that the proprietor is to be relieved from liability for its own negligence. That is a forgiving standard compared with the bright line rule some states apply, and it is still no reason to leave the word out. Put it in and the argument disappears.

Why the badly written form survived

The court called this a close case, which tells you not to rely on the outcome. What saved the document was one sentence in which the rider released any and all claims, actions and causes of action of every kind and nature arising out of any and all personal injuries. The court held it was difficult to construe that as anything other than a release of liability for negligence. It then dealt with the missing party name by reading the document as a whole: the stable's name appeared twice elsewhere, and the injuries released were expressly those resulting from the rental of the horse and equipment, which the opening line said were rented from that stable. Courts should refrain from reading ambiguity into an agreement where none exists, and the ordinary meaning of common words governs.

The contrast that shows where the line sits

The plaintiff pointed at another Ohio decision in which a livery stable's contract was found so general in nature as to be meaningless and unenforceable. The court distinguished it on two grounds that translate directly into drafting advice. That other agreement leaned heavily on indemnity language, and it never expressly said the stable was being released from personal injury claims. So the difference between an enforceable form and a meaningless one came down to whether the document actually contained the word release attached to personal injury claims, rather than a promise to indemnify or hold harmless. Those are different concepts, they do different work, and a form built only out of indemnity language may not release anything at all.

The willful and wanton claim is the one that always survives

Here is the part every Ohio operator should sit with. The plaintiff had pleaded that the stable's conduct was willful, wanton and malicious. The court held that even a valid and enforceable exculpatory contract would not relieve the operator from liability for that sort of conduct, so summary judgment on that claim was error and it was sent back. A footnote makes it sharper still. She produced no evidence at all to support the willful and wanton allegation, and it did not matter, because the stable's motion rested entirely on the release and never argued that the evidence was missing. Read that as a practical warning about litigation rather than about drafting. A release moves the fight, it does not end it, and a claim framed as willful and wanton gets past the document by definition.

What willful and wanton looks like in a guide business

Since that is the route around every Ohio release, it is worth knowing what tends to be alleged. Sending a customer out on equipment somebody has already reported as faulty. Running water you know is beyond the group in front of you. Ignoring a weather warning because the trip was already paid for. Putting a beginner somewhere you would not put yourself. Continuing to use gear that failed last month because it held up afterwards. None of those require malice. They require a decision made in the face of a known problem, which is why the written record of what you knew and when you knew it is worth more here than another paragraph of release language. Neighbouring operators will recognise the same ceiling described in the Kentucky piece. The recurring paperwork failures behind these disputes are gathered in the review of releases that fell over.

Rental operations carry the extra exposure

The case was about renting rather than guiding, and the difference matters. The claims were that the operator picked the wrong horse for the rider, supplied the wrong equipment and pointed her down the wrong trail. Substitute a kayak, a set of waders, a loaner rod and a stretch of river and the shape is identical. When you hand a customer equipment and send them off without you, three things become critical: matching the gear and the route to the person in front of you, recording what you handed over, and keeping a service history for each item. An operation that rents should also assume its customers are less experienced than they claim, because the counter is where people overstate their ability and there is nobody aboard later to correct it.

Ordinarily prudent and knowledgeable party of the same class

The test the court used contains a phrase worth unpacking, because it cuts in a direction operators do not expect. The document is read as an ordinarily prudent and knowledgeable party of the same class would understand it. The relevant class is your customer, not you. Somebody who has rented a horse or booked a trip once in their life is not reading your paragraph the way a proprietor reads it, and Ohio measures the document against their understanding. That is why a form written in plain sentences about the actual activity beats one assembled from legal phrases. It also means that if your typical customer is a complete beginner, the standard is applied through the eyes of a complete beginner.

Release, indemnify and hold harmless are three different promises

Since the difference between the enforceable form and the meaningless one turned on this, it is worth being precise. A release says the customer gives up their own claim against you. An indemnity says that if somebody else sues you over something connected to the customer, the customer will cover your loss. A hold harmless clause is usually a version of the second. Many booking forms contain only the second and third because they were copied from commercial contracts where those clauses belong, and their author never noticed that the document says nothing about the customer's own claim. If your form uses the words indemnify and hold harmless but never uses the word release attached to the customer's personal injury claims, you may be holding a document that does not do the job you think it does. That is a five minute check and it is the highest value thing in this article. The same three way distinction decides cases in the Indiana analysis too.

A close case is not a green light

It would be easy to read this decision as permission to be casual, and that reading has cost operators money in other states. The court reached its conclusion with visible reluctance, called the document poorly drafted, described the question as close, and observed that it wondered whether it might have decided the other Ohio livery stable case differently. A form that survives on those terms is a form that got lucky with a panel. The margin between the enforceable release and the meaningless one in the two Ohio cases is a couple of drafting choices, and both operators paid for the litigation either way. The point of writing a clear document is not to win the appeal, it is to make the argument short enough that nobody has one.

Sirens Call, AK

Assumption of risk is a separate defence

The stable pleaded two things: that the rider had assumed the risk of injury and that the release barred her claim. Those are different arguments and they fail in different ways, which is a reason to build for both. The release depends on the wording of a document. Assumption of risk depends on what the customer knew and accepted about the activity, which is supported by the hazard description you gave them, the briefing you delivered and the experience they told you they had. An operator who writes the release well and describes the risks poorly has half a defence. Write the hazard list as though the release might fail, and write the release as though the hazard list might not be enough, because in Ohio both propositions get tested in the same motion.

What to do when a customer overstates their ability

The claims in this case included the choice of animal, which is really a claim about matching the activity to the person. Guides face the identical judgment constantly and usually make it on the basis of what the customer said when they booked. Two habits protect that decision. Ask the experience question in writing so the answer is recorded in the customer's own words rather than in your memory, and note it when your own observation on the day differs from what they told you, along with what you did about it. Moving somebody to easier water, putting a first timer in the front of the boat, deciding not to wade a particular run: these are the decisions that answer a willful and wanton allegation later, and they are worthless if nobody wrote them down.

The recreational user statute, and who it protects

Ohio's landowner provision at R.C. 1533.181 is short and worth knowing. An owner, lessee or occupant of premises owes no duty to a recreational user to keep the premises safe for entry or use, extends no assurance through the act of giving permission that the premises are safe, and assumes no responsibility for injury to person or property caused by any act of a recreational user. It then adds a clarification most states omit, stating that the protection applies to privately owned nonresidential premises whether or not those premises are kept open for public use and whether or not the owner denies entry to certain individuals. That last part is unusually generous to landowners, and it is worth mentioning to anyone whose ground you cross, since many assume that restricting access costs them the protection.

Where the statute stops being about you

As everywhere else in this series, the landowner shield is aimed at people who let others onto their ground, not at businesses selling the activity. Read it as a description of your access relationships rather than as a defence for your operation. The practical questions it raises are about the arrangement with the person who owns the launch, the field you park in, the bank you walk down. Get those arrangements in writing, note whether anything is being paid, and make sure the landowner understands their own position rather than assuming it. That conversation costs a coffee and it protects access, which is worth more to most guide businesses than any single season's bookings.

Drafting an Ohio form

Five moves, all of them cheap. Use the word negligence, since Ohio does not demand it but nothing is gained by omitting it. Use the word release attached to personal injury claims, because that is the distinction that separated the enforceable form from the meaningless one. Name the released parties explicitly rather than relying on a court to infer them, which it did here but might not next time. Say nothing that purports to cover willful or wanton conduct, since that part fails and the rest of the document does not need it. And write the whole thing in sentences your least experienced customer could repeat back, because that is the reader the test uses. A first document is easier to build from the introduction to these forms than from a competitor's page.

How Ohio compares with its neighbours

The wording standard here is noticeably softer than in states that demand specific terms, and noticeably firmer than in states that will read any sweeping clause down to whatever the law permits. Operators working across a border should notice that the same document can behave very differently a few miles apart: the analysis in the Michigan piece turns on the breadth of the words themselves, while the approach described in the Pennsylvania piece asks a different question again. The practical answer for a multi state operation is a form drafted to satisfy the fussiest jurisdiction you work in, since nothing is lost by being clearer than a particular state requires.

Records are the defence against the claim the release cannot stop

Because willful and wanton conduct is outside every Ohio release, the operating record is what answers that allegation. Keep an equipment log with dates and a named person responsible. Write down when a customer reports a problem and what was done. Note the conditions and the decision when you cancel or change a trip, and note it when you do not cancel, because the reasoning matters as much as the outcome. Record the briefing. None of this is complicated and all of it is the evidence that separates a defensible decision from one that looks reckless in hindsight. Weather and cancellation habits in particular are laid out in the contingency planning notes.

Getting ready for the season

Pull your form and check three things: that it says release, that it says negligence, and that it names the parties being released. Then look at the operation with the willful and wanton standard in mind, because that is the exposure the paperwork does not reach, and it usually lives in a maintenance list nobody has cleared. If you rent equipment, build the service history now rather than after somebody asks for it. Talk to your landowners about the recreational user provision so they know where they stand. Confirm current licensing and permit requirements with the issuing agency before taking bookings. Coverage is what responds to the claims a release cannot stop, and how those policies fit together is set out in the captain insurance breakdown, with federal guidance on business insurance as a reasonable first orientation. State specific water and season detail is collected in the Ohio guide hub.