budget-variance-analysis
Budget Variance Analysis Skill
Produces a complete variance analysis from numbers through to root cause explanation and management commentary.
Required Inputs
- Actuals and budget figures (paste as table or describe line by line)
- Period (month / quarter / YTD)
- Materiality threshold (e.g. £10k or 5%)
- Known reasons for variances (if any)
- Audience (CFO / board / management / auditor)
Output Structure
1. Variance Summary Table
| Line Item | Budget | Actual | Variance £ | Variance % | F/A |
|---|---|---|---|---|---|
| Revenue | |||||
| Cost of Sales | |||||
| Gross Profit | |||||
| Opex | |||||
| EBITDA |
F = Favourable | A = Adverse
2. Material Variance Commentary
For each variance above threshold:
[Line item] — £[amount] F/A ([%])
- Root cause: [Specific explanation — not "timing" without detail]
- Permanent or timing? Will this reverse next period?
- Management action: What is being done
- Forecast impact: Does this change full-year outlook?
3. Top 3 Variances Requiring Attention
Ranked by materiality and strategic significance.
4. Forecast Revision
Does the full-year forecast need updating? State revised expectation and key assumptions.
5. Executive Summary
3-4 sentences of management commentary suitable for a board pack.
Quality Checks
- All variances above threshold explained
- Root causes specific (not vague)
- Favourable/Adverse correctly labelled
- Forecast impact stated for material variances
Example Trigger Phrases
- "Write a variance analysis for these actuals vs budget: [paste]"
- "Explain why we are over budget on [cost line]"
- "Write the variance commentary for our finance review"
- "Produce a budget vs actual analysis for Q[N]"
More from mohitagw15856/pm-claude-skills
user-research-synthesis
Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps.
26prd-template
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
20stakeholder-update
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
19competitive-analysis
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations.
18meeting-notes
Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.
17executive-summary
Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.
15