Paddle Greene gets better when local paddlers share what they actually saw. A good update can fix a stale detail, flag a change, or move a launch up our field review queue. Here is what makes an update genuinely useful, and what happens to it after you send it.
The details that help most
You do not need to write a full report. A few specific observations beat a long general one:
- Parking: where you actually parked, how full it was, and what time of day
- Launch condition: the surface, the carry distance, and how easy it was to get in and out
- Restrooms and amenities: what was open, and whether anything is seasonal
- Water conditions you saw: wind, current, weeds, debris, or boat traffic
- Crowding: how busy it was, and the best time of day to avoid it
- Access changes: closures, construction, new fees, or signage you noticed
- A photo or two: the launch, the parking area, and the shoreline tell us a lot
Dates matter. "Busy by 10 am on the Saturday of July 4th weekend" is far more useful than "it gets crowded."
What we do with it
When an update comes in, we note it and, where it adds something current, we fold it into the guide and label it as a community update. That is a real status in our system, and it is kept separate from a Paddle Greene field visit on purpose. We do not present a reader update as our own firsthand review. You can see how the labels work on the field review status page.
If your note points to something that needs eyes on the ground, it helps us schedule a visit and prioritize the field review queue.
One thing we will not do
We will not publish sensitive access details that could harm a fragile launch or a private put-in. If something is informal or easily damaged, tell us, and we will handle it carefully rather than mapping it for everyone.
Ready to send one
The submit an update page has the current way to reach us. If you are heading out and want a refresher on conditions first, Before You Paddle covers what to check.