A valid draft team becomes real field work when the CIS is saved, and only newly assigned people should be notified.
Track
Assignments
Phase
Assignment confirmation
Starts with
Valid team ready to save
Ends with
New assignment visible
Ops has finished a valid booking team. Saving the CIS records the assignment, identifies newly added people, and exposes the linked context in mobile without approving any daily Program.
Ops saves a CIS with a newly assigned guide or assistant.
The final review confirms people, roles, and booking dates.
This is the key moment: the saved team establishes assignment visibility, not daily Program approval.
Guide and assistant remain explicit assignment roles.
People already on the team are separated from genuinely new assignments.
Unrelated CIS edits do not create duplicate assignment alerts.
Mobile now reflects the canonical booking-team assignment.
Reviews and saves the valid booking team.
Receives newly assigned work and opens its CIS context.
Records the assignment and notifies only newly added people.
The final booking team on the CIS
Why: Confirm who becomes operationally committed.
A new assignment notification linked to CIS context
Why: Understand the newly assigned work.
Saving a new team creates assignment visibility and notifications, never daily Program approval.