Explaining Budget Variances to Funders

A copy-paste AI prompt that builds a variance table and a plain-language narrative for your funder, and flags where a reallocation may need approval.

What This Prompt Does

Give it your line-by-line budget-versus-actual comparison and the approval terms from your agreement. It returns a variance table, a short narrative a funder can read without a finance background, and a list of gaps you still need to fill.

Remove the names of individuals and any confidential terms before you paste anything. Leave out individual salaries and beneficiary details. Follow your organization's data policy on what may go into an AI tool.
You are helping a grants manager explain budget variances to a funder. Work only from the data I give you. Do not guess causes. Reporting period: [REPORTING PERIOD] Budget and actuals, including committed costs not yet recorded: [BUDGET LINES WITH BUDGET, ACTUAL AND COMMITTED AMOUNTS] Significance threshold: [DOLLAR AMOUNT] and [PERCENT] Reallocations already approved or made so far under this award: [CUMULATIVE TOTAL] Agreement terms on approval and reallocation: [PASTE CLAUSES] Causes from program staff: [PASTE NOTES] Do the following. 1. For every line, calculate the variance amount (budget minus actual) and the variance percent. Label it Favorable if actual is below budget and Unfavorable if above. Count committed costs when judging what remains. 2. Flag every line above BOTH the dollar and percent threshold. Mark the rest "Below threshold". 3. Classify each flagged line as Timing (the approved activity will still happen, only earlier or later) or Genuine (the activity cannot proceed as planned, the cost is ineligible, the budget assumption is no longer realistic, or commitments are slipping). Say whether the cause will continue or was a one-time event. Where a period variance does not carry into year to date, say it was probably timing. 4. Explain each flagged line in plain language with quantified components. List each component with its amount, include items that offset in the other direction, and keep adding the next largest until about 80% of the variance is explained. If my notes do not support a component, write "Cause not supplied" instead of inventing one. 5. For favorable underspends on personnel or critical activities, say whether it may mean vacant positions or undelivered work. 6. Flag any line that may need prior approval. If my agreement has a percentage test on transfers, check whether it applies to the cumulative total of changes and not to each change alone. Treat changes to staffing or time commitment as possibly needing approval even if small. Quote the exact clause you rely on. If no clause covers it, say so. Output, in this order: A. A table with these columns: Line | Budget | Actual | Variance amount | Variance % | Favorable/Unfavorable | Timing or genuine (leave blank for Below threshold lines) | Quantified cause | Approval needed and clause quoted B. A short funder-ready narrative covering only the flagged variances, in simple language. C. A list of questions for me wherever a cause is missing or the components do not add up.
Open it, with the prompt already in:ChatGPTClaudeGemini(opens empty)

How to Use It

  1. Pull budget and actuals for the same period, ideally year to date, and add committed costs. Do this monthly or quarterly so variances surface early and you can tell the funder before the final report.
  2. Choose your significance threshold, a dollar amount paired with a percent, so you explain a few large variances well instead of many badly.
  3. Ask program staff what happened. Finance often cannot see the causes.
  4. Paste the approval and reallocation clauses from the agreement, plus your running total of reallocations.
  5. Run the prompt. If approval is needed, write the request: list the categories to increase and decrease with dollar amounts, and give reasons and basis for the change.

Check the Output

  • Add up the explained components for each flagged line. They should reach most of the variance, and each needs an amount.
  • Test every timing or genuine call against the definitions of a favorable and unfavorable variance and the step 3 wording. A timing label only fits if the activity will still happen.
  • Compare each approval flag with the quoted clause and your cumulative total, and ask of each material variance whether it will continue or was a one-time event. Confirm the quote is really in your agreement.