Skip to content
Back to skills

Structure For Each Variance Narrative

ASecurity

'Sub-skill of variance-analysis: Structure for Each Variance Narrative

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 9, 2026
businessgo

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill structure-for-each-variance-narrative --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Structure For Each Variance Narrative?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Structure For Each Variance Narrative
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-structure-for-each-variance-narrative/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-structure-for-each-variance-narrative)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: variance-analysis-structure-for-each-variance-narrative
description: 'Sub-skill of variance-analysis: Structure for Each Variance Narrative
  (+2).'
version: 1.0.0
category: business
type: reference
scripts_exempt: true
---

# Structure for Each Variance Narrative (+2)

## 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.