What is the RACEF framework for variance commentary?

RACEF stands for Role, Action, Context, Examples, Format. It is a structured prompt framework designed for finance professionals using AI tools. For variance commentary, you define the AI's role (Finance Business Partner), the action (write commentary), the context (actual vs budget figures and known drivers), examples of the tone and style you want, and the format (paragraph length, sentence structure). The result is a usable first draft, not a generic output.

Which AI tool works best for variance commentary?

Claude Projects is the strongest choice for ongoing variance commentary because you can store your chart of accounts, reporting pack templates, and commentary style guide as project knowledge. This means you do not re-explain your cost centre structure every month. ChatGPT with a well-structured system prompt works similarly. Copilot for Excel is useful if your variance data is already in Excel and you want to generate commentary directly from the spreadsheet.

How much time does AI variance commentary save?

Finance teams we work with typically cut variance commentary time by 60-80%. A management pack covering 6-8 cost centres that previously took 2-3 hours to write takes 30-45 minutes after implementing RACEF prompt templates. The time saving is not in the AI writing the final version, it is in eliminating the blank-page problem and the iteration cycles to get to a polished draft.

Can I use these prompts with my existing ERP and Excel setup?

Yes. These prompts work with any ERP output. You copy the variance figures from your ERP or Excel, paste them into the Context section of the prompt, and Claude or ChatGPT generates the commentary. You do not need any integration between your ERP and the AI tool. The workflow is: export data, fill in the prompt template, review and edit the output.

Do I still need to review AI-generated variance commentary?

Yes, always. AI generates a first draft based on the context you provide. It does not know about the management meeting that explained a cost overrun, the one-off item that was deliberately excluded from the clean number, or the strategic context behind a deliberate volume trade-off. The human reviewer adds that layer. The prompts handle structure and language; you add judgment and business context.

Variance Commentary Prompts: RACEF Templates

Why Variance Commentary Takes So Long

Variance commentary is one of the most time-consuming tasks in a monthly close cycle, and one of the most resistant to efficiency gains. Unlike reconciliations, which can be automated by matching logic, commentary requires language. You need to explain what happened, why it happened, and what it means for the business. That requires judgment. But it also requires writing, and writing from a blank page every month is slow.

The finance teams we work with typically spend 2-3 hours per month on variance commentary for a management pack covering 6-8 cost centres or P&L lines. Most of that time is not analysis. The analysis is done. It is the drafting: finding the right words, maintaining a consistent tone across sections written by different people, and iterating until the commentary actually reflects what happened rather than what was easy to write.

RACEF-structured prompts eliminate the blank-page problem. You fill in the data. The AI produces a structured first draft. You review, adjust for context, and publish. For most teams, that shifts 60-80% of the commentary time out of drafting and into the value-adding work of reviewing and refining.

How We Built This With a Manchester Finance Team

One of our clients is a professional services business based in Manchester with around 150 staff across three practice areas. Their Financial Controller was spending over three hours each month drafting variance commentary for the board pack. The pack covered six cost centres, two revenue lines, and a headcount section. Each section was written separately, often by different people, leading to inconsistent tone and significant editing time before the pack went to the board.

We built a Claude Project for their monthly close process. Into the project knowledge we loaded their chart of accounts, their cost centre descriptions, two prior board packs as style references, and a set of RACEF prompt templates for each commentary section. The result: the first month using the system, commentary time dropped to 40 minutes. The second month, after refining the prompts based on the board's feedback, it dropped to 35 minutes. The quality improved because the AI was consistent in a way that seven people writing independently never quite managed.

The prompts below are adapted from the library we built for that client. They work in Claude Projects, ChatGPT with a system prompt, or Copilot with appropriate context. Fill in the square brackets with your actual data.

Want to go deeper? Our AI for Finance Leaders course covers this in detail with practical templates and exercises.

The Four Prompt Templates

Each template follows the RACEF structure: Role, Action, Context, Examples, Format. Copy the template, fill in the brackets, and paste into Claude or ChatGPT. For ongoing use, load these into a Claude Project or ChatGPT Project so you are not pasting the framework each month, only the data. For the full explanation of how RACEF works in finance contexts, see our RACEF framework guide.

Template 1: Revenue Variance Commentary

Use this for any revenue line where actual performance differs from budget. Works for total revenue, product/service line splits, or regional breakdowns.

