Role Playbooks4 min read

Turn a Budget Variance Table Into Evidence-Tagged Commentary With AI

Use AI to structure budget commentary without letting a plausible guess become a financial explanation.

Bokili EditorialPublished September 23, 2026· Verified September 23, 2026

Budget variance table flowing through evidence cards into management commentary

A budget table can show that spend is £42,000 above plan. It cannot show why. When a finance team asks an AI tool to “explain the variance”, the model may turn a numerical pattern into a fluent cause. That is useful drafting behaviour in the wrong place. A monthly commentary should separate what the ledger proves, what operational evidence supports and what still needs an answer.

Do not ask the model to discover a cause from the numbers

Calculate the variance first. Then give the model approved evidence and require every causal statement to show where it came from.

Use AI for structure, not unsupported diagnosis

The UK Government Data Quality Framework treats quality as fitness for purpose and warns that completeness does not guarantee accuracy. It also recommends communicating known quality problems. For variance commentary, that means a clean table is only the start. The reviewer still needs to know the period, baseline, account definition, missing inputs and the source behind any explanation.

The NIST Generative AI Profile identifies confabulation as a risk: a system can present false or inconsistent content confidently. The UK Government AI Playbook adds a practical control—define roles, human intervention, evaluation and quality evidence across the life cycle. Applied to finance, the model may organise approved facts, but the analyst owns the calculation, the evidence boundary and the final judgement.

Three labels for every commentary sentence

FACT

A value computed from the approved table: actual, plan, absolute variance, percentage variance or a defined trend.

SUPPORTED CAUSE

An explanation backed by a named source such as an invoice, contract change, hiring record or note from the accountable owner.

QUESTION

A plausible line of enquiry that has not yet been evidenced. Phrase it as a question, never as an explanation.

Turn a budget variance table into a controlled AI workflow

The evidence-tagged commentary workflow

1
1. Lock the calculation
Use the spreadsheet or finance system to calculate actual, plan, variance and percentage. Do not ask the language model to recreate totals from a long paste.
2
2. Build a small evidence pack
For each material line, add the source, owner, date and one short evidence note. Remove personal, restricted or unnecessary data before using an approved AI tool.
3
3. Draft with strict labels
Ask the model to use only the table and evidence pack. Require FACT, SUPPORTED CAUSE or QUESTION at the start of each sentence.
4
4. Review and publish without the labels
Check every number against the table and every cause against its source. Resolve or retain open questions. Remove working labels only after review.

Worked example: software spend is 18% above plan

Suppose the approved table shows software spend of £118,000 against a plan of £100,000. The evidence pack contains a renewed security licence invoice for £11,500 above the planned amount, dated 6 September. It also contains an owner note saying that two planned cancellations have not yet appeared in the ledger. There is no evidence for the remaining difference.

Reading is a start. Practice makes it stick.

Start learning

	Unsafe commentary	Evidence-tagged draft
Variance	Software costs rose because the team added new tools.	FACT — Software spend is £18,000, or 18%, above plan.
Supported cause	The increase was driven by security needs.	SUPPORTED CAUSE — £11,500 relates to the security licence renewal, supported by the 6 September invoice.
Gap	The rest reflects delayed cancellations.	QUESTION — Have the two planned cancellations been credited, and in which period will they appear?

This draft is less dramatic, but it is more useful. It tells the reader what is known, how much of the variance has evidence and which answer is still needed. It also gives the analyst a clear route to completion instead of hiding uncertainty inside polished prose.

A prompt that keeps the evidence boundary visible

Draft the commentary from approved inputs

You are helping to structure a monthly budget commentary. Use only the variance table and evidence notes below. Do not infer causes from numerical patterns. Write one sentence for the material variance and prefix every sentence with FACT, SUPPORTED CAUSE or QUESTION. A SUPPORTED CAUSE must name its evidence. If evidence is missing, write a QUESTION. Keep amounts, periods and signs exactly as supplied.

FACT — Software spend is £18,000, or 18%, above plan. SUPPORTED CAUSE — £11,500 relates to the security licence renewal, supported by the 6 September invoice. QUESTION — Have the two planned cancellations been credited, and in which period will they appear?

Use fictional or approved data for practice. Follow your organisation’s rules for financial and personal information.

Reviewer’s five checks

Recalculate every amount and percentage in the source system.
Confirm that each cause names a real source, owner and date.
Keep assumptions and unresolved items as questions.
Check that the period, currency, sign convention and baseline are explicit.
Have the accountable analyst approve the final wording.

Tag one variance in ten minutes

Choose one material variance from a safe practice table.
Write the fact without any cause.
Add one evidence note with its owner, date and source.
Ask an approved AI tool for a three-sentence tagged draft.
Trace each number and cause back to the source.
Turn every unsupported explanation into a question.

Carry the evidence into the next handoff

The same discipline helps beyond finance. The AI handoff card shows how to carry inputs, checks and open issues into human review. The acceptance-test guide keeps drafting separate from judgement. For a management audience, the project decision brief turns status material into a clear request without hiding uncertainty.

Make uncertainty visible before prose becomes final

AI can reduce the effort of shaping a consistent commentary. It should not promote a guess into a cause. Lock the calculation, attach a small evidence pack, label each sentence and keep unanswered points visible. The result is a faster draft that a reviewer can actually audit.