The Pre-Trip Workflow for Steelhead Alley Guides: How I Use SHA Conditions to Avoid a No-Fish Day

Why the workflow exists

The cost structure of a guide trip is asymmetric. A no-fish day on a blown-out river costs the guide a refund or a comp, a damaged referral, and a future booking. A no-fish day on a fishable river costs the client a fishing day they would have spent anyway. Spending an extra 30 minutes the evening before to choose the right water is the highest-leverage time a guide spends.

This piece walks through the three decision windows I use, with concrete reference to the SHA features that drive each decision. It's written from the guide's chair, not the consumer angler's. The expectations are different.

Window 1: Booking-call window (T-3 to T-7 days)

The conversation that begins "Are we still on for Saturday?" happens on Wednesday or Thursday. Whether the answer is "yes, plan to leave at 5:30," "let me suggest moving to Sunday," or "let's reschedule to next weekend" depends on the 7-day forecast index.

What SHA features I use

• 7-Day Forecast Alley Index -- the projected fishability score for each day. Excellent or Good in the Saturday slot is a green light; consecutive Poor days are the rescheduling signal.
• Per-river 7-day forecast detail -- the forecast index is the regional summary, but each river has its own projection. A Saturday "Poor" Alley Index might still leave the Salmon River fishable because Lake Ontario rivers respond to different weather patterns than Lake Erie rivers.
• NWS 7-day weather + precipitation outlook -- the upstream input that drives the forecast. A 30%+ chance of significant rain in the 48 hours before the trip is a yellow flag for any Erie tributary.

The decision logic

Three days out, I look for one of these patterns:

1. Green light -- forecast index Good or Excellent + no significant precipitation forecast in the 48 hours before. Confirm the trip.
2. Yellow flag, watch -- forecast index Good but precipitation forecast in the 24-48 hour window. Confirm the trip but flag a backup. Re-check the day-before.
3. Red flag -- forecast index Poor + precipitation forecast + the Alley as a whole is dropping. Call the client now, propose moving the trip. Don't wait for the morning-of decision.

The reschedule conversation 4 days out is dramatically easier than the cancellation conversation 4 hours out. The 7-day forecast index is what enables the conversation to happen at the right time.

Window 2: Day-before window (T-1 evening)

This is the highest-leverage window. The client is committed; the trip is confirmed; the question is which river + which access point + which technique + which client expectations to set.

What SHA features I use

• Live current Alley Index -- regional snapshot, top picks, watch/skip lists. Tells me which rivers are in shape RIGHT NOW.
• Per-river current rating -- the Excellent / Good / Fair / Poor for each candidate river. Combined with the recent trend, this is the trip-day target.
• Per-river flow + clarity + water temp current readings -- the raw numbers that drive the rating. The rating gives me the headline; the numbers tell me what the day will actually look like (slow water on a flow at p15 vs aggressive water at p65 are different days even with the same rating).
• Day-analysis lookback -- "show me how this river has been responding the last 7 days." Tells me if the current Excellent rating is on the way down from a peak or steady. A river at 200 CFS dropping from 350 CFS at peak is different fishing than a river at 200 CFS that's been flat all week.
• Storm tracker / projection -- if a storm rolled through earlier in the week, the day-analysis shows me the recovery curve. The closer the day-of-trip is to the predicted full-recovery point, the more confident I am.

The decision logic

I rank the candidate rivers + pick the top 2-3 + then choose between them based on:

1. Client skill + comfort. A first-time client gets the easier wading + clearer water + more forgiving structure. An experienced angler can handle bigger water with more nuance.
2. Drive time + access logistics. The optimal-conditions river might be 90 minutes away; the Fair-rated river might be 20 minutes away. The drive-time-adjusted expected fish-per-hour matters more than raw conditions.
3. Weather window. A 36F + light snow morning is different fishing than a 50F + sun morning. Some rivers handle one better than the other.
4. Crowding likelihood. Friday-afternoon Salmon River is different from Wednesday-morning Salmon River. Saturday on the Cattaraugus differs from Sunday on the same water.

The Plan B + Plan C requirement