ROLE: You are a senior Finance Business Partner preparing board pack commentary for a UK management team. You write clearly, directly, and without jargon. ACTION: Write variance commentary for this month's revenue performance against budget. CONTEXT: - Revenue line: [e.g. Consulting Revenue, Product A, UK Region] - Actual: £[X] - Budget: £[Y] - Variance: £[Z] ([Favourable/Unfavourable]), [X]% - Key drivers: [Driver 1 e.g. project delays in Q1 pipeline converting in April], [Driver 2 e.g. three new clients onboarded above initial estimates] - Prior month variance: [£ amount, F/U] - Board context: [Any strategic context the board needs e.g. "this line is being monitored against the growth target agreed at February board"] EXAMPLES: Do not use passive voice. Do not start with "This variance is due to". Be specific about amounts. If the variance is favourable, acknowledge what drove it without being promotional. FORMAT: Two to three sentences of narrative commentary. One sentence on the primary driver with the amount. One sentence on secondary driver if material. One outlook sentence if relevant. No bullet points. No subheadings.

Good output looks like:

“Consulting revenue was £42k favourable against budget, driven by the conversion of two pipeline clients that were expected in May but contracted in April, contributing £38k of the variance. A further £4k came from a scope extension on the Henderson project not included in the original budget. May is expected to be broadly on budget as the pipeline normalises.”

What to edit out:

Generic phrases like “the team performed well”, vague references to “market conditions” without specifics, or passive constructions like “this was driven by”.

Template 2: Cost Overrun Commentary

Use this for any operating cost line that is over or under budget. Includes a section for flagging one-off items and whether action is being taken.

ROLE: You are a Financial Controller writing management commentary for the monthly board pack. Your tone is direct and factual. ACTION: Write commentary explaining this month's operating cost variance. CONTEXT: - Cost category: [e.g. Professional Fees, IT Costs, Marketing Spend] - Actual: £[X] - Budget: £[Y] - Variance: £[Z] ([Favourable/Unfavourable]), [X]% - Main drivers: [Driver 1], [Driver 2] - One-off items included in actual: [Any one-offs e.g. "£8k legal fee for contract review not budgeted"] - Recurring vs timing: [Is this a structural overspend or a timing item?] - Action being taken: [If overspend is material and not timing, what is being done?] - YTD position: [£ YTD variance and F/U] EXAMPLES: If the overspend is timing-related, say so plainly and state when the reversal is expected. If it is structural, acknowledge it and state what action is being taken. Do not soften material overspends with vague language. FORMAT: Three to four sentences maximum. Lead with the variance amount. Identify the driver. Clarify timing vs structural. End with action or outlook if material.

If the variance is favourable: explain whether it is genuine underspend or timing (e.g. invoice delayed to next period)
If structural: the AI will flag it clearly so you remember to address it in the pack narrative
YTD field prevents the AI from treating a monthly blip as a systemic problem

Template 3: Volume vs Price Bridge

Use this when you need to decompose a revenue or cost variance into volume (quantity) and price (rate) components. Common in commercial reporting, retail, and professional services billing analysis.

ROLE: You are an FP&A analyst building a variance bridge for the commercial finance review. ACTION: Write the commentary section for a volume/price decomposition of [revenue line / cost line]. CONTEXT: - Total variance: £[Z] ([F/U]) - Volume component: £[V] ([F/U]) — effect of [selling more/fewer units / using more/fewer hours] than budgeted - Price component: £[P] ([F/U]) — effect of [selling at higher/lower price / paying higher/lower rate] than budgeted - Volume: [X] units/hours actual vs [Y] budget, [percentage]% [above/below] - Average price/rate: £[A] actual vs £[B] budget, [percentage]% [above/below] - Interaction effect if material: [Note if volume and price variances largely offset each other or compound] EXAMPLES: Explain the relationship between volume and price clearly — if they move in opposite directions, lead with the dominant one. If both are unfavourable, say which was the larger driver and why. Avoid saying "the bridge shows" — just explain what happened. FORMAT: One paragraph, four to five sentences. Include the component amounts in the narrative. Close with the net position and whether this is expected to persist.

Works for any line with a quantity and rate component: revenue, direct labour, materials cost, fee income
Particularly useful for professional services firms tracking billable hours vs fee rates
For more complex bridges (mix effects, currency), add a Mix component field to the Context section

Template 4: Headcount and Payroll Variance

Use this for the people cost section of the management pack. Separates headcount (volume) from rate (average salary) effects and handles the vacancy position cleanly.

