Give each statement a visible status
Separate observed results, estimates, forecasts and targets. An observed result needs a period and source. An estimate needs a basis. A forecast describes an expected outcome under stated assumptions; a target describes an intended outcome.
Use these distinctions beside the relevant number, chart or statement. A general disclaimer at the back of the deck leaves readers to work out which parts of the main argument it qualifies.
Explain the assumptions that drive the conclusion
Start with the conditions that matter most to the argument. If a projected outcome depends heavily on demand, pricing or delivery timing, give those inputs a visible place near the outcome. Ask the person responsible for the model to identify and check the important drivers.
The main presentation needs enough information to explain the reasoning. The appendix can hold the calculation detail, source notes and additional scenarios. Use the same definitions and reporting period in both.
“The model assumes the next phase starts after the required approval.” This explains a dependency. “The next phase starts in June” would require additional support and a visible basis for the timing.
Show scenarios without implying probabilities
Scenarios can help explain how the case changes when an input changes. Name the inputs that differ and keep other conditions consistent, or explain why they also change. Use the team’s checked model rather than creating an attractive range for the slide.
A lower, central and upper case does not establish how likely each outcome is. If no probability analysis has been carried out, avoid visual language that implies one. A chart should show the comparison the analysis actually supports.
Distinguish dependencies from commitments
An expression of interest, a proposed agreement and a signed commitment represent different states. Describe the actual status and any conditions material to the argument. Identify dates where an update could change the position.
Treat project milestones the same way. Show completed work separately from future gates. If the next phase requires an approval, agreement or additional funding, connect that dependency to the milestone rather than burying it in a footnote.
Use the uncertainty to guide the next conversation
End with the questions that matter for the decision ahead. Which inputs need verification? What information will become available next? Who is responsible for resolving each open point? This makes uncertainty useful to the discussion.
Before sharing, have the relevant factual, technical or financial owner review the presentation alongside its sources. The Banyan case includes fictional financial examples that demonstrate how assumptions and scenarios can stay visible within an investment narrative.
- StatusFacts, estimates, forecasts and targets labelled.
- BasisImportant assumptions shown near the conclusion.
- ComparisonScenario differences explained without unsupported probabilities.
- DependenciesConditions and future gates made explicit.
- ReviewInputs checked by the people responsible for them.