How to Log a Trip While You're Still On It

There is a particular silence that falls about three weeks after you get home. Someone asks what the trip cost, or what that small restaurant near the cathedral was called, and you find that you genuinely do not know. You were there. You have four hundred photos. The answer is gone anyway.

Most of what we have written here is repair work — rebuilding a travel log retroactively from receipts, photo libraries and old passports. That method works, and if you have twenty undocumented years behind you it is the only option available. But it is expensive. Budget an evening per year of travel, and accept that the result will always be thinner than the thing itself.

This article is about the other end of the problem: not creating the debt in the first place. What to write down while you are still standing in the place, how long it honestly takes, and where our own app helps you versus where it simply makes you type.

The window is much shorter than it feels

Hermann Ebbinghaus mapped the decay of memory in the 1880s by memorising nonsense syllables and testing himself at intervals. His curve is brutally steep at the start: a large majority of the material is gone inside the first day, after which the remainder fades slowly. A 2015 replication by Murre and Dros reproduced his numbers closely enough to confirm the shape holds (Murre & Dros, PLOS ONE, 2015).

Be careful with that finding, though. Ebbinghaus was memorising meaningless syllables, not walking around a temple in the heat with someone he loves. Lived experience is far stickier than a random three-letter string, and nobody should claim a holiday evaporates in 24 hours. What does behave like a nonsense syllable is the detail: the name of the guesthouse, the number on the receipt, the code of the airport you connected through at 6am. Those are arbitrary tokens attached to a vivid experience, and they go first, quietly, while the experience itself stays.

That is the practical lesson. You do not need to record how the trip felt — you will keep that for years. You need to record the arbitrary parts, and you need to do it before the end of the day.

The four things that decay fastest

After doing this on our own trips and rebuilding several from scratch, the same four items are always the ones missing:

• Exact names. "That seafood place" is not recoverable. The full name is, if you write it once.
• Amounts, with the currency you actually paid in. More on this below — it is the item people most confidently believe they can reconstruct, and most reliably cannot.
• Airport codes and routing. Layovers vanish from memory almost immediately because they do not feel like places. We have written separately about how to log every airport you pass through, and the retroactive version of that job is genuinely tedious.
• One line on why it mattered. Not a diary entry. One sentence. "Booked because the ferry was cancelled" is worth more in five years than three paragraphs of scenery.

Everything else — the shape of the days, who you were with, the weather — you will still have.

Money is the one thing you cannot reconstruct

The common assumption is that the card statement is a backup, so amounts can wait. It is not a backup, for three reasons.

First, the conversion happens at the wrong moment. A card transaction in a foreign currency is converted when the merchant's bank submits it for processing, using the rate in effect on that processing date — not the date you handed over the card. If you buy dinner on a Friday and the restaurant batches its transactions on Monday, you are charged at Monday's rate (NerdWallet on why statement rates do not match the rate you looked up). Your issuer's foreign transaction fee and margin are then layered on top. The number on the statement is a real number, but it is not the number you experienced.

Second, the description is useless. "SumUp *8812 LISBOA" tells you nothing about which of the six meals it was.

Third, cash is entirely invisible. Every market, tip, taxi and entry fee paid in notes leaves no trace at all unless you write it down at the time.

Recording the amount and currency on the day fixes all three. In MapMyWorld the expense form defaults its date to today and lets you pick the currency and whether it was card or cash (client/src/components/trips/expense-drawer.tsx), and the server converts to your home currency using the European Central Bank reference rate for that specific date, fetched per expense (server/currency.ts). Our longer piece on what trips actually cost goes into the per-day currency handling in more detail.

Photos are a safety net, not a record

Your phone is already logging two of the four items for you. Every photo carries a capture timestamp, and if Location Services is enabled for the camera it carries coordinates too — visible by swiping up on the image or tapping the info button (Apple: see photo and video information on iPhone). That is a genuinely useful fallback, and it is the backbone of the retroactive method.

But note what it does not give you: no name, no price, no reason. And it is conditional — if you have turned camera location off, which Apple documents as a one-switch change under Location Services, the coordinates were never written in the first place (Apple: manage location metadata in Photos). Plenty of people have done exactly that on purpose, which is a position we have some sympathy with — we make the case for an app that does not follow you around elsewhere.

Treat photos as evidence you can mine later, not as the record itself.

The four-minute pass

The method is deliberately small, because a method that takes twenty minutes will be abandoned by day three.

Once a day, usually while something is charging:

1. Add the places you went to by name. Not every corner — the ones you would mention to someone. Two or three a day is normal.
2. Enter the day's spending, in the currency you paid. Card and cash both. If you are unsure of a cash amount, put in your best estimate and move on; an estimate entered today beats a certainty invented in March.
3. Add one line of context to anything unusual. Why you changed hotels. Why the bus cost triple.
4. If you flew, add the airports — including the one you only sat in.

That is it. There is no step five, and there is deliberately no daily journal prompt.

How this works in the app

A few mechanics are worth knowing, because they remove most of the friction:

• The trip switches itself on. A trip with a start date moves from planned to ongoing on its own, and to completed once the end date passes, via a daily job (server/jobs/tripStatusTransition.ts). You are not maintaining a status field by hand.
• It works with no signal. Places added offline go into a local IndexedDB queue and are sent the moment you reconnect (client/src/lib/pending-places.ts). This matters more than it sounds: the four-minute pass usually happens somewhere with bad wifi.
• Notes and per-trip task lists live in a drawer on the trip, and are a Pro feature (shared/schema.ts, TIER_LIMITS).

What it will not do

We would rather you know this now than discover it on day four.

• There is no background capture of any kind. Nothing is recorded unless you type it. That is a deliberate design decision, not a missing feature, but it does mean the method above is the product — there is no passive mode to fall back on.
• The offline queue needs a name. You have to type something for the place; it cannot resolve an unnamed pin without a network round trip.
• The Free plan is a demo, not a trip companion. It allows 5 places — a lifetime allowance, so deleting one does not free the slot — plus 10 countries, 1 trip, 10 airports and 1 friend. A single real two-week trip will exhaust it. Pro is $7.99 a month, $59.99 a year, or $199.99 once for lifetime access.
• Our exchange rate is not your bank's. We use ECB reference rates, which are mid-market. Your card's rate includes a margin and possibly a fee, so our home-currency figure will sit slightly below what your statement eventually says. For weekends and dates the ECB has not published, the code falls back to the current rate (server/currency.ts). Treat the converted total as a good comparative figure, not an accounting record.
• Photo uploads are Pro only.

What you get back

The reason to spend four minutes a day is what exists at the end of it. Because the amounts carry dates and categories, the trip page can show your daily spend across the days actually elapsed rather than a flat average, a second figure with flights and accommodation stripped out — which is the number that tells you whether the destination is expensive or your flight was — and a card-versus-cash split (client/src/pages/trip-detail.tsx).

None of that is available to a trip logged from memory in March. The categories will be guesses, the dates will be wrong, and the cash spending will be missing entirely.

The trip is going to happen either way. Four minutes a day decides whether you still have it in ten years.

Start your record — free.