← Release notes

Version 20260727T201938Z · July 27, 2026

Independent Traveler Checklists and Preparation Status

Traveler checklists can be managed independently, while preparation status now reflects only the work actually configured for a tour.

Traveler Checklists

  • Traveler Checklists can now be selected, applied, edited, and removed directly on an active tour without creating an Operations flow or task.
  • Checklist items remain per-tour definitions evaluated for every traveler. Operators can add or remove items after application, while protected items must first be unlinked from any Operations task that tracks them.
  • Operations may optionally track the whole checklist as All travelers ready or track selected checklist items such as a time-sensitive visa requirement. Adding a checklist item never creates an Operations task automatically.
  • Operations templates expose the same optional checklist-item and whole-checklist completion choices when a Traveler Checklist is linked.

Preparation Overview

  • The preparation header now includes configured Operations tasks in its overall progress, alongside bookable reservations and an applied Traveler Checklist.
  • A dimension that is not configured is excluded from the percentage. A tour with no preparation work shows zero progress instead of appearing complete.
  • The header clearly identifies overdue work, open blocking work, and when the tour is ready to depart.
  • Uncalculated checklist data is shown as awaiting calculation instead of a misleading zero-percent failure.

Bookings And Due Dates

  • Flights are bookable by default, matching hotels, including inbound flight segments.
  • Explicit Operations task due dates update immediately. Template-relative dates continue to follow the tour start date.

Reliability

  • Applying a combined template validates all selected Operations, checklist, and materials definitions before writing and reports any partial outcome accurately so it can be retried safely.
  • Checklist saves remain successful even if the follow-up Operations refresh fails, and a concurrent newer preparation calculation no longer produces a false refresh error.