Skip to desk content
Field Ops Desk

No active trip yet. Field Ops will keep one Water → Species → Presentation context in view.

Start a new trip
A worn field notebook lying open on wet river stone, a pencil across the page and a brass lantern beside it.

After the trip

Field Debrief

Record what you actually observed: water state, weather, forage, the presentation you tried, how the system behaved, and what you learned. The next trip can say “last time you encountered this condition, here is what you recorded.”

This is not a catch log. Exact fishing locations stay off. Named public waters only.

Everything you record here stays in this browser. Nothing is uploaded. Keep a copy with the export on the reference page.

Public conditions context

Where are you fishing?

Choose a named public water and the desk will pull a broad public weather read for that area. This is trip context, not a fishing pin, access guarantee, or bite prediction.

236 seeded waters across the West, Midwest, South, and Northeast. Search by name or state.

Pick a water above to load current public weather context for the trip.

Named public water is optional. Leave it undeclared if you would rather file the observation by condition class alone.

Your field practice

What you noticed last time

  1. Notes · what stood out
  2. Comparisons · the same water twice
  3. Tests · a call named in advance

What that makes possible next: Notice one variable at a time. Write down what changed and what you would watch next; three debriefs carrying those two lines is enough to start comparing one against another.

Next trip · explicit experiment

Kept separately from what you learned. It is saved with the next debrief for this water and later returns as a test to revisit—not as a probability.

What did this water teach me?

These are your own prior observations under named conditions. They are starting notes for the next trip, not probabilities or catch forecasts.

Your first debrief starts the record. Do not grade the trip; record what changed your next decision.

0 observations · 0 lessons · 0 named waters

Observation record

What you saw

Fill only what you observed. Unknown is an honest answer. The desk will not invent a hatch, a bite, or a location.

Water state

Clarity

Weather class

Species · common name is enough

Forage seen · presentation attempted

Forage class

Presentation family · not a lure SKU

Equipment behavior · knot

How the system behaved

Knot outcome

Coordinate pairs in the notes are stripped on the way in.

Trip to trip

What your record actually says

Your debriefs and your on-water sessions, read together. It describes what you logged — including what you never logged, which on a handful of trips is the more useful half. Everything from here to the bottom of the page reads whichever trips you choose below, so narrowing to one river in one season asks the same questions of that river in that season.

Which trips

Reading all 0 trips on this device.

Detail

Across trips

Not enough on file yet

Patterns need more than one trip. The desk will not manufacture a trend out of a single record, and it will not rank anything until there is something to rank. Debrief two or three trips and this board starts telling you things — beginning with what you have never tried.

Trip to trip · what you have never tried

The shape of the hole

Counting is the easy half. Counting says you have fished stained water and you have fished a streamer; it never notices that you have not once put the two together. These grids cross two things at a time and draw the squares you have missed, because on a personal record the missing squares are the only claim that is fully honest.

Coverage

Three records and this grid starts working

Coverage crosses two things at once — water colour against presentation, temperature against presentation — and shows you the squares you have never fished. On one or two records every square is empty, which is true and useless. Come back after a few debriefs.

Trip to trip · what you did about it

Which levers you actually pull

Every change you log on the water goes in here with whatever happened next. Most anglers pull two levers and believe they pull six — this is the unarguable version, including the ones you have never touched at all.

The change ledger

Nothing to read back yet

Every time you log a change on the water — depth, speed, size, water — the desk keeps the sequence around it. Three changes in and this board starts telling you which levers you actually pull, which you have never touched, and how long you leave something alone before you get restless. None of that is available from a catch total.

Trip to trip · the one call the desk makes

The plan, against the day

Trip Prep says: start with this presentation family. It is the only prediction this desk makes, and until now it was erased the moment you recorded what you actually fished — so the one call it makes had never once been read back against the water. There is no score here. Leaving the plan is usually you being right in front of water this desk has never seen; what is worth seeing is whether you leave it in the same condition every time.

One day at a time

The sessions, as they went

Everything above reads your trips together. This reads one. A day drawn on a real minute axis is the only way anybody notices the shape of their own session — the ninety minutes at the start with nothing logged, the three changes inside eight minutes after the first refusal, the hour that produced everything.

No on-water sessions on this device yet. Start one from the On the Water page and the day will be here afterwards, minute by minute, including the minutes nothing happened in.

Observation history

Observation history

    ← Back to the desk Trip Prep

    236 named public waters on the desk · none of them are pins

    Northern Lantern House Labs

    Field Ops Desk

    Named public waters only · no exact coordinates · nothing assumed without a check · nothing is added from another tool until you confirm.