How to use the Trip Manager

The Trip Manager is the control center for saved trips.

Use it when you want to understand what your current workspace is, save it, switch to another trip, or clean up older versions.

The main question this modal answers is:

Am I working in a scratch draft or a saved trip, and what will happen if I save, load, duplicate, rename, or delete something?

What this modal is for

Open Manage My Trips from the header menu, then use My Trips to:

start a new trip
save the current workspace
search your saved trips
load another saved trip into the workspace
rename a trip
duplicate a trip into a new branch
delete a trip you no longer need

It also explains what is saved in this browser and what is not shared to other browsers or devices.

Step 1: Read the header status first

Before touching any buttons, read the status line in the header.

It tells you:

which user/session is active
whether the current workspace is saved or unsaved
whether the workspace matches the active trip

These signals tell you whether the next save action will update an existing trip or create a new saved trip.

Step 2: Use the top action buttons deliberately

The top-left toolbar gives you the two main actions:

New Trip
Save and/or Save As...

Button: New Trip

Use New Trip when you want to leave the current trip behind and start fresh.

Use it when:

you want a new planning workspace
you want to switch to a different route or concept
you do not want to keep editing the current trip

If the current workspace has unsaved changes, the Trip Manager may ask whether you want to save before continuing.

Button: Save

If the current workspace is backed by a saved trip, the button is Save.

Use it when:

you want to update the current saved trip with your latest workspace changes
you are continuing the same plan rather than making a new branch

This updates the active saved trip instead of creating another one.

Button: Save As...

If the current workspace is a Scratch draft, the save action is Save As....

Use it when:

you want to turn the scratch draft into a saved trip
you want to preserve the current workspace before loading something else

This creates a new saved trip rather than overwriting an existing one.

Step 3: Use search when the list gets crowded

The search field on the right filters trips by name.

Use it when:

you have many saved versions
you remember part of the trip name
you want to narrow the list before loading, renaming, or deleting

If the search returns nothing, the modal will show No matching trips rather than hiding the fact that other saved trips still exist.

Step 4: Pay attention to the workspace status panel

The panel under the toolbar tells you whether the current workspace is:

Saved trip
Scratch draft

That distinction matters because it changes what saving and loading mean.

Use it to answer:

am I editing a saved trip
or am I still in an unsaved draft

If the panel says Saved trip, Save updates that saved trip.

If it says Scratch draft, the current work stays temporary until you save it with Save As....

Step 5: Read the Storage help box

The Storage help section is one of the most important warning areas in the modal.

It explains:

Saved here: trips, planner inputs, and route files stay in this browser on this device
What survives: refreshing or closing the app keeps your workspace and saved trips available here
What does not: trips do not sync across browsers, profiles, or devices in v1
Risk to avoid: clearing this site’s browser data or using private browsing can remove saved access

Use the Storage help box as this rule:

saved trips stay in this browser on this device
they do not sync across browsers or devices in v1
clearing site data can remove them

Step 6: Use the trip row actions carefully

Each saved trip row shows:

trip name
short trip ID tag
active badge when relevant
last updated time
action buttons

The main row actions are:

Load
Rename
Duplicate
Delete

Button: Load

Use Load when you want to replace the current workspace with that saved trip.

Important: Load replaces the current workspace.

If the current workspace contains changes you want to keep, save them first.

Load is the right action when:

you want to continue working on that exact saved trip
you want to compare another saved version
you are returning to prior work

Button: Rename

Use Rename when the trip itself is still the same plan, but the current name is no longer clear or useful.

Use Rename when:

the route stays the same but the name is no longer clear
several saved versions need clearer labels
you want the list to be easier to scan

Rename changes the label, not the underlying trip content.

Button: Duplicate

Use Duplicate when you want to branch into a new version without overwriting the original.

Use it when:

you want to try a different campsite layout
you want to compare two versions
you want to test different inputs without losing the original trip

Use Duplicate instead of overwriting when you still need the original trip for comparison.

Button: Delete

Use Delete only when you are sure the trip is no longer needed.

The delete confirmation explicitly warns:

Delete trip
This cannot be undone

So treat delete as cleanup, not as a casual version-management tool.

Step 7: Understand the unsaved-changes warning

If you try to leave the current workspace by loading another trip or starting a new one while unsaved changes exist, the Trip Manager may stop and ask what you want to do.

The modal gives you three choices:

Save and/or Save As...
Continue Without Saving
Cancel

Use them like this:

choose the save option if you want to preserve the current workspace first
choose Continue Without Saving only when you are comfortable discarding the current unsaved state
choose Cancel if you want to stop and think before switching contexts

This warning prevents accidental loss of unsaved work.

Step 8: Understand the delete confirmation

If you choose Delete, the modal shows a dedicated confirmation panel before removing the trip.

Use this confirmation to check:

this is the correct trip
you do not need it for comparison later
you are not deleting the only saved version you still need

Recommended order

Use this sequence:

Read whether the current workspace is a saved trip or a scratch draft.
Save the current workspace before switching away if the changes matter.
Use Load to reopen prior work.
Use Duplicate before making major experimental changes.
Use Rename to keep versions understandable.
Use Delete only for cleanup after you are sure a version is no longer needed.

Common mistakes this modal helps avoid

Watch out for these:

loading another trip before saving the current scratch draft
overwriting the active trip when you really meant to branch with Duplicate
assuming saved trips sync across browsers or devices
using private browsing or clearing browser data and expecting saved trips to survive
deleting a trip that you still needed as a comparison point

What to do next

After you understand the Trip Manager, continue with: