Prepare a forecast-to-target brief
Combine current performance and forward indicators into a recurring forecast of likely month-end or week-end results.
How this works
Combine current performance and forward indicators into a recurring forecast of likely month-end or week-end results. Use this during a reporting period when managers need an estimate of likely closing performance against a target. The brief should explain uncertainty and drivers without treating the target as the expected result.
Run the established forecasting methods on a reconciled snapshot, compare their outputs and explain material differences. Keep actuals, forecasts and targets in separate fields. AI summarizes the evidence while formulas or approved analytical code produce the numerical estimates.
Before you start
Forecast method
Obtain the team's existing method, seasonal assumptions and validation history.
Current data
Collect actual performance and approved forward indicators with a shared cutoff.
Target definition
Confirm the metric, period and target basis.
Prepare the inputs
- actuals
- Required
dated observations, units and source
Check completeness through the stated cutoff.
- forward_indicators
- Required
pipeline, orders or other approved drivers
Preserve status and probability definitions.
- forecast_method
- Required
versioned formulas or model configuration
Do not silently replace the established method.
- target
- Required
metric, value and closing date
Ensure it matches the forecast's definition and period.
Implementation, step by step
Reconcile the snapshot
- Check actual totals, missing dates and indicator freshness.
- Separate late-arriving records from true zero activity.
Checkpoint: The forecast input is complete for its declared scope.
Run approved methods
- Calculate each estimate with the established formulas and assumptions.
- Retain method version, parameters and any excluded records.
Checkpoint: The numerical forecast is reproducible.
Compare with the target
- Compute the forecast gap and relevant scenario range.
- Keep target, actual and forecast values visibly distinct.
Checkpoint: The brief has a clear expected-versus-required comparison.
Explain differences
- Identify which data and assumptions drive changes between methods or prior runs.
- Label plausible explanations as hypotheses when the data does not establish cause.
Checkpoint: The narrative is evidence-backed.
Prepare owner review
- Present decisions that the forecast informs without promising corrective results.
- Record owner adjustments separately from model output and explain their basis.
Checkpoint: The forecast history preserves accountability.
Decisions along the way
Methods disagree materially
Show both estimates and investigate differing assumptions.
Seasonal comparison is unavailable
Use the established fallback or label the forecast less supported.
Target definition changes
Reconcile the comparison before describing a gap.
What you will produce
close-forecast-brief.md
MarkdownA concise outlook for the period owner.
Include: actual · target · forecast · range · drivers · questions
forecast-run.csv
CSVA reproducible record of each run.
Include: cutoff · method · parameters · estimate · target_gap · override
Check the result
- Reconcile actuals with source totals.
- Recompute forecasts and gaps using deterministic calculations.
- Verify comparisons use the same period and metric definition.
- Check uncertainty and owner overrides are visible.
When something goes wrong
Forward data is stale
Run a clearly labeled limited-data scenario or defer the estimate.
Formula references break
Repair and verify the model before drafting numerical conclusions.
Unexpected event invalidates assumptions
Record the break and request an owner-approved revised scenario.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: forecast month-end completed orders.
Inputs
At day 15, actual completed orders are 120. Approved linear method projects 240 for a 30-day month; target is 300. A separate committed-order method projects 260.
Expected result
Synthetic result: show forecasts of 240 and 260, gaps of 60 and 40, and explain method differences. Do not report 300 as expected merely because it is the target.
Run a small pilot
Start small
Run alongside the existing forecast for several comparable periods.
Record the baseline
Record forecast error, manual preparation time and override reasons.
Agree success criteria
Agree accuracy and interpretability criteria before operational reliance.
Stop or revise
Stop confidence claims when source completeness or method applicability fails.
Keep the scope clear
- Forecasts are conditional estimates and cannot promise period-end results.
- A brief does not authorize spending, staffing or commercial commitments.
Check before using
Reconcile the source data and show uncertainty. A forecast is a scenario estimate, not a promised outcome.
Business activities
- Manage finances and accounting
- Review business performance
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: Existing forecast scripts · Current actuals and future bookings · Targets and calendar effects
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow