Define required Fishing work
Identify the exact CIS dates and client groups that require Fishing Programs.
After saving the CIS, review which dates and client groups require fishing delivery. The result is demand that Fishing can turn into exact Programs; it is not itself an executable field plan.
From trip demand to Programs
- Start from the trip's operational dates, lodge context, and guide or team assignments.
- Identify the fishing days and groups that require delivery.
- Make missing, changed, or incomplete demand visible to the operator.
- Hand that demand to Fishing Programs and readiness.
- Let Fishing create or adjust the exact Programs that own the field day.
- Keep a trip-level rollup so the company can see whether required work has progressed through reporting and review.
One date can require more than one Program
Do not treat one trip day as one automatic Program. Different client groups, beats, or guide teams can require separate Programs on the same date.
| CIS owns | Fishing owns |
|---|---|
| The trip commitment and the work it requires. | The daily Program and its execution. |
| The rollup link back to required delivery. | The report and outcome for each Program. |
| Explaining why demand exists. | Resolving the field plan and accepted exceptions. |
Make missing work actionable
A useful trip view shows the exact date or group still missing a Program and why. It should not hide skipped work behind a count, and a day with no fishing requirement should remain out of field-work blockers.
Follow Fishing, Guides, and CIS for the complete handoff from client commitment to a reviewed field outcome.