Every trip plan includes 2 backup rivers in known geography. If the primary river is unexpectedly blown out (flow gauge offline + no recent reading on arrival + visual confirmation it's the wrong color), the guide drives to Plan B without losing the day. The client never sees the Plan A → Plan B transition as panic; it's pre-planned.

Window 3: Morning-of-trip window (T-0 dawn)

The morning check is a confirmation, not a decision. If the workflow worked the day before, the morning is simply "the river still reads Excellent / Good / Fair, the gauge is updating, I'm comfortable putting the client on this water."

What SHA features I use

• Live USGS gauge reading (refreshing every 15 min) -- the headline number. Hasn't moved overnight = green light. Moved up 15-30 CFS = yellow flag for a rising-river morning. Moved up more than 30 CFS = check the storm tracker + recent rainfall to see if the river is responding to delayed runoff.
• Water temperature -- the morning thermal context drives technique selection. Below 38F = slow dead-drift, bigger flies, more split shot. 38-45F = standard nymphing. Above 45F = consider swung flies + streamers.
• Clarity inference -- the system's flow-ratio-derived clarity gives me the headline. Visual confirmation on arrival is the final check.
• Solar clock + barometric pressure trend -- the secondary inputs. Steady or slightly falling barometric pressure with overcast = good fishing window. Sharply rising post-front = expect slower morning.

The decision logic

If the morning reading matches what I expected the night before, drive to the river. If it doesn't match (the river is up significantly, or down significantly, or showing readings outside the prior 24-hour range), pause + re-check the storm tracker + recent rainfall. A 30-minute morning pause to verify is dramatically cheaper than a 4-hour trip to wrong water.

Window 4: Post-storm recovery (the day-analysis case)

Some trips are scheduled for the day AFTER a significant rain event. Whether the river is fishable depends on a recovery curve that varies by river.

What SHA features I use

• Day-analysis lookback over the last 72 hours -- shows me the hourly flow + temp + clarity progression. I can see when the river peaked, how fast it dropped, how the clarity recovered.
• Per-river historical recovery patterns -- the Chagrin recovers faster than the Salmon River; the Cattaraugus recovers slower than the Elk. Knowing the typical curve for each river is critical.
• Live current state vs the optimal range -- the river might be at 280 CFS now, but the optimal is 150-350. The question is whether the curve trajectory says it's heading toward the bottom of the range or past it.

The decision logic

A river dropping from peak to optimal-high is often the best fishing of the week. A river dropping FROM optimal-low to BELOW optimal-low is often slower than its current rating suggests. The day-analysis lookback tells me which side of the curve I'm on.

The practical heuristic: if the river has been at or below optimal-high for 12+ hours and is still dropping, the fishing window is closing -- get there early. If the river just hit optimal-high in the last 3-6 hours and is dropping, the window is opening -- the next 18-36 hours are likely the best of the week.

Setting client expectations

The workflow above produces a trip plan. Setting client expectations is a separate skill: tell the client what to expect, in honest detail, before the trip.

• "Conditions are Excellent. We should have a great day."
• "Conditions are Good. We should have a productive morning; the afternoon might slow down."
• "Conditions are Fair. We're working harder for fewer fish. Realistic expectation: 2-4 hookups in 6 hours."
• "Conditions are Poor and I think we should reschedule."

The client who knows what to expect handles the day's outcome better than the client who thought every Steelhead Alley trip produces 20-fish days. Expectation calibration is half the work.

What the workflow assumes (and where it fails)

This workflow assumes a guide has:

• Working knowledge of at least 5-6 candidate rivers in the region (so Plan B + Plan C exist in known geography)
• Ability to read SHA's per-river optimal flow ranges + clarity classifications + temperature zones
• Honest assessment of own technique + client capability matchups
• Reliable access to phone signal at the candidate water (to re-check before driving)

Where it fails: rare events that don't show up in the gauge data + the forecast. A localized chemical spill, an active construction site discharging sediment, a sudden up-stream dam release in dam-controlled water. The workflow gives high accuracy on the predictable; it cannot capture the unpredictable.

Honest gaps

• This workflow is steelhead-season specific. Summer warmwater trip planning has different decision logic that I'll cover in a separate piece.
• The Lake Ontario rivers (Salmon, Genesee, Oak Orchard, Eighteenmile-Niagara) operate on dam-controlled regimes that change the typical workflow -- the dam release schedule matters as much as weather.
• I treat the SHA forecast index as a confidence-adjusted estimate, not a guarantee. Some weeks the forecast is dead-on; some weeks the projection misses the timing of a system by 24 hours.

Continue learning

• How We Score Rivers -- the methodology behind the ratings this workflow uses.
• Reading Steelhead Water -- on-water decision-making after the trip plan is set.
• Catch and Release Biology -- client-handling science for high catch-and-release days.
• Should You Fish Steelhead During Spawn? -- the spring-specific ethics framework.
• Guardians of Chrome: Conservation Guide -- broader conservation framework.
• Public API: Alley Index -- the same data feed available to LLM tools and integration partners.