Planning help

Self-Drive Trip Planning Service

Service pages should eventually support higher-touch planning without displacing the self-serve planning experience. This v1 structure exists to keep the architecture ready.

At a glance

Service type
Planning support
Use case
Higher-touch route or itinerary help
Planning role
Future service architecture
Best paired with
Itineraries, road trips, timing decisions

Self-Drive Trip Planning Service is best for

  • travelers who want help narrowing route choices
  • future premium planning paths

Less ideal if you want

  • users who only need basic informational pages

When extra planning help makes sense

Service pages should support travelers who still need help after comparing routes, regions, and practical guides.

  • Service pages should remain downstream from self-serve planning content.
  • They should support users with friction that content alone does not fully solve.
  • The architecture should stay consistent with the planning-platform hierarchy.

Pages that should precede a service decision

Service pages should stay connected to the core planning entities instead of becoming isolated commercial endpoints.

Where to go next