> ## Documentation Index
> Fetch the complete documentation index at: https://docs.innerlogic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Track survey participation

> See completion by group, save a participation report, and email regular updates.

See how many invited people have completed a survey, broken down by group. Participation reports work while a survey is running and after it closes.

## Before you begin

Participation reports are available for scheduled, active and closed surveys. To open them, you need **Schedule Surveys** in your access profile and at least **Viewer** access to the survey.

* **Owners and editors** of the survey can create, edit, delete and schedule reports.
* **Viewers** can open saved reports.
* Being an organization admin isn’t enough on its own. You also need **Owner** or **Editor** access to that survey to change its reports.

You see only the groups your access covers. Menus and buttons depend on your access, so you may see fewer options than this guide describes.

## Open participation reports

1. In the sidebar, under **Survey Hub**, select **Active Surveys**.
2. Open the three-dot menu beside the survey and choose **Participation Reports**.

The **Participation metrics** page lists **Report templates**. **Default view** is always the first row, followed by any saved reports.

## Read the default view

* Choose a dimension, such as Department, in the first column heading to group people. Only the dimensions set up for this survey are listed.
* **Completed** is how many people finished. **Sent** is how many were invited, not counting anyone a contact sync or **Remove non-completers** removed from the survey. **Completion** is completed divided by sent. Select a column heading to sort by it. The table starts sorted by **Completion**, highest first.
* **Survey overall** stays at the top and covers the whole survey, even if you can see only some groups. When you use **Participant filters**, it counts only the people the filters keep.
* To look inside a group, select its name and choose a dimension under **Break down by**. Select the dimension name above the table to go back. **Hide breakdown** hides the rows under the group’s total, and **Show breakdown** brings them back.
* To keep a group in view for comparison, select **Add comparison row**, choose a dimension, then select a value. The row stays below **Survey overall**. Drag comparison rows to reorder them, or select **×** to remove one.
* Use **Include only** or **Exclude** under **Participant filters** to narrow who is counted. A **Filtered total** row then shows the totals for the people you kept. Changing the filters or tag source clears your comparison rows. Your filters aren’t kept. Comparison rows and tag source stay in the page address, so refreshing or sharing the link keeps them, but they aren’t saved as a report.
* A **—** means the group is smaller than your organization’s confidentiality minimum, so its completed count and rate are hidden. **Sent** is still shown.

## Save a report you’ll reuse

1. Select **New report**.
2. Enter a **Report name** and choose a **Tag source** (see below).
3. Choose a **Primary anchor**, which is the main tag to group by. You can also add **Secondary anchors**. Tick **Show Totals** on a secondary anchor to add a total row for it.
4. If needed, add **Participant filters**.
5. Select **Create report**.

Everyone who opens a saved report sees the same setup, limited to the groups they have access to.

In a saved report, use **Search...** to find rows by name, and the filter button beside it to narrow the rows.

## Choose a tag source

When someone is invited to a survey, Innerlogic saves a copy of their tags, such as department and location. Survey results use this saved copy. Later changes to your contact list, including a contact sync, don’t move anyone in the results.

If your contact list changes while the survey is running, for example when two teams merge, you can choose which tags a participation report uses:

* **Survey snapshot tags** (default): the tags people had when they were invited.
* **Current contact tags**: people’s latest tags in your contact list.

To show a restructure while the survey is open, update your contact list first, then set the report to **Current contact tags**. The choice is saved with the report and used by its scheduled emails.

Renaming a tag value is different: the new name shows everywhere straight away, with nothing else to do.

## Download or email updates

* **Export CSV** saves the table on screen, including comparison rows and the current sort. The file opens in Excel or any spreadsheet app. On the default view, **Save PDF** opens your browser’s print dialog.
* To email regular updates, select **New schedule** under **Participation report schedules**:
  * Choose the report and the days to send on. Days are counted from the survey’s start date, so **0** is launch day.
  * Choose a send time and time zone.
  * Add recipients, and the data each one can see.
* Recipients get an email with a secure link to an Excel file. Links expire after 30 days. **Invalidate links** cancels them sooner, and **Send now** sends an update straight away.

## After the survey closes

If people moved between groups during the survey, an organization admin can update the survey’s saved tags after it closes. This replaces everyone’s saved tags with their current contact tags. Survey results, new PDF reports and exports then group people by today’s contact list.

1. Open the survey’s three-dot menu and choose **Update Tags**.
2. Select **Refresh invitation tags** and confirm.

Refresh is available only after the survey closes. An admin can undo the most recent refresh for about 30 days. Reports and emails already sent don’t change.

## Ask for help

If a count looks wrong or an option is missing, contact your organization’s Innerlogic contact. See [Who to contact](https://docs.innerlogic.com/en/troubleshoot-access.md#who-to-contact). Include the survey name, the report name and what you expected to see. Do not send confidential response data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.