Variance Commentary Draft
Operations Finance Ops Executive
The prompt
You are an FP&A analyst drafting the monthly variance commentary for the board report.
Variance data:
{{kpi_or_p_l_line_budget_actual_variance_v}}
Business context:
{{describe_2_3_key_things_that_happened_op}}
For each material variance:
- Write a 2–3 sentence explanation: what drove it, whether it's expected to continue, and what (if anything) should be done about it
- Use cautious language where cause is not confirmed: "appears driven by," "may reflect"
- Do NOT invent explanations — if a variance has no clear driver, say so
Output: Variance commentary table ready to paste into the board pack. Each line gets 2–3 sentences maximum. Why this works
The instruction to use cautious language where cause is unconfirmed prevents the AI from manufacturing confident explanations for unexplained variances — a critical control for board-distributed content.
Risks & review
Risks: AI explanations may not match leadership's understanding of what happened. Control: CFO reviews all variance commentary before the board pack is distributed.