01 Overview
Most rafting trip reports read like a social media post: we put in here, we took out there, the water was big, we had a blast. That is fine for a scrapbook, but it is nearly useless to the next paddler trying to decide whether a river is within their ability. A useful trip report is a safety document. It tells a stranger what the river was actually like at a specific flow, what went wrong, and what they should watch for. It does not exaggerate, and it does not omit the parts that were scary or confusing.
The core problem is that river conditions change constantly. A rapid that was a straightforward wave train at one level can become a powerful hydraulic at another. A channel that was clear in June can be plugged with a strainer in July. Because of that, a trip report is never a guarantee. It is a snapshot. The best reports make that clear. They give enough detail that a reader can compare their own skills and equipment to the writer’s, and then make a conservative decision. If a report encourages someone to paddle beyond their ability, it has failed. The goal is to reduce uncertainty, not to replace judgment.
This article explains how to write a report that actually helps. It covers what to record before you launch, what to note during the run, how to describe hazards without drama, and how to present safety and rescue information so it is useful rather than intimidating. It also explains what not to do: no invented statistics, no named sources, no claims that a line is safe for everyone. The river does not care about your confidence. A good report respects that.
02 Reading the river before you go
Before you can write a useful report, you need to gather the kind of information that matters. Start with the class. River difficulty is usually described on a Class I to V scale, but that rating is only meaningful when tied to a flow. A Class III at low water can feel like a Class II, and the same rapid at high water can be a Class IV or worse. So record the class you actually encountered, not just the guidebook rating. If you are unsure, say so. It is better to write “we judged this to be Class III at this level” than to pretend certainty.
Next, record the flow. If there is a gauge, write down the reading and the unit. If there is no gauge, describe visual cues: how much of a rock is exposed, where the eddy lines form, whether the water is clear or muddy, and how fast it is moving. Also note the water temperature and air temperature. Cold water is a hazard even on a sunny day, and it changes what gear is necessary. Note the weather forecast and whether it changed during the trip. Rain can raise a river quickly, and a report that ignores that is incomplete.
Finally, record the logistics. Where is the put-in and take-out? How many miles did you actually run? How long did it take? Were there any portages, mandatory scouts, or difficult access points? These details help others plan, but they also help them avoid surprises. If you had to walk around a rapid, say why. If a take-out was hard to find, describe it. The more concrete you are, the more useful the report becomes.
03 Gear that actually matters
A trip report should describe the safety gear that was used and why. Do not list brand names. Instead, describe function. Everyone on the water should wear a properly fitted personal flotation device and a helmet appropriate for the river. A throw bag is essential, and at least one person in the group should carry a whistle and a knife. A first-aid kit, a repair kit, and a way to communicate or signal for help are also important. In remote sections, a communication device may be the only way to call for rescue. Spare paddles and a way to warm a hypothermic paddler are worth mentioning if conditions were cold.
Beyond the basics, the report should note what actually mattered. Did you use the throw bag? Did someone swim? Did a helmet take a hit? If so, describe what happened without dramatizing it. That information helps readers understand the consequences of a mistake. If you carried gear that you never used, that is fine, but say so. It helps others decide what to bring. If you wished you had brought something, say that too. Honest gear notes are more valuable than a packing list copied from a website.
Also describe the craft and the group. Were you in a raft, a cataraft, a kayak, or a canoe? How many people were in the group, and what was the range of experience? A report from a group of expert kayakers running a Class V section is not directly applicable to a family in a raft on a Class II. Stating the group’s skill level helps readers calibrate. If the group included beginners, note how they handled the rapids. If the group had a guide, say so. The goal is not to brag but to give context.
04 The run itself
The heart of a useful trip report is a clear, sequential description of the run. Start with the put-in. Describe the access, the current, and any immediate hazards. Then move downstream, rapid by rapid or section by section. For each significant rapid, give the class at the flow you observed, the line you took, and any alternative lines you saw. If you scouted, say where and why. If you portaged, describe the portage. If a rapid was straightforward, say that too. Not every rapid needs a paragraph, but the ones that could surprise someone do.
Use plain language. Instead of “it was gnarly,” describe what the water was doing. Was it a wave train, a hole, a ledge, a sieve, a constriction? Were there eddies above or below? Was the current pushing into a wall or undercut? Was there a hydraulic that held a swimmer? These details let a reader visualize the rapid and compare it to their own experience. Avoid words that only convey emotion. “Terrifying” tells us about you, not the river. “A large keeper hole with a recirculating backwash on river left” tells us something we can use.
Also describe the pace and the overall character of the run. Was it continuous whitewater or pool-drop? Were there long flat sections? Was the wind a factor? Did the water level change during the day? If you had to make a decision to continue or turn back, explain why. If you encountered other groups, note how they were doing, but do not name them. If you saw wildlife or scenery, you can mention it briefly, but keep the focus on the river and safety. The best reports read like a set of instructions for the next group, not a story for your friends.
05 Hazards and how to handle them
Every trip report should prominently describe the hazards that were present and how the group managed them. The most common river hazards are strainers, undercut rocks, and hydraulics. A strainer is any obstacle that lets water through but traps people or boats, such as a fallen tree or a fence. They are often invisible from upstream and can be deadly. If you saw one, describe its location and how you avoided it. If you had a close call, say so. That is not embarrassing; it is useful. Undercut rocks are another serious hazard. They can trap a swimmer underwater. Note any rocks that appeared undercut at the flow you ran. Hydraulics, or keeper holes, can recirculate a person or boat. Describe the size and location of any significant holes, and whether they were retentive.
Other hazards include cold water, foot entrapment, and high water. Cold water can cause shock and rapid loss of function, even for strong swimmers. If the water was cold, say so and describe what protective clothing was worn. Foot entrapment happens when a swimmer tries to stand in moving water and gets a foot stuck. The safest response is to float on your back with your feet downstream until you reach calm water or an eddy. If you saw anyone try to stand, note it as a caution. High water changes everything. If the flow was high, describe how it affected the rapids and the group’s decisions. If you turned around because of high water, that is a valuable report.
Finally, describe any rescue or near-miss. If someone swam, where did they swim? How did they get out? Was a throw bag used? Did anyone go through a hydraulic? How long were they under? These details help others understand the consequences of a mistake. Do not exaggerate, and do not minimize. Just report what happened. If you are not sure, say you are not sure. The goal is to help the next group avoid the same situation.
06 Safety and rescue basics
A trip report should include a clear safety and rescue section, but it must not encourage paddling beyond ability. Start by stating the group’s training and experience. Did anyone have swiftwater rescue training? Was there a designated safety boater? Did the group have a plan for a swim? If not, say so. A report that omits this information is incomplete. Then describe the safety equipment that was carried and how it was rigged. For example, was the throw bag accessible from the captain’s seat? Was there a flip line or a rescue harness? These details matter.
Next, describe any rescue that occurred. If someone swam, explain how the group responded. Did they use a throw bag, a live bait rescue, or a boat-based rescue? Did they set up a safety eddy below the rapid? If the swimmer self-rescued, describe how. If the group had to perform a boat flip or a tethered rescue, explain the steps without giving instructions that could be misapplied. The purpose is to show what worked and what did not, not to teach a course. Always emphasize that rescue techniques require practice and that improvised rescues can be dangerous. Never suggest that a particular technique is safe for everyone.
Finally, include a caution about the limits of your report. River conditions change. A rapid that was clear can become a strainer after a storm. A flow that was moderate can become high overnight. Skills matter more than any report. If you are not sure you can handle a rapid, do not run it. Scout, portage, or choose a different river. A trip report is not a permission slip. It is a tool for planning, and it should always be paired with local knowledge, current conditions, and a conservative assessment of your own ability. If your report encourages someone to take on more than they can handle, you have written the wrong kind of report.
07 Frequently asked questions
How much detail is enough? A useful report gives enough detail that a stranger can picture the river at the flow you ran. That means class, flow, distance, hazards, and the lines you took. It does not need to be a novel, but it should not be a tweet. If you are unsure whether to include something, ask yourself: would this help someone decide whether to run this river? If yes, include it. If it is only about your personal experience, leave it out or keep it brief.
Should I include my mistakes? Yes. Mistakes are often the most valuable part of a report. If you flipped, swam, missed a line, or had a close call, describe it. Do not frame it as a failure. Frame it as information. Other paddlers can learn from what went wrong. The same goes for decisions to portage or turn around. Those are not signs of weakness; they are signs of good judgment. A report that only describes success is not trustworthy.
What about named sources or statistics? Do not invent them. If you want to cite a gauge reading, that is fine because it is a measurement. But do not make up a statistic like “most accidents happen here” unless you have a real source. Do not quote a named expert unless you actually spoke to them and have permission. Generic statements like “many paddlers consider this rapid dangerous” are acceptable if they are clearly general. The safest approach is to stick to what you observed and what you know.
How do I write about a river I have not run? You do not. A trip report should be based on firsthand experience. If you are compiling information from other sources, call it a guide, not a trip report. And always include a disclaimer that conditions change and that readers should verify current conditions and assess their own skills. The river is not a static course. It is a living system, and your report is only one snapshot in time.