Structure each request around the family mandate
Family office travel can combine board obligations, private commitments, family movements and time-sensitive personal requirements within one complex itinerary. A decision-ready request distinguishes the passengers, purpose, route, timing, baggage, service needs and internal decision-makers without disclosing information that is unnecessary for assessment. It should also identify which entity or principal gives the instruction and where flexibility exists. The Business workspace supports a consistent briefing process, while the office remains responsible for lawful disclosure, authority to act, internal approvals and the accuracy of every detail submitted.
- Mission profile: Record dates, airports, passenger numbers, baggage, schedule flexibility, accessibility needs and relevant preferences, then identify whether the request concerns business aviation, leisure and family travel or another eligible mission.
- Authority and disclosure: Confirm the requesting entity, principal or beneficiary, internal cost owner, authorized approver and information that may lawfully be shared. Use role descriptions where sufficient and provide identity details only when required for assessment, contracting or flight performance.
- Connected arrangements: Note any multi-stop sequence, accompanying staff, pets, surface transfers or wider personal logistics that may affect timing. Any related service must be separately assessed and expressly confirmed by the responsible provider.
Support the office's own governance process
The Business workspace helps administrators keep continuity across recurring movements: request history, Broker Partner exchanges and available proposals stay in one account environment, which makes handovers between team members far easier. Identify the request owner, the reviewers and the final decision-maker before a request is released, and check membership, permissions, notifications, history and export functions against the actual account. Fiduciary authority, spending limits and approval policy remain defined by the family office under its own mandates.
- Defined responsibilities: Assign an internal request owner, reviewer and final approver according to the office's mandates. The platform does not validate powers of attorney, delegated authority, beneficial ownership, family governance or a user's right to act for a principal.
- Proportionate information: Limit submitted information to what is necessary for the mission and follow the office's confidentiality, privacy, cybersecurity and retention procedures. No page statement should be treated as a guarantee of masking, isolation, secrecy or technical security.
- Professional coordination: Where travel decisions involve trustees, protectors, advisers or wealth-management teams, establish the required legal, tax, compliance and accounting review outside the platform before commitment.
Compare proposals against operational priorities
An eligible request may be made available to independent participating vetted Broker Partners, which decide whether to respond and what they can propose. Family office teams should compare the contractual carrier, aircraft, route, timing, passenger and baggage assumptions, included services, exclusions and total price rather than relying on a category name or cabin image. They should also confirm which party is responsible for each connected arrangement and how material changes will be handled. Availability, suitability, pricing and provider participation remain mission-specific until the relevant parties complete their confirmations.
- Aircraft and route: Review passenger and baggage capacity, cabin layout, range, proposed fuel stops, airport suitability, slots, permits and alternatives. The operator alone confirms aircraft suitability and retains operational control of the flight.
- Commercial terms: Compare the contracting party, price components, taxes where applicable, payment milestones, cancellation terms, liability limitations, insurance information and treatment of changes. A request does not guarantee multiple proposals, availability, a saving or a booking.
- Provider responsibilities: Distinguish the Broker Partner's coordination scope from services performed by operators, handlers, caterers, security firms or ground providers. Review the participating Broker Partner network as background information, not mission-specific operator approval by IONA JETS.
Maintain continuity through office-controlled records
Staff changes, succession planning and evolving family structures make documented handovers important. The workspace may preserve administrative context where functions are available, but the family office remains responsible for records, access reviews and continuity. It should retain approved requests, considered proposals, decision rationale, contracts, passenger information, invoices and post-flight material in designated systems. No retention period, complete history, automatic reassignment, export, recovery, separation between families or uninterrupted access should be assumed without explicit confirmation in current terms.
- Independent record keeping: Retain the approved request, proposals considered, decision rationale, signed contracts, passenger information, invoices and post-flight records within the office's own systems according to its legal and records-management requirements.
- Access transitions: When personnel, advisers or mandates change, administrators should review account membership, revoke obsolete access, document new authority and verify any transfer procedure. Platform access does not itself establish succession, delegation or ownership of records.
- Multiple families or entities: A multi-family office should verify whether the available account structure, functions and contractual terms suit the separation it requires. Do not assume data, billing, permissions or histories are isolated by family, entity or mandate without explicit confirmation.
.png)
