Skip to main content

Demographic level comparisons

How to request demographic level comparisons and what to expect from our team

Written by Jessie Walsh

🔐 Who can use this feature?

Map a demographic group's name from a previous survey to its current name, so your year-over-year trends stay connected even when a team or department is renamed. Culture Amp automatically matches demographic groups between surveys when the values are identical. When a name changes between surveys, for example a team renamed from Product Support to Customer Support, a demographic level comparison bridges that gap.

Before you begin

  • Ensure your comparison survey is loaded at the overall level and all question matches are finalized.

  • ⚠️ Warning: Finalizing question mapping after loading demographic comparisons will erase all manual comparison data. Complete question mapping first, then request your demographic comparisons.

Step 1: Submit your comparison request

Our support team will work with you to set up your demographic comparisons, however much or little you already have prepared. Reach us through any of these options:

Option A: From your survey's Comparisons page

  1. Go to Surveys and select your survey, then select Edit survey.

  2. In the left-hand menu, under Settings, select Comparisons.

  3. Find your comparison in the list and select its ⋮ menu, then select Demographic matches.

  4. Scroll to the Request demographic matching section at the bottom of that page, fill in the Demographics to match field, then submit.

Option B: From your survey report

  1. Open your survey report and select the Compared to dropdown at the top.

  2. Select Manage your comparisons.

  3. Find your comparison in the list and select its ⋮ menu, then select Demographic matches.

  4. Scroll to the Request demographic matching section at the bottom of that page, fill in the Demographics to match field, then submit.

Option C: Chat or email with our support team directly

Open a Support Conversation to speak with our Product Support team.

If you already have a mapping document or template prepared with the required mappings, share this in the conversation directly.

ℹ️ Note: See the following template example, which you can copy and populate with your desired mappings ahead of time and send through when you're ready. This is the best option if you already know the mappings that are required and do not need support to send you a specific worksheet showing what is mismatched across the surveys.

Whichever option you use, tell us which demographics you'd like compared (for example, Division, Department, or Location), and share any name changes you already know between surveys. You don't need to wait for us to send a worksheet first.

Step 2: Review your matching worksheet

If you don't have a mapping spreadsheet prepared, Support can pull the demographic values from both surveys and send you a worksheet, with the rows that are already matched and the rows that need your attention marked for you.

The worksheet marks each row in one of three ways:

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, so you're welcome to change any row, including green ones, if you want a different mapping or need full customization. If you'd rather start from a blank template instead, let Support know and they'll send one across.

Step 3: Return your worksheet

Add notes explaining anything that needs context, then return the file to Support. We'll load your comparisons as soon as we receive it.

Limits on mapping demographic values

  • Same-value limit: 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.

  • Team-split limit: 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, Onboarding (2026) and Product Support, Seasoned (2026) could both map to Product Support (2025).

  • No standard unmatching: Whether a demographic was matched automatically or you mapped it yourself on the worksheet, it generally can't 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, contact Support to discuss whether it's feasible for your situation before proceeding.

ℹ️ Note: A demographic is the overall header, such as Department. A demographic value is what's assigned to a person under that header, such as Product Support.

FAQ

What if my demographic values are completely different between surveys?

That's exactly what this process is for: fill in the rows with the correct mapping. If a value has no equivalent in the new survey (for example, a team that no longer exists), note that on the worksheet and Support will handle it.


💬 Need help? Open a Support Conversation to speak with our Product Support team.

Did this answer your question?