Who is this article for?
- Admins and reporting users who work with dashboards
- Global teams with participants across multiple time zones
Symptoms
- In one time zone, the period filter shows 4 periods.
- At the same moment, users in an earlier time zone see only 3 periods.
- The “current” period appears to be missing for those users.
Root cause
The period filter respects the signed‑in user’s local time. If a cycle’s start time is still in the future in the user’s local time, that period is not shown in the filter.How the survey‑based period filter works
- Relevant surveys per dashboard
- Excluding future cycles
- Merging periods
- Selection
When can an expected period be missing?
- None of the survey’s questions are used in any chart on the dashboard
- The period is still in the future in the user’s local time
- The user does not have access to the underlying survey
FAQ
- Why does Team A see four periods while Team B sees only three?
- Can we force time‑zone‑independent visibility?
- We operate globally. How can we avoid confusion?
Best practices for global setups
- Always communicate start times in UTC plus local times
- Where possible, choose start times so key regions fall within “today” simultaneously
- For staggered rollouts, clearly indicate when a period becomes visible by region