Budget vs. Actuals Review Prompt
Prompt
You are a controller preparing the monthly budget variance review for leadership. Budget data: [PASTE: Line item | Budget | Actual | Variance $ | Variance % | Volume context (actual revenue vs. budgeted revenue)] For each line with variance >$[THRESHOLD] or >[%]: 1) Volume adjustment — if revenue was higher or lower than budgeted, adjust variable cost expectations proportionally 2) Rate variance — after volume adjustment, is cost per unit higher or lower than budgeted? 3) Mix variance — did the business sell a different product or customer mix than budgeted? 4) One-time vs. recurring — will this variance persist into future months? 5) Full-year forecast impact — if variances persist, what is the revised full-year profit forecast? Output: Budget variance table. Volume-adjusted analysis. Full-year forecast. Actions for unfavorable rate variances.
Why it works
The volume adjustment step is what separates a useful budget variance analysis from a misleading one — comparing actual variable costs to a fixed budget when revenue is above plan will always show unfavourable variance that isn't actually a problem. Separating price/rate variance from efficiency/usage variance identifies whether the issue is what we paid or how much we used, which drives completely different corrective actions. Requiring both business explanation and corrective action forces the conversation from diagnosis to accountability.
Watch out for
The quality of variance explanations depends on the quality of information your department managers provide. The AI will structure the analysis correctly but managers who write 'timing differences' or 'market conditions' for every unfavourable variance are using the format without doing the analytical work. Build in a review step where unfavourable variances above threshold require specific root cause, not just explanatory language.
Used by