PlaysbyMoat8
Back to the library
The workflow guideFinance

Maintain a rolling financial outlook

Refresh expectations beyond the calendar year without confusing the forecast with a performance target.

6 implementation stepsIntermediate

How this works

Refresh expectations beyond the calendar year without confusing the forecast with a performance target.

Refresh expected financial outcomes over a moving horizon while keeping the approved target intact. Explain changes through updated actuals and assumptions, and distinguish a forecast revision from permission to spend or a revised performance commitment.

Before you start

Defined operating scope

Finance refreshes expectations over a rolling horizon using actuals and current business assumptions.

Required source material

Obtain Actuals; Current business assumptions; Planning horizon. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

Actuals are provisional or unreconciled. Label the period accordingly and avoid treating it as a closed baseline.

Prepare the inputs

actuals
Required

Closed-period figures and status

Reconcile to the approved accounting source.

assumptions
Required

Volume, prices, costs and timing

Record owner, date and basis.

horizon
Required

Number of future periods and cadence

Extend consistently after each closed period.

prior_outlook
Required

Previous version and targets

Preserve comparisons without overwriting history.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check actuals, assumptions, horizon, prior_outlook before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected actuals and any missing required fields.

  2. Update the latest actuals and assumptions

    • Replace completed-period forecasts with reconciled actuals and review the assumptions for remaining periods.
    • Reconcile actuals and test formulas across the added horizon period.

    Checkpoint: A saved intermediate result for: Update the latest actuals and assumptions.

  3. Extend the agreed rolling horizon

    • Extend the agreed horizon by adding the new future period, carrying formulas and explicit assumptions rather than copying unexplained values.
    • Compare versions by driver and check that target, forecast and actual remain separate.

    Checkpoint: A saved intermediate result for: Extend the agreed rolling horizon.

  4. Explain changed expectations and decisions needed

    • Explain changes from the prior outlook by driver, identify decisions needed and retain targets separately for performance discussion.
    • Reconcile actuals and test formulas across the added horizon period.

    Checkpoint: A saved intermediate result for: Explain changed expectations and decisions needed.

  5. Reconcile the proposed result

    • Reconcile actuals and test formulas across the added horizon period.
    • Compare versions by driver and check that target, forecast and actual remain separate.

    Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.

  6. Package the result and unresolved work

    • Review bias and distinguish expected outcomes from targets and funding approval.
    • Forecasts express current expectations, not guaranteed outcomes or spending approval.

    Checkpoint: An updated outlook and assumptions log. Unresolved items remain visible in the review record.

Decisions along the way

Actuals are provisional or unreconciled.

Label the period accordingly and avoid treating it as a closed baseline.

A manager requests a forecast equal to the target without evidence.

Keep expected outcome and target separate and ask for the supporting assumption change.

A formula breaks when the horizon extends.

Reconcile the model and stop sharing the updated version until calculations are corrected.

What you will produce

rolling-financial-outlook-result.json

JSON

An updated outlook and assumptions log. Label proposed and completed states separately.

Include: period · actual · forecast · target · assumption_version · change_driver · decision_needed · outlook_version · status · evidence_reference · review_note

rolling-financial-outlook-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving prior_outlook.

Include: source_reference · question · owner · next_action

Check the result

  • Reconcile actuals and test formulas across the added horizon period.
  • Compare versions by driver and check that target, forecast and actual remain separate.
  • Inspect actuals and assumptions in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Review bias and distinguish expected outcomes from targets and funding approval.

When something goes wrong

Actuals are provisional or unreconciled.

Label the period accordingly and avoid treating it as a closed baseline. Retain the affected evidence and recovery status.

A manager requests a forecast equal to the target without evidence.

Keep expected outcome and target separate and ask for the supporting assumption change. Retain the affected evidence and recovery status.

A formula breaks when the horizon extends.

Reconcile the model and stop sharing the updated version until calculations are corrected. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Maintain a rolling financial outlook for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Prior outlook expected 100 units in October and 110 in November. October actual is 90; revised November demand supports 105. Target remains 110.

Expected result

Synthetic expected result: Outlook shows October actual 90, November forecast 105 and November target 110 in distinct fields, with the demand change recorded. No funding authorization follows from the forecast.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure forecast error by horizon; assumptions reconciled and preparation time.

Stop or revise

A formula breaks when the horizon extends. Pause affected records and apply this recovery: Reconcile the model and stop sharing the updated version until calculations are corrected.

Keep the scope clear

  • Forecasts express current expectations, not guaranteed outcomes or spending approval.
  • Finance owners review assumptions, bias and material decisions before using the outlook.

Check before using

Review bias and distinguish expected outcomes from targets and funding approval.

Business activities

  • Manage finances and accounting
  • Review business performance

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Actuals · Current business assumptions · Planning horizon

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