> 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/what-methods-are-available-for-survey-distribution.md).

# What methods are available for survey distribution?

We understand that not all employees have regular access to computers, especially in industries with field workers or non-desk jobs. We have several methods to ensure all employees can participate in the survey:

1. **PIN Survey**:
   * Each employee can access the same link using a PIN that identifies them. The PIN will also store any demographic data you wish to collect from the participants so they do not need to self-identify.
2. **Kiosk Setup**:
   * You can set up dedicated kiosks or stations with laptops or tablets at your workplace.
   * Employees can use these to complete the survey during designated times.
3. **Paper Surveys**:
   * While less common now, we still offer paper surveys as an option.
   * However, we recommend this as a last resort due to potential issues with delayed returns and confidentiality.
4. **Mobile/SMS Access**:
   * We can send unique IDs or links via text message for employees to complete the survey on their smartphones.


---

# 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/what-methods-are-available-for-survey-distribution.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.