Private flight checklist for travel-day coordination

Start with the latest confirmed plan

Open the current itinerary and review the next movement. Check the date, local time, airport, confirmed meeting point and passenger group. If you are using a saved copy, compare its version or export time with the current information before relying on it.

Look for unresolved requests and decide whether any need a direct call. A note recorded in a system does not necessarily mean the responsible person has acknowledged it. Confirm the contact route for questions that cannot wait.

Check the handoffs that affect the traveler

Review the transition from pickup to departure and from arrival to the next destination. The traveler should know where to go and whom to contact without reading the full planning history. Coordinate with the broker about the information supplied by the operator.

• The traveler can open the intended itinerary or has an appropriate backup reference.
• The correct departure meeting point is clear.
• The departure transfer owner has the current arrangement.
• The arrival transfer owner knows how updates will reach them.
• Any special service request has an explicit confirmation or visible pending owner.
• The covering assistant and broker have each other’s contact route.

Communicate changes as actions

When something changes, identify who needs to do something differently. An executive may need a revised pickup instruction, while a meeting host needs an updated arrival expectation. Those are different messages even when they come from the same trip change.

Label a requested change as pending until confirmed. Once the broker confirms it, update the shared record and give the affected people a concise summary. Use direct communication when timing makes an unread notification insufficient.

Travel-day coordination note
Trip / next leg:
Current confirmed plan checked at:
Open request:
Person resolving it:
People who need an update:
Action required:
Next check-in trigger:
Urgent contact route:

Use a shared workspace without assuming it does everything

WingStack brings itinerary information and trip communication together. Before relying on it for travel day, ask your broker to show how your team sees confirmed updates and how the passenger receives them. Test that experience on the devices your team actually uses.

A shared record supports coordination, but it does not replace the operator’s instructions or a direct conversation when an issue is urgent. At the end of the day, record any handoff that was unclear so the next trip starts with a better process rather than the same workaround.