FIELD CHECKLIST · BEFORE THE RAMP
Twenty minutes before the ramp.
The thing that ends a day early is almost never in the tackle box. It’s a locked gate, or a gauge nobody looked at. Work top to bottom: open the trip in Field Ops, make sure the water still works, figure out what the fish are likely doing, and then build one presentation. Only reach for the other tools if a question’s still open after that.
1 · Can you fish it safely and legally?
Check the current regulation, access status, weather, wind, water, hazards and return route for the water you’re going to and the date you’re going. If one of those has taken away the margin, change the plan now, while changing it is free.
- Rules, seasons, limits, closures and access checked against the controlling source.
- Wind and waves compared with the boat, bank or wading plan.
- Temperature, current, visibility, fire, ice, smoke or other hazards considered where they apply.
- Ramp, gate, road, parking, trail and return route still usable.
- A real turnaround point and a backup option chosen.
A forecast isn’t a return plan. If wind is supposed to build, decide before you launch what speed or what wave height sends you back. If a river is rising, know which gauge or release notice matters and what number makes a crossing or a shoreline a bad idea. If the access depends on a gate, know when it locks. The check isn’t finished until it ends in a number you’ll actually honor.
Check the named water in Field Sense → · Read Conditions & Access →
2 · Does the water still match the plan?
An open reservoir under working wind is a different job than a protected cove or a tight river seam. Look at water type, structure, pressure, recent conditions and access before you decide the fish are the problem.
- Primary water type and structure still match the day.
- Wind, flow, level, clarity and recent weather haven’t quietly redrawn the useful water.
- Pressure and conservation limits are accounted for.
- The platform—bank, boat, kayak, wade, pier or ice—can actually reach the water you intend to fish.
Name one or two physical clues you expect to find when you get there. If wind is supposed to make one bank useful, what’s the tell—surface drift, stained water, bait flicking, foam, grass laying over? If the whole plan rides on a stable weed edge or one depth band, make sure the current water level hasn’t put it out of reach.
Don’t defend a destination because you already drove to it. Water gets to change after the research is finished.
3 · What’s the fish probably doing here?
Work out what the fish needs before you start judging tackle. Species, water type, season, temperature, holding water and what it’s likely eating should narrow down the kind of presentation first.
- You know which species you’re after, because it’s documented there or because you picked it on purpose.
- The holding water fits this kind of water and today’s conditions.
- Temperature and season are context, not a bite score.
- Forage only counts if you actually saw it.
- The first presentation has a depth, a speed, a path and a reason.
If you’re still not sure what that forage was, use Hatch Match to sharpen it, then take it back to Species & Presentation. A bug on the water isn’t a vote for a lure brand.
Open Species & Presentation → · Refine forage only if needed →
4 · Can the setup execute that presentation?
Rod, reel, line, leader, terminal tackle and lure all have to agree about the job you just declared. The weakest connection is not impressed that the other five were expensive.
- Rod ratings fit the presentation and the lure’s working resistance.
- Reel, line and leader are compatible with the job and the expected load.
- Damaged line, rough guides, worn hooks or hard rating conflicts are fixed before the first cast.
- The landing plan matches the fish, bank, boat, net, cover and current.
- If the only unresolved piece is the actual connection, hand that job to Knot Analyst.
And the no-purchase answer is still on the table. If maintenance, rigging, a different angle or a different assignment makes the setup you own do the job, the tackle aisle will get along fine without you today.
Check system fit in Tackle Link → · Resolve the connection in Knot Analyst →
5 · Is the backup a real backup?
A backup only helps if it survives the thing that killed the first plan. Two ramps on the same exposed reservoir both fail in the same wind. Two mountain waters up the same closed road are one plan wearing two names.
Pick something with a different failure mode. Sheltered water when wind is the risk. Bank access when the ramp is a question. Lower elevation when snow is moving in, another watershed when a localized closure is possible, or something that isn’t fishing at all when conditions make responsible fishing a bad idea.
Verify it before you leave the house. “There is another lake over there somewhere” gets a lot less reassuring after dark.
6 · What ends the day?
Set the no-argument thresholds while everyone is dry, warm and not staring at a promising piece of water. Lightning, rising flow, worsening wind, smoke, fatigue, equipment failure, a missed return window, fish stress, a closure, an uncertain route — any of those can end the day before the fishing question gets solved.
That isn’t planning failing. That’s planning working. The return route, the fish, the access and the people don’t get less important because the bite finally turned on.
Then go fishing — and keep the trip in Field Ops.
Field Ops Desk keeps the trip in one place: what you saw, what you changed, and the debrief afterward. The other tools each answer their one question and hand it back, so you don’t end up with five half-records of the same morning.
Once the stuff that could cancel the day is covered, quit optimizing in the parking lot. Fish the first idea cleanly, watch what happens, change one thing for a reason you could say out loud, and bring that sequence home.
Done is when the obvious mistakes are off the table.
Everything after that is the part you came for.