- This topic has 0 replies, 1 voice, and was last updated 3 months, 3 weeks ago by Adam Fitzpatrick.
As you may have heard us say many times at J+D previously, a good forecast is like a good story – each chapter has a clear beginning and end and it is obvious how each chapter links together. But a good story is nothing without the synopsis/ blurb – and that is where your forecast schematic can play a valuable role in supporting your wider forecast model.
A schematic serves a number of roles:
1) It helps you to map out your initial thinking as to how the forecast could be structured
2) It helps to stimulate debate about whether more detail is required (or indeed, where the forecast can potentially be simplified)
3) It helps to save a lot of time by getting all key stakeholders to review and potentially approve the schematic before time is spent creating the model itself
As by including your schematic alongside your forecast, this is constant and helpful reminder of the structure that has been agreed. For anyone reviewing your forecast for the first time, if your schematic is the first tab in the file, then it can act as a top-level summary before the reviewer delves into the detail.
Take a look at a fairly simple example schematic that we created for NASH, assuming in this case that the priority patient sub-group of interest is that of stage F2.
- This topic was modified 3 months, 3 weeks ago by Will James.
You must be logged in to reply to this topic. Login here