An agency intends to stock.
A plan may identify a water, season, week, species, or allocation. Weather, hatchery operations, water conditions, access, or emergencies can change execution.
Stocking data field guide
Learn what planned, completed, annual, seasonal, and historical records actually mean; why state programs cannot be read as one uniform dataset; and what to verify before you travel.
Start with the verb
A plan may identify a water, season, week, species, or allocation. Weather, hatchery operations, water conditions, access, or emergencies can change execution.
A scheduled record is more specific than a general plan, but it is still future-facing until the agency reports completion.
Completed records are stronger evidence of an event, but they do not reveal where fish moved, how many remain, or whether every named section received the same treatment.
Annual totals and historical events help establish program context. They should not be presented as a current date or used to promise a future stocking.
If the agency says “planned,” trout.app should say planned. If it reports “completed,” the page can say completed. Normalization should organize meaning, not strengthen the claim.
Field-by-field interpretation
| Field | What it can tell you | What it cannot tell you alone |
|---|---|---|
| Water name | The agency’s named destination or catalog entity. | The exact reach, county, or access point when names repeat. |
| Date | A scheduled or completed day when the source provides one. | Whether the event occurred unless the record type says completed. |
| Week / month / season | A broader operational window. | A precise stocking day. |
| Quantity | A published allocation, event count, or annual total. | Current fish abundance or distribution. |
| Species | Species reported in the source record. | Every species naturally present in the water. |
| Section / reach | The boundaries or segment associated with the record. | Permission to access every bank or adjacent property. |
| Blank value | The source did not expose a reliable value in that field. | Zero. |
Eleven programs, different evidence
trout.app preserves state-specific fields because forcing every program into one generic schedule would create false consistency.
| State | Current catalog source pattern | Use it for |
|---|---|---|
| Pennsylvania | Current PFBC schedule plus 2026 stocked-stream sections and annual summaries | Dates, species, section context, and quantities where PFBC exposes dependable totals |
| New York | Planned spring stocking plus historical actual records beginning in 2011 | Separating current plans from long-term completed history |
| New Jersey | 2026 spring allocations, stream/lake schedules, classifications, and fall program context | Reading allocations and seasonal programs by water type |
| Maryland | Spring schedule plus mapped, dated stocking activities | Comparing schedule records with agency activity records |
| North Carolina | NCWRC 2026 schedule and classification-specific water records | Planning within Hatchery Supported, Delayed Harvest, and other management context |
| Georgia | 2026 stocking frequencies, recently stocked waters, and weekly reporting | Understanding frequency and recent activity without inventing exact dates |
| Kentucky | Annual plans, monthly schedule, dated archive, and cumulative stocking map | Comparing planned cadence with dated and cumulative records |
| Tennessee | 2026 schedule and recent stocking report | Separating future schedule context from recent activity |
| Virginia | Stocked and wild reach layers plus DWR stocking program information | Connecting stocking context to mapped reach identity |
| West Virginia | Frequency codes, completed 2026 stockings, map, and regulation tables | Reading program frequency alongside completed events |
| South Carolina | Completed weekly reports plus reviewed public-access and water inventory | Completed activity and access context without treating classification as a stocking guarantee |
Why schedules change
Agencies may adjust stocking because of high or low flows, water temperature, ice, drought, road or access conditions, hatchery constraints, equipment problems, severe weather, or emergency closures. A delayed event is not necessarily a data error. The important question is whether the source has updated the plan or published completion.
A five-step workflow
Resolve repeated names and make sure the record refers to the section you intend to visit.
Is it planned, scheduled, completed, recent, annual, or historical?
Older records may be useful history while being unsuitable for near-term planning.
Look for revisions, delay notices, current regulations, and source-specific notes.
A stocking record does not guarantee safe conditions, public access, parking, or permission.
Common interpretation errors
It is better to show “quantity unavailable” than to imply zero, and better to show “scheduled” than to imply completed.
Official-source starting points