How a date range control works
You place the control on the report page and set a default period. Every chart configured to inherit it re-queries when the reader changes the selection, so one report can answer questions about last week, last quarter and last year without anyone editing it. Charts can also be pinned to a fixed period, which is how a long-term trend stays put while everything around it moves.
Two settings sit alongside it and matter as much. Scope decides whether the control governs the whole report or only the page it sits on — a mismatch here is why some charts appear to ignore the reader. The comparison setting decides what the change indicators are measured against: the immediately preceding period of the same length, the same period a year earlier, or a fixed range you nominate.
Why the date range control matters
It is the difference between a report and a screenshot. One well-built page with a working control replaces a stack of monthly documents and lets a client answer their own follow-up question instead of asking for a new export.
It is also the most common source of the sentence “the numbers changed”. They usually did not; the period did. Two people looking at the same report with different selections will hold entirely different views of the month, and neither will realise the other is looking at something else. Making the selected range visible on the page prevents an argument that otherwise recurs every quarter.
Common mistakes with date range controls
Leaving the default set to a period that includes today. The current day is incomplete by definition, so it drags every rate down and makes the last column of every chart look like a collapse. Data latency does the same thing to the most recent days, particularly where conversions are still being attributed, so a default ending yesterday can also mislead.
Forgetting to connect every chart to the control is next: half the page responds and half does not, and nobody can tell which is which. Then there is the comparison period. A previous-period comparison across a festival, a holiday or a month of different length produces an arrow with no meaning, and for a seasonal business it is almost always the wrong choice.
How to act on it
Default to a complete, recognisable period — last month or the last full week — and exclude the incomplete current day wherever the tool allows. Check that every chart and scorecard on the page is genuinely inheriting the control before you share the link.
Show the selected range as text on the report, so a forwarded screenshot still carries its own context. Pick the comparison deliberately: a year-on-year comparison for seasonal demand, a previous-period comparison for steady demand. Where recent days are still settling, note the delay somewhere on the page rather than explaining it in every meeting. These small habits are what stop a reporting dashboard generating more questions than it answers.