Trip statuses show where a trip is in your process. They appear on the Trips list, on each trip's own page, and on your dashboard, and you can filter trips and the calendar by them.
TripLoft ships with Draft, Active, Booked, Traveled, Paid, Canceled, and Archived. You can adapt that list to match how your agency actually works. Go to Settings > Trip Settings and click Edit.
What you can and can't change
Three statuses are marked System Controlled with a lock icon: Draft, Canceled, and Archived. TripLoft sets these automatically as part of how trips work, so they can't be renamed or removed. You can still drag them to reorder the list.
Everything between them is yours:
Rename a status by typing in its field.
Reorder by dragging the handle on the left.
Remove one with the trash icon.
Add a new one with Add Status at the bottom.
Click Save when you're done.
Renaming a status
Existing trips keep their status and simply display the new name. Nothing moves and nothing is reassigned.
TripLoft asks you to confirm, because a rename reaches two other places:
Automations triggered by that status are updated to the new name, and any active ones stay active.
Workflows using the status in an auto-apply condition are updated to the new name, but if auto-apply was enabled, it gets switched off. Turn it back on once you've checked the workflow still does what you want.
Deleting a status
You can delete a status even when trips are using it. The dialog asks you to pick a replacement first, lists the affected trips by name so you can see exactly what's changing, and reassigns them all when you confirm.
The knock-on effects are heavier than a rename:
Automations triggered by that status are updated to the replacement, but any active automations in your templates or inside an affected trip are set to inactive. You'll need to reactivate them yourself.
Workflows using the status in an auto-apply condition are updated to the replacement, and auto-apply is disabled if it was on.
Good to know: Trigger workflows for status change is off by default, so the reassignment happens quietly. Turn it on and every affected trip is treated as a real status change, firing any workflows that watch for it. On a large group of trips that can be a lot of activity at once.
