Are Liability Waivers Enforceable in Rhode Island?

Newport's Cliff Walk runs eighteen thousand feet along the top of the Atlantic shoreline and draws hundreds of thousands of visitors a year. After a young man was catastrophically injured when the ground gave way, the city argued it owed him nothing, because Rhode Island's recreational use statute treats everyone using land opened for recreation as a trespasser. The Supreme Court refused to let the city hide behind that. What defeated the immunity was not a document but a pattern: the city knew the walkway was unstable, knew people had already been hurt, and did not guard or warn. That reasoning is the most important thing a Rhode Island guide can take from the state's law, because it describes exactly how a known problem turns into liability nothing on paper will fix. The wider survey lives on the liability and waivers hub. A working summary of one Supreme Court decision and one statute. Not advice, and not a substitute for a lawyer looking at your operation.

Are liability waivers enforceable in Rhode Island?

Start from the statute, because that is where the state has actually spoken.

Rhode Island's law about recreational injuries is built around its recreational use statute rather than around a body of decisions on signed releases, and no case read for this page decides the enforceability of a pre-injury release for a paying guide's customer. That is a real gap and worth saying plainly rather than papering over. What the state does tell you is more useful than it sounds. It tells you when a landowner's immunity disappears, it tells you that taking money is one of the two things that ends it, and it tells you, through Berman v. Sitrin, 991 A.2d 1038 (R.I. 2010), exactly what kind of knowledge converts an immunity into a duty.

Catch A Trophy, TX

The statute, and the baseline it sets

The General Assembly enacted the recreational use statute in 1978 to encourage private landowners to make their land free and open to the public. An owner who directly or indirectly invites or permits anyone to use the property for recreational purposes without charge does not thereby extend any assurance that the premises are safe, does not confer on that person the legal status of an invitee or licensee to whom a duty of care is owed, and does not assume responsibility for injury caused by an act or omission of that person. The court described the legislative intent as treating those who use private property for recreation as though they were trespassers, so that landowners owe no duty other than to refrain from willful or wanton conduct. In 1996 the definition of owners was expanded to include the state and its municipalities.

Where the immunity stops

The limits are set out in R.I. Gen. Laws section 32-6-5, which says nothing in the chapter limits in any way any liability that would otherwise exist for the willful or malicious failure to guard or warn against a dangerous condition, use, structure or activity after discovering the user's peril, or for any injury suffered where the owner of land charges the people who enter for recreational use. A carve out follows for land leased to the state, where consideration received for the lease is not treated as a charge. A second subsection deals with rights of way designated by the coastal resources management council and with public access stipulated as a permit condition, giving those landowners limited liability under the chapter.

What willful or malicious actually means here

This is the part with the most practical value, because the court defined the words rather than gesturing at them. Willful means voluntary and intentional. Malicious means substantially certain to cause injury. To guard means to protect from harm or danger, especially by careful watching, and to take precautions. A warning is the pointing out of a danger, especially to someone who would not otherwise be aware of it. Then the court adopted a three part description drawn from Georgia's near identical statute: a willful failure to guard or warn requires actual knowledge that a condition exists involving an unreasonable risk of death or serious bodily harm, that the condition is not apparent to those using the property, and that having this knowledge the owner chooses not to guard or warn, in disregard of the possible consequences.

Read those three elements as a checklist for your own water

Every guide has candidates. A submerged obstruction that appears at certain flows. A dock plank that moves. A wading access with an unmarked drop. A launch where the current sets hard against a piling. Ask the three questions in order. Do you actually know about it? Would a customer see it for themselves, or is it hidden from someone who has not been there before? And knowing about it, have you either guarded against it or pointed it out? Answering yes to the first two and no to the third is the exact configuration the statute strips protection from, and no signature on a form changes the analysis, because this is about duty rather than about contract.

The number of injuries did the work

The court was explicit about what tipped the balance, saying it was the number of serious injuries flowing from a known risk that brought it to its conclusion. It also contrasted decisions from other states where the landowner won because there was no knowledge: a Georgia park where officials were unaware of any other accidents in the area, and a federal case where the plaintiffs pointed to not an iota of evidence that the landowner knew a barricade was damaged. Knowledge is the hinge, and repetition is how knowledge gets proved. That is the argument for keeping a record of incidents and near misses, because the difference between an unlucky first occurrence and a known danger is a history somebody can produce.

Charging is the other exit, and it is the one guides walk through

The statutory shield is for people who open land without charge. A guide business takes money. That is the second exception in plain terms, and it means an operator should not think of the recreational use statute as protecting their operation. It also means the statute is mostly relevant to you as a description of the position of whoever owns the ground you cross. If they take nothing, they are inside the shield. If they take a fee from you or your guests for access, they may not be, and that is a conversation worth having before the arrangement starts rather than after an incident.

What counts as a charge is narrower than you would guess

The court noted an earlier decision holding that a fee charged to park a car did not amount to a fee for admission, so the state could still invoke the statute. The statute itself excludes consideration received under a lease to the state or a subdivision from the meaning of charge. Those details matter when an access arrangement is informal. A landowner who lets you park in exchange for a case of something at Christmas is in a different position from one who invoices you per head, and neither of them has read the statute. Getting the arrangement written down, with the money question answered explicitly, protects the relationship as much as anything else.

Assuming control has consequences

One thread in the case deserves separate attention because it applies to operators who take over a piece of ground. The city did not own the Cliff Walk, which runs as a public easement over private land. It had, however, assumed authority and exercised control over it by regulation and maintenance, enacted ordinances restricting access and limiting use to foot traffic, and taken millions in public funding for it, declaring its authority in order to qualify. The court weighed all of that. The transferable lesson is that control and responsibility travel together. An operator who maintains a launch, builds steps down a bank, clears a trail or posts rules about how a piece of ground is used has assumed something, whatever the deed says.

Absurd results and nugatory exceptions

The reasoning included two arguments worth knowing because they recur whenever somebody stretches an immunity too far. The court said it will not construe a statute to reach an absurd result, and that reading the exception the way the city urged would render the exception nugatory, meaning it would have no work left to do. The city's position was that it could only be liable if an employee happened to be present, saw a visitor approaching the unstable edge, and failed to warn them. That reading would have made the exception practically unusable, and courts resist that. It is a useful reminder that immunities have limits and that arguing for the widest possible version tends to produce the narrowest possible result.

Clearwater Inshore, FL

The other defendant won, and the reason matters

Two parties were sued and only one lost the immunity argument. The preservation society that owned some of the land underneath the path was granted summary judgment, and the Supreme Court affirmed that outcome on a different basis from the trial court, concluding that with or without the statute the society owed no duty to people using the path. The distinction is control. The society held title. The city ran the thing: it regulated access, maintained the walkway, restricted it to foot traffic, and pursued public money for it. When a claim arrives, the question is not only whose name is on the deed but who was actually operating the place. For guides, that is a reason to be clear about which business is responsible for which piece of the day, particularly where a lodge, a landowner and an operator all have a hand in it.

Not apparent to those using the property

The middle element of the three part test is the one operators can most easily act on, and it is worth thinking about separately. A danger that is obvious to any adult standing in front of it sits differently from one that is invisible until it hurts somebody. Cold water is apparent. A shelf that drops away two feet from the bank is not. A fast chute is apparent to anyone watching. A submerged cable is not. That distinction should drive what you point out. Spending your briefing on hazards everybody can see, while saying nothing about the one thing they cannot, gets the emphasis exactly backwards, and the statute's own definition of a warning, pointing out a danger to one who would not otherwise be aware of it, tells you which category deserves the words.

Chooses not to guard or warn, in disregard of the consequences

The third element is about the decision rather than the danger, and it is where most defensible operations distinguish themselves. Guarding does not require eliminating the hazard. It means taking precautions, watching carefully, doing something. Rerouting around a spot at certain flows, roping off a section of dock, keeping guests off a bank until the guide is in position, adding a step where one is needed: all of those are guarding. So the honest question is not whether your water contains dangers, because all water does. It is whether, knowing about a specific one, you did anything at all. An operator who can point to a response, even an imperfect one, is in a different position from one who filed the knowledge and moved on. The same distinction decides cases under the standard described in the Maine analysis.

Public access conditions and the coastal provision

Rhode Island's statute contains a subsection that will matter to some coastal operators and their landowners. Where the coastal resources management council designates a right of way as part of its designation process, or stipulates public access as a condition of granting a permit, the landowner automatically has limited liability under the chapter, subject to the same exceptions. In a state with as much shoreline access litigation as this one, that is a provision worth knowing about when you are negotiating a route to the water. It also underlines the general shape of the scheme: the legislature has been willing to extend the shield to encourage access, while keeping the two exits open. Neither of those exits closes because somebody signed something at the truck. Operators working the same coastline further south should read the New Hampshire piece alongside this one.

Where that leaves a release in this state

Given the gap in the case law, the practical position is to write a document that does its work regardless of how the enforceability question is eventually answered. Describe the activity in specific terms. Describe the risks, including the serious ones, and especially the ones a first time visitor would not see for themselves, since pointing out a danger to somebody who would not otherwise be aware of it is exactly what the statute means by a warning. Record that the description was given and received. Include an ordinary negligence release, drafted clearly and confined to that, because there is no reason to reach further and every reason not to. Anyone starting from nothing should work through the introduction to these documents before drafting a word.

The warning half of the document is doing double duty

This is the point to carry away. In a state where the immunity turns on whether a known danger was guarded against or pointed out, the hazard description in your paperwork is not decoration around the release. It is evidence that you performed the second half of an obligation the statute describes in terms. Write it accordingly, in the language you would use standing on the bank, and update it when the water changes. A hazard list written three seasons ago for a different stretch of river is worse than none at all, because it shows a practice that stopped being maintained.

How Rhode Island compares

The knowledge threshold here is stricter for a claimant than the ordinary negligence standard applied to most guide operations, but the exits are narrow rather than nonexistent, and the charge exception removes the statute from your side of the ledger entirely. Neighbouring states arrive at similar places by different routes: the analysis in the Connecticut piece turns on public policy in a snow tubing setting, while the approach in the Massachusetts piece asks whether the activity was voluntary and nonessential. An operator working across those lines should assume the documents behave differently in each.

Before the season starts

Walk your water and write down every hazard you know about that a first time guest would not see. Decide for each one whether you are guarding against it, warning about it, or both, and record the decision. Start an incident and near miss log if you do not have one, because the case turned on a pattern of injuries and patterns only exist in writing. Ask every landowner whose ground you use whether they take anything for access, and put the arrangement on paper. Then look at coverage, since a claim that clears the knowledge threshold is the kind that ends businesses, and the way these policies are built is explained in the captain insurance breakdown, with the federal summary of business insurance as a first orientation. Check the current licensing and permit position with the issuing agency well before you take bookings. Local detail for these waters is collected in the Rhode Island guide hub, and the piece on releases that failed covers the administrative errors that undo good paperwork. Weather calls belong in the same file, and the contingency routine is written to be logged.