Drilldown Behaviour

This article explains drilldown behaviour for charts and tables in Model Reef.

You will learn:

  • How to navigate from visuals to underlying variables.

  • What information is shown on drilldown.

  • How drilldown supports auditability and review.

Drilldown links the presentation layer back to the modelling layer.

1

What drilldown does

When you drill into a chart or table item:

  • Model Reef opens details about the underlying series.

  • You can see which variables, categories or drivers contribute to the number.

  • You can open the relevant Variable or Driver Editor from there.

This lets you move from high level views to the assumptions that generate them.

2

How to drill down

Typical drilldown interactions include:

  • Clicking a series name or value in a chart legend.

  • Clicking a table row or cell with drilldown enabled.

  • Using a context menu option such as "View details" or "Open variable".

Exact controls depend on the specific dashboard component.

3

Information shown on drilldown

On drilldown you may see:

  • The list of contributing variables or drivers.

  • Category and branch context.

  • Notes and attachments on those variables.

  • Links to open the full Variable Editor or Timing modal.

This gives reviewers enough context to understand where a line comes from.

4

Editing from drilldown

If you have edit permissions on the model or branch:

  • You can open the Variable or Driver Editor from the drilldown view.

  • You can then change inputs, timing or formulas.

  • After saving, charts and tables update to reflect the new assumptions.

Viewer-only users can inspect details but will not be able to edit.

5

Review and audit workflows

Drilldown supports review workflows by:

  • Allowing reviewers to follow the trail from dashboards to assumptions.

  • Making it easy to test the effect of assumption changes.

  • Helping teams align on which variable to adjust when numbers look off.

Use drilldown regularly to keep high level reporting connected to the underlying model logic.


Last updated

Was this helpful?