B1 B2 Visa Travel Itinerary for Tourist Visa

A travel itinerary has never gotten anyone a US visa. It's not a document that earns points, and no officer ever stamped an approval because your spreadsheet had nice borders. What it does is narrower and more useful than that: it gives the person across the window a clear picture that your trip is real, has a shape, and ends on a specific date.

Visitor visas — B-1 for business, B-2 for tourism, B1/B2 for both — are for people coming to the US temporarily. If you're applying as a tourist, your itinerary should read like a tourist wrote it. Sounds obvious. Plenty of applications still get it wrong.

Here's a format you can copy, a 15-day route people actually use, and a quick test for whether your city split holds up.

What a B1/B2 travel itinerary is actually for — and what it is not

It is a short, dated plan that shows where you'll be, when, and when you fly home. It answers three questions before they're asked: when do you arrive, how long are you staying, where do you sleep.

It is not a booking confirmation, a legal document, or a guarantee of entry. Nobody is phoning your hotel to check. Making a detailed itinerary is one step in preparing a strong B1/B2 application — the visa itself, your form, your fee, your interview, and your ties back home all carry more weight than the itinerary.

The point is consistency, not luxury. A clean two-star plan you can explain beats a five-star fantasy you can't.

The five things every itinerary needs: dates, cities, nights, accommodation, return flight

Cover all five or the thing is unfinished.

• Arrival date — the day you land, matching what you put on your DS-160.
• Departure date — the day you fly home. This matters most. An itinerary with no return date is a red flag.
• Cities in order — the sequence you'll actually travel, not a wish list.
• Nights per city — how many nights you sleep in each place. Nights, not "days." Nights are harder to fudge.
• Accommodation — hotel name and city for each stop. The area or neighbourhood is fine if you haven't picked a hotel yet.
• Return flight — airline and route, at least tentatively.

That's five categories. It should fit on one page. And if you count in days instead of nights, stay consistent — half the confusion in applicant threads comes from counting the arrival day twice.

A worked day-by-day sample: the 15-day multi-city route applicants actually use

This is the split that keeps showing up among people applying for B1/B2 visas: 4 days New York, 2 D.C., 2 Orlando, 2 San Francisco, 2 LA, 3 Vegas. Written out properly, it looks like this:

Fifteen nights. Arrival March 3, departure March 18. Every city has a name, a night count, and a place to sleep.

Other applicants compare different routings — swapping LA and San Francisco out for Boston and more East Coast time, which cuts two long flights out of the trip. Both versions work. What matters is the arithmetic, not the postcard list.

Is your city split believable? Testing days against travel time

Here's the test: how much of each city's "days" disappears just getting there?

• A short domestic flight — D.C. to Orlando, LA to Vegas — eats about half a day once you count security, boarding, bags, and the drive at each end.
• A cross-country flight — Orlando to San Francisco, or D.C. to California — eats most of a day.
• A train, like D.C. to New York, eats half a day if you count getting to the station.

Apply that to your own plan:

• 2 nights in a city you flew across the country to reach is roughly one usable day. Rushed.
• 2 nights somewhere you reached by a short flight or train is fine.
• Two long cross-country hops in a 15-day trip and two full days are gone before you see anything.

Now add up your travel days. If your itinerary claims 15 sightseeing days across six cities and three long flights, it doesn't add up — and a sharp officer will do that math in their head while you talk.

The working rule: at least 2 nights per city, 3 if you had to cross the country to get there. Ten days in New York and D.C. reads more like a real holiday than ten cities in ten days.

How much detail is enough — flights, hotels, budgets, and how firm bookings need to be

One page. Dated. Nothing invented.

Include: dates and total nights, cities in travel order, nights per city, a named hotel or specific area for each stop, and a return flight with airline and city pair. A rough cost per day is optional but useful — it gives you a total you can say out loud if someone asks how the trip is funded.

Skip: paid, non-refundable bookings. Buying international tickets before you have a visa is a bad idea, and refundable holds or "planned" labels do the job. Skip the hour-by-hour schedule too. Nobody's asking what you'll eat on day six.

