PlatixHelp center

Trip guide

Review the trip setup

Check what Platix understood before a trip is generated, including blocking decisions, details planning cannot receive, and where each saved field goes.

Open a saved trip setup and select Review setup. Decisions to make block creation; planning support still needed and planning notes do not. Expand Where your saved details go to see which part of planning each field reaches. Review setup never starts a build.

Last verified 2026-09-12

Trip Setup is the editable plan Platix builds from your prompt, your imported itinerary, or your own manual entry. Review setup checks that saved plan before any trip is generated from it, so you can see what Platix understood while it is still cheap to change.

This is a different check from Review a trip. Trip review evaluates a finished itinerary. Review setup evaluates the instructions the itinerary will be built from.

Run the review

Open a saved trip setup and select Review setup in the header. The review reads the currently saved version of your setup. It does not create a trip, and it does not change anything you have saved.

If you have unsaved edits open in a form, save them first. The review only sees saved values.

Decisions to make

These are the findings that stop trip creation. Platix needs an answer before it can build anything, usually because a required value is missing or two instructions disagree.

A common example: your route has nights left unallocated and you have not allowed Platix to make reasonable assumptions. Either assign the remaining nights yourself, or turn on Platix may make reasonable assumptions in trip basics.

Resolve these in the editor, or answer them in Open decisions and let Platix propose the field changes for you to apply.

Planning support still needed

These findings mean a detail you saved cannot be passed through to the planner in the shape you gave it. Your data is not lost and nothing is deleted. The planner simply will not receive that detail the way you wrote it.

Examples include a note longer than the planner's field supports, a day-trip parent base that cannot be represented, or a traveler and children combination the planner cannot express.

These findings do not block trip creation. That is the important part. Your trip will build successfully, and it may still be built from an incomplete reading of your instructions. If a finding here covers something you care about, change the setup so the detail fits, or plan to correct it in the trip afterward.

Planning notes

Notes record assumptions and observations that are expected to be fine. A working duration that Platix derived rather than read, or open stay nights it intends to allocate, appear here.

Notes do not block creation and usually need no action. They are worth a glance when the trip that comes back is not the trip you pictured.

Where your saved details go

Expand Where your saved details go to see which part of planning each of your saved fields reaches. Each field is grouped by destination:

  • Trip structure and Route checks mean the value reaches the trip-level plan.
  • Day scheduling, Day planning context, and Trip and day timing mean it reaches the day planner.
  • Needs interpretation during planning means the value is passed as language for Platix to interpret, not as a hard constraint.
  • Not connected yet means the field is saved but not used by planning at this time.
  • Needs review means Platix could not classify the field, and you should read it yourself.
  • Applied to setup fields means the value already shaped your saved setup directly.

Use this when a trip keeps coming back without something you asked for. A detail sitting under Not connected yet explains a missing outcome that no amount of rewording will fix.

Review, prepare, and create

Three controls sound similar and do different things:

  • Review setup inspects the saved plan. It never starts a build.
  • Prepare trip validates and freezes the exact saved version you are looking at, then reports anything blocking. It does not queue generation.
  • Create trip appears only after a successful preparation of that same version, and starts generation.

Editing your setup after preparing it invalidates the preparation, and you will need to prepare again. This is deliberate: it guarantees the trip is built from the version you actually reviewed.

If the setup changes while reviewing

The review is bound to one saved version. If the setup changes underneath it, the dialog tells you the saved setup changed and asks you to reload before reviewing again. Nothing you saved is affected. Reload and run the review once more.

Verify critical facts separately

Review setup checks your instructions for structural problems. It does not confirm anything about the world. Opening hours, prices, availability, transit schedules, visa rules, and entry requirements still need checking with the provider or an authoritative source.

Next