> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/syntax/chart-and-table-syntax/period-toggle-rules.md).

# Period Toggle Rules

{% stepper %}
{% step %}

### Period toggle options

Typical period toggle options include:

* Daily view (where supported).
* Weekly view.
* Monthly view.
* Quarterly view.
* Semi annual view.
* Annual or financial year view.
* Custom date ranges.

These are applied at dashboard or report level.
{% endstep %}

{% step %}

### Relationship with model granularity

The model has a base granularity, such as weekly or monthly. Period toggles:

* Do not change the underlying calculation grid.
* Instead, aggregate or slice the existing time series to match the view.

Examples:

* A monthly model can be shown in quarterly or annual view by aggregating months.
* A weekly model can be summarised to months or quarters.

The opposite — such as breaking monthly into daily — is not supported because it would require invented detail.
{% endstep %}

{% step %}

### Impact on charts and tables

When you change the period toggle:

* Charts recompute their x axis periods and y values using appropriate aggregation.
* Tables regroup rows or columns by the chosen period.
* KPI cards recalculate where they depend on period ranges (for example next twelve months metrics).

All visual elements on the dashboard stay consistent with the new view.
{% endstep %}

{% step %}

### Comparing across periods

Period toggles are useful for:

* Viewing detailed patterns in monthly or weekly view.
* Summarising long horizons in annual view for board and investor packs.
* Switching between short term and long term perspectives without creating separate dashboards.

You can use the same dashboard structure with different toggles for different audiences.
{% endstep %}

{% step %}

### Best practice

For effective use of period toggles:

* Design charts so they still make sense at multiple period resolutions.
* Avoid overloading dashboards with too many period-specific labels.
* Communicate clearly which period view you are using when sharing screenshots or exports.

This reduces confusion about what numbers represent.
{% endstep %}
{% endstepper %}

## Related articles

* [Period Selector](/syntax/understanding-the-interface/period-selector.md)
* [Scenario Toggle Behaviour](/syntax/scenario-syntax/scenario-toggle-behaviour.md)
* [Liability Variables: what is, rules, what it affects](/help/drivers-variables-and-timing/liability-variables.md)
* [Build a Multi Period Comparison Dashboard](/how-tos/dashboards-and-reporting/build-a-multi-period-comparison-dashboard.md)