Why consolidate 2 Budget leaves into this page?

Because the useful action is one control system. Nightly Log, Variance Check belong together when a traveler is making the same money decision.

What should I do first for actuals vs plan?

Start with the ledger row that can cost money soonest. Then build the packet, check the proof table, and calendar the next date or decision.

Is this a spreadsheet page?

No. The sheet is just one tool. The page is the control desk: what number to know, what proof to keep, what choice to make, and what to do when the plan bends.

What should stay in the future breakout queue?

Highly specific search questions, country variants, card-by-card examples, route-specific price studies, and traveler-type versions should break out later without weakening this canonical desk.

How should I use the source links?

Use them to verify rules, fees, rights, and current terms before money moves. Editorial structure helps you ask the right question; the live provider or official source confirms the current answer.

THE TREASURY DESK - CANONICAL CASE FILE

Actuals vs Plan - Nightly logs, variance checks, and the simple post-trip truth about where the money went.

Actuals vs Plan travel budget dossier: Nightly logs, variance checks, and the simple post-trip truth about where the money went. Includes ledger rows, proof checks, timing, scenarios, mistakes, rescue flow, and queued breakout guides. Variance is not confession. It is the map that makes the next trip easier.

Case intake

This canonical page consolidates nightly-log, variance-check.

Control ledger

Plan: track Original category number; proves Expectation; avoid Changing it retroactively.

Actual: track Clean final spend; proves Reality; avoid Mixing estimates and posted charges.

Variance: track Difference and percent; proves Where the plan held or broke; avoid Only looking at total.

Cause: track Price, behavior, weather, logistics; proves Useful lesson; avoid Turning it into blame.

Packet build

Compare categories, not just totals.

A trip can hit the total while hiding a food overage and transport savings. The lesson lives in the category.

Use percent and dollars.

A small category can have a huge percent swing that does not matter. A large category can drift quietly.

Name the cause neutrally.

Was the variance destination price, planning error, mood spending, weather, or a deliberate upgrade?

Keep the lesson portable.

The point is a next-trip rule, not a perfect autopsy.

Timing strip

During trip

Use the nightly log to preserve rough actuals.

Cleanup

Replace rough notes with posted card and cash totals.

Review

Calculate variance by category and cause.

Next planning

Apply the top three lessons before setting a new target.

Decision rules

If it repeats, give it a line.

A cost that happens daily, per booking, per traveler, or per movement is not incidental on a real trip.

If it can block the trip, check it early.

Fees, payment limits, route costs, cancellation rules, and refund windows belong in planning, not panic.

If it is optional, name what it replaces.

Splurges are fine when they have a swap. They break budgets when they arrive as add-ons without a cut.

If it teaches you something, keep the lesson.

The cleanup is not shame. It is the next trip getting cheaper, calmer, or more honest.

Scenario drawers

Food is way over

Check whether the floor was wrong, the destination was pricier, or you chose more upgrades than planned.

Transport is under

That may be a reusable lesson: better lodging location, walkability, or transit pass worked.

The total is fine but one category blew up

Keep the good news and still learn from the category. Both can be true.

You hate the numbers

Look for one next action only. No one needs a moral trial for gelato.

Mistakes and rescue flow

Changing the plan after the trip to make variance disappear.
Only reviewing the total.
Treating deliberate upgrades like mistakes.
Leaving the lesson vague.

If the trip created debt, stop next-trip planning until repayment is scheduled.
Identify whether the issue was target, timing, or behavior.
Protect fixed bills first.
Write a smaller, calmer next-trip rule.

Source box

Future breakout queue

Nightly Log
Variance Check

Frequently asked questions

Why consolidate 2 Budget leaves into this page?: Because the useful action is one control system. Nightly Log, Variance Check belong together when a traveler is making the same money decision.
What should I do first for actuals vs plan?: Start with the ledger row that can cost money soonest. Then build the packet, check the proof table, and calendar the next date or decision.
Is this a spreadsheet page?: No. The sheet is just one tool. The page is the control desk: what number to know, what proof to keep, what choice to make, and what to do when the plan bends.
What should stay in the future breakout queue?: Highly specific search questions, country variants, card-by-card examples, route-specific price studies, and traveler-type versions should break out later without weakening this canonical desk.
How should I use the source links?: Use them to verify rules, fees, rights, and current terms before money moves. Editorial structure helps you ask the right question; the live provider or official source confirms the current answer.