✈️ AwardWise ← Back to AwardWise

Guides · Budapest trip, end to end

Budapest trip, end to end

One search answers "is there a seat on this day." A trip answers "does the whole thing hold together." This guide walks the whole Trips feature on one real award trip: a conference in Budapest, five airports, and a return that refuses to be simple.

It is the worked example, not the reference. If a word here is unfamiliar, the Trips guide defines it: what an anchor is, what a leg is, how a pool works, what the verdict bar and the health rail are claiming. This page shows all of it happening to one trip, in order, start to finish.

The trip is a real one, and its shape is worth stating before any screenshot, because the shape is the planning problem. One thing is fixed: EMNLP 2026 runs Oct 24 to 29 in Budapest, and a jet-lag buffer day means arriving by Oct 23. Almost everything else flexes. The transatlantic hop leaves from the US West Coast: SFO is home, but positioning from LAX or SEA is fine. It can land at any major gateway: FRA, MUC, or VIE are all acceptable, because each has its own way onward to Budapest, including a 2.5 hour train from Vienna. The dates flex too: leaving Oct 19, 20, or 21 all work, and earlier just means more time to explore. Award inventory gets to decide among all of those, which is exactly what hunting is for.

The return is the opposite kind of problem. Its route is fixed: VIE → MUC → SFO, in that order, with the Munich stop a deliberate part of the plan rather than a layover accident. What flexes there is only the date of each segment, and the pick depends on which days the award deals actually show seats. Choosing that pair of dates then settles the small Budapest to Vienna hop that starts the chain. One trip, two opposite problems: a leg where everything is negotiable, and a chain where nothing is negotiable except when.

Every screenshot below is the real Trips UI, and the prices in the completed-trip figures are the real trip's, exactly as it was planned on Aug 17, 2026. Award availability moves daily, so read them as a true story rather than as bookable fares. Where a number is unknown the app shows "—", and so does this guide.

1. Start from what can't move

Most trips have one fixed thing. A conference. A wedding. A table you waited three months for. AwardWise calls it an anchor, and a trip starts there rather than at a search box. Open Trips, then Start a trip from an anchor, and pick Event. (The other two anchor types, A flight worth the trip and A table worth the trip, are marked coming later; Event is the one that ships today.)

For Budapest that reads: event EMNLP 2026, venue Budapest, dates Oct 24 to Oct 29, a +1 day jet-lag buffer, a ±2 date flex band, event airport BUD, flying from SFO, LAX, SEA, flying into FRA, MUC, VIE.

The form recomputes as you type. Nothing is saved until you press Create trip.

Watch the block labelled So: under the event dates. It is doing the arithmetic you would otherwise do on a napkin:

Add the ±2 flex band and those two dates become two windows: a fly-in window of Oct 21 – 23 and a fly-out window opening Oct 30. Windows are the whole point. They are not filters and they never reject a flight. They are the shape the anchor casts over the rest of the trip, and every later check measures against them.

Under the windows the form lists exactly what Create trip · 4 legs will write, by name, before you press it. The button counts them, and the list above it is headed Creates 4 empty legs:

• Outbound · SFO/LAX/SEA → FRA/MUC/VIE · Oct 21-23
• Onward hop · FRA/MUC/VIE → BUD · Oct 21-23
• Stay in Budapest · Budapest · Oct 23-30
• Return · BUD → SFO/LAX/SEA · Oct 30 - Nov 1

What the anchor wrote. Four legs, every one of them empty, and a health rail that already knows what is missing.

A leg is one hop of the trip waiting to be filled. It carries a declared route (SFO/LAX/SEA → FRA/MUC/VIE, all three origins at once) and a declared date span, and nothing else. It is a question, not an answer. Note that the stay is a marker rather than a search: AwardWise does not book lodging yet, and the card says so instead of pretending.

The other door

You do not have to start from an anchor. Start an empty trip instead (the link under the Create button) gives you a bare trip you can fill by hand, or from a search using Save to trip on any result row. Add an event to it later from + Add ▾, under Anchor, and the trip offers the same derivation retroactively as Create legs around EMNLP 2026. Same windows, same four legs, arrived at from the other side.

An anchored trip with no legs yet offers both doors at once.

2. Hunt one leg

