Plan-versus-actual grounded in the same model history you forecast with.
Product · Variance
Explain plan vs. actual — with the trail intact.
Variance analysis is only useful when the explanation is traceable. Bridge Town keeps the model, the inputs, the results, and the revisions together, so you can see what moved and why.
/ what it gives your team
What variance analysis gives your team
Source data and results kept together for review, not scattered across files.
Claude investigates the drivers behind every material move.
Versioned explanations you can revise without losing the original context.
/ how it works
From actuals to explanation.
Load actuals and the relevant plan version into the model.
Ask Claude to find the biggest moves and inspect the drivers.
Review the calculation path, the tables, and the draft explanation.
Commit the explanation with the version that backs it.
/ common uses
Budget vs actualsForecast bridgesDepartment spendBoard variance packs
/ questions
Good to know
- Can it explain variances automatically?
- Your connected assistant inspects the model and drafts the explanation. Bridge Town provides the versioned data, model, and results it works against.
- How is this different from a spreadsheet variance tab?
- The explanation stays connected to versioned logic, source data, and results — not stranded in a separate static worksheet.
/ keep exploring
The rest of the workspace.
Put variance on the right footing.
Connect in one click and build your first model free.
Connect to ClaudeBridge Town stores, runs, and versions the work; it does not run a language model on your behalf.