Accesses and beats
Use access and beat context in a Fishing Program while keeping each source of truth clear.
Fishing uses an access and beat to make a Program practical: where the team is going, how it will reach the water, and what was actually used. The Program is the operational context for that choice, not the home for every rule, agreement, or piece of local knowledge behind it.
The three connected responsibilities
| Area | What it owns |
|---|---|
| Fishing | Choosing access and beat context for a Program, then recording actual use in the field. |
| Field Knowledge | Curated Beat Passport detail, seasonal context, pressure, hazards, license watchouts, and recommendation evidence. |
| Accesses & Landowners | The operational crossing, dated agreement, operating rules, owner responsibility, and charges. |
Select the beat and verify its access context
Before a Program starts, use Beat Passport and seasonal context to understand the water. Confirm the access path and applicable operating rules through Accesses & Landowners.
In Guide Mobile, the guide selects the beat. Trailhead shows access availability and other constraints that affect whether that choice can proceed. The attached access context supports planning, but it is not a second free-form selection presented as equivalent to choosing the beat.
This does not make Fishing the owner of the underlying records. A new hazard, seasonal observation, or missing context belongs in Field Knowledge. A gate instruction, eligibility boundary, commercial term, or charge path belongs in Accesses & Landowners.
Record what really happened
The field day can differ from the plan. Record the access and beat actually used with the Program and its report so the company can understand the outcome. That field fact can support three different kinds of follow-through:
- Fishing can explain the execution and report outcome.
- Field Knowledge can review the outcome as evidence for future decisions.
- Accesses & Landowners can trace a real crossing to the rule and owner effects that apply on that date.
The execution timeline records entry and exit through the access attached to the Program. Record the actual crossing rather than assuming the planned path was used. See Execute the Program for the field procedure.
Keep the handoff visible
Use the Access → Beat → Program flow for the full decision and feedback path. It shows why a field usage record is not the same thing as a commercial agreement or a curated recommendation.