Optimal survey result aggregation windows
Last updated: November 10, 2025
Teamspective uses survey result aggregation windows to help you ensure reports are both comprehensive and filled with fresh data.
This article helps you find the optimal aggregation window for your organization.
For more details about reporting calculation logic, please check these articles:
📄 How are Engagement survey question scores calculated?
📄 How are KPI and Theme scores calculated in Engagement?
Find your optimal aggregation window
How you run surveys determines the best way to set up reporting and result calculation. Find your approach from the options below, and you'll get a solid recommendation.
An aggregation window is the time range of responses included in a report. For question-level scores, for example, a 10-week window means all responses from the last time question was asked, and 10 weeks prior to that are counted. For themes and KPIs the window would consider the latest survey, and all other surveys within 10 weeks from that point in time.
Aggregation windows can be configured by admins in Engagement settings, or in the settings of each survey program.
1) Quarterly or annual surveys to whole organization
💡 Recommended aggregation window: 10 weeks
Any window shorter than your survey interval works well. Then reports will only use responses from the latest survey and compare trends with the older ones.
2) Quarterly or annual surveys, split into targeted surveys
💡Recommended aggregation window: 10 weeks
Keep the window shorter than your survey interval, otherwise multiple survey rounds might be included for some parts of your organization.
Also keep the window long enough to capture all the different targeted surveys. If the window is too short, some targeted surveys might be unnecessarily excluded from the reports.
3) Recurring surveys, no custom question schedules
If you run recurring surveys and HAVE NOT set custom schedule to any questions, this recommendation is for you.
💡Recommended aggregation window: 1 week for questions and 8-15 weeks for KPIs and Themes.
Match the window to how frequently all questions are asked. If all your questions rotate through in 12 weeks, then set the window to 12-13 weeks to ensure reports always include one full set of results for all questions.
On question level, 1 week window is recommended. This way you avoid accidentally mixing answers from multiple survey rounds.
4) Recurring surveys, custom schedule on some questions
If you run recurring surveys and HAVE set custom schedule to some questions, this recommendation is for you.
💡Recommended theme and KPI aggregation window: 8-15 weeks
Match the window to how frequently all questions are asked. If all your questions rotate through in 12 weeks, then set the window to 12-13 weeks to ensure reports always include one full set of results for all questions.
💡Recommended question level aggregation window: two options
1) To show only the most recent results, use a window of 1 week. This way the older results are always excluded.
2) To accumulate responses across multiple rounds, match window to that longer period. At maximum set it to same as the theme and KPI level window.
Summary
Survey TypeRecommended WindowNotes
Survey type | Recommended window | Notes |
Quarterly/annual (whole org) | 10 weeks | Keep it shorter than your survey interval |
Quarterly/annual (split to targeted surveys) | 10 weeks | Make long enough to capture all target groups |
Recurring (no custom) | 1 week (questions), 8–15 weeks (themes/KPIs) | Match duration of full question rotation |
Recurring (custom question schedules) | 1 week or match rotation | Depends on goal: recent vs. cumulative |