Overview

Field Knowledge is Trailhead's intelligence layer. It helps the company answer: what do we know about this water, season, and conditions—and how should that shape tomorrow's Fishing decisions?

What Field Knowledge is responsible for

Field Knowledge gathers and curates the experience that would otherwise live only in people’s memory or scattered reports. It turns that experience into useful context for operators and guides before the next field day.

Use Field Knowledge to:

• maintain Beat Passports with productive runs, hazards, fly patterns, and the conditions that matter;
• keep seasonal observations, license requirements, and pressure patterns useful and current;
• review what reports, photos, catches, and conditions are teaching the company;
• identify where the company needs better or more complete context; and
• share practical signals and watchouts with the people planning or delivering the day.

The implemented web surface is write-first and contains five main areas: Passports, Seasonal, Pressure, Context Quality, and FIE Quality. Passports contains Overview, Species, Environments, and the compatibility Safety Standards area. Guide Mobile is the read-mostly peer: Beats and Signals bring relevant context back to the people preparing and delivering Programs.

The organization-wide Environment Catalog stores reusable environment descriptions, risks, management guidance, and an optional maximum fishable current speed. A Passport selects an active catalog entry and inherits those details without copying them; its Beat-local environment characteristics stay separate. Availability in a deployed organization depends on the corresponding database migration being applied.

Access follows lodge scope

Field Knowledge is capability-based rather than manager-only. People with global Trailhead lodge visibility can work across lodges; lodge-scoped users can read and write Beat and Seasonal knowledge inside their accessible lodges. People with no Trailhead lodge access receive no Field Knowledge capabilities.

How it improves the product path

Field Knowledge runs alongside the core path rather than replacing it. CIS defines the client commitment. Fishing plans and records the field work. Guides makes the people side ready. Operations keeps the company aware of live risks and closure.

Field Knowledge helps each of those decisions become better informed. A well-kept Beat Passport or a seasonal observation can help the company choose a stronger plan; a reviewed Fishing Report can add evidence that improves the next recommendation.

What Field Knowledge receives and shares

Keep the boundary clear

Field Knowledge owns curated intelligence and the feedback loop from the field into future decisions. It does not own the Program or its execution, the client trip, the guide's own license or readiness record, or the Operations command view. It uses those records as context while they remain with their source areas.

A healthy knowledge loop

The company can explain why a recommendation makes sense, not just repeat it. What happened in the field is reviewed and used to improve future choices, and important gaps in local knowledge are visible before they become avoidable surprises.

Next: see how Operations uses trusted signals to close the day.