LearnGrok
Prompts
PromptIntermediatePrompting

Budget reforecast bridge for executive decisions

Build a reconciled reforecast bridge and decision list for FP&A teams preparing executive review materials.

5 min read

Nothing here is financial advice, and none of it replaces your own checks.

These prompts help you turn actual results, the approved budget and revised operating assumptions into a reforecast bridge that executives can act on. They are for FP&A teams preparing a review pack, where a plausible narrative is not enough and every material number needs a source.

Nothing here is financial advice, and none of it replaces your own checks. Use the prompts to draft and test management-reporting work products. Your finance lead and relevant decision-makers remain responsible for the figures, assumptions and decisions.

Key point

Start with comparability

A bridge is only useful when actuals, budget and forecast cover the same period, scope, currency and sign convention.

1. Check the source documents first

Start with Reforecast source and reconciliation check. Paste the actuals, budget and assumptions as separate labelled blocks. Do not combine them into one spreadsheet extract without labels. The prompt needs to identify whether, for example, the budget is full year while actuals are year to date, or whether cash is reported at group level but operating costs are for one business unit.

Use its source-control table as the working record for the pack. Assign an owner to every unresolved item before you start explaining movement. Common problems include:

  • Revenue stated net of rebates in actuals but gross in budget.
  • A hiring assumption with no start month or fully loaded cost.
  • Cash movements that omit capex or working capital.
  • KPI definitions that changed between planning cycles.
  • Forecast assumptions stated as percentages with no base volume.

Watch out

Do not force a number into an unresolved gap

An unexplained plug may make a bridge add up, but it removes the evidence executives need to trust it.

2. Build the four bridges

Run Revenue, cost and cash bridge only after the source check shows that the inputs are comparable, or clearly records the exceptions. This prompt separates revenue, operating costs, closing cash and operational drivers. Keep those bridges separate even if your final pack shows a combined headline table.

The split matters. A revenue shortfall can reduce cash, but an increase in receivables days can also reduce cash without changing revenue. Likewise, delayed hiring may improve the near-term cost forecast but create a delivery risk. The bridge should make those relationships visible rather than hiding them in one variance line.

Set a materiality threshold before running the prompt. Use the threshold already applied in your planning process. Ask the model to name material drivers individually and group only genuinely immaterial items. The output should state a start point, an end point and a residual for every financial bridge.

Check

A bridge has passed its first test when the start point plus every quantified movement equals the end point, with a zero explained residual.

If a residual remains, do not label it “other” unless you have identified its source. Keep it as unresolved and assign it for follow-up.

3. Separate evidence from interpretation

Use Driver narrative and sensitivity review to write the explanation around the numbers. It asks for evidence, confidence and what could change the outcome. This stops the common error of presenting an operational assumption as a proven cause.

Read the “Timing versus structural” section closely. Timing items should have a clear expected reversal or rescheduling point, such as a contract start date moving into the next month. Structural items should represent a more lasting change, such as a revised price list, a sustained cost increase or a changed demand assumption. If the source material does not establish the classification, keep it unresolved.

The sensitivity section is deliberately constrained. It should report only alternative cases supplied by your team. Do not ask the model to create upside cases, downside cases or probabilities from thin evidence.

4. Draft the executive memo last

Use Executive reforecast memo and decisions after the bridge and narrative are checked. Paste both, along with the meeting date and reporting period. The memo puts the decision request after the headline position, bridge summary and risks, so executives can see the supporting evidence before they are asked to act.

A decision request must be specific. “Discuss cost control” is not a decision. “Approve a pause on the named recruitment requisitions until the next forecast review” is a decision request, provided the source material supports it. Where evidence does not support a decision, the prompt instructs the memo to say so.

Note

Keep decisions separate from forecast commentary

A forecast can report an issue without implying that a particular response has been approved or is appropriate.

5. Run a release check

Finish with Board pack bridge quality check. It compares the bridge, memo and source-control record. Use its severity column to decide what must be corrected before circulation. A critical issue is normally a non-reconciling total, inconsistent period, unsupported headline claim or missing cash explanation.

