> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq.md).

# Pre-Survey FAQ

Answers to the questions that come up before your survey opens: who takes part, how participants receive it, how confidentiality works, and how to prepare your participant file and communications. Once the survey is live, use the [Survey Live FAQ](/knowledge-base/step-4-deploy-employee-survey/survey-live-faq.md).

***

## Confidentiality

* [Is the survey confidential?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/is-the-survey-confidential.md): how TalentMap protects individual responses, and the minimum group size for any report.

***

## Who takes part

* [Should we include new employees in our survey?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/should-we-include-new-employees-in-our-survey.md)
* [Should we survey contract or term employees?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/should-we-survey-contract-or-term-employees.md)

***

## Distribution and access

* [What methods are available for survey distribution?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/what-methods-are-available-for-survey-distribution.md): email invitations, shared links, and PIN access.
* [How long should the survey be open?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/how-long-should-the-survey-be-open.md)
* [How long does it take to program my survey?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/how-long-does-it-take-to-program-my-survey.md)
* [Survey Accessibility and Assistive Technology](/knowledge-base/step-2-develop-questionnaire/questionnaire-design/survey-accessibility-and-assistive-technology.md): what participants using screen readers and other assistive technology can expect.

***

## Participant file

* [Can I make changes to my PIF?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/can-i-make-changes-to-my-pif.md)
* [Why am I getting invalid entries in my import log?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/why-am-i-getting-invalid-entries-in-my-import-log.md)
* [Participant Information File](/knowledge-base/step-3-pre-survey-communication-and-setup/participant-information-file.md): the full guide to preparing and uploading your file.

***

## Participant Directory

* [Does Participant Directory change answers participants already submitted?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/does-participant-directory-change-answers-participants-already-submitted.md)
* [What happens to a survey when someone leaves our organization?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/what-happens-to-a-survey-when-someone-leaves-our-organization.md): what deactivating a participant does to open and closed surveys.
* [Can I still upload a participant file for a survey?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/can-i-still-upload-a-participant-file-for-a-survey.md)
* [Can one survey use more than one participant list?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/can-one-survey-use-more-than-one-participant-list.md)
* [Participant Directory Overview](/knowledge-base/survey-design-and-deployment/participant-directory-overview.md): the full guide to shared participant lists.

***

## Communications

* [How can we effectively communicate the survey to our employees?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/how-can-we-effectively-communicate-the-survey-to-our-employees.md)
* [What languages are available for communications material?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/what-languages-are-available-for-communications-material.md)
* [Are there standard invitations for Pulse surveys?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/are-there-standard-invitations-for-pulse-surveys.md)
* [Survey Communications](/knowledge-base/step-3-pre-survey-communication-and-setup/survey-communications.md): templates for invitations, posters, and info sheets.

{% hint style="info" %}
**Sharing with participants.** Most of these answers are written for the survey team. If a participant asks you whether the survey is confidential, the [Is the survey confidential?](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq/is-the-survey-confidential.md) answer is safe to forward as written.
{% endhint %}

***

## Related Articles

* [Survey Live FAQ](/knowledge-base/step-4-deploy-employee-survey/survey-live-faq.md)
* [Response Rate Strategies](/knowledge-base/step-3-pre-survey-communication-and-setup/response-rate-strategies.md)
* [Email Whitelisting](/knowledge-base/step-3-pre-survey-communication-and-setup/email-whitelisting.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talentmap.com/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.