Interview guidance on this is plain: know your arrival and departure dates, know where you're staying, and know how long you're staying in each place. If you can say those three without checking your notes, you're ready.

Writing an itinerary when your trip is still tentative

Most first-time applicants haven't booked anything. That's normal. Don't fake certainty you don't have.

Label the top line something like "Planned itinerary — not yet booked." Then keep the skeleton firm anyway: fixed arrival date, fixed departure date, cities in order, nights per city, a hotel or area per stop. The shape stays solid even when the bookings don't exist yet.

What not to do: leave the dates as "sometime in June," or write TBD in every hotel cell. Tentative is fine. Vacant is not.

And if you're asked whether it's booked, answer honestly. "This is the plan, I haven't booked flights yet" is a normal answer. Getting caught claiming bookings you don't have is a much worse one.

Making the itinerary match your DS-160, visa length of stay, and interview answers

Three versions of one story: the itinerary, the DS-160, and what you say out loud. They need to agree.

• Arrival date. Whatever date you gave as your intended arrival on the DS-160 should be the first date on your itinerary.
• Length of stay. If the form says three weeks, the itinerary can't total 10 days.
• US contact. If you listed a hotel as your point of contact, that hotel should appear in the plan.
• Purpose. A tourist itinerary should look like tourism — cities, sights, family visits. If you're applying as B-1 business, show meetings or a conference instead.

Lay all three side by side before the interview. Most inconsistencies are typos and half-changed plans, not lies. They still cost you.

Answering the officer's itinerary questions: dates, stays, and what you plan to see

The questions are short. Keep your answers shorter.

• "When are you travelling?" — both dates: arrive March 3, return March 18.
• "How long are you staying?" — "Fifteen nights."
• "Where are you staying?" — the first hotel and city. The rest if asked.
• "What do you plan to see?" — two or three real things per city. The Statue of Liberty and the Met in New York. The Smithsonian in D.C. Universal in Orlando. Not "whatever's there."

What not to do: memorize a script. Officers hear rehearsed answers all day. Know your own plan well enough to talk about it like someone who made it.

Quick answers to what people keep asking

Can I travel as a tourist in the USA on a B1/B2 visa?

Yes. Visitor visas are for temporary entry — B-2 covers tourism, B-1 covers business travel, and the combined B1/B2 covers both. Build your itinerary around whichever purpose you're travelling under.

What's the recommended itinerary for a US visa application?

There's no official one. The version applicants share most is 15 days: 4 New York, 2 D.C., 2 Orlando, 2 San Francisco, 2 LA, 3 Vegas. Others swap LA and San Francisco for Boston and more East Coast time. Either way, cities, nights, and total days need to line up with your stated dates.

How do I write a travel itinerary for a visa application?

In this order: dates, cities and nights, accommodation, return flight. Then check it against your DS-160 and keep every version of it consistent.

What's the 90-day rule for a B1/B2 visa?

Don't take this one from a blog. Rules about how long you can stay and what you can do after arriving come from US immigration authorities and they change. Check the official State Department and USCIS pages for the current position.

Itinerary mistakes that make an application look padded

• Back-to-back cities with no travel time. Six cities in eight days, flying between all of them. The math collapses and it reads as padding.
• No return date. The biggest one. A plan that never ends looks like someone who isn't planning to leave.
• Vague hotels everywhere. "Hotel TBD" against every stop says you haven't actually thought about the trip.
• Days that don't add up. City nights totalling 15 but dates spanning 19 days. Small errors like this make the whole thing look decorative.
• A different story on the DS-160. Answers in the interview that contradict your form are hard to explain away.
• A trip too long for your circumstances. Three months off work with no explanation invites questions. Ask for a trip you can actually justify.

If you're staring at a blank page, grab the free itinerary checklist — it's a one-page fill-in for dates, cities, nights, stays, and return flight, plus the consistency check to run before your interview. Fill in your own numbers, put your city split through the 2-nights test, and walk in knowing exactly what you're going to say.