Press Hunt flights on the Outbound leg. AwardWise composes the search from what the leg already declares, so you are not retyping SFO/LAX/SEA and the dates you set two minutes ago.

The declared span is the default hunt window. The panel says which span it is about to search, and offers the individual days if you want to narrow to one:

One search over the declared span, not one search per day. Picking a single day chip narrows it to that day.

Then it is the ordinary results table, with two differences. A chip at the top says Hunting for Leg 1 · Outbound, so a table you scroll for ten minutes never loses track of why it is open, and beside it sits Back to Budapest (EMNLP 2026). And the save control on every row is now a one-click Add to Leg 1 · Outbound rather than a generic picker.

The chip keeps the hunt anchored to its leg, however long you scroll. The save control on each row reads Add to Leg 1 · Outbound.

The real Budapest outbound hunt returned 1,220 economy awards over the Oct 19 – 21 span. That is the number that makes trips necessary. You are not going to hold 1,220 rows in your head, and you should not have to hold three of them either.

3. Build the pool, then choose

Add more than one. Each leg keeps a pool of options, and the leg header counts them (2 options). Exactly one option is ✓ Picked; it is the one that counts toward the trip's totals. The rest sit underneath, each tagged OPTION, costing nothing and waiting.

One picked, the rest held. Each unpicked option shows its delta against the pick.

Three things to do with a pool:

• Pick swaps which option counts. It saves immediately and the trip's totals move with it. A notice reports the delta and offers Undo for 12 seconds, which is one step, not a history.
• Add a note stores the judgment the numbers cannot: "3 seats, but the connection is tight." Six weeks later that sentence is the only reason you will remember why the cheaper option lost.
• Drop removes an option you have ruled out. Clearing several at once is offered as Drop 1 option on the leg header.

To compare options properly rather than by scrolling, open the leg's ⋯ menu and choose Compare in a table. It lays the pool out as rows with columns you can sort, each row carrying its own Pick. Close it with the ✕. The N options pill beside the leg's name does something quieter: it shows and hides the pool in place.

4. Shape the trip

What the anchor wrote is a guess. It is meant to be edited.

Dates. The ✎ beside a leg's date line opens two real date fields with Save and Cancel, and a line telling you what saving does: "Sets this leg's dates and its hunt window." Both, together, which is the point. Move the leg and the next hunt follows it.

Editing a leg's dates. ESC cancels, Enter saves.

Routes. The ✎ beside the route line does the same for airports. This is how a leg that started as FRA/MUC/VIE becomes a specific VIE once you know which gateway you are actually using.

New legs. + Add a leg declares one by hand. A leg with no route yet shows Declare a route → and the note "Declare a route to hunt this leg." There is nothing to search until you say from where and to where. The Budapest return starts exactly like this.

Deleting. A trip's ⋯ menu offers Delete trip, and the confirm names what goes with it: Delete trip "Budapest"? Its 4 legs and 1 anchor go with it. This cannot be undone. Removing a single leg confirms the same way, counting its saved options.

5. Read the verdict

The rail down the right side of a trip is the answer to "what is this actually costing me." (On a narrow window it sits above the timeline instead; same tiles, same claims.)

• Trip Effective Cost, with the line recomputes under your wallet beneath it. Miles are priced at your cents-per-point valuations, not a published chart and not ours. If you have not set your own, per-program defaults stand in. See What is "Effective Cost"? for the arithmetic.
• Trip Award Cost and Cash fares, kept apart rather than blended, because miles spent and dollars spent are not the same kind of pain.
• Hunted legs, which is where the honesty lives. On the brand-new trip it reads —: nothing has been hunted, so there is no fraction to state and it does not invent a zero. Once the outbound carries an option it reads 1 of 3 priced (three of the four legs are flights that can be hunted; the fourth is the stay), and once all three do it simplifies to 3 hunted. A total that covered only part of the trip would be a lie told with real numbers, so the count sits next to it.

Saved awards go stale. Every option carries the date its award data was last seen (Award data last seen Aug 10, 2026 · 5 days ago), past a week it earns a STALE badge, and the card says plainly that seats and price may have changed and to re-search before booking. AwardWise will not refresh it behind your back and call it current.

