This guide covers how to test Onboarding and Exit (Experience) surveys end-to-end in the Culture Amp platform: setting up and launching a test survey, the participant experience, the interviewer experience (Full Workflow), and reporting. Onboarding and Exit share most of the testing flow; the differences are called out where they matter. Run everything as a clearly labeled test and remove the test data when you are done (see Clean Up).
Before You Begin
Choose your testing approach
With colleagues (recommended for a full end-to-end test) – run the test with a small group of willing colleagues who know it is a test, for the most realistic experience, including real emails and the full notification flow.
Solo, with dummy users – use a small set of dummy/test users (and optionally yourself), to validate the admin and participant experiences.
Note: You cannot fully simulate the interviewer (Full Workflow) experience solo; use a colleague for that.
Set up dummy users (solo testing):
Create 1–3 clearly named dummy users (e.g. TEST USER 01 - Do Not Use) in Culture Amp (Settings > Users > Add User) or via a partial import.
Give each a real email address you can access (a personal address, or a +alias of your work email (e.g. yourname+test01@company.com), so you can receive invitations and complete the survey as that user.
Assign the users a distinctive value in a demographic (e.g., Department = "TEST GROUP") to validate filtering and reporting without mixing test data into real demographic values.
To test each perspective yourself, log in using the email address assigned to each dummy account. This controls which experience each dummy user takes on:
Set one dummy user as the participant (employee): They'll receive the survey invitation and complete the survey
For Full Workflow only: assign a real, accessible email as the interviewer. They'll receive the assignment notification and can add interview notes
Optionally: add your own user as a participant for the full participant experience alongside the dummy users.
After testing, archive or delete the test survey and deactivate the dummy users (see Clean Up).
Choose your workflow
Onboarding and Exit Surveys support two workflow types. Identify which you are testing first:
Workflow | Description | Invitation method |
Survey Only (Basic) | Survey sent to employee; results appear in the dashboard on submission | Manual or Automatic |
Survey + Interview (Full) | Survey followed by an optional interviewer follow-up | Manual only |
Recommendation: use Manual invitation method for testing. Automatic launch relies on real start/end dates in user profiles, which you generally do not want to set on test users.
Onboarding vs Exit at a glance
Setting | Onboarding | Exit |
Template | Choose one of 5 Onboarding templates | Use the Exit Survey template |
Invitation timing | Days after start date (auto) or manual | Days before end date (auto) or manual |
Key risk | None specific | Setting a Last Day of Employment auto-deactivates the user on that date |
Interviewer classify | Not applicable | Interviewer can classify the exit (voluntary/involuntary, regrettable/not) |
Important Notes
Onboarding and Exit surveys are continuous – each participant goes through their own individual process triggered when they are invited, unlike the single-window Engagement survey.
By default, these surveys are non-confidential. Admins and assigned interviewers can view individual responses based on the following settings, which are locked at launch:
Reporting Group Minimum is 0
"No protection" is ticked
Indirect protections are none
Raw data extract is enabled.
Email communications cannot be disabled for Onboarding/Exit surveys; only the recipient list controls who receives them.
The single automatic reminder cannot be turned off or rescheduled, and additional reminders cannot be added (unlike Engagement Surveys). Admins can push a manual reminder anytime from the Responses page.
Admins can push a manual reminder anytime from the Responses page.
Participants cannot be bulk imported; add them individually from the Responses page.
Allow Individual Responses must be enabled before launch (locked after) for interviewers to view responses, cancel processes, or classify.
Responses cannot be edited once submitted; an admin can reset a submitted response from the Responses page.
The platform supports one email address per Exit survey and per user. To use a personal address (e.g., for someone who has left), update the Email field in their user profile before sending.
A user can only be re-invited if their previous response is in the 'Completed' state; for Exit surveys, the user must also be reactivated first.
In the Full Workflow, a process must be marked ‘Complete’ (not just Submitted) before they can be re-invited.
The Action Framework, Focus Areas, and PowerPoint export are not available for Experience surveys.
Setting Up and Launching a Test Survey
Step 1: Create and Name the Survey
From the Surveys page, click Create Survey and choose a template: one of the 5 Onboarding templates, or the Exit Survey template.
Rename clearly, e.g., "TEST - Onboarding" or "TEST - Exit Survey".
Mirror your real onboarding/exit questions where possible so the test is representative.
Step 2: Configure Confidentiality
On the Confidentiality page, note that Onboarding and Exit surveys are non-confidential by default, so admins and assigned interviewers can view individual responses based on the following settings, which are locked at launch:
Reporting Group Minimum: 0
"No protection" ticked
Indirect protections: none
Raw data extract: enabled
What to validate
Confidentiality is set as intended before launch (especially Allow Individual Responses if you're testing the Full Workflow).
Step 3: Configure the Launch Plan
On the Launch Plan page, configure invitation and reminder settings:
Setting | Onboarding | Exit |
Invitation | Days after start date (auto) or manual | Days before end date (auto) or manual |
Survey Due | Default due date | Default due date |
Reminder | Days before due date to remind | Days before due date to remind |
Send Time | Time of day for all comms | Time of day for all comms |
Interview Reminder (Full only) | Days before interview due date | Days before interview due date |
Note: Email communications cannot be disabled; only the recipient list controls who receives them.
Step 4: Launch at the Overall Level
Click Launch Now. This activates the survey so individual processes can be created; it does not send invitations yet.
Unlike Engagement surveys, there is no Participants page. Participants are added individually from the Responses page.
Step 5: Add Test Participants Individually
Go to your survey > Responses > Select Employees (or Add User to create a profile first).
Pick 1-3 colleagues or dummy users who have agreed to take part. For each, set the Survey Due Date, Interview Due Date (Full Workflow only), Last Working Day (Exit only – see warning), and the Interviewer (Full Workflow only).
Click Send to trigger the invitation.
What to validate
Invitations send only to your chosen test participants.
(Exit) No real user is unintentionally scheduled for deactivation.
Exit Survey Warning: Entering a Last Day of Employment date causes the system to automatically deactivate that user on that date. To test safely:
Recommended: set the Last Day of Employment only on dummy records, never on real accounts.
Or leave the Last Day of Employment blank; the Exit survey still works, since deactivation is triggered by the date field, not the survey.
Or set and immediately clear the date, via partial import or Settings > Users > [User] > End date once the test is done.
Participant Experience (Including Notifications)
Each participant goes through their own individual process tied to their dates.
Invitation email: sent immediately when the process is created and Send is clicked, from notifications@cultureamp.com, with a unique personal link (should not be shared). It includes the survey name (with any TEST prefix), a Start Survey link, a link to the Reporting Rules, and the due date. If Slack/MS Teams is enabled, it also arrives there.
Automatic reminder: sent per the launch plan if not submitted; cannot be turned off. Admins can also push a manual reminder from the Responses page. Additional reminders cannot be scheduled.
Welcome Screen: shows the organization's message and confidentiality settings.
Completing: responses autosave; participants can save and exit, return via the original link while it is open, and switch devices.
Submission: a Thank You page appears, with options to rate the survey or Redo Survey (resets answers and sends a new link).
Once submitted, responses cannot be edited by the participant; an admin can reset a response if a tester needs to redo it.
What to validate
Invitation arrives (check spam), and the link opens; the Welcome Screen shows correct confidentiality/reporting rules.
Variables (manager name, start date, survey name) resolve correctly.
The survey works on mobile and desktop and saves progress between pages.
Submission produces the expected confirmation screen.
The automatic reminder arrives per the launch plan if not submitted.
If Slack/MS Teams is enabled, notifications arrive there too.
Interviewer Experience (Full Workflow Only)
Skip this if you are testing the Basic workflow. The Full Workflow adds the Interviewer role (typically a manager or HR team member) who reviews responses and conducts a follow-up.
Prerequisites
The survey is Full Workflow (Survey + Interview). Quick check: if you can change the Invitation Method on the Launch Plan page it is Basic; if you cannot, it is Full.
Allow Individual Responses is enabled in Confidentiality (locked after launch) so the interviewer can view responses.
The interviewer is an active user with platform access.
The process is created from the Responses page with the interviewer assigned and both due dates set.
Note: Only one interviewer per process; switching mid-process sends the new interviewer a fresh assignment notification.
Steps and notifications
Assignment email (notification 1): sent when the process is created and Send is clicked, with the participant's name, survey due date, interview due date, and a platform link. Cannot be disabled.
Access before submission: the interviewer can log in anytime via Feedback > Surveys and is directed to their Responses view (only their assigned processes). If Allow Individual Responses is on, they can view responses as submitted.
Submitted alert (notification 2): sent when the participant submits, prompting review. Cannot be disabled. The interviewer can then view full responses, add interview notes, and print or take notes offline.
Conducting the interview: add notes in the Interview tab. For Exit surveys, classify the exit (voluntary/involuntary, regrettable/not) in the Classify tab.
Interview reminder (notification 3): sent per the 'Interview Reminder' field if the interview is not completed.
Notification summary
Notification | Who receives it | When triggered | Can be disabled |
Survey Invitation | Participant | Process created and Send clicked | No |
Slack/Teams Invite | Participant | Same time as email (if enabled) | No |
Automatic Reminder | Participant (if not submitted) | Per Reminder field in Launch Plan | No |
Manual Reminder | Participant (if not submitted) | When admin clicks Send a Reminder | Yes (admin-controlled) |
Interviewer Assignment | Interviewer | Process created | No |
Survey Submitted Alert | Interviewer | Participant submits | No |
Interview Reminder | Interviewer (if not completed) | Per Interview Reminder field | No |
What to validate
The assignment email arrives on process creation and shows the participant name and both due dates.
The interviewer can log in and find the process in their Responses view, and view individual responses (requires Allow Individual Responses).
The submitted alert arrives after the participant submits.
The interviewer can add and save notes in the Interview tab, and (Exit) the Classify tab works.
Clicking Complete closes the process, and the PDF export includes both responses and interview notes.
The interview reminder arrives the correct number of days before the interview due date.
If Slack/MS Teams is enabled, all notifications arrive there too.
Note: Marking a process Complete matters. A process must be Completed (not just Submitted) before the participant can be re-invited. In the Full Workflow this is set by clicking Complete after viewing the response.
Reporting Views (Including Notifications)
Experience surveys do not support the Action Framework, Focus Areas, or PowerPoint export. Reporting is non-confidential by default, so individual responses are visible to admins (and interviewers in the Full Workflow).
Prerequisites
The survey is launched and at least one test participant has submitted.
Allow Individual Responses and Raw Data Extract were enabled before launch (both lock at launch; raw data extract is on by default).
Reporting Group Minimum is 0.
Step 1: Open the Responses Tab (Admin Report)
From the Surveys page, click View Reports next to your test survey. This opens the Responses tab, the default for Onboarding/Exit.
The tab shows each invited employee and their status: Awaiting Response, Awaiting Interview (Full Workflow), Awaiting Classification, or Completed. Filter by name/email, survey status, or demographic.
Note: the Responses tab shows all demographics enabled on the survey; the Insights tab only shows values from participants who have submitted.
Step 2: View an Individual Response
Click 'View Response' next to a test participant to see all answers, interview notes (Full Workflow), and classification data (Exit). You can export the response or Reset it if the tester needs to redo it.
Note: do not export raw data from the individual response view (this errors). Export raw data from the Operations page or Insights report instead. Non-admin viewers do not see the Responses tab even with Allow Individual Responses on; it is visible only to admins and assigned interviewers.
Step 3: Explore the Insights Report
The Insights tab summarizes participation, factor-level scores, and question results.
Date Range filter uses the process launch date (when the process was created), not the submission date – e.g., a participant invited in December but submitting in January is grouped under December.
Trend: the Lifecycle Survey Trend shows trends based on past responses in your date range, only when an Index Factor is set and the Reporting Group Minimum is 1 or less.
Impact Analysis: identifies which factors correlate most with the outcome score (e.g. Onboarding or Exit Experience).
Step 4: Explore the Heatmap, Comments, and Comparisons
Heatmap: shows how demographics compare across questions; only rating questions appear (open-text excluded).
Comments: open-text responses; the date range filter categorizes comments by the date the survey was issued, not submitted.
Comparisons: compare over time or against Culture Amp's Onboarding/Exit benchmarks. Internal comparisons are only against the same template type (Attributed Continuous); automatic comparisons are not supported, so load closed surveys manually via Add Survey.
Step 5: Export Raw Data
From Surveys > Operations, or the Export menu on the Insights tab, download the raw data extract (includes name, email, employee ID, and all responses).
In the extract: The date column shows the submission date (unlike Insights, which filters by process-created date).
If raw data is not enabled, request a De-identified Raw Data Extract from Culture Amp Support.
Note: PowerPoint export is not available and cannot be enabled.
Step 6: Preview as a Viewer
Click Preview next to a shared report on the Sharing page to see what a non-admin viewer sees (without the Responses tab).
Reporting notifications
Notification | Who receives it | When triggered | Can be disabled |
Report Access Notification | Any user granted report viewer access | When admin shares and selects Notify | Yes (use 'Publish without notifying’) |
Unopened Report Reminder | Viewers who have not opened the report | 1 week after the initial notification | No |
Note: there are no report owner nudges, focus area reminders, or action check-in notifications for Experience surveys (the Action Framework does not apply). MS Teams report notifications are disabled by default and must be enabled at the account or survey level by contacting Product Support.
What to validate
The Responses tab shows all test participants with correct statuses.
You can View Response for individuals (requires Allow Individual Responses).
The PDF export of an individual response includes answers and interview notes (Full Workflow).
Insights shows participation and factor scores; the Date Range filter groups by process launch date.
Trend displays (requires Index Factor and Reporting Group Minimum of 1 or less); the Heatmap displays for your test demographic values; the Comments tab shows open-text.
You can export raw data from the Operations page or Insights tab.
The report access notification arrives when shared, and the unopened report reminder arrives 1 week later if not opened.
If Slack/MS Teams is enabled, the report notification arrives there too.
Clean Up
The goal is to remove all test data so it does not persist in reporting or on profiles.
Close the test survey from Surveys > Launch Plan > Close Now (outstanding responses can no longer be submitted after closing).
Decide whether to keep or delete the test data. If you keep it closed (i.e., for later reference), mark it clearly TEST and exclude it from any consolidated dashboards or BI exports.
Delete the test survey to permanently remove all associated response data. Deleting the survey is the most complete clean-up step — once deleted, all participant responses, interview notes, and classification data are removed and will not appear in reporting or exports.
(Exit) If you set a Last Day of Employment for a colleague, re-import the user file or clear the end date so they are not deactivated.
For dummy users, deactivate them: Culture Amp records cannot be permanently deleted; rename their name, email, and employee ID to a clear TEST placeholder if you need to free those values up.
Do not rely on deactivating dummy users alone to remove their data. Deactivating a user does not remove their survey response data. The responses remain attached to the survey until the survey itself is deleted.
Clear or reset the test demographic value you assigned to the dummy users.
Test Completion Checklist
# | Test point | Expected result |
1 | Survey created, named TEST, confidentiality set | Correct template; settings set before launch |
2 | Launched at overall level | Survey active; no invitations sent yet |
3 | Test participants added individually | Only test users invited; (Exit) no real deactivation scheduled |
4 | Participant experience | Invite, link, welcome screen, autosave, Thank You/Redo all work |
5 | Automatic reminder | Sent per launch plan if not submitted |
6 | Interviewer assignment (Full Workflow) | Assignment email arrives with participant and due dates |
7 | Interviewer access and notes | Can view responses, add notes, classify (Exit), Complete process |
8 | Interviewer notifications | Submitted alert and interview reminder arrive |
9 | Responses tab | All participants shown with correct statuses |
10 | Individual response view | Answers, notes (Full), classification (Exit) visible; reset works |
11 | Insights, Heatmap, Comments, Comparisons | Display correctly with date-range behavior understood |
12 | Raw data export | Exports from Operations/Insights; PowerPoint correctly unavailable |
13 | Report sharing notification | Access notification arrives; unopened reminder after 1 week |
14 | Cleanup done | Survey closed; (Exit) end dates cleared; dummy users deactivated; test demographic value cleared |
💬 Need help? Type "Ask a Person" in a Support Conversation to speak with a Product Support Specialist.










