🔐 Who can use this feature?
Survey types: Attributed (Snapshot), Unattributed, Attributed (Continuous)
Subscriptions: Any package with Engagement or Effectiveness
To track year-over-year progress across departments or locations in a survey, consistent data is key. Culture Amp automatically connects matching demographic groups between surveys when the names are identical, but team names don't always stay the same. Demographic Level Comparisons bridge that gap, allowing you to map past results to new group names, like comparing last year's "Product Support" team directly to this year's "Customer Support."
Before you begin
Ensure your comparison survey is loaded at the overall level and all question matches are finalized.
⚠️ Important: Finalize all question mapping first. Making changes to question mapping after loading demographic comparisons will erase all manual comparison data.
How to request demographic level comparisons
Our support team will work with you to get your demographic comparisons set up, however much or little you have prepared.
Step 1: Submit your request
You can reach us in a few ways:
From the Survey Summary Imports (Historical Data) page: select a previously imported survey and use the "Request demographic matching" form
From the Survey Report Comparisons view: open your survey report, locate the comparison, and request demographic matching from there
By starting a chat or email with our support team directly
In your request, let us know which demographics you'd like compared (e.g. Division, Department, Location). If you already know what the name changes are between surveys, share those details and we'll work straight from them. you don't need to wait for us to send a worksheet first.
Step 2: We prepare the worksheet (or work from yours)
If you don't have anything prepared, our team will pull the demographic values from both surveys and send you a pre-populated worksheet with the rows that need your attention already highlighted. If you already have a mapping document or template you'd prefer to use, just share it and we'll work from that instead.
When we send a worksheet, you'll see three types of rows:
Color | What it means | Your action |
🟢 Green | Already matched automatically | No action needed, but you can change these if you'd like a different mapping |
🟡 Yellow | We've suggested a match based on similarity | Confirm it's correct, or let us know the right match |
🔴 Red | We couldn't find a confident match | Fill in what the value should map to |
The colors are a guide, not a constraint. You're welcome to change any row, including green ones, if you want a different mapping or need full customization.
If you'd prefer to start from a blank template instead, just let us know and we'll send one across.
Step 3: Review and return
Check the rows that need your attention and add any notes in the Notes column if something needs explaining. Return the file to us and we'll load the comparisons straight away.
What if my demographic values are completely different between surveys?
That's fine, that's exactly what this process is for. Fill in the rows with the correct mapping. If a value existed in the old survey but has no equivalent in the new one (e.g. a team that no longer exists), note that in the Notes column and we'll handle it appropriately.
Important limitations to be aware of
One current value maps to one previous value. Each demographic value in your current survey can only be mapped to one value in the comparison survey. For example, you can map "Customer Support" (2026) to "Product Support" (2025), but you can't map "Customer Support" (2026) to both "Product Support" and "Customer Success" from 2025, it must be one or the other.
Example:
Multiple current values can map to one previous value. The reverse is possible: if a single team from a previous survey has since split into two teams, both current values can map to the same previous value. For example, "Product Support" (2025) could map to both "Product Support, Onboarding" and "Product Support, Seasoned" (2026).
If a demographic was automatically matched by the platform, it cannot be unmatched through a standard process. In rare cases there may be options available, but these are complex and not guaranteed. If this is something you need, please contact support to discuss whether it's feasible for your specific situation before proceeding.
ℹ️ Note:
Demographic = overall demographic header e.g. Department
Demographic value = demographic value assigned to the user e.g. Product Support
💬 Need help? Open a support conversation to speak with our Product Support team.