🔐 Who can use this feature?
Roles: Account administrators (Culture Amp Support runs the export for you on request)
Survey types: 360 Effectiveness
Subscriptions: Any package with Effectiveness
Ask Culture Amp Support for an Excel file that lists every feedback request in an Effectiveness 360 survey, who each request is from and about, and whether it has been submitted. The file is a snapshot of the moment Support runs the export, so it does not update afterward.
How the export differs from the Participation report
The words "participation report" can mean two different things:
Participation export: An Excel file with one row per feedback request. Support runs it for you, and this article explains it.
Participation report: The in-product report that shows response rates, which you can filter by demographics. Read about it in Individual Effectiveness 360 Survey Participation Report.
Which surveys you can request it for
You can request the export for any survey created from one of these four templates:
Individual Effectiveness 360
Leadership Effectiveness 360
Manager Effectiveness 360
Feedback 360 (Pulse)
It works whether the survey is admin-driven or employee-driven, with or without a coach.
The export is not available for Manager Effectiveness 180, Manager Effectiveness 180 (Pulse), Team Effectiveness, or any other survey type. Those are standard surveys rather than 360 processes, so they have no 360 feedback requests to list.
Request the export
Open a Support Conversation.
Ask for the Effectiveness 360 participation export and name the survey.
Support sends you the Excel file.
ℹ️ Note: The file shows, for each named reviewer, whether they submitted. The product does not show employees which individual reviewers have submitted (see Individual Effectiveness 360 Flows and Permissions), so share the file with care.
For updated figures later, request a new export.
What each column means
The file has one worksheet with six columns.
The example below shows how the file looks when you open it in Excel. The names and IDs are fictional.
In this example, Priya Raman's process has five rows, and Daniel Okafor's has four. Lucas Ferreira has no employee ID, so his email address appears in reviewer_id.
status:Completewhen the feedback has been submitted.In Progressfor everything else, including requests the reviewer has not opened yet.response_type: The role the reviewer plays for this employee, as shown in the next list.reviewer_name: The full name of the person giving, or asked to give, the feedback.reviewer_id: That person's employee ID, or their email address if they have no employee ID on file.reviewee_name: The full name of the employee the feedback is about.reviewee_id: That employee's employee ID, or their email address if they have no employee ID on file.
The response_type column contains one of four values:
subject: The employee's own self-review. This role is labeled Employee in a 360.manager: The employee's manager.co_worker: A co-worker of the employee.direct_report: A direct report of the employee.
Why reviewer and reviewee can be the same person
On every subject row, the reviewer and the reviewee are both the employee, because the employee is reviewing themselves. Each employee listed in the file has one of these rows.
In the example below, the highlighted rows are the self-reviews. Priya Raman and Daniel Okafor each appear on one subject row with their own name and ID on both sides.
Other rows list a reviewer and the employee they are giving feedback to. A person can appear on several rows. In the example, Mei Tanaka reviews both employees, and Priya Raman reviews Daniel Okafor as his direct report.
How rows are counted
Each row is one feedback request, and the self-review counts as a request. For example, an employee with 1 manager, 3 co-workers, and 2 direct reports produces 7 rows: 1 self-review, 1 manager, 3 co-worker, and 2 direct report.
These rows do not appear in the file:
Reviewers who were removed from a process
Processes that were deleted
Preview responses created while previewing the survey
Reviewers who have since been deactivated still appear.
Track outstanding feedback requests with the file
Outstanding requests: Filter
statustoIn Progressto list every request that has not been submitted, with the reviewer and the employee.Workload: Count rows per
reviewer_idto see how many requests each person has across the survey, including their own self-review.Self-reviews: Filter
response_typetosubjectto see each employee's self-review and whether it isCompleteorIn Progress.Number of reviewers: Remove duplicate
reviewer_idvalues to count the unique people who were asked for feedback, including employees asked to review themselves.Overall completion: Count the
Completerows against all rows.
What the file does not include
The file has only the six columns above. It does not include:
Feedback scores or comments
Demographics
Due dates or submission dates
Process stage
Coaches
Reminder history
To see participation filtered by demographics, use the in-product Participation report. For combined feedback results across employees, see Individual Effectiveness 360 Survey Insight Report. For an individual's feedback content, see Share and Review Individual Effectiveness 360 Survey Feedback.
➡️ Next steps
💬 Need help? Open a Support Conversation to speak with our Product Support team.