Variance Analysis
AnthropicOfficialPublished by Anthropic
- Skill
- Guidelines
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to financial variance analysis, enabling users to break down discrepancies between actual results and budgets, forecasts, or prior periods. It covers decomposition techniques for revenue, headcount, and operating expenses, alongside best practices for setting materiality thresholds, writing actionable variance narratives, and constructing text-based waterfall charts to communicate financial drivers to leadership.
What it does
- Provides formulas for price/volume, rate/mix, and headcount-driven variance decomposition.
- Establishes a framework for setting materiality thresholds to prioritize investigation.
- Defines a standardized structure for writing concise, causal, and actionable variance narratives.
- Offers a methodology for creating text-based waterfall charts to visualize financial bridges.
- Outlines a three-way comparison framework for Budget, Forecast, and Actual performance.
- Includes metrics for tracking forecast accuracy and identifying systematic variance trends.
When to use it
- When preparing monthly or quarterly variance commentary for executive leadership.
- When analyzing budget vs. actual performance to identify operational drivers.
- When investigating unexpected fluctuations in revenue, expenses, or headcount.
- When performing period-over-period trend analysis or year-over-year growth comparisons.
- When evaluating the accuracy of financial forecasts to improve future planning.
Advantages
- Standardizes the language and structure of financial reporting across the organization.
- Reduces noise by focusing investigation on material variances.
- Promotes causal analysis rather than superficial reporting.
- Facilitates clear communication of complex financial drivers through waterfall logic.
- Helps identify systematic biases in budgeting and forecasting processes.
Usage examples
- “Explain how to decompose a revenue variance where both units sold and average price changed.”
- The skill provides the price/volume decomposition formula, showing how to isolate the volume effect, price effect, and mix effect to explain the total variance.
- “How should I structure a variance narrative for a board report?”
- The skill provides a template including the line item, primary driver, business reason, outlook, and required action, along with a quality checklist.
- “Create a text-based waterfall for an operating expense variance.”
- The skill provides a format to list the starting budget, individual drivers (e.g., headcount, discretionary spend), and the final actual amount to reconcile the variance.
- “What thresholds should I use to decide which variances to investigate?”
- The skill suggests a framework based on financial statement materiality, line item size, and volatility, with specific percentage guidelines for different comparison types.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/variance-analysis/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip variance-analysis.zip -d .agents/skills
Documentation by Anthropic
Variance Analysis
Important: This skill assists with variance analysis workflows but does not provide financial advice. All analyses should be reviewed by qualified financial professionals before use in reporting.
Techniques for decomposing variances, materiality thresholds, narrative generation, waterfall chart methodology, and budget vs actual vs forecast comparisons.
Variance Decomposition Techniques
Price / Volume Decomposition
The most fundamental variance decomposition. Used for revenue, cost of goods, and any metric that can be expressed as Price x Volume.
Formula:
Total Variance = Actual - Budget (or Prior)
Volume Effect = (Actual Volume - Budget Volume) x Budget Price
Price Effect = (Actual Price - Budget Price) x Actual Volume
Mix Effect = Residual (interaction term), or allocated proportionally
Verification: Volume Effect + Price Effect = Total Variance
(when mix is embedded in the price/volume terms)Three-way decomposition (separating mix):
Volume Effect = (Actual Volume - Budget Volume) x Budget Price x Budget Mix
Price Effect = (Actual Price - Budget Price) x Budget Volume x Actual Mix
Mix Effect = Budget Price x Budget Volume x (Actual Mix - Budget Mix)Example — Revenue variance:
Budget: 10,000 units at $50 = $500,000
Actual: 11,000 units at $48 = $528,000
Total variance: +$28,000 favorable
Volume effect: +1,000 units x $50 = +$50,000 (favorable — sold more units)
Price effect: -$2 x 11,000 units = -$22,000 (unfavorable — lower ASP)
Net: +$28,000
Rate / Mix Decomposition
Used when analyzing blended rates across segments with different unit economics.
Formula:
Rate Effect = Sum of (Actual Volume_i x (Actual Rate_i - Budget Rate_i))
Mix Effect = Sum of (Budget Rate_i x (Actual Volume_i - Expected Volume_i at Budget Mix))Example — Gross margin variance:
Product A: 60% margin, Product B: 40% margin
Budget mix: 50% A, 50% B → Blended margin 50%
Actual mix: 40% A, 60% B → Blended margin 48%
Mix effect explains 2pp of margin compression
Headcount / Compensation Decomposition
Used for analyzing payroll and people-cost variances.
Total Comp Variance = Actual Compensation - Budget Compensation
Decompose into:
1. Headcount variance = (Actual HC - Budget HC) x Budget Avg Comp
2. Rate variance = (Actual Avg Comp - Budget Avg Comp) x Budget HC
3. Mix variance = Difference due to level/department mix shift
4. Timing variance = Hiring earlier/later than planned (partial-period effect)
5. Attrition impact = Savings from unplanned departures (partially offset by backfill costs)Spend Category Decomposition
Used for operating expense analysis when price/volume is not applicable.
Total OpEx Variance = Actual OpEx - Budget OpEx
Decompose by:
1. Headcount-driven costs (salaries, benefits, payroll taxes, recruiting)
2. Volume-driven costs (hosting, transaction fees, commissions, shipping)
3. Discretionary spend (travel, events, professional services, marketing programs)
4. Contractual/fixed costs (rent, insurance, software licenses, subscriptions)
5. One-time / non-recurring (severance, legal settlements, write-offs, project costs)
6. Timing / phasing (spend shifted between periods vs plan)Materiality Thresholds and Investigation Triggers
Setting Thresholds
Materiality thresholds determine which variances require investigation and narrative explanation. Set thresholds based on:
Financial statement materiality: Typically 1-5% of a key benchmark (revenue, total assets, net income)
Line item size: Larger line items warrant lower percentage thresholds
Volatility: More volatile line items may need higher thresholds to avoid noise
Management attention: What level of variance would change a decision?
Recommended Threshold Framework
| Comparison Type | Dollar Threshold | Percentage Threshold | Trigger |
|---|---|---|---|
| Actual vs Budget | Organization-specific | 10% | Either exceeded |
| Actual vs Prior Period | Organization-specific | 15% | Either exceeded |
| Actual vs Forecast | Organization-specific | 5% | Either exceeded |
| Sequential (MoM) | Organization-specific | 20% | Either exceeded |
Set dollar thresholds based on your organization's size. Common practice: 0.5%-1% of revenue for income statement items.
Investigation Priority
When multiple variances exceed thresholds, prioritize investigation by:
Largest absolute dollar variance — biggest P&L impact
Largest percentage variance — may indicate process issue or error
Unexpected direction — variance opposite to trend or expectation
New variance — item that was on track and is now off
Cumulative/trending variance — growing each period
Narrative Generation for Variance Explanations
Structure for Each Variance Narrative
[Line Item]: [Favorable/Unfavorable] variance of $[amount] ([percentage]%)
vs [comparison basis] for [period]
Driver: [Primary driver description]
[2-3 sentences explaining the business reason for the variance, with specific
quantification of contributing factors]
Outlook: [One-time / Expected to continue / Improving / Deteriorating]
Action: [None required / Monitor / Investigate further / Update forecast]Narrative Quality Checklist
Good variance narratives should be:
[ ] Specific: Names the actual driver, not just "higher than expected"
[ ] Quantified: Includes dollar and percentage impact of each driver
[ ] Causal: Explains WHY it happened, not just WHAT happened
[ ] Forward-looking: States whether the variance is expected to continue
[ ] Actionable: Identifies any required follow-up or decision
[ ] Concise: 2-4 sentences, not a paragraph of filler
Common Narrative Anti-Patterns to Avoid
"Revenue was higher than budget due to higher revenue" (circular — no actual explanation)
"Expenses were elevated this period" (vague — which expenses? why?)
"Timing" without specifying what was early/late and when it will normalize
"One-time" without explaining what the item was
"Various small items" for a material variance (must decompose further)
Focusing only on the largest driver and ignoring offsetting items
Waterfall Chart Methodology
Concept
A waterfall (or bridge) chart shows how you get from one value to another through a series of positive and negative contributors. Used to visualize variance decomposition.
Data Structure
Starting value: [Base/Budget/Prior period amount]
Drivers: [List of contributing factors with signed amounts]
Ending value: [Actual/Current period amount]
Verification: Starting value + Sum of all drivers = Ending valueText-Based Waterfall Format
When a charting tool is not available, present as a text waterfall:
WATERFALL: Revenue — Q4 Actual vs Q4 Budget
Q4 Budget Revenue $10,000K
|
|--[+] Volume growth (new customers) +$800K
|--[+] Expansion revenue (existing customers) +$400K
|--[-] Price reductions / discounting -$200K
|--[-] Churn / contraction -$350K
|--[+] FX tailwind +$50K
|--[-] Timing (deals slipped to Q1) -$150K
|
Q4 Actual Revenue $10,550K
Net Variance: +$550K (+5.5% favorable)Bridge Reconciliation Table
Complement the waterfall with a reconciliation table:
| Driver | Amount | % of Variance | Cumulative |
|---|---|---|---|
| Volume growth | +$800K | 145% | +$800K |
| Expansion revenue | +$400K | 73% | +$1,200K |
| Price reductions | -$200K | -36% | +$1,000K |
| Churn / contraction | -$350K | -64% | +$650K |
| FX tailwind | +$50K | 9% | +$700K |
| Timing (deal slippage) | -$150K | -27% | +$550K |
| Total variance | +$550K | 100% |
Note: Percentages can exceed 100% for individual drivers when there are offsetting items.
Waterfall Best Practices
Order drivers from largest positive to largest negative (or in logical business sequence)
Keep to 5-8 drivers maximum — aggregate smaller items into "Other"
Verify the waterfall reconciles (start + drivers = end)
Color-code: green for favorable, red for unfavorable (in visual charts)
Label each bar with both the amount and a brief description
Include a "Total Variance" summary bar
Budget vs Actual vs Forecast Comparisons
Three-Way Comparison Framework
| Metric | Budget | Forecast | Actual | Bud Var ($) | Bud Var (%) | Fcast Var ($) | Fcast Var (%) |
|---|---|---|---|---|---|---|---|
| Revenue | $X | $X | $X | $X | X% | $X | X% |
| COGS | $X | $X | $X | $X | X% | $X | X% |
| Gross Profit | $X | $X | $X | $X | X% | $X | X% |
When to Use Each Comparison
Actual vs Budget: Annual performance measurement, compensation decisions, board reporting. Budget is set at the beginning of the year and typically not changed.
Actual vs Forecast: Operational management, identifying emerging issues. Forecast is updated periodically (monthly or quarterly) to reflect current expectations.
Forecast vs Budget: Understanding how expectations have changed since planning. Useful for identifying planning accuracy issues.
Actual vs Prior Period: Trend analysis, sequential performance. Useful when budget is not meaningful (new business lines, post-acquisition).
Actual vs Prior Year: Year-over-year growth analysis, seasonality-adjusted comparison.
Forecast Accuracy Analysis
Track how accurate forecasts are over time to improve planning:
Forecast Accuracy = 1 - |Actual - Forecast| / |Actual|
MAPE (Mean Absolute Percentage Error) = Average of |Actual - Forecast| / |Actual| across periods| Period | Forecast | Actual | Variance | Accuracy |
|---|---|---|---|---|
| Jan | $X | $X | $X (X%) | XX% |
| Feb | $X | $X | $X (X%) | XX% |
| ... | ... | ... | ... | ... |
| Avg | MAPE | XX% |
Variance Trending
Track how variances evolve over the year to identify systematic bias:
Consistently favorable: Budget may be too conservative (sandbagging)
Consistently unfavorable: Budget may be too aggressive or execution issues
Growing unfavorable: Deteriorating performance or unrealistic targets
Shrinking variance: Forecast accuracy improving through the year (normal pattern)
Volatile: Unpredictable business or poor forecasting methodology
Files
- ATTRIBUTION.mdAdded by AutoGineer926 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md11.0 KiB
ATTRIBUTION.md
Attribution
This folder is an unmodified copy of the Agent Skill "variance-analysis", distributed by AutoGineer (https://autogineer.com/agent-skills).
Commit: e050c2ec856373787143d7057663a6ebd1277df3
Published by: Anthropic (https://github.com/anthropics)
Publisher: Anthropic (https://github.com/anthropics)
Licence: Apache License 2.0 (https://github.com/anthropics/knowledge-work-plugins/blob/e050c2ec856373787143d7057663a6ebd1277df3/finance/LICENSE)
Licence evidence: licence file finance/LICENSE
Retrieved: 2026-11-07
The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.
Files added by AutoGineer
ATTRIBUTION.md: this file, written by AutoGineer
LICENSE: copied from finance/LICENSE
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · finance/skills/variance-analysis · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from finance/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download variance-analysis.zip