A fly fishing hatch journal can start with an insect description, a time, and a presentation. You do not need a confident Latin name before the note becomes useful. Record what was visible, what the fish appeared to be doing, and which fly you actually tried; add an identification later if you can support it.
A fly-fishing discussion about matching the hatch illustrates the common difficulty of connecting unfamiliar insects with fly patterns. It supplies the learning question. Fisheries education, rather than forum catch claims, supports the distinctions below.
Begin with an observation window
Before changing flies, watch from a stable bank position. Write the start and end time of a short observation period. Describe insects on the surface, flying above it, or resting nearby, together with the part of the water you could see. “No insects seen in the near-bank lane” is more honest than “no hatch anywhere.”
Add a photograph when it can be taken without disturbing habitat or entering uncertain water. A rough body-length estimate such as 8 mm (0.3 inches) should remain labelled approximate. If you have no scale reference, record small, medium, or large relative to flies in your own box instead of inventing a measurement.
Separate the insect from its life stage
Idaho Fish and Game's aquatic-insect introduction explains that aquatic insects spend at least part of their life underwater and highlights mayflies, caddisflies, and stoneflies as important groups reflected in fly patterns. That provides a starting vocabulary, not a universal hatch calendar.
Keep separate fields for broad group, apparent stage, and confidence. An entry might read “possible mayfly adult; pale body; upright wings; identification uncertain.” If all you know is “small dark flying insect,” save that. A guessed species name can make later comparisons look more precise than the original observation was.
Describe feeding without declaring the cause
Maryland DNR's fly-fishing guide distinguishes underwater nymph imitations from surface dry flies and discusses observing subsurface feeding and rises. Use those categories to describe the fishing problem: activity below the surface, repeated surface rises, or no visible feeding.
A rise alone does not identify the insect being eaten. Note where and how often activity appeared, then record your presentation as a separate test. Keep the fly's pattern name, hook size, whether it was fished on or below the surface, and the lane and drift attempted. If a fly took a fish, the result supports that presentation on that occasion; it does not confirm the insect's species.
Keep a journal entry short enough to repeat
Use this compact record after a trial:
| Field | Example note | | --- | --- | | Observation | Small pale insects over the near-bank lane; exact group uncertain | | Fish activity | Several surface rises in the slower seam | | Presentation | Named dry-fly pattern and actual hook size; upstream drift | | Result | One take during a short trial; missed; no landed catch | | Next question | Repeat the drift before changing pattern |
Include session duration and unsuccessful presentations. Otherwise the journal becomes a collection of winning flies with none of the context explaining how many attempts they received.
Build a local reference after the trip
Review photographs with an agency identification resource or a knowledgeable local source. Keep the original description even when you add a later identification. Over several visits, compare similar stretches and observation times; a regional hatch chart can suggest what to look for, but it cannot replace what was seen that day.
Use a notebook, your own notes, or the free fishing-log template. This is a manual observation workflow, not a claim that FishPal identifies insects or supplies hatch forecasts. For choosing a fishable bank position before observing, see our small-stream bank-fishing guide. If route surfaces or a seated fishing position shape your visit, use the accessible-facilities planning guide to check the whole route before travelling.