ROLE: You are a Finance Business Partner writing the people cost section of the monthly management pack. ACTION: Explain the payroll and headcount variance against budget for this period. CONTEXT: - Headcount actual: [X] FTE - Headcount budget: [Y] FTE - Vacancy position: [Z] roles open, expected hire dates: [dates or "unknown"] - Payroll actual: £[A] - Payroll budget: £[B] - Variance: £[C] ([F/U]) - Volume effect (headcount below budget saving): approximately £[amount] - Rate effect (higher/lower average cost per head): approximately £[amount] - One-off items: [Redundancy costs, bonuses paid early, employer NI changes if applicable] - Affected departments: [List] EXAMPLES: Separate the headcount underspend from any rate effects clearly. Note any vacancies that are in active recruitment and the expected cost impact when filled. Do not mention individual names or salary figures. FORMAT: Two distinct paragraphs. Paragraph one: headcount position and volume effect on cost. Paragraph two: rate effects and one-offs. End with a one-sentence forward-looking note on the vacancy fill timeline and expected budget impact.

The vacancy position field is critical: without it, the AI treats headcount underspend as a pure saving rather than a recruitment lag
Rate effects often include employer NI changes, salary review timing, or grade mix shifts — add these explicitly
Works with any currency; adjust the format request if your board pack uses a different convention

Setting This Up in Claude Projects

The most effective way to use these prompts is to load them into a Claude Project so you are not re-pasting the templates every month. Here is the setup we use with clients.

Create a new Claude Project called “Monthly Commentary Pack” or similar
Add project knowledge: your chart of accounts, cost centre descriptions, and two recent board pack sections as style examples
Create a Skill (or custom instruction) for each template above, with the role, action, examples, and format sections pre-filled. Leave blank fields for context inputs
Each month, open the project, select the relevant Skill, paste in the actuals from your ERP or Excel, and generate the draft
Review the output, add business context the AI cannot know, and paste into your pack template

After the first two or three cycles, you will refine the prompts based on what your board or management team responds to. The prompts above are starting points, not final versions. Most of our clients make three to four edits in the first two months before the output consistently hits the mark.

For teams new to AI for finance, our AI finance audit includes a review of your current commentary process and a recommendation on whether Claude Projects, ChatGPT Projects, or a different setup suits your workflow best.

What the AI Cannot Do

These prompts save significant time, but they do not replace judgment. The AI generates commentary based on what you tell it in the context section. If you leave out the strategic context — the restructuring that explains the headcount underspend, the board decision that made the overspend deliberate, the trading conditions that make the revenue miss look worse than it is — the commentary will be technically accurate but miss the point.

The other limitation is data quality. If your actuals are wrong because of a misposting or an accrual that has not yet been processed, the commentary will be confidently wrong. The prompts are only as good as the numbers you put into them.

The workflow we recommend is: generate the draft, then read it as if you are the CFO seeing it for the first time. Ask whether it tells the right story. Add what the AI could not know. Cut anything that reads as generic filler. The AI gets you to an 80% draft in minutes. The final 20% is yours to add. For a broader view of how AI fits into the FP&A workflow, see our guide to AI in FP&A.

Where to Start

Pick one commentary section from your next management pack and run it through Template 1 or Template 2. You do not need to set up Claude Projects to test this — paste the prompt into Claude.ai or ChatGPT directly, fill in the brackets, and see what comes back.

Once you have seen the quality of the first draft, you will know whether this is worth building into a proper Claude Project setup for your full pack. Most finance teams who try it once do not go back to writing commentary from scratch. For teams who want help building and refining the full prompt library, our AI consulting team runs a one-day commentary prompt workshop as part of broader finance transformation engagements.

For finance professionals who want to develop their AI skills more broadly, our AI for Finance Leaders training covers RACEF prompting in detail, with worked examples across reporting, FP&A, and month-end close workflows.

Work with Prime AI Solutions

Self-Paced

AI for Finance Leaders

8 modules covering FP&A, reporting, automation, and governance. No coding required. From £99.

View course

Team Training

Live Workshop for Your Team

Half-day or full-day live sessions for finance teams. Tailored to your tools, workflows, and industry.

See workshops

Audit

AI Finance Audit

We map your finance function, identify what to automate, and give you a prioritised action plan.

Learn more

Done For You

AI Consulting

We design and build the workflow, configure the tools, and train your team. 90-day typical engagement.