Assumptions And Scenarios
Work with explicit assumptions and compare how they change the model.
On this page
Name the case you are modeling
A useful scenario makes its assumptions recognizable: for example, a different development timeline, cost case, or commercial assumption. Name the case for the change it represents.
When an asset has multiple indication tracks, confirm the track you are editing. Different tracks can have different development paths and model inputs.
Review inputs before calculating
Inspect development stage, phase durations, costs, probabilities, discounting, and commercial inputs exposed by the model. Check units and time assumptions. Attach sources or explain the rationale for material changes.
An editable assumption is not a verified fact. Keep evidence and analyst judgment distinguishable in notes and review.
Inspect saved models
From the asset workspace, use View Results to inspect a saved model and Edit Inputs to revisit its assumptions. Check the model label, indication track, and updated information before making changes.
If you want a separate case, use the workflow's save/new-model controls and a distinct label. Confirm the saved result rather than assuming an edit created a new scenario automatically.
Compare like with like
When comparing outputs, identify which inputs differ and which remain fixed. A difference in rNPV can come from development timing, probability, costs, revenue assumptions, or several changes at once.
Read the Workspace methodology and probability-of-success methodology for the calculation basis and limitations. These modeled outputs require professional evaluation in the context of your decision.