How to tell the output is wrong

Check the model output against the underlying files, not against whether it sounds coherent. Pay particular attention to these failure signs:

If you see this Check this Do this next
A variance has the right direction but wrong size Formula, unit, period and sign Recalculate from the named source fields
Cash moves without a driver Working capital, capex and financing lines Add the missing cash-flow source or mark it unresolved
A narrative claims a cause Evidence column and source wording Downgrade it to an assumption if causation is not evidenced
A decision has no owner or deadline Decision table Return it to the meeting sponsor for completion

For version-dependent product behaviour or input handling, check the xAI documentation overview before using sensitive or large reporting material.

Stop

Do not circulate a polished memo with unresolved material residuals

A clear caveat is better than a false reconciliation in an executive pack.

When it does not work

If the bridge is incomplete, return to the source-control output rather than repeatedly rewriting the memo. Supply the missing period, scope, driver definition or source field. If the bridge reconciles but the narrative is weak, rerun the driver review with the relevant operating commentary. If the final quality check says “Do not release”, correct the named source issue, rebuild the affected bridge and rerun the release check.

Copy-ready prompts

5 prompts. Open one to read it, or take the whole pack.

1Reforecast source and reconciliation checkUse this first, before building the bridge. It identifies missing inputs and confirms that the three planning views can be compared.
You are reviewing inputs for an FP&A reforecast bridge. Compare the documents below: Actual results, Approved budget, and Revised operational assumptions.

[Paste actual results, including period, currency, entity, revenue, cost of sales, operating expenses, capex, working-capital movements, cash, and operational KPIs]

[Paste approved budget, using the same fields where available]

[Paste revised operational assumptions, including volume, price, headcount, hiring dates, churn, payment terms, inventory, capex, and timing assumptions]

Create a source-control table with these columns: Metric or driver | Actual source and period | Budget source and period | Revised assumption source | Unit and currency | Comparability status | Issue or missing item | Required owner action.

Then provide:
1. A reconciliation checklist for revenue, costs, cash and key drivers.
2. A list of all period, scope, currency, accounting-treatment, and sign-convention differences.
3. A list of assumptions that cannot yet be translated into a financial impact.

Do not calculate a bridge. Do not fill gaps with estimates. If a value is absent, contradictory, or not comparable, write “unresolved” and state exactly what document field, period, or owner is needed. Treat all figures as management-reporting inputs, not financial advice.
2Revenue, cost and cash bridgeUse this after the inputs reconcile. It produces the core movement analysis for the reforecast pack.
Create a reforecast bridge from Actual results and Approved budget to the Revised forecast, using the revised operational assumptions supplied below.

[Paste reconciled actual results]

[Paste reconciled approved budget]

[Paste revised operational assumptions]

[Paste the reporting period, currency, materiality threshold, and whether favourable variances are shown as positive]

Build four separate bridges in this order: Revenue, Operating costs, Closing cash, and Key operational drivers.

For each financial bridge, use this exact table format:
Start point | Driver category | Driver name | Budget amount | Actual-to-date amount | Revised forecast amount | Movement versus budget | Movement versus latest actual run rate, if calculable | Timing or structural | Evidence and calculation note.

Use only these driver categories where relevant: volume, price or mix, timing, foreign exchange, headcount, productivity, supplier cost, discretionary spend, capex, working capital, financing, and other. Split “other” into named drivers when information permits.

After the tables, write:
- A five-bullet executive readout, with the largest movements first.
- The three most important links between operational assumptions and cash.
- A list headed “Unresolved bridge items”.

Reconcile every bridge mathematically. State the start point, end point, and residual for each. If a driver cannot be quantified, show its amount as “unresolved”, exclude it from totals, and explain what is needed to quantify it. Do not invent allocations, run rates, or causal explanations. Treat this as management reporting, not financial advice.
3Driver narrative and sensitivity reviewUse this when the bridge numbers are complete but the reasons for the movement are unclear or need a sharper executive narrative.
Review the reforecast bridge and operational assumptions below. Produce an executive-level explanation of the movement in revenue, costs, cash and key drivers.

