Write a Plain-English Expense Variance Narrative

Every monthly reporting package needs an expense commentary, and writing it well is a specific skill: you have to explain why opex came in where it did without burying the reader in line-by-line detail. This prompt produces that narrative, grouping related categories so the story reads logically instead of as a list. The key analytical move is separating timing from substance. A category that's 'over budget' because an invoice landed a month early is a very different story from one that's genuinely overspending, and lumping them together misleads the reader. The prompt explicitly calls out timing versus true variance, which is exactly the distinction non-finance readers miss on their own. It writes for an accessible audience, uses real figures from your inputs, and stays within your word limit so it drops straight into the package. Because attribution can be uncertain, it hedges where it should — you're getting a polished draft, not a set of unverified claims.

What you can expect back

May operating expense ran modestly above plan, driven largely by timing rather than structural overspend. Marketing was $40K over, almost entirely because the annual conference sponsorship was paid in May rather than the budgeted June — a timing shift that should reverse next month, not incremental spend. Cloud infrastructure came in $15K higher, tied to a usage spike from the product launch; we expect this to partially normalize as launch traffic settles, though some may persist. Professional services were $12K over for outside counsel on a contract review, a one-time engagement. Offsetting these, payroll was $30K under plan from an open engineering role, and travel was $8K lower than budgeted. Netting timing-driven and one-time items against genuine savings, total operating expense finished roughly $29K above plan, most of which is expected to reverse or not recur.

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Tag each driver as timing or structural in your input if you know — the model leans on your labels and hedges appropriately where you don't.
• 02Group naturally related lines (all the launch-driven costs together) so the narrative tells one story instead of five fragments.
• 03Keep the word limit tight; reporting packages reward a commentary an executive can read in thirty seconds.
• 04Have it end with the net number so readers get the bottom line even if they skim the detail.

Adapt it for your case