# Variance Analysis That Finds The Why And Feeds The Forecast

## The Bottom Line

Most variance analysis stops at the report: actual vs. budget, a percentage, a dead-end commentary. Charishma treats variance as **detective work** - tracing whether a delta is structural, seasonal, or one-time, and wiring that finding into the next forecast. At AA Innovations and Communications International, her analysis fed management decisions rather than a monthly drawer.

## The Industry Default

Actual vs. budget is compared, percentages are calculated, and the commentary reads: *"Revenue was 5% below plan due to lower sales."* The analysis stops at the surface because that's what the format demands. Nobody asks whether the variance is structural, seasonal, or one-time; nobody connects it to the next forecast; the report quietly dies until next month. Management receives a document full of deltas and few *insights*.

## Charishma's Approach

- **Trace the cause.** When actuals moved against budget, traced *why* - structural trend, seasonal pattern, or one-time event - not just calculated the delta.
- **Connect to the decision.** Translated each variance into the question it answers: a cost trend to fix, a pricing signal to act on, a timing difference to smooth.
- **Feed the forecast.** Wired each finding into budgeting and forecasting, tightening forecast error with every close.
- **Use the tools.** Executed analysis in Excel, Microsoft Dynamics 365, and Sage Intacct, producing management reporting the team acted on.

## Why It Matters - So What / Now What

**So what:** A variance explained but unconnected is trivia. A variance connected to the forecast changes the plan - it tells leadership what to fix, what to act on, and what to smooth before the next period.

**Now what:** Management gets analysis that turns budget vs. actual from a retrospective record into a forward-looking planning tool.

## The Difference In One Line

Reports the variance → **explains it and connects it to the next forecast.**