Reassignment and history
Change the current booking team without rewriting protected field-work history.
When availability or operating needs change, Ops edits the existing CIS booking team, removes or replaces the affected person, and lets Trailhead validate the replacement's role and dates.
After save, only newly added people receive notifications and mobile assignment views refresh to the current team. Unchanged people do not receive duplicates.
Changing a CIS booking team updates the current commitment but does not rewrite completed assignments, Programs, or Fishing Reports. Any downstream Program or report effect still requires separate review.
When one created Program needs another primary guide for a specific CIS day, Management uses Replace Guide from that Program before execution starts. Trailhead validates the replacement and changes the CIS day, Program, allocation, and linked transfer together. The assistant stays unchanged, the reason is recorded, and completed work remains protected. This action is not available through generic Program editing or mobile.
For an approved Program, Trailhead rebuilds the replacement Guide's pending reminder delivery. Treat the delivery status as operational evidence: a failed or pending reminder can be retried, but reassignment success does not guarantee that a push or in-app notification already reached the device.