Trip review checks a saved itinerary in two layers: deterministic checks find concrete schedule and route problems, while broader planning feedback looks for pacing, meal, lodging, and experience concerns. Together, they help you spot problems before you share, book, or travel from a plan.
Run the review
Open a trip you can edit and select the review action. Platix evaluates the current saved itinerary, so save day and stop changes before running it.
The review opens with a plan health score, a summary, severity counts, and detailed findings. The score is a quick signal; the findings are where the work happens.
Understand severity
Findings are grouped by severity:
- Critical means the trip may not work as written, such as overlapping stops, a day that cannot fit its scheduled time, or a missing overnight stay when the day needs one.
- Warning means the plan deserves a closer look, such as rushed pacing, an accommodation label without a mapped accommodation stop, or a meal that may be missing.
- Note means Platix noticed something worth considering, but it may be completely acceptable depending on your travel style.
Each finding may include a category such as lodging, meals, schedule, pacing, routing, logistics, or experience. When Platix can identify the affected day, use Open Day to jump directly to the part of the trip that needs attention.
What Platix checks
The rule-based part of trip review can identify issues such as:
- A day with no accommodation when an overnight stay is expected.
- An accommodation label without a mapped hotel or accommodation stop.
- Missing lunch or dinner coverage on full travel days.
- Activities whose start time and duration overlap.
- Stops without a usable start time or duration.
- Scheduled activity time that cannot fit within the day before travel buffers.
- Too little time between stops based on estimated travel time and transition buffers.
- Duplicate explicit meal roles, such as two stops both marked as dinner.
- Activities scheduled after a departure stop.
- Morning, afternoon, evening, lunch, or dinner labels that do not match the scheduled time.
- Stops that appear to be scheduled on a closed weekday when opening-day data is available.
- Overnight route shapes that suggest avoidable backtracking or inefficient pacing.
Meal review is intentionally practical. Arrival days only need dinner coverage, full days usually need lunch and dinner coverage, and departure days are skipped. Not every trip requires a restaurant reservation for every meal. A travel day, overnight flight, staying with friends, or flexible meal plan can make a warning acceptable.
Contextual feedback
Platix can also look across the trip and point out route, pacing, meal realism, rest, or experience concerns that one schedule rule might miss. This review uses a sanitized trip snapshot. Booking numbers, private booking notes, detailed costs, and chat history are not sent into the review context.
If the AI portion is unavailable or only partially completed, the dialog will say so. The rule checks still run across the saved days and stops, so the review can remain useful even when the qualitative layer is limited.
Work through findings
Open the relevant day, make the change, and run the review again. You can also use trip chat to ask about the current trip, day, stop, or visible map area.
Some findings can show a Help me decide action. Use it when you want Platix to compare possible remedies, such as keeping the route as is, changing a stop, or accepting a warning because it matches your intent. If the recommendation is useful, apply it from the review dialog. If the recommendation misses your preference, adjust it or handle the item yourself.
Verify critical facts separately
Trip review is planning support, not a live operating guarantee. Opening hours, prices, availability, transit schedules, weather, visa rules, and entry requirements can change. Confirm critical details with the provider or an authoritative source before travel.