Above the timeline sits the map strip: the whole trip as one thin ruler, with gold bars for the anchor and the stay, dots for the flight legs, and the derived windows drawn to the same day scale. Click any mark and the timeline scrolls to that leg. As you scroll, the strip condenses to a slim ruler and stays pinned, so the map never leaves you.

Beneath the verdict runs the health rail, three tiers deep: Fix first, Check, To do. It re-runs after every change, and its summary line is a sentence about this trip. On the freshly created Budapest trip it reads:

Nothing in that rail can stop you. Set the Outbound to Oct 20, a day before the fly-in window opens, and the save goes through. The rail files it under Check, and clicking the item scrolls the timeline to the leg it means:

The date outside the window is accepted, then flagged. A window is a derivation, and you may know something it does not.

There is no "all clear" tier, because the all-clear lives where you are already looking: a leg that fits its window carries the receipt on its own card, as a small gold tag quoting the dates ("◄ fits fly-in · Oct 22 – 23"). A passing check is a real claim about real data, never a green light invented from missing inputs — a check whose inputs are unknown says nothing at all.

6. Chains you assemble yourself

Here is where the Budapest trip stops being tidy, and where you should know exactly what the app does and does not do for you.

The return is not one flight. It is fixed as VIE → MUC → SFO, that routing and no other, with only the dates free to move:

The two are not independent. A VIE → MUC on Nov 2 rules out an MUC → SFO on Nov 2 if the connection does not make sense, and pairs fine with Nov 3. The BUD → VIE hop that precedes them follows whichever pair you settle on.

AwardWise searches one direction at a time. It does not search a round trip, and it does not pair segments for you. So you work the chain by hand, and the trip is what holds it:

1. Declare a leg per segment: one for VIE → MUC, one for MUC → SFO, one for BUD → VIE.
2. Hunt each as its own one-way, over its own declared span.
3. Pool the options that survive on each, and read the dates across the pools yourself. Keep the ones that pair.
4. Write the reason in a note. "Only works with the Nov 4 MUC → SFO" is the kind of thing you will not reconstruct later.
5. Pick one per leg. The verdict bar totals the chain, and the health rail checks each leg against the fly-out window.

The compatibility judgment is yours today. The trip does not make it for you, and this guide is not going to imply it will. What the trip does is keep every option, every date and every reason in one place, so the judgment is one you make once and can still read six weeks later.

The chain, resolved: Oct 30, Nov 1, Nov 4 — three one-ways read across their pools until the dates paired.

7. How it ended

This trip was planned for real, in one evening, exactly the way the sections above describe — and it closed. Here is the finished shape, as the verdict rail reported it:

The verdict on the finished trip. Every number below is this trip's own.

• Outbound · SFO → FRA · Oct 20 · Condor DE2097, nonstop, 11h 10m · 45,000 Alaska miles + $66 taxes, 4 award seats.
• Onward hop · FRA → BUD · Oct 22 · Condor DE4467, 1h 35m · $102 cash. The awards on this short hop were not worth their miles, so cash won — the point of pricing both sides.
• Stay in Budapest · Oct 23 – 30, wrapped around EMNLP.
• BUD → VIE · Oct 30 · Austrian OS634, 50m · 12,500 Aeroplan + $98 taxes — departing the day the fly-out window opens.
• VIE → MUC · Nov 1 · Austrian OS185, 1h · $135 cash. Cash won twice.
• MUC → SFO · Nov 4 · United UA195, nonstop, 12h · 40,000 Aeroplan + $256 taxes, 9 award seats.

The chain resolved exactly as section 6 says it must: each segment hunted over its own window as its own one-way, then the dates read across the pools — Nov 1 pairing with Nov 4, the Munich stop preserved on purpose. The verdict's totals for the whole shape: 97,500 miles (45,000 Alaska + 52,500 Aeroplan), $237 in cash fares, about $420 in award taxes, roughly 27 hours in the air — and a Trip Effective Cost of $1,830 under the wallet's own valuations. The health rail's last word: "Nothing broken. 1 stay to cover." The one open item is the hotel, which AwardWise does not book yet and says so.

What a trip is for

A search finds a seat. A trip is the thing that remembers: what is fixed, what that implies, what you found, what you rejected and why, and what it costs under your own valuations. Nothing in it is guessed on your behalf, and nothing you enter is overruled.

For the parts on their own, without a trip wrapped around them, read Trips.

Start a trip from your own anchor →