A strong Kenya itinerary is a sequence of compatible travel systems, not a contest to fit the most names onto a map.
7 days: one clear geographic story
Nairobi plus one safari circuit such as Mara or Amboseli/Tsavo. Protect arrival and departure days from heroic transfers.
10 days: add one meaningful contrast
Pair two compatible reserves or add coast with a flight. The extra nights should deepen the route, not simply add another hotel key.
14 days: expand regionally, not randomly
Build one northern/southern safari circuit plus a meaningful coast or mountain extension. Use the added time to slow down difficult terrain or connect a second compatible region.
Transfer days are real days
- Road safari circuits work best between geographically compatible reserves.
- Bush flights save rough-road hours and can materially change the usable safari day.
- Coast extensions usually work best by flight or planned rail/road rather than adding them casually.
What to cut first
If the route requires backtracking, a same-day long transfer plus sightseeing, or repeated one-night stops, cut the least distinctive leg. Road safari time is real travel time; map distance understates rough-road fatigue.
How to pressure-test the route
Before booking, write each change of base in door-to-door terms: checkout, station or airport access, waiting time, the main leg, last-mile transfer and check-in. In Kenya, the headline journey time can hide the part that consumes the day. A route such as Nairobi plus one safari circuit such as Mara or Amboseli/Tsavo works best when the long transfer sits between substantial stays rather than between two one-night stops.
Give every base a job. One should anchor the arrival, another should unlock a region, and any third base should add something that cannot be reached comfortably from the first two. If two consecutive stops deliver similar scenery or require backtracking, combine the nights. The result is usually a calmer itinerary with more usable mornings and evenings.