Travel project case

Map Responsibilities Before a Delegation Charter Enquiry

For a proposed delegation visit, begin with the travellers, the fixed meeting and the separate ground destinations after arrival. The project manager needs more than a preferred flight time. A responsibility map should identify who approves the journey, who coordinates the enquiry and which party confirms the proposed flight. Use that map to collect the outstanding decisions before requesting proposals.

Identify the client’s approving role

Choose the person authorised to accept the proposal and request a revision. Distinguish that role from collecting travellers’ preferences or maintaining the meeting calendar. A delegation can otherwise produce several apparently final requests that describe different passenger lists or timings. Keep the decision route concise so the aviation contact knows whose acceptance matters and the project team knows which choices remain open.

Give the broker a complete request

Jet Insite’s role is charter brokerage, distinct from the operating carrier that confirms the proposed aircraft and flight arrangement. Prepare the requested route, dates, passenger count and baggage information for that coordination. Include the return or intermediate movement being considered. Keep the aircraft and itinerary questions attached to the request, then record the operating carrier’s confirmation when the proposal is accepted. This gives the delegation a clear route from initial preferences to reviewed arrangements.

Keep personal information in the proper process

The shared project sheet can record practical roles and counts without circulating every traveller’s personal document. Provide the information requested for the actual booking through the appropriate channel. Name the person responsible for collecting and updating it. This separates ordinary delegation coordination from the handling of information needed by the aviation parties, rather than assuming one unrestricted group document should serve every purpose.

Connect ground stages as their own workstream

Allocate the passengers and bags to the actual onward destinations and proposed vehicles. Record the relevant arrival facility once the aviation arrangement identifies it. Ground bookings need their own acceptance unless a proposal explicitly combines the scope. A flight can be clearly described while a hotel journey remains incomplete, so the project review should test those connected stages rather than stopping at the aviation total.

Maintain one approved itinerary version

When a traveller, meeting or route changes, record the revision and ask the affected parties to review it. Keep accepted changes distinguishable from suggestions. The final travel file should identify the broker’s coordinating contact, the operating carrier, the accepted flight arrangement and the separately confirmed ground stages. Include the current client decision contact and any questions still awaiting an answer. Use one approved itinerary version when coordinating the delegation’s next movement.

Questions before the next step

Does the project manager choose the operating aircraft independently?

The request can state preferences, but the proposed aircraft and itinerary need the relevant aviation confirmation. Keep the broker and operating carrier’s roles clear.

How should a changed delegation itinerary be recorded?

Identify the requested revision and the parties affected, then preserve their accepted updates with one current itinerary. A changed meeting or passenger list should not silently replace the confirmed aviation and ground arrangements.

Company information and next steps

Use Jet Insite’s charter-booking guide for the aviation brief — Use the booking guide to organise the proposed routing, traveller information and questions for the charter enquiry.

Discuss your own requirements directly with the relevant company. Confirm the scope, availability and written terms for your project.

Continue planning

Explore travel, vehicle care and project guides