> 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-1-prepare-for-action/prepare-for-action-faq/when-should-we-schedule-the-questionnaire-design-call.md).

# When should we schedule the questionnaire design call?

Here are the key points about scheduling the questionnaire design call:

1. **Timing**: It's recommended to schedule the call at least 3 weeks prior to the survey launch. This allows time for potential follow-up calls and revisions. You have the flexibility to book sooner if you prefer. 
2. **Booking process**:
   * You can book the call directly using your consultants' calendar link provided in the task details.
   * Look for a "Questionnaire Design Meeting" option when booking.
3. **Purpose**: This initial call is to go through the full questionnaire with your consultant. The consultant will help you craft new questions or edit existing ones as needed.
4. **Preparation**: Before the call, you'll receive:
   * A draft of the new standard questionnaire (which has some new sections since 2024)
   * A copy of your previous survey for comparison

Remember, it's better to schedule this sooner rather than later, especially if you anticipate needing follow-up discussions or team reviews after the initial design meeting.


---

# 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-1-prepare-for-action/prepare-for-action-faq/when-should-we-schedule-the-questionnaire-design-call.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.