Start with the handoff
North Quay Airport is a fictional example for ground-service teams.
For a turnaround coordination question, first identify the role responsible for the next handoff. Check the current, approved reference for any operating requirements, and take exceptions to the accountable operational role through your established local route.
This page explains coordination roles and information flow; it is not an operating procedure or a system of record. Certified procedures remain in their approved sources. Use the local source that applies to your team and location.
Choose the coordination path
These examples show how to route a question, not how to perform an operational task.
Ask the role handing over to clarify the missing coordination detail. If the detail affects an operating requirement, consult the current approved reference or raise the question with the accountable operational role.
Notify the coordination lead through the established local communication route, state what changed and which service teams may be affected, and ask the accountable operational role to determine the next coordination update.
Separate the known facts from the open decision. The coordination lead can align the handoff; the operational duty role owns escalation when the issue requires an operational decision.
Illustrative role map
Example responsibilities only; this authored reference is not a system of record or local policy.
| Role | Coordination responsibility | Handoff or escalation |
|---|---|---|
| Turnaround coordination lead | Keeps the coordination picture aligned and makes unclear ownership visible. | Routes unresolved coordination questions to the accountable operational role. |
| Service-team lead | Shares the team’s current coordination update and identifies dependencies affecting its handoff. | Raises changed or unclear dependencies through the established local route. |
| Operational duty role | Takes operational exceptions that require an accountable decision. | Directs the decision or escalation using the organization’s approved local process. |
Worked handoff: two references name different contacts
Illustrative coordination example; no live workflow or channel is represented.
In this fictional North Quay example, Coordination Brief revision 4 names Service Lead A for the next information handoff, while the current team roster names Service Lead B.
The service-team lead sends both titles, revision details, and the conflicting role labels to the coordination lead through the established local channel.
The authorized roster owner confirms that Service Lead B is the current handoff contact. The coordination lead corrects the brief and asks the affected teams to confirm receipt.
The teams check the corrected brief and acknowledge the same contact. This resolves the information-routing mismatch; it does not alter aircraft procedures or authorize operational work.
If the accountable contact cannot be confirmed, keep the question open and use the established operational escalation route.
Use learning and procedures for different purposes
Choose material that matches the role and the question.
Build coordination understanding
Use learning approved for the reader’s role to understand handoffs, role boundaries, and how to raise an unclear dependency.
- Check that the learning is intended for your role and location.
- Use the owner’s approved route when learning content appears outdated or conflicts with local direction.
Follow certified operating requirements
For instructions on performing operational work, use the current certified procedure in its approved source. This coordination page does not replace or reproduce that procedure.
- Confirm the reference applies to your role and operating context.
- Raise a conflict or uncertainty with the accountable operational role before relying on an interpretation.