The host coordinator connects the visiting crew with local support arrangements and the relevant local operations liaison. The visiting crew lead shares the crew’s arrival and headcount with the host, then relays the agreed arrangements to the crew.

Worked example: Two vehicles arrive, but the host expected one. The crew lead checks in with the host coordinator; together they reconcile the headcount and confirm the agreed meeting point before the group separates. The host updates the local operations liaison if the change affects the local coordination plan.

This orientation explains coordination roles; it is not operational policy. For regulated, safety-critical, or sensitive matters, the host and visiting crew must use the current, domain-owner-approved material applicable to the location and their roles. If applicability or a direction is unclear, pause that coordination decision and ask the host coordinator to connect you with the responsible local owner. Do not treat a general company policy list as proof that a rule applies at this location.

Use the host-confirmed arrival point and text directions for the current location. If an image is unclear or conflicts with the written route, ask the host coordinator to confirm the directions before relying on either version. The sector photograph is general context and does not identify the Northbank arrival point.

Before updates begin, the host coordinator and visiting crew lead agree which channel to use, who should receive updates, and who will pass an unresolved coordination issue to the relevant local owner. The communications liaison can help with that handoff.

Example: If the crew lead sends an update and receives no confirmation, the crew lead checks with the host coordinator rather than assuming the intended group received it. The host coordinator then confirms the next handoff with the local liaison.