> 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/what-are-the-recommended-timelines-for-various-project-phases.md).

# What are the recommended timelines for various project phases?

Here is an overview of the typical project timeline for an engagement survey:

1. **Initial Phase (1-4 weeks)**:
   * Strategic Alignment session
   * Kickoff call
   * Survey design (1-4 weeks, can extend up to 6 weeks)
2. **Pre-Survey Phase (2-3 weeks)**:
   * Pre-survey communication (1-6 weeks)
3. **Survey Phase (2-3 weeks)**:
   * Data collection (typically 2 weeks, rarely more than 3 weeks)
4. **Analysis and Reporting Phase (1-2 months)**:
   * Online reporting becomes available
   * In-depth analysis and connecting the dots
   * Presentation of results to leadership team (in stages)
5. **Post-Survey Phase (6-8 months)**:
   * Ongoing access to online reporting

Overall timeline:

* From signing contract to strategic alignment: As quick as a few days
* Kick-off call then takes place within a few days of the Strategic Alignment
* From kickoff to survey launch:
  * For new clients: Recommended 6-8 week window
  * For experienced clients: Can be as tight as 4-5 weeks

It's important to note that the entire process typically spans about three months, broken down into these phases:

* Month 1 - 2: Strategic Alignment, Kickoff, survey design, email list preparation, communication planning
* Month 2: Final launch preparations, Data collection (2-3 weeks), initial reporting (last week)
* Month 3: Rolling out results to the rest of the organization

These timelines can be adjusted based on your organization's size and specific needs. We're flexible and can work with you to create a timeline that best suits your requirements.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.talentmap.com/knowledge-base/step-1-prepare-for-action/prepare-for-action-faq/what-are-the-recommended-timelines-for-various-project-phases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.