# Build an Executive Dashboard

This guide explains how to build an executive level dashboard in Model Reef using charts, KPIs and core statements. The goal is to give leaders a fast, reliable view of cash, growth, margins and key risks without exposing unnecessary model detail.

Dashboards in Model Reef are always scenario specific. Each dashboard reads from a single model and its outputs.

## Before you start

You should have:

* A complete three statement model for the scenario you want to present.
* Core drivers and variables in place for revenue, costs, capex and funding.
* Valuation configured if you want to include NPV or IRR metrics.

If those are not ready, start with:

* **Build a Full Financial Model from Scratch**
* **Build a DCF Model (FCFF)**

## What you will build

By the end you will have:

* An executive dashboard layout that shows:
  * Revenue and EBITDA over time.
  * Cash and net debt trajectory.
  * Key unit or operational metrics.
  * A small set of headline KPIs such as NPV, IRR and runway.
* A dashboard that can be reused across planning cycles by simply updating the underlying model.

{% stepper %}
{% step %}

### Decide the executive questions you want to answer

Before adding any charts, clarify which questions the dashboard must answer, for example:

* How fast are we growing and how profitable is that growth.
* How much cash do we need and when.
* What does the business look like at the end of the planning horizon.
* How do current plans compare to last plan or last year.

Write down three to five key questions. The dashboard should be designed to answer those with minimal extra clutter.
{% endstep %}

{% step %}

### Choose your core metrics

For most executive dashboards, you will need at least:

* Revenue.
* Gross profit and gross margin.
* EBITDA or operating cashflow.
* Closing cash and net debt.
* Simple unit metric if relevant, for example active customers or stores.

Decide which of these matter most for your stakeholders and which can sit in a supporting report instead.
{% endstep %}

{% step %}

### Build or reuse the underlying charts

In the dashboard or chart layer:

* Create line charts for over time trends:
  * Revenue by period.
  * EBITDA by period.
  * Closing cash or net cash by period.
* Add KPI cards for point in time metrics, such as:
  * Current year revenue and EBITDA.
  * Minimum cash balance.
  * Peak debt.
  * NPV, IRR and payback if you use valuation outputs.

Use the existing chart engine to pull data from:

* Categories and sub categories.
* Variables and drivers.
* Valuation outputs where appropriate.

Keep each chart focused and avoid mixing too many series into a single visual.
{% endstep %}

{% step %}

### Arrange the dashboard layout

Arrange the dashboard visually in a way that matches the decision flow:

Top row:

* One or two KPI cards with NPV, IRR and minimum cash.
* A line chart for revenue or total income.

Middle row:

* EBITDA or operating cashflow chart.
* Cash or net debt trajectory chart.

Lower row:

* One or two charts for key operational metrics, for example units, headcount or unit economics.

Aim for a layout that an executive can scan in under a minute and still understand the trajectory and risk profile.
{% endstep %}

{% step %}

### Set period and units defaults

Executives often think in annual or quarterly time frames even if the model is monthly or weekly.

* For each chart:
  * Set a default period aggregation, for example annual or quarterly.
  * Choose units such as thousands or millions.
* Check that legends and labels remain readable at those levels.

You can keep more detailed monthly views in separate dashboards or reports for finance users.
{% endstep %}

{% step %}

### Add light scenario context if needed

If you want to show multiple scenarios to executives, you have two options:

* Present each scenario as its own dashboard, switching models between sections of the conversation.
* Prepare separate models for Base, Upside and Downside, and export key metrics to a comparison table outside Model Reef.

Avoid mixing too many scenario lines onto a single chart. Instead, keep the executive dashboard focused on one scenario at a time and use a dedicated scenario comparison output when needed.
{% endstep %}
{% endstepper %}

## Check your work

* The dashboard answers the main executive questions you wrote down.
* Charts and KPIs are easy to read without finance training.
* Metrics are consistent with the same model outputs in other views and exports.
* Period and units are appropriate for an executive audience.

## Troubleshooting

<details>

<summary>Dashboard feels cluttered or overwhelming</summary>

Remove charts that do not directly support a key question. Move detail into supporting dashboards for the finance team.

</details>

<details>

<summary>Executives focus on different metrics than the ones presented</summary>

Adjust the selection of charts and KPIs after a few uses, based on what questions actually come up in conversations.

</details>

<details>

<summary>Difficult to keep dashboards consistent across models</summary>

Use a standard layout and naming convention, and treat one executive dashboard as a template to follow in new models.

</details>

## Related guides

* [LP Reporting Dashboard](/use-cases/portfolio-funds-vc-pe-and-family-offices/lp-reporting-dashboard.md)
* [Building Your Model](/help/building-your-model.md)
* [COA Import](/help/quickbooks-integration/coa-import.md)
* [Drivers Syntax](/syntax/drivers-syntax.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.modelreef.io/how-tos/dashboards-and-reporting/build-an-executive-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.