Here’s a realistic way forward that might actually have a shot at clearing the walls of red tape with NOAA and the co-managers, instead of just hoping they’ll look the other way. It’s not pure volunteer self-reporting (which, let’s be honest, they’d treat as anecdotal BS), but a “hybrid angler-assisted + independent verification pilot” that builds on what WDFW is already rolling out with the app while adding the kind of defensible checks the feds and tribes demand.
Make eCRC reporting through the MyWDFW app a straight-up license condition for the Skagit/Sauk CnR steelhead fishery. Every angler logs every encounter—fish landed, break-offs, even the skunked days—with a quick mandatory checkbox to cut down on the usual under-reporting. The app already works offline, so the dead zones on the Sauk aren’t a deal-breaker; data syncs when you hit coverage. That gives you a near-census from the folks actually fishing, which is a hell of a lot better than traditional estimates on a small, dedicated fishery like this.
But nobody at NOAA is going to sign off on the “honor system” alone. So we add a low-cost verification layer: 1–2 WDFW-trained and certified volunteer creel clerks doing stratified random intercepts at the main access points and launches. Fishing clubs and TU /Steelhead Unlimited chapters are who I’d tap.
Focus on weekends and peak days, aiming to check 20–30% of the effort. They do quick on-bank interviews to validate a subsample of the app reports—nothing fancy, just enough to statistically backstop the self-reported numbers. Throw in a few trail cameras at key gravel bars for effort counts. WDFW already uses volunteers for scale sampling and tagged-fish stuff on the OPthis is just an extension of that model. It keeps costs way down while giving the data the professional-grade credibility the tribes expect from their own test fisheries.
For escapement and abundance, stick with the existing spawning ground surveys (which already lean on volunteers in places) and layer in targeted WDFW drone flights over the open gravel bars. Not hobbyist buzz jobs—official agency flights with the proper FAA permits and wildlife protocols to avoid screwing with eagle nests. The Wild & Scenic designation doesn’t ban permitted state monitoring; it just means you can’t treat it like your backyard toy. WDFW is already flying drones for other work in the Skagit Wildlife Area, so the infrastructure exists.
In-season management stays conservative: set encounter triggers with a 10–15% buffer below the RMP limit, use weekly uploads plus the clerk data to project forward, and close with 48-hour notice if needed. The fishery’s small and the run timing is predictable enough that real-time pinging isn’t required. Lag from dead zones gets covered by the buffer.
This setup doesn’t need a total rewrite of the FMEP up front. Propose it as a one- or two-year pilot amendment to the existing Skagit RMP—NOAA has green-lit similar adaptive management tests when the state brings solid validation data. Run the app census side-by-side with the clerk subsample in Year 1, show the numbers match within acceptable error, and you’ve got the evidence to make it permanent. Tribes get invited to the table early at North of Falcon to help shape it, so it doesn’t look like the state is trying to cheap out on accountability.
Cost-wise, you’re probably looking at $50–80k a year—mostly for a couple part-time seasonal clerks, some camera upkeep, and minimal drone support. That’s a fraction of what full manned creel plus aircraft used to run, especially with the budget reality we’re all living under.
I’m not saying this is a slam dunk or that it magically erases the red tape. The feds and co-managers are still going to be cautious as hell about ESA take. But it’s a hell of a lot more realistic than hoping they’ll accept pure self-reporting, and it actually uses the tools WDFW already has in play (the app rollout, existing volunteer programs, drone capability). If the forum crowd wants to push this, draft up a clean one-pager with this outline, get some co-signs from the local TU chapter and the regulars here, and get it in front of the Steelhead team and the Commission. Offer to help coordinate the volunteer side—that shows real buy-in instead of just another complaint thread.
I’m certainly no expert, but I think this hybrid approach at least gives us something to take to the table that might not get laughed out of the room.
We’d still need to overcome things like app adoption and honesty, sampling bias, repeat encounters with the same fish, and mortality vs encounter rate.
