Segment order
Whether the sequence supports the traveler's actual commitments.
Complex Itineraries
Make every segment serve the complete journey
Bring multi-city, open-jaw, mixed-cabin, and connection-heavy requests into one clear itinerary brief before comparing individual flights.
- 01Segment-by-segment clarity
- 02Cabin continuity
- 03Fixed dates and dependencies
The request in context
Complex trips need one source of truth
When a journey has several stops, reviewing each flight separately can hide conflicts between dates, airports, cabins, or ticket conditions. A structured request makes the order and dependencies visible.
Derek can review the itinerary as a whole: which cities are required, which dates are fixed, where the cabin matters most, and how connections affect the journey. The result is a clearer decision framework, not a guarantee of a particular routing.
Journeys that benefit from a structured brief
- 01Multi-city travel
For journeys with several required destinations and a defined order or date sequence.
- 02Open-jaw travel
For trips that arrive in one city and depart from another rather than retracing the same route.
- 03Mixed-priority segments
For journeys where cabin, timing, or flexibility matters differently on each segment.
Itinerary Review
What Derek evaluates
The review focuses on dependencies that are easy to miss when flights are considered one by one.
Fixed dates
Which dates cannot move and which segments have a usable window.
Airport continuity
Whether arrival and departure airports create an unintended transfer burden.
Cabin continuity
Where cabin changes appear and whether they match the traveler's priorities.
Connection logic
How connections affect the complete itinerary rather than a single flight.
Ticket conditions
Which conditions or separate-ticket dependencies require attention.
Clear expectations
Complexity creates additional dependencies
- A requested sequence may not be available exactly as described and no routing is guaranteed.
- Separate flights or ticket conditions can introduce dependencies that must be reviewed for a specific option.
- Submitting an itinerary is not a reservation and does not hold any segment.
How It Works
Three steps from request to decision
The process stays focused on the trip information and the tradeoffs that can be confirmed.
- 01
Map every required segment
List each city pair, fixed date, traveler count, cabin priority, and important dependency.
- 02
Derek reviews the sequence
Segment order, airports, connections, cabin continuity, flexibility, and conditions are considered together.
- 03
Review the complete journey
Assess the itinerary as one plan and decide which tradeoffs are acceptable.
Questions before requesting
Frequently asked questions
These answers explain the review process. Specific flights, products, and conditions still require confirmation for the individual request.
A multi-city request includes several flight segments. An open-jaw trip typically arrives in one city and returns from another. A journey can include both patterns.
List them in travel order, with fixed dates and acceptable date windows for each segment. Note any surface travel or meetings that create a dependency between flights.
Yes. State where the cabin is essential and where it is flexible. Any proposed itinerary should show cabin details segment by segment.
No. The ticket structure depends on the specific options presented. Any separate-ticket or condition-related dependency should be made clear before a decision.
Start with the trip
Share the journey you want Derek to review
Provide the route, dates, traveler count, cabin preference, and the tradeoffs that matter most. Submitting the request does not create a reservation.