FA-301e · Module 3

Variance Management

3 min read

Not all variances are created equal. A $50K over-spend on a program generating $500K in attributed pipeline is a favorable variance — you should spend more. A $50K under-spend because a program was never launched is an unfavorable variance — the budgeted outcome was not achieved. The dollar amount of the variance tells you the magnitude. The context tells you whether to celebrate, investigate, or escalate.

Budget Variance Classification:
──────────────────────────────────────────────────────
Type            Over Budget    Under Budget
──────────────────────────────────────────────────────
With ROI        Favorable       N/A
  → Spent more, got more.      (can't underspend
  → Evaluate scaling further.   with positive ROI)

Without ROI     Unfavorable    Favorable
  → Spent more, got nothing.   → Saved money on
  → Root cause + corrective.    something unproductive.

Execution Lag   Timing         Timing
  → Spend shifted to           → Spend delayed,
    later period.                will catch up.
  → Reforecast phasing.        → Reforecast phasing.
──────────────────────────────────────────────────────

Classify every variance before deciding
whether it is good news or bad news.
The dollar amount alone does not tell you.

Do This

Classify variances by type (ROI-driven, non-ROI, timing) before flagging them
Require root cause documentation for any unfavorable variance above $25K
Track variance trends — consistent over-spend in one function indicates a systemic planning issue

Avoid This

Treat all over-budget items as negative without checking whether they generated returns
Treat all under-budget items as positive without checking whether outcomes were delivered
Ignore timing variances — they indicate execution issues even if the annual total balances