Dashboard date controls should explain which event date is filtered, which time zone governs it and whether compared periods are complete. This month versus last month can be misleading when the current period is only partly elapsed. Define comparison semantics before choosing labels and percentage-change visuals.
Let’s plan your dashboard date controls.
Bring your workflow, constraints and open questions. We’ll help you define the requirements and work through a practical next step.
Identify the date that answers the question
An order can have creation, approval, dispatch and payment dates. A filter labelled Date does not explain which one determines inclusion. Use the metric's owning definition and make important differences visible.
For a hypothetical operations dashboard, completed during the period and created during the period are different populations even when both display a completed count.
Use a date-comparison worksheet
| Decision | Meaning to specify | Failure to test |
|---|---|---|
| Event date | Which business event controls inclusion? | Same record appears in unexpected periods |
| Time zone | Which boundary defines a day? | Midnight records move between totals |
| Relative range | What does Last month mean? | Rolling days confused with calendar month |
| Comparison | Full or equivalent elapsed period? | Partial month compared with full month |
| Completeness | Are all expected inputs available? | Delayed feed shown as falling demand |
| Baseline zero | How is change represented? | Undefined percentage shown as a normal figure |
Have the metric owner approve calculations and exclusions. The interface should not choose the comparison that produces the most attractive chart.
Preserve context across views
Apply compatible definitions to charts, tables and exports. If one component uses a different event date or cutoff, explain it rather than presenting the values as directly reconcilable.
Saved views should preserve the intended relative or absolute date rule. A view created in January should not unexpectedly continue showing January when users thought they saved This month.
Validate boundary examples
Use synthetic records near midnight and period ends. Include late-arriving data and a period with no eligible records. Confirm labels, totals and comparison messages explain the outcome.
Review the experience with decision-makers. A mathematically valid percentage may still encourage a mistaken conclusion if the population or completeness differs.
Date-range questions
Should incomplete current periods be hidden?
Not necessarily. Label them and choose an appropriate comparison so users understand the limits.
Can every metric use the same date field?
Only where that matches each metric's meaning. Shared controls need explicit semantics for the components they affect.
Pair date controls with scheduled-report freshness, and discuss metric presentation with Drema's UI/UX team.