Period Toggle Rules
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.
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.
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.
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.
Related articles
Last updated