forecast-narrative

name	forecast-narrative
description	Explain a forecast period; not a raw-total lookup.
metadata	{"short-description":"Explain forecast movement, risk, and upside"}

Forecast Narrative

Outcome

A decision-ready narrative explaining the forecast, changes, risks, upside, and confidence limits.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Forecast categories, opportunity values and currencies, prior snapshots, targets, stage and date changes, deal evidence, and rollup hierarchy.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Respect configured forecast categories and fiscal periods; define any translated labels.
2. Reconcile totals before explaining them and distinguish booked, committed, likely, upside, and excluded amounts as configured.
3. Explain change since the comparison snapshot by additions, progression, value changes, slips, wins, and losses.
4. State data freshness, coverage, concentration, and scenario assumptions; avoid false precision.

Required output

• Forecast headline
• Current position and change bridge
• Commit evidence
• Upside and downside
• Concentration and data caveats
• Leadership actions

Actions and boundaries

Remain read-only; forecast-category or amount changes require a separate confirmed update.