Budget Variance Explainer
Writes the story behind a number somebody else owns.
🔴 This skill never produces a figure. The user supplies the variance. The skill explains it.
If asked to calculate, recalculate, forecast or correct a number, decline and say the finance
system is the source of truth.
Inputs
- The variance, supplied by the user: line, period, budget, actual, difference
- Mail, meetings and files for the period, through Email, Meetings and Enterprise Search
references/config.md for the cost-centre vocabulary and the house commentary structure
Procedure
- Restate the variance exactly as given. If a figure is missing, ask for it. Never derive one.
- Search the period for discussion touching the line: approvals, delays, hiring, scope
changes, supplier issues, one-off events.
- Assemble candidate causes, each with the evidence link that supports it.
- Rank by how directly the evidence speaks to the line. An approval email naming the cost
centre outranks a general remark in a meeting.
- Write the commentary in the house structure from config. For each cause: what happened,
when, the evidence link, and whether it is expected to recur.
- State plainly what is unexplained. If the evidenced causes do not account for the variance,
say so and quantify the gap in the user's own figures.
Output
Commentary in the house structure, then:
| Cause | When | Evidence | Recurring? | Accounts for |
Closing line: evidenced causes, and the unexplained remainder stated in the user's figures.
Definition of done
Every cause carries an evidence link, the unexplained remainder is stated rather than smoothed
over, and no figure originated here.
"Largely unexplained" is an honest and useful answer. A variance commentary that explains
100% of everything is usually fiction, and finance reviewers know it.
When there is no data
- No discussion found for the line: say the period carries no evidenced cause, and stop. Do not
reach for a plausible-sounding reason.
- Evidence contradicts itself: present both and say they conflict.
Boundaries
- Never calculate, recalculate or forecast. Not even arithmetic on supplied figures.
- Never state a cause as certain when the evidence is circumstantial. Label it.
- Never write commentary that attributes a variance to a named individual.
- Draft only. The commentary goes to the user, not into a reporting pack.
Self-check
- Did any number originate in this output rather than from the user? If so, remove it.
- Does every cause have a link?
- Is the unexplained remainder stated plainly?
1---2name: budget-variance-explainer-33description: Drafts the narrative behind a budget variance from the context the user supplies and the discussion in mail and meetings, never producing or changing the figure itself. Use when the user asks to explain a variance, draft the commentary for a budget review, write the story behind the numbers, or prepare variance notes before a finance meeting.4metadata:5 source: https://skillmd.com/skills/kesslernity/budget-variance-explainer-36---78# Budget Variance Explainer910Writes the story behind a number somebody else owns.1112🔴 **This skill never produces a figure.** The user supplies the variance. The skill explains it.13If asked to calculate, recalculate, forecast or correct a number, decline and say the finance14system is the source of truth.1516## Inputs17- The variance, supplied by the user: line, period, budget, actual, difference18- Mail, meetings and files for the period, through **Email**, **Meetings** and **Enterprise Search**19- `references/config.md` for the cost-centre vocabulary and the house commentary structure2021## Procedure221. **Restate the variance exactly as given.** If a figure is missing, ask for it. Never derive one.232. **Search the period** for discussion touching the line: approvals, delays, hiring, scope24 changes, supplier issues, one-off events.253. **Assemble candidate causes**, each with the evidence link that supports it.264. **Rank** by how directly the evidence speaks to the line. An approval email naming the cost27 centre outranks a general remark in a meeting.285. **Write the commentary** in the house structure from config. For each cause: what happened,29 when, the evidence link, and whether it is expected to recur.306. **State plainly what is unexplained.** If the evidenced causes do not account for the variance,31 say so and quantify the gap in the user's own figures.3233## Output34Commentary in the house structure, then:3536| Cause | When | Evidence | Recurring? | Accounts for |3738Closing line: evidenced causes, and the unexplained remainder stated in the user's figures.3940## Definition of done41Every cause carries an evidence link, the unexplained remainder is stated rather than smoothed42over, and no figure originated here.4344**"Largely unexplained" is an honest and useful answer.** A variance commentary that explains45100% of everything is usually fiction, and finance reviewers know it.4647## When there is no data48- No discussion found for the line: say the period carries no evidenced cause, and stop. Do not49 reach for a plausible-sounding reason.50- Evidence contradicts itself: present both and say they conflict.5152## Boundaries53- **Never calculate, recalculate or forecast.** Not even arithmetic on supplied figures.54- Never state a cause as certain when the evidence is circumstantial. Label it.55- Never write commentary that attributes a variance to a named individual.56- Draft only. The commentary goes to the user, not into a reporting pack.5758## Self-check59- Did any number originate in this output rather than from the user? If so, remove it.60- Does every cause have a link?61- Is the unexplained remainder stated plainly?