Review and save the CIS
Confirm the complete trip, save its assigned team, and make the current CIS available to downstream work.
Use the final review to confirm the booking, itinerary, passengers, needs, and team together. Saving makes the CIS the current operating reference and can create new assignment notifications.
Review the whole promise
- Check the booking shell, travel, stays, passenger roster, and passenger needs.
- Return to any incomplete or incorrect area before confirming the trip.
- Confirm each booking-team member, explicit role, and assignment dates.
- Save the CIS only when the complete trip matches the intended operation.
- Continue by reviewing the fishing work the trip requires.
| A successful review means... | It does not mean... |
|---|---|
| The trip promise is clear enough for operational follow-through. | Every Fishing Program has been executed or closed. |
| People can refer to one trusted trip record. | CIS owns guide readiness or report content. |
What saving triggers
Save handoff
From confirmed trip to visible assignment
- 01Trailhead
Record team roles
Attach each role to the correct CIS dates.
- 02Trailhead
Identify new assignments
Separate newly added people from unchanged team members.
- 03Trailhead
Create notifications
Alert only the people receiving a new assignment.
- 04Guide
Open the linked CIS
Review the trip context and assigned role in mobile.
- Only newly assigned people should receive an alert; unrelated edits must not notify unchanged team members again.
- The notification opens the linked CIS context and assigned role.
- Saving assignment visibility does not approve or create every required daily Program.
Check the result, not only the save action
Confirm that the saved team, roles, dates, and trip context are visible. If a newly assigned person cannot open the CIS, review their field profile, lodge access, and assignment rather than creating a duplicate team entry.
Next: review required Fishing work.