The New Kind of Music Travel
People used to drive an hour for a show. Now they fly across an ocean.
The Eras Tour reset what the average fan considers a reasonable distance for a concert. Americans booked Stockholm and Warsaw because the European dates were cheaper than the domestic ones, even with the flights. Beyoncé's Renaissance run pulled the same trick. Vegas residencies have made the city a permanent music destination, with U2 at Sphere, Adele at the Colosseum, and Silk Sonic before that all turning a weekend in Nevada into the whole point of the trip. Glastonbury still draws over 200,000 people a year, most of them traveling from somewhere else. Phish fans have built three-show summer runs into a 30-year tradition, and the band's annual New Year's run in New York is now its own micro-tourism economy.
This is not a quirk anymore. Gig-tripping is a subculture with its own vocabulary, its own forums, its own spreadsheets shared in group chats. A 2024 survey from a major ticketing platform put the share of U.S. concertgoers who had traveled out of state for a show in the last year at roughly 1 in 3. The number for fans under 35 was closer to half.
And here is the problem nobody warns you about: the bigger the trip, the harder it is to remember.
Why Documenting a Music Trip Is Different From Documenting a Show
A single show has clear bookends. You showed up, the lights went down, the band played, you went home. The whole thing fits inside one evening, and your brain stores it that way.
A trip does not have bookends. It has a fuzzy start (the airport? the first beer? the moment you walked into the first venue?) and a fuzzier end (the last show? the cab to the airport? the flight where you actually crashed?). Three shows in five days bleed into each other. The cities bleed into the shows. By the time you are home, you cannot remember which night the encore went long, which city had the better opener, or which bar you ended up at after which gig.
The risk on a music trip is not forgetting any one set. It is losing the through-line. The shows survive because they were loud and obvious. What disappears is everything between them.
The Trip as One Chapter, Not Four Entries
Here is the position this whole piece is built on: a music trip is a single memory unit with multiple shows as beats inside it. Not four disconnected concerts that happened to land in the same week.
If you treat your trip like four floating entries, you lose the trip. You will have four solid concert logs and no record of the actual experience that made you book the flights in the first place.
So the structure is simple. Log each show. Then log the trip itself as its own separate entry, a chapter that holds the things that do not belong to any single night. The trip entry is where the flight playlist lives. The friend you went with. The city you ate in. The morning you got lost trying to find coffee. The bar across from the venue that became your bar for the week. None of that fits cleanly inside a setlist log, and if you do not give it its own container, it evaporates inside a year.
Four show entries plus one trip entry. That is the framework. Everything else is detail.
What to Capture That Isn't the Show
These are the memories that disappear fastest, because they do not have an obvious place to go. They are also the memories that, five years later, you will care about more than the setlist.
Capture these for the trip:
- The flight playlist you made the night before takeoff that you still listen to. Screenshot it. Save the link. This is the soundtrack of the trip, and you will forget what was on it within a month.
- The pre-show bar. Not the venue, the bar. The one with the wrong wallpaper where you ate fries before the doors opened. Write down the name.
- The walk to the venue. What neighborhood, what time, what the weather did. One sentence is enough.
- What you ate after. Late-night food is half of why people travel. Log it.
- The merch you bought and the merch you almost bought. The almost is the better story most of the time.
- The people. Who you went with, who you met in line, the couple at the next table who flew in from somewhere weirder than you did.
- The morning after. The breakfast the morning after the last show where you and your friend were too tired to talk about it yet. That silence is the trip.
None of this is a setlist. All of it is the trip.
Per-Show Capture Without Killing the Vacation
This is where most people overshoot. They decide they are going to document everything, then they spend the whole vacation typing into a phone, and by show three they have given up entirely and have nothing.
The rule we use, and the one that actually survives a real trip, is 90 seconds per show. On the walk to dinner after the show, before you sit down, you open your phone and log five fields. Five. Not fifteen.
- Opener and headliner
- One song that hit harder than expected
- One detail from the room (the crowd, the venue, the lighting)
- Where you were standing
- Who you were with
Then the phone goes away for the rest of the night. You eat. You drink. You argue about the encore. You do not document while it is happening.
This is the position: documentation that kills the trip defeats the entire purpose of the trip. The discipline is brevity. If your system asks for more than 90 seconds in the moment, your system is broken, and you will quit using it by night two.
This is also the case for a Snapshot journal on a trip specifically. It is lighter, lower stakes per entry, and built for exactly this kind of fast capture. You are not writing an essay. You are dropping a flag in the ground so future-you can find the memory again. The Concerts Remembered app does the same job in one tap when you are too tired to write, which on a multi-city trip is most nights.
The classic concert journal still has a place on a music trip, but it is not the per-show tool. It is the recap tool, which we will get to in a minute.
The Travel Diary Layer
Every show on a trip happens in a specific city, and the city is part of the memory whether you log it or not. The trick is logging the geographic anchors deliberately so the trip becomes retrievable years later.
The format is short. For each show, add one line that ties the music to the place:
"The show was at Roundhouse in Camden, the bar after was The Hawley Arms, we got the last tube back."
That is the entire entry. Venue, neighborhood, the bar that became the after-spot, one logistical detail that places you in the city. You do not need more than that. What you need is the specificity, because "we saw a great show in London" will not bring anything back in five years, and "we walked from Roundhouse to The Hawley Arms and barely made the last Northern Line train" will.
Do this for every city. Three shows, three of these lines, plus the trip entry that holds the connective tissue. That is the geographic skeleton of the trip.
A useful sibling piece to read alongside this is our Concert Bucket List guide, which is the aspirational version of the same idea. The bucket list is what you are dreaming about. This piece is the field guide for when you actually go.
The Trip Recap: One Page That Holds It All
On the flight home, you owe yourself one page. Not a journal entry per show, those are already done. One page that holds the whole trip.
This is the page you will actually re-read. It is also the page that is worth doing in a classic Concerts Remembered journal instead of on a phone, because the deeper entry deserves the slower medium.
The one-page recap has five things:
- Best set of the trip. Just one. Force the choice.
- Most surprising city. The one you did not expect to love, or the one that let you down.
- The one moment you will tell people about. The story that is going to come out at dinner parties for the next two years. Write it down before you tell it ten times and it calcifies into a bit.
- The thing that made you decide to do this again. Because you will. Name what hooked you so you can chase it next time.
- What you would do differently. Logistics, timing, the show you should have skipped to actually sleep. The note to your future self planning the next one.
Five prompts. One page. Done before the plane lands.
This works as a companion to our 5-Minute Post-Concert Rule, which is the same principle applied to a single show. A trip just stretches the rule out: 90 seconds per show in the moment, one page on the way home.
The Repeat Trip Problem
If you saw the Eras Tour in Paris, Stockholm, and London, you have a problem. Three cities, same setlist, and somehow each one feels completely different. How do you keep the entries distinct so they do not collapse into one blur six months later?
The answer is structural. Do not lean on what was the same about the show, because the show was the same. Lean on what was different about the city.
For each city, force yourself to name three things that were unique to that night. Not the songs. The crowd, the room, the weather, the bar after, the friend who flew in for that one city, the conversation in line, the way the closer hit at midnight in a place you had never been before. The setlist is the constant. The city is the variable. Document the variable.
This is also why the trip-as-chapter framework matters most for repeat trips. The chapter holds what the individual entries cannot, which is the cumulative feeling of seeing the same band light up three different rooms in three different countries in five days. That feeling does not live in any single show entry. It lives in the trip.
For the bigger picture of how all of this stacks up over time, our piece on building a concert archive gets into the long-term system. And if you want to see how a multi-city trip compares to the average concertgoer's year, How Many Concerts Does the Average Person Attend Per Year puts the numbers in context.
FAQ
What counts as concert tourism?
Any trip where the show is the reason you went, not a thing you tacked on. If you flew to Vegas because U2 was at Sphere and you would not have gone otherwise, that is concert tourism. If you happened to be in Vegas for a wedding and caught a show, that is not. The distinction matters because the documentation approach is different. A music trip needs its own chapter. A show on a non-music trip is just a show entry inside whatever you were already doing.
How many shows is a music trip?
Two or more in a planned sequence, in our opinion. One show in another city is a trip with a show in it. Two or more, especially over consecutive nights, becomes a sequence, and a sequence needs the trip-as-chapter framework or it collapses into a blur.
Should I document during the show?
No. The 90-second rule happens after, on the walk to dinner. Documenting during the show pulls you out of the show, which is the one thing you flew across a country to be inside of. Trust your memory for the next two hours after the lights go down, then capture the five fields before you eat.
What if I miss a show in my log?
Backfill it the next morning, fast, before the next show overwrites it. Three fields are better than zero. Opener, one song, one detail from the room. Do not try to reconstruct the whole night a week later from photos. You will lose the texture and you will write something generic. Catch it in the morning while the coffee is still cold.
Do I need a separate journal for trips?
Not separate, but a lighter format helps. The Snapshot journal exists for this exact use case, fast entries that do not demand a full-page reflection per show. The full journal is better suited to the trip recap on the flight home, where the page deserves the weight. Use both if you have them, the light one in the city, the deeper one on the way back.
What is the single most important thing to capture?
The connective tissue. The bar across from the venue, the train you took, the friend who flew in for that one city, the breakfast where nobody could talk yet. These are the details that vanish first and matter most. The show is loud and you will remember it. The 11 a.m. coffee after night three is what makes the trip feel like a trip, and it has the shortest shelf life in your memory.
How do I handle festivals like Glastonbury or Bonnaroo?
Treat the festival itself as the chapter, and individual sets as the beats. You will see 15 acts in three days. You cannot log them all in full, and trying will ruin the festival. Pick a top three each day, log those at 90 seconds each, and write the festival recap on the flight or train home. The festival entry holds the camping, the friends, the weather, the food line at 1 a.m. The set entries hold the music. Same framework as a multi-city trip, just compressed.
What about residency trips like Vegas?
Same framework, easier execution. You are in one city, often one room, often back to back nights of the same act. The repeat-trip problem applies hard, because the setlist barely changes night to night. Lean on what was different each night: the crowd, your seats, the conversation at the bar between sets, the night a guest came out. The city stays constant, so the variation lives inside the room. Document that.
Share: