> For the complete documentation index, see [llms.txt](https://ailyze.gitbook.io/ailyze-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ailyze.gitbook.io/ailyze-docs/common-research-workflows/analyze-employee-feedback.md).
# Analyze Employee Feedback
This page shows you how to analyze employee feedback — engagement surveys, pulse surveys, and exit interviews — and compare results across departments, teams, and tenure.
{% hint style="info" %}
**What you need:** the Free Plan or higher, plus your feedback as a spreadsheet (XLSX or CSV) or as documents (DOCX or PDF).
**What you will have at the end:** [themes](/ailyze-docs/reference/glossary.md#theme) in the open-ended comments, charts for your rating questions, and side-by-side comparisons by group.
{% endhint %}
## Step 1: Pick the workflow that matches your data
| Your data is… | Use |
| ------------------------------------------------------ | ------------------------------------------------ |
| An **engagement or pulse survey export** (spreadsheet) | **"Analyze xlsx/csv files"** |
| **Exit interviews** written up as documents | **"Analyze docx/pdf files"** |
| **Recorded** stay or exit interviews | **"Transcribe Audio/Video"** first, then analyze |
Engagement surveys are usually spreadsheets, so this guide follows the **xlsx/csv** path.
## Step 2: Set up department and tenure comparisons
Employee feedback is most useful when you break it down by group.
1. Start **"Analyze xlsx/csv files"** and upload your survey export.
2. At **"Choose the type of Analysis"**, pick **"Analyze text, numerical, categorical, etc. survey data across all columns"** for the full picture.
3. In **"Configure Column Types"**, drag **Department, Team, Tenure band, Location,** and **Manager** into **"Segments"**.
4. Check that rating questions sit under **"Numerical Data"** (you get histograms) and single-choice questions under **"Categorical Data"** (you get bar charts).
5. Let Evidano theme the open-ended comments (for example, *"What would make this a better place to work?"*).
6. Click **"Create Project and Start Analysis"**.
{% hint style="warning" %}
**Protect anonymity.** Keep groups large enough that no one can be identified. If a [segment](/ailyze-docs/reference/glossary.md#segment) has very few respondents, consider merging it — or leave out the **"Respondent Name/ID"** column so quotes stay anonymous.
{% endhint %}
## Step 3: Read your results
* **Themes** in open-ended feedback (for example, *workload*, *recognition*, *career growth*) with [frequencies](/ailyze-docs/reference/glossary.md#frequency).
* **Segment comparisons** — how engagement drivers differ by department or tenure. Switch between each group and the **"Overall"** view.
* **Quotes** that illustrate each theme for your readout (anonymized as needed).
* **Charts** you can export for the board deck.
See [Compare groups and segments](/ailyze-docs/analyze-data/compare-groups-segments.md) to get the most from segments, and [How to read your results](/ailyze-docs/analyze-data/how-to-read-your-results.md) for a tour of every panel.
## Step 4: Report to leadership
* Click **"Chat to generate report or chart"** and ask: *"Summarize the top 3 themes for the Engineering department vs the company average, with one quote each."*
* **"Download as DOCX"** for the written summary, or **"Share/ Add Collaborator"** (Pro) for a living link.
* Write a short leadership summary — see [Create an executive summary](/ailyze-docs/create-deliverables/create-an-executive-summary.md).
{% hint style="info" %}
**Heads-up:** Downloading a report and sharing a link need the **"Pro Plan"**. See [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md) for what each plan includes.
{% endhint %}
## A realistic example
> **Scenario:** A **1,200-person engagement survey** with ratings, a few single-choice items, and two open-ended questions. You segment by **department** and **tenure**, theme the open-ended fields, and get a dashboard showing where sentiment dips, which themes drive it, and quotes for each group — ready for an all-hands and a board appendix.
## Next steps
* [Analyze open-ended survey responses](/ailyze-docs/common-research-workflows/analyze-open-ended-survey-responses.md)
* [Compare groups and segments](/ailyze-docs/analyze-data/compare-groups-segments.md)
* [How to read your results](/ailyze-docs/analyze-data/how-to-read-your-results.md)
* [Survey research best practices](/ailyze-docs/methods-and-best-practices/survey-research-best-practices.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ailyze.gitbook.io/ailyze-docs/common-research-workflows/analyze-employee-feedback.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.