One Trip or Two? Four Rules for Where a Trip Ends and the Next Begins

You flew to Lisbon for a three-day conference, then stayed on for a week in the Algarve. Your partner flew out to meet you on day four. Is that one trip or two?

Most people never ask. They log whatever shape the booking had, and the question only surfaces years later, when the numbers stop making sense: a "trip" that cost £3,000 over ten days, half of it paid by an employer, with a daily average that describes neither the conference nor the beach.

Where one trip ends and the next begins is a real decision, and it is worth making once, on purpose, before you have fifty trips in your record. This article gives you four rules that settle almost every case, a short list of awkward cases and how the rules handle them, and the reason the choice matters more than it looks.

Why the boundary matters

A trip is a container. Everything you attach to it inherits its edges: the dates, the places, the airports, the money. Get the edges wrong and every figure computed from them is wrong too, quietly.

Three things break first.

Daily averages. Any per-day spending figure divides a total by a number of days. Merge a four-day work trip into a ten-day holiday and the average now blends hotel rates you chose with hotel rates someone else chose. Neither half is readable any more.

Comparisons. The point of a long record is being able to say "Porto was cheaper than Seville" or "we always overspend on the first two days". That only works if each trip is a like-for-like unit. A trip that is secretly two trips is an outlier in every comparison you run.

Memory. When you scroll back through your history, the trip name is the index. "Portugal 2026" tells you less than "Lisbon conference" and "Algarve with Sam", and it hides the fact that the second one happened at all.

There is outside precedent for taking the boundary seriously. Two institutions that care about money draw it carefully. Tax rules treat a mixed business-and-leisure trip by counting days: under US rules, a trip counts as primarily business only when business days outnumber personal ones, and that classification decides whether the airfare is deductible at all. Annual travel insurance draws the line at home: trip length is counted from the day you leave to the day you get back, many policies cap a single trip at 31 days, and on some policies a trip that runs over the cap is not covered at all. Neither of those rules is about your travel record, but both show the same thing: the boundary you pick changes the numbers you get.

Rule 1: Going home ends the trip

The cleanest rule, and the one that settles most cases on its own: a trip ends when you sleep at home.

Fly to Rome, come home, fly to Athens three weeks later: two trips, however close together. Spend six weeks moving through Southeast Asia without coming home: one trip, however many countries and flights it involved. Home is the one boundary nobody argues about, and it matches the way insurers count.

"Home" means where you normally live. If you live abroad, home is your current base, not the country on your passport. A weekend trip from your flat in Berlin to Prague is a trip; flying back to see your parents in Manchester is also a trip, even though you might call it "going home".

Rule 2: A change of purpose starts a new trip

The Lisbon case is where Rule 1 is not enough. You never went home, but the trip changed character on day four: who paid, who you were with, why you were there.

When the reason for the trip changes, split it. A conference followed by a holiday is two trips that happen to share a flight. A wedding followed by a week of exploring is two trips. A family visit followed by a solo city break is two trips.

The test is simple: would you describe the two halves differently if someone asked? If you would say "I was there for work, then I stayed on", you already think of it as two trips. Record it the way you think of it.

Splitting also keeps the money honest. The conference half can hold the expenses you paid and will claim back; the holiday half holds what you actually spent of your own. A few weeks later, the holiday's daily figure tells you something true about the Algarve.

Rule 3: A change of company starts a new trip, if it changes the trip

Your partner arriving on day four is a softer signal than a change of purpose, but it often comes with one. The hotel changes, the pace changes, the budget is suddenly shared.

If the people you are travelling with change and that changes how the trip runs, split it. If a friend joins you for two dinners in the middle of a solo month, it is still one trip: their visit is a note on a few places, not a new container.

This rule is the least strict of the four, and it should be. Its job is to stop a trip from containing two incompatible spending patterns, not to create a new trip every time someone joins you for lunch.

Rule 4: Very long stretches get cut at natural seams

A gap year, a six-month sabbatical, a long working stint abroad: Rule 1 says these are one trip, because you never went home. Sometimes that is right. Often it produces a single container so large it stops being useful.

If a single trip would run past about a month, look for a natural seam and cut there. Good seams are a change of country or region, a change of mode (the overland stretch versus the island-hopping stretch), or a stretch where you stopped moving and simply lived somewhere.

That last case may not be a trip at all. Three months renting a flat in Mexico City and working remotely is closer to living somewhere than visiting it. That distinction is covered in more detail in what each place status does to your record.

The month threshold is not magic. It is roughly where insurers start charging differently, and roughly where a single daily average stops describing anything you would recognise.

The awkward cases

Most trips fall straight out of Rule 1. These are the ones that do not.

The day trip from a base. You are in Lisbon for a week and spend a day in Sintra. Same trip: you slept in Lisbon. Sintra is a place within the trip, not a trip of its own.

The overnight layover. You fly London to Sydney with a night in Singapore. One trip. The layover airport belongs to the trip; Singapore as a country is a separate decision, governed by whatever rule you use for what counts as visiting a country.

The commute that became a habit. If you are in Brussels every other week for work, recording each visit as a trip is honest but noisy. Either log each one consistently, or log the first and add the later ones as dated notes. Pick one approach and stick to it.

The trip that went home in the middle. You went to Spain for two weeks but flew home for three days in the middle for a funeral. Rule 1 says two trips. If that feels wrong because the two halves were a single plan, keep it as one and note the gap: the rules exist to make your record readable, and you are the reader.

The road trip across borders. One trip, because you never went home, however many countries it crosses. How to record each country without losing the thread is covered in how to log a road trip that crosses six countries.

Writing the rule down

The rules matter less than applying them the same way every time. A record built on a rule you change every year is harder to read than one built on a rule you disagree with but kept.

So write your version down, in one or two lines, somewhere you will see it the next time you log a trip. For example:

A trip ends when I sleep at home, or when the reason for being there changes. Anything over a month gets cut at a change of country.

Then, when a case comes up that the rule does not settle, decide it, and add a line. After a dozen trips the rule stops growing.

How this works in MapMyWorld

In MapMyWorld a trip is an explicit container with its own start and end dates, and the boundaries you choose shape everything the app shows about it.

Each place you log can belong to one trip, and the trip page lists the places attached to it in date order (shared/schema.ts, places.tripId; server/storage.ts, getTripPlaces). That is why splitting the Lisbon conference from the Algarve holiday matters: Sintra belongs to one, Lagos to the other, and each trip page reads as its own story.

Expenses belong to a trip too, and the trip page divides the total by the trip's days to give a daily figure, plus a second figure with flights and accommodation removed, which shows what the destination itself cost (client/src/pages/trip-detail.tsx). Both are only meaningful if the trip has one purpose. For sorting individual costs within a trip, see seven rules for sorting travel spending.

Every trip also carries a trip type, from Business Trip and Family Vacation to Weekend Getaway and Around the World, and a transport mode (client/src/components/trips/TripFormDialog.tsx). Those labels are what make Rule 2 visible later: a split conference-and-holiday shows up as one Business Trip and one Beach Holiday, rather than a single trip that is neither.

Departure, arrival and layover airports are recorded against the trip they belong to (server/routes/trips.ts), so a well-placed boundary also keeps your airport log readable. The detail is in how to log every airport you pass through.

The Free plan holds one trip; Pro, from $7.99 a month, removes that limit, which is when splitting trips the way these rules suggest becomes practical across a whole history.

The short version

• A trip ends when you sleep at home.
• A change of purpose starts a new trip.
• A change of company starts a new trip only if it changes how the trip runs.
• Anything longer than about a month gets cut at a natural seam.
• Whatever rule you pick, write it down and apply it the same way every time.

Go back to the last trip you logged that mixed work and leisure. If it is still one container, split it and look at the two daily figures side by side. That comparison is usually the moment the rule stops feeling fussy.