[Paste completed reforecast bridge]

[Paste revised operational assumptions]

[Paste prior forecast commentary or current trading commentary, if available]

Use this exact structure:
1. “What changed”: six bullets, each stating the metric, direction, amount, period, and named driver.
2. “Why it changed”: a table with columns Metric | Financial movement | Operational cause | Evidence from source material | Confidence level (high, medium, low) | What could change the outcome.
3. “Timing versus structural”: classify each material movement as timing, structural, mixed, or unresolved. Explain the classification in one sentence.
4. “Sensitivity items”: list only sensitivities supported by supplied assumptions. For each, show Assumption | Base case | Alternative case, if provided | Affected metric | Direction of impact | Missing quantification.
5. “Management interpretation”: a maximum of 180 words, written for an executive review.

Do not describe correlation as causation unless the supplied material establishes causation. Do not create alternative cases, probabilities, or forecast amounts where none are supplied. Mark conflicting evidence as “unresolved” and quote the conflicting source fields. Treat all content as management reporting, not financial advice.
4Executive reforecast memo and decisionsUse this to turn the checked bridge into a short decision document for the executive meeting.
Draft an executive reforecast memo from the materials below. The memo must explain the movement from Approved budget to Revised forecast and end with decisions needed from the executive team.

[Paste checked revenue, cost, cash and key-driver bridges]

[Paste driver narrative and sensitivity review]

[Paste meeting date, reporting period, company or business-unit name, currency, and materiality threshold]

Write in this exact format:

Subject: Reforecast review, [reporting period]

Purpose: Two sentences stating what the executive team is being asked to review and decide.

1. Headline position
A table with columns Metric | Approved budget | Revised forecast | Variance | Variance % | Primary driver. Include revenue, gross profit or cost of sales where supplied, operating costs, operating profit or loss where supplied, closing cash, and up to three operational KPIs.

2. Bridge summary
Four bullets covering revenue, costs, cash, and key drivers. Each bullet must name the largest quantified movement and its evidence.

3. Risks and unresolved items
A table with columns Item | Effect on forecast | Confidence | Owner | Required clarification before decision.

4. Decisions needed
Number each decision. For every decision, state: Decision requested | Why now | Financial or operational consequence if deferred | Named owner | Decision deadline. Include only decisions supported by the supplied material. If no decision is justified, write “No decision request supported by the current evidence”.

5. Appendix: bridge reconciliation
Show start point, end point, quantified movements, unresolved movements, and residual for revenue, costs and cash.

Use neutral, precise language. Do not present estimates as facts. Do not add recommendations that are not supported by the source material. This is a management-reporting draft, not financial advice.
5Board pack bridge quality checkUse this as the final review before the bridge and memo go into an executive or board pack.
Act as a quality reviewer for the reforecast bridge and executive memo below.

[Paste final reforecast bridge]

[Paste final executive reforecast memo]

[Paste source-control table, if available]

Test the pack against these checks: arithmetic reconciliation, consistent periods, consistent currency, consistent sign convention, consistent scope, source traceability, distinction between actuals and forecast, distinction between timing and structural movements, complete cash explanation, and clear decision ownership.

Return exactly three sections:

1. Quality-check table
Use columns Check | Pass, fail, or unresolved | Evidence found | Exact correction required | Severity (critical, material, minor).

2. Contradictions and unsupported statements
For each issue, quote the relevant bridge or memo wording, identify the conflicting number or missing source, and provide replacement wording only if the source material supports it.

3. Release decision
Write one of these outcomes: “Ready for executive review”, “Ready subject to listed corrections”, or “Do not release”. Then list the critical corrections in priority order.

Do not silently correct figures. Do not infer missing data. If totals reconcile only because of an unexplained residual, mark the relevant check as fail. Treat this as management-reporting quality control, not financial advice.

Last checked against xAI’s own pages on 2026-08-21. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

More in Prompting

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →

Advertise on LearnGrok

$420.69one-time, for a 30-day run

Square works best. PNG, JPEG or WebP, up to 2 MB.

Stripe on the next step. Live once approved.