Why the group chat always loses the booking

Group chat trip planning breaks in the same four ways every time. Here is why a chat thread cannot hold a trip, and what to move into instead.

Leo BjörklundCEO at Deline7 min read

Group chat trip planning always starts well. Somebody sends a photo of a place, everyone agrees it looks incredible, dates get thrown around, and for about four days the thread is the most fun conversation you are having. Then somebody books something, and the group chat quietly stops being a planning tool and becomes an archive nobody can search.

This is not a complaint about WhatsApp. A group chat is a brilliant place to decide things and a terrible place to keep them, and the difference between those two jobs is the whole reason every group trip ends up with the same four problems.

The four ways group chat trip planning breaks

1. The scroll problem

A group chat is sorted by when something was said, not by when it happens. So the hostel confirmation someone posted six weeks before the trip is at the bottom of nine hundred messages, below a hundred memes and an argument about which airport is worse.

People work around this by screenshotting things, which is the tell. A screenshot is somebody manually copying information out of the thread because they know they will never find it again - and now the group has two copies, one of which is wrong the moment the booking changes.

2. Nothing is authoritative

In a thread, "I've booked the Rome place, 4 nights, arriving the 12th" and "we could do 4 nights in Rome from the 12th?" are the same shape of message. Both are grey bubbles. There is no difference in the interface between a fact and a suggestion, so the group has to remember which was which.

That is the source of the specific dread of the night before a trip, when somebody asks whether the airport transfer was actually booked and four people scroll in silence.

3. There is no shared state, only shared messages

This is the deep one. A chat does not hold a plan; it holds an argument about a plan, in chronological order, and each person builds their own private model of the trip out of it. Those models are always slightly different, and nobody discovers the difference until you are standing somewhere.

A shared document is the usual attempted fix, and it half works. The doc is accurate exactly as long as one person keeps updating it, which is until they get busy. Then it is a stale document that people trust, which is worse than no document.

4. The money never resolves

Numbers in a chat are the worst of all of it. "I paid for the taxi, it was 34" is real information, it scrolls away in an hour, and it will be needed in eleven days. Nobody keeps a running total. At the end, one person volunteers to work it out, spends an evening on a spreadsheet, and gets it slightly wrong in their own disfavour.

How to split costs on a group trip is the longer answer, but the short one is: the numbers have to live somewhere that adds them up.

What to move out of the chat

Not the chat itself. The banter is the point of a group trip and no app is going to replace it - trying to move a group off WhatsApp entirely is how good tools die. Move three things:

  • Anything with a time on it. Trains, check-ins, reservations, the flight. Those belong on something that sorts by when they happen, not by when they were mentioned.
  • Anything with a booking reference. The reference is the thing somebody needs at 11pm at a reception desk, and it should take one tap to find, not a scroll.
  • Anything with a number on it. Every shared cost, the moment it happens, in something that keeps a total.

What stays in the chat: deciding. Arguing about the route, sending the photos, agreeing what to do tomorrow. That is what threads are good at.

The proposal problem, and how to fix it cheaply

The one thing groups genuinely lose when they move the plan out of the chat is the ability to float an idea. In a thread you can say "what about a day trip to Tivoli?" and it costs nothing. In a rigid itinerary tool, adding it means putting a thing on the plan that is not really on the plan.

The fix is for the plan itself to be able to hold a maybe. In Deline that is a proposal: it sits on the timeline as a dotted branch with a hollow stop, so it is visibly not booked. Anyone can add one, everyone can see it, and when the group agrees it joins the line properly. It keeps the low-stakes suggesting that makes a chat useful, without the ambiguity that makes it dangerous.

Making the move without annoying everybody

The reason groups stay in the chat is not that they think it works. It is that moving costs something and the cost lands on the person who suggests it. Three things make it stick.

  1. Do it before the first booking, not after the third. Backfilling is what kills it.
  2. One link, no setup. If joining takes more than a tap and a name, half the group will do it "later" and one person never will. That person will then ask the chat where everyone is staying.
  3. Post the link in the chat and then use it yourself. The first three things you add are what convinces everyone else it is worth opening.

That is really all it takes. The group chat keeps doing what it is good at, and the trip stops living in it. The group trip planning checklist covers what else is worth sorting before you go.

Questions people ask

Why is a group chat bad for planning a trip?

A group chat is ordered by when something was said rather than when it happens, so bookings get buried. It also cannot distinguish a confirmed plan from a suggestion, keeps no shared state that everyone can trust, and never totals up the money.

Is a shared Google Doc better than a group chat for trip planning?

Slightly, and only while somebody maintains it. A doc gives you one place to look, but it goes stale the moment its owner gets busy, and a stale document that people still trust is worse than no document.

What should stay in the group chat?

Deciding things. Arguing about the route, sending photos, agreeing what to do tomorrow. Move out anything with a time, a booking reference or a number on it, and leave the conversation where it is.

How do you get a whole group to actually use a trip planning app?

Start before the first booking, pick something that people join from a single link without setup, and add the first few things yourself. Groups do not resist the app, they resist the effort of moving, so remove the effort.

Android

Android is on its way.

Deline is on iPhone first. Leave your name and email and you might get the chance to be one of the first Android testers.

Used for Android and nothing else, then deleted. The privacy page says how to be taken off.

Tripline is now