Start a clean forecast cycle
Drop the three current operating sources together. The Studio checks the set, fingerprints it, archives any active cycle, seeds a clean run, and binds every response to the new Cycle ID.
Required: cumulative invoices, cumulative open orders, and FY27 Sales Sync Inputs.
Optional context: CEOHeader_latest.json, forecast_log.json, and book_history.json. Learning files are inventoried but never exposed as sales-leader inputs.
Active cycle
No controlled cycle has been started in this browser.
Two governed forecast views
The internal forecast remains the approved sales commitment. Finance may create a separate external-facing view without changing what sales submitted or sees.
Pre-release assumptions
Protected Finance assumptions included in the internal starting point before leader assignments are issued.
External top-side overlay
Confidential hedges and management adjustments applied only to the external-facing forecast after channel approval.
Internal and external forecast bridge
The bridge preserves the approved sales forecast and shows exactly how Finance reaches the external-facing view.
Actual close status
Final only when every channel is locked; mixed channel status is partially final.
Revenue shape
Final actuals include locked close adjustments. Forecast separates baseline, weighted pipeline and leader judgment.
Monthly forecast by channel
Internal sales-accountability forecast. P1–P12 reconcile to the chart and the company total; click a channel to open its builder.
What is driving the full-year call
Separates run rate, named initiatives, and other pipeline; compares each channel with plan and FY26.
Named initiatives against plan
Realized revenue plus probability-weighted future pipeline, with the weighted-to-gross ratio as a pipeline-quality signal.
Build and close the year
Open an actual month to finalize it, or a projected month to adjust run rate. Locked actuals exclude pipeline and run-rate judgments.
Account-level run rate
Top-20 accounts always retain their own baseline forecast. A specific account call changes only that account and replaces macro treatment for the same periods.
Pipeline by initiative
Weighted incremental revenue; order-received rows stay visible but add $0 to avoid double counting open orders.
Forecast by product family
Future channel forecasts are allocated using the same fiscal-period family mix in FY25–FY26; known open orders retain their own family.
Revenue mix
Full-year forecast.
Initiative allocation rules
Source-data rules that attribute realized revenue to initiatives. Rule definitions are maintained with the forecasting team; pipeline basis decisions are owned by sales leaders.
Observations on your forecast
The Studio evaluates the forecast you have now—not every put-and-take used to reach it.
Questions to be prepared to answer
Respond here while the reasoning is fresh. Answers can become executive talking points.
Submission talking points
A concise end-state narrative for the executive review.
Activity history · detailed audit record
Every non-model change remains available for traceability, but is excluded from the executive narrative.
Forecast method
Simple enough to audit, strong enough to operate.
- Actuals: source invoice revenue remains open for close until Finance locks each channel-period; locked periods use final reported actual.
- Close adjustments: gross-to-net, deferrals, and other close entries affect only reported actuals. They never change future pace, seasonality, account shares, pipeline, or run-rate baselines.
- Current month: the proven month-end engine blends in-month completion with 12-month pace, seasonality and momentum, then shows the confirmed open-order floor.
- Future baseline: trailing daily pace × recent momentum × same-period fiscal seasonality. Confirmed open orders are a floor, not an add-on.
- Pipeline: opportunity value × stage probability, placed in its expected period or spread across its stated quarter. “Won – order received” is excluded from incremental impact.
- Leader judgment: every run-rate or pipeline change requires a written reason. Forecast Review evaluates the resulting end-state; detailed changes remain in the collapsed audit record.
- Product family: actuals use the source category; close differences are shown separately, while future baseline uses historical fiscal-period mix.
Hosted connection wizard
Complete the steps in order. Required fields block readiness; optional services can remain disabled.
Name the environment and tell the browser where the hosted application and its server API will live. Use the development or test environment first.
Identify the single-tenant Entra application, the managed identity used by the server, and the group that may enter this commissioning panel. Paste identifiers only - never secrets.
Point the managed identity to the approved read-only Forecast Intake location. The app must not receive tenant-wide file access and must not be able to edit source files.
Point the server to the write-controlled Forecast Control workspace and the Azure services that hold cycle state, snapshots, diagnostics, and secrets. Enter resource names and URIs only.
Choose how assignments are opened and how leader work returns. The recommended hosted flow sends authenticated links and receives centrally autosaved submissions - not returned HTML files.
Review configuration completeness, then ask the protected server to test its own identity and resources. Browser-only validation is amber. A service turns green only when a backend health response reports success.
Setup findings
Plain-language next actions based on the current configuration and test evidence.
Public configuration summary
Review before exporting. No credential or secret fields exist in this build.
What the hosted backend must expose
The browser never tests Graph, SQL, Storage, or Key Vault with credentials. Protected server endpoints perform those checks and return sanitized results.
Forecast review preview
Current end-state observations; detailed questions and responses live in Forecast review.