Proving Where You've Been
A clear record of days, borders, and locations — the kind residency audits, tax filings, and visa checks ask for. Reconstruction is where cases break down.
The answer
If someone later asks where you were — a tax authority, an immigration officer, a court — the answer that holds is the one you can show with records made at the time.
Reconstructing a timeline from email, calendar, and memory usually doesn't survive that kind of scrutiny.
Last updated:
Why it matters
The moments where this matters — a residency audit, a border inspection, a tax question — usually show up long after the fact.
Months later. Sometimes years.
By then, the only record you have is whatever trail you happened to leave: email, calendar, a credit card statement, maybe a passport stamp or two.
That trail has holes. Short stays disappear first. Layovers are the worst — by the time anyone asks, you’ve already forgotten which terminal you spent four hours in, or whether you crossed passport control.
This isn’t a theoretical problem. It’s the everyday failure mode of people who thought they were paying attention.
How it works
The question is usually some version of: where were you on this specific day, how many days did you actually spend in that state, or when exactly did your residence change?
What holds up is a day-level record. Not a month-level guess. Not “I was there most of the summer.” Specific days, specific locations, and — this is the part that matters — made at the time.
There’s no single source that covers everything.
Passport stamps
- Captures
- International border crossings.
- Misses
- Internal movement inside Schengen, the EU, or the US.
Credit card statements
- Captures
- Days with transactions.
- Misses
- Cash days, guest days, most transit days.
Calendar entries
- Captures
- Days with meetings and events.
- Misses
- Every day without one.
Travel bookings
- Captures
- Nights where a flight or hotel was booked.
- Misses
- Day trips, changed plans, someone else's booking.
Entry / exit systems
- Captures
- Border crossings in participating jurisdictions (e.g. EES).
- Misses
- Everything outside those jurisdictions.
Continuous location record
- Captures
- Every day, specific places.
- Misses
- Whatever it stops running for.
Most people end up with a patchwork of these. Gaps where a few days matter most.
Two government sources worth pulling now if you haven’t: the US CBP I-94 travel-history portal returns your last five years of US entries and exits, Source: US Customs and Border Protection — I-94 Travel History and the EU’s Entry/Exit System (EES) will carry short-stay Schengen crossings as it rolls out. Source: European Commission — Entry/Exit System
Neither is a complete log. Both are useful inputs that help you spot the gaps in your own record — the travel footprint tool lays them out on a world map so missing days are visible at a glance.
The record that holds the position is the one that existed before the question was asked.
Where people get this wrong
Memory doesn’t hold up. People overestimate how well they remember where they were six months ago, let alone three years. When the memory is inconvenient — a trip that pushes a day count over — it tends to accommodate. Auditors know this. The IRS expects contemporaneous records, not reconstructions. Source: IRS — Recordkeeping
Credit cards aren’t a record. They’re one input, and they miss cash days, guest days, transit days, and anywhere someone else’s card covered the bill. A statement is evidence of a transaction. Not proof of presence.
Short visits vanish first. The hardest things to reconstruct are the easiest to forget: a long weekend, a one-night layover, a Tuesday morning flight. Exactly what residency and day-limit rules tend to care about — see our guides on tax residency and the Schengen 90/180 rule for where this bites.
Starting the record after the question arrives. The moment you realize you need a day-level log is usually the moment it’s too late to make one for the year in question. Reconstructed records count for something. They count for less than records that were already there.
Your move
See your record
Start with what you can already reconstruct. Then see where the gaps are.
The problem
The questions come later.
Without a record already in place, you're reconstructing from memory.
Let Chrono count for you
Scan to install. Chrono starts tracking immediately.
Takes 10 seconds
Prefer to install manually?
Questions
- What travel records actually matter in a residency audit?
- Records that existed when the thing happened. Passport stamps, I-94 arrival/departure records, credit-card charges, travel bookings, and border-system data (e.g., EES in Europe) all help. A continuous location record is the strongest form because it fills in the gaps the other sources leave.
- Do I need to track every day?
- If residency or day-limit rules can apply to your situation, yes. Missing days aren't neutral. They're gaps in the record you'd use to defend your position.
- Can I reconstruct my travel timeline later?
- You can, and sometimes you have to. But reconstructed records weigh less than contemporaneous ones. If you know a question is plausible, building the record now is cheaper than rebuilding it later.
- Can I get my own travel history from the government?
- US entries and exits are available through the CBP I-94 portal. Schengen border crossings will be captured by the EU Entry/Exit System as it rolls out. Both are partial records, not a complete log.
Related guides