A trip with several people almost always starts in a group chat. Three destination ideas, two polls, a rental link lost under forty messages, and one question that keeps coming back: "wait, who booked the tickets?"
Here's how to set up that trip in a single Flots project, shared with every traveler, from choosing the destination to packing.
Create a shared "Trip" project with every traveler
A trip has a start, an end and dozens of details to sort out in between. A Flots project gives it a space of its own, with its tasks, notes, documents and milestones.
Create the project, then add each traveler using the email of their Flots account. The Editor role lets them read and write everywhere in the project. The Reader role is for someone who follows without organizing, parents who just want the itinerary, for example. A Reader can still be assigned a task: they can tick it off, but not edit it.
One thing to check before sending the invitations: the project owner's plan is the one that counts. The Individual plan includes 3 shared projects, with up to 3 collaborators per project on top of you. For a larger group, the Pro plan includes unlimited shared projects and collaborators.
How roles and invitations work is explained in the guide working together in a shared project.
Choose the destination on a whiteboard or in a note
Choosing the destination works better outside the chat thread. Two options, depending on your group.
The whiteboard, for those who think in a jumble. Attached to the project, several people can draw on it live: each person drops their suggestion in a block, pastes a screenshot of the rental they spotted, links the ideas that go together. Images dropped on the whiteboard are also added to the project's documents.
The note, for those who want to compare. A table with one row per destination and a few columns: travel time, estimated budget, what appeals to whom. Several people can fill it in at the same time, and a banner at the top shows who's there.
Either way, the discussion stays in the same place as the rest of the planning. Nobody has to scroll back up the thread to find out why Sicily beat the Cyclades.
Split the tasks: tickets, lodging, insurance, activities
Once the destination is settled, list what needs booking. Each row becomes a task in the project, with a due date and a name.
| Task | Example due date |
|---|---|
| Book the plane or train tickets | As soon as the dates are set |
| Book the lodging | Right after the tickets |
| Check everyone's travel insurance | Before paying for anything non-refundable |
| Choose and book two or three activities | A few weeks before departure |
| Check ID documents | A month before departure |
Put a name on every task. Whoever handles the lodging finds it among their own tasks, and the day they check it off, the rest of the group sees it without having to ask in the chat.
"Activities" hides several bookings: give it one sub-task for diving, one for the guided tour, one for the last-night restaurant. And set a reminder on the lodging's free cancellation deadline, a date that costs money if you let it slip by.
On the calendar side, four dated milestones are enough: destination chosen, transport booked, lodging booked, departure. Every traveler sees on the project card which one comes next. When it shows up as "Overdue:", it's time to nudge the group.
Tickets and bookings: travel documents in one place
Every booking produces a file: PDF tickets, lodging confirmation, insurance certificate. Whoever books it drops it in the project's Documents tab, and the others find it there, without asking for it by message.
Flots accepts PDFs and photos, taken straight from the app on mobile. A PDF opens in preview without downloading, with zoom, and downloads in one tap if you need it elsewhere.
File them in one folder per type: transport, lodging, insurance. On departure day, nobody digs through their email for their boarding pass, even when another traveler received it.
The day-by-day itinerary in a shared note
The itinerary fits in a project note. One heading per day, and under it the arrival time, the route, the booked activity, the restaurant address. Flots notes handle headings, lists, tables and checkboxes.
Each person fills in the day they're in charge of. Whoever booked the diving adds the meeting time, whoever handles transport adds the return train.
Once you're there, it's what everyone checks over breakfast. Pin it: it'll be the first thing shown when the project opens.
The packing checklist, with checkboxes
A second note serves as a checklist. A shared section for what gets split (first-aid kit, adapters, speaker), then one section per traveler for their own things. One checkbox per item.
The shared section settles the duplicates question. If the first-aid kit is checked under Léa's name, nobody brings a second one.
The trip dates in everyone's calendar
Sharing a project doesn't pool calendars: each traveler keeps their own, with their own appointments. There are two ways to get the trip into it.
The first is the dated tasks you've been given: departure, check-in, the cancellation deadline. They're in your list, and you can drag them onto a slot in your calendar.
The second is for groups that already set up a Google calendar for the trip. Connect your Google account to Flots: that shared calendar shows up next to yours, in its own color. The guide several calendars, one color each walks through the setup.
Back home, the project stays there, with the tickets, the itinerary and the checklist. For the next trip, the packing checklist is already written.
Plan your next trip together in a shared project.
Assigned tasks, tickets, itinerary and checklist in one place.


