Hire an AI department budget difference and options review

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A variance report by line: budget, actual, gap and the evidence for each
• A bridge from total budget to total actual, with recurring and one-off causes kept apart
• Two or three options for the rest of the year, each with its assumptions
• A short decision update for the budget owner
• A hand-back summary with one next step

How it does the job well

• Never move money or change a budget. You explain and propose only.
• A cause needs evidence from the files you were given. If there is none, write MISSING: evidence for <line>.
• Keep recurring drivers and one-off or timing differences apart.
• Agree the question and the decision it supports before analysing.
• Check the data first: date range, grain, missing values, duplicates and definitions.
• Compare like with like: same period length, definitions and segments.
• Separate what the data shows from what it might mean, and give confidence levels.

Mistakes it avoids

• Reporting a change without checking whether tracking or definitions changed.
• Treating correlation as cause.
• Averages that hide important segments or outliers.

What a good result looks like

An example, not your task: The month-end report shows a department over budget and the owner wants to know why.

• Variance report. Budget, actual and gap for each line, with the cause and the evidence for the biggest ones.
• Bridge. A walk from total budget to total actual, with recurring, one-off and timing causes kept apart.
• Options. Revised plans for the rest of the period, each with its assumptions and trade-off.
• Decision update. A short note with the variance, the choices, their effects and the facts still missing.
• Hand-back summary. Files saved, MISSING lines, checks missed and one next step.

How the work is checked

• The variance bridges from budget to actual with nothing left over.
• Every cause points to a source or a MISSING line.
• Recurring and one-off costs are kept apart in the bridge and the options.
• Nothing was sent and no budget was changed.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Budget variance explainer. Works out the gap on every line and traces the largest to your records. Marks each cause as recurring, one-off or timing. Hands the variance table to the next step.
• Department budget planner. Builds revised options for the rest of the period from that table, using stated assumptions and the owner's limits. Hands the options to the last step.
• Stakeholder update writer. Writes a short note with the variance, the choices, what each choice costs and the facts still missing.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id explain-a-department-budget-overrun only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/explain-a-department-budget-overrun/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The approved budget, line by line, for one period
• Actual spending for the same lines and period
• The reporting period and currency
• Known changes in the business, such as a new hire or a price rise (optional)
• Limits set by the budget owner on what can change, such as no job cuts (optional)
• Who the update is for and when they need it

Helpful context (optional)

• Invoices or notes behind the biggest lines.
• The budget owner's limits on what can change.

Tools and access

• A chat AI that opens spreadsheet files: It needs to read your budget and actuals. It also lets you check the bridge totals yourself.
• Any good chat AI: It only needs your notes pasted in. A tracker connection is a bonus, not a need.

Functions and deliverables

• Department budget difference and options review: Check actual spend against the budget. Trace major differences to the records and draft choices for the budget owner.
  • A variance report by line: budget, actual, gap and the evidence for each
  • A bridge from total budget to total actual, with recurring and one-off causes kept apart
  • Two or three options for the rest of the year, each with its assumptions
  • A short decision update for the budget owner
  • A hand-back summary with one next step
• Budget variance explainer: Find out why your actuals missed budget. Give it actual and budget numbers and get each gap split by cause, plus short notes for leadership.
  • A breakdown of each variance by cause
  • Volume, price and mix amounts
  • Short written commentary
  • A waterfall chart outline
  • A list of gaps worth action
  Source: Anthropic.
• Department budget planner: Build a department budget from past spending and targets. Get a monthly plan, variance reports and ideas to move money between teams.
  • Budget by department and line
  • Phased monthly plan
  • Variance report with causes
  • Reallocation suggestions
  Source: Burhan Sebin.
• Stakeholder update writer: Turn your rough progress notes into a weekly, monthly or launch update for leaders, engineers, partners or customers, sized to the reader.
  • A draft update sized to your reader, ready to paste
  • A status colour with a one-line reason
  • Each risk with a plan or an owner
  • Each decision with options and a recommendation
  • A list of facts you still need to add
  • A version for a second reader (optional)
  Source: Anthropic.
• Metric definition writer: Share a metric, calculation and business use. Get a YAML definition, validation results and questions for the data owner.
  • A filled metric, dimension or entity YAML
  • A validation report
  • dbt-ready field names
  • Notes on edge cases
  Source: Nimrod Fisher.

Tasks you can use it for

• The month-end report shows a department over budget and the owner wants to know why.
• You must explain a variance to your manager or finance lead by Friday.
• A department head asks what they can do about the rest of the year.
• You are not sure if an overrun is a one-off or a new monthly cost.

Limits to check before starting

• One line looks odd and you only need a quick answer. Use the Budget variance explainer.
• You are building next year's budget. Use the Department budget planner.
• You need accounting adjustments or an audit of accruals. Ask your accountant.
• You are checking stock count differences. Use the Warehouse stock variance reviewer workflow.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It is a zip with HANDOFF.md and the skill files this workflow uses.
• Give the folder to Claude, ChatGPT or Gemini and say "Follow HANDOFF.md".
• Attach the budget and the actuals. Name the period and the person who will read the update.
• Read the variance table first. Check that each cause matches what you know about the department.
• Fix any wrong assumption in the options, then send the update to the budget owner.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/explain-a-department-budget-overrun for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.