> 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-2-develop-questionnaire/questionnaire-faq/can-we-customize-the-standard-questionnaire.md).

# Can we customize the standard questionnaire?

Yes, we offer a high degree of customization for our standard questionnaire. Here are the key points about customizing the survey:

* **Full Flexibility**: We provide a lot of flexibility when it comes to customization. There are no strict limitations tied to the percentage you can customize.
* **Easy Editing**: You can easily customize questions by pulling them from our question vault. Once added to your survey, you can further edit them, add terminology, etc. The process is simple, similar to editing a Google doc.
* **Expert Guidance**: Our organizational psychologists work with you on customizations. They can advise on the implications of changes to ensure the survey's integrity and interpretability are maintained.
* **Mapping Tool**: We have a mapping tool that allows us to map custom questions to benchmark questions. This helps in comparing data across surveys, even with customizations.
* **Strategic Approach**: When customizing, we encourage thinking about actionability. We typically ask clients to consider what actions they would take for high or low scores on each question. This ensures the survey provides valuable, actionable insights.

While we offer extensive customization options, we always aim to balance this with maintaining the survey's validity and benchmarking capabilities. Our team is here to guide you through this process to create a survey that meets your specific needs while providing reliable, actionable data.


---

# 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-2-develop-questionnaire/questionnaire-faq/can-we-customize-the-standard-questionnaire.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.