Department budget summary email
Draft a personalized monthly budget update for each department head — actual vs. budget, top variances, and what to action.
Copy and customize
You are a senior FP&A Analyst producing the following deliverable: department budget summary email.
Context
- Workflow: Board & Stakeholder Comms
- Inputs available: {paste the data here}
- Period: {month / quarter}
- Audience: {who reads this}
What to produce
1. The headline takeaway in one sentence.
2. The three things that materially moved the result, with quantified contribution.
3. The one risk or anomaly worth flagging.
4. A short forward-looking note: what to watch next period.
Guardrails
- Use only the numbers provided; do not invent values.
- Cite a row reference for every claim.
- Flag anything you cannot reconcile rather than smoothing it over.
Run it in four steps
- Export department-level actual vs. budget for the period and note any in-flight context from the FP&A partner.
- Paste it into
{paste the data here}, set{month / quarter}, and name each department owner in{who reads this}for the personalized emails. - Run it to draft a per-department update with top variances and recommended actions.
- Read each draft for tone and accuracy before sending; a budget note to an owner carries more weight than an internal table.
When to reach for this prompt
Use monthly, the day after the close pack is final. Best for FP&A partners managing multiple department heads who each need a tailored update.
What you can expect back
Subject: Marketing — March budget update
Hi [Owner],
You came in -$28K (-4%) vs. budget for March:
- Paid media: +$120K (Q1 push), as planned
- Events: -$80K (we deferred the SaaStr booth)
- Tools: -$22K (Marketo seat reduction)
Top variance to investigate:
- Agency fees +$48K over budget — confirm the SOW change was approved
YTD: -$110K (-5%) — pacing well to land within annual envelope.
— FP&A
This prompt has real limitations you should understand.
Email tone defaults to neutral-professional, which lands as generic for execs who know you well. Add one sentence of human context (a callout from your last 1:1, a project that's mattering this month) or skip the email and call instead.
Generic tone reads as careless
Email tone defaults to neutral-professional, which lands as boilerplate for anyone who knows you. Add one human sentence per email or skip the prompt entirely — a five-line plain email beats a tidy template that says nothing.
Variance does not equal action
A department $28K under budget might be pacing well — or it might be a hiring delay that becomes a problem next quarter. The prompt cannot tell. "Top variance to investigate" is a hypothesis, not a finding.
Sensitive variances need a call
Compensation, retention, and restructuring variances should never go out by email — even from FP&A. The prompt will draft them anyway. Filter the variance list before letting it suggest anything for a written update.
What your data needs to look like
- Department-level actual vs. budget for the period
- A short note from the FP&A partner on any in-flight context
- Department owner names and reporting structure
See how FinanceOS handles this prompt on real financial data.
Book a 20-minute walkthrough. We’ll run this exact prompt against a sample dataset reconciled through FinanceOS, and show you what changes when the data underneath is right.
Book a walkthrough