Everybody who fishes has stood there watching a fish come all the way in, look at the thing, and leave. Do it three times in a row and the usual response is to open the tackle box, which is the most satisfying variable and almost always the wrong one to test first.
There’s a better first move, and it’s free. Work out what the refusal has already told you. A fish that turns at your feet and a fish that veers off inside the final foot haven’t given you the same information — the first mostly tells you the lure got its attention, the second has signed off on nearly your whole presentation. Knowing which is which keeps you from spending an afternoon testing things the fish already approved.
Hook the Horizon · Free tool
The Refusal Reader
A fish followed and didn’t eat. Annoying, sure, but that fish just told you more than the last hour of empty casts did, and part of the question is already settled. Tell it what you actually saw and it’ll tell you what to quit testing.
1 What did it actually do?
2 Fishing for what? Optional — it changes the emphasis.
Settled — stop spending casts here
Still live
Run this next — one variable
Read the next follow, not just whether it ate. Farther out, closer in, or gone entirely — each one means something different, and that’s where most of the answer is.
This reads one follow at a time. Field Deck 02 carries all eleven refusal signatures, ten tests that each change one thing, with a result table for every outcome, six species cards, and a 52-page print set you can cut apart and keep in the box.
What to do with the answer
Change the one thing it names, and then — this is the part almost everybody skips — read the next follow instead of waiting for an eat. A fish that follows from farther away, closes to a shorter distance, or breaks off earlier than last time has told you which direction you moved. You can read that on every cast. Eats don’t show up nearly that often.
And if follows stop altogether after a change, put it back exactly how it was. That’s the strongest signal in the whole business, and it gets misread as the fish moving off all the time.
Where this goes next
The long version of this is in why fish follow but won’t eat, which gets into why the last few feet are where the decision happens. If the problem is the day rather than the fish — the river came up, the wind swung, the lake turned over — that’s a different question, and Common Situations is the place to start.
If the refusal points at the connection, Knot Analyst is where to sort it out. Species & Presentation helps when the presentation itself needs rebuilding, and whatever you change is worth logging in Field Ops before you forget which change did what.