> 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/timelines-and-deliverables.md).

# Timelines and Deliverables

Your survey program follows the seven TalentMap steps, and each step has a deliverable and a typical planning range. Use this page to build your internal timeline and to see which tasks your team owns.

***

## Your first three tasks

1. Log in to the TalentMap Portal (Klient) to view the tasks to complete during this survey period. The portal gives you visibility on every step of your project, access to all resources, real-time data, and a view of year-over-year survey projects.
2. Contact your Project Manager if you need help with the portal or cannot find your login invite.
3. Identify and notify the people who will be part of your survey team so they can start preparing their deliverables.

***

## Planning range by step

These ranges describe a typical engagement survey. Your Project Manager will confirm dates for your program.

| Step                                      | What you deliver                                                      | Typical planning range                          | What changes the timing                             |
| ----------------------------------------- | --------------------------------------------------------------------- | ----------------------------------------------- | --------------------------------------------------- |
| **1. Prepare for Action**                 | Strategic Alignment session, kickoff call, named survey team          | As quick as a few days after contract           | Executive availability for the alignment session    |
| **2. Develop Questionnaire**              | Signed-off questionnaire, scales, and demographics                    | 1 to 4 weeks, potentially up to 6 weeks         | Number of review rounds and custom items            |
| **3. Pre-Survey Communication and Setup** | Participant information file, email whitelisting, communications plan | 1 to 6 weeks, commonly in parallel with Step 2  | Data readiness in HR systems and IT lead time       |
| **4. Deploy Employee Survey**             | Survey open, monitored, and closed                                    | Typically 2 weeks, rarely more than 3 weeks     | Organization size, shift work, and reminder cadence |
| **5. Analyze, Interpret and Report**      | Compass reports live, HR preview, executive presentation              | 1 to 2 months for analysis and staged reporting | Number of leadership groups receiving presentations |
| **6. Discuss, Clarify and Plan**          | Agreed priorities and action planning approach                        | Variable and not time-bound                     | Leadership calendar and depth of follow-up work     |
| **7. Communicate and Take Action**        | Results shared with employees, action plans tracked                   | Ongoing                                         | Your action planning cadence                        |

{% hint style="info" %}
**How the steps roll up.** From kickoff to survey launch, new clients should plan a 6 to 8 week window. Experienced clients can run as tight as 4 to 5 weeks. Most programs plan to roll results out to the organization in month 3, which is an example planning milestone rather than a fixed duration.
{% endhint %}

{% hint style="info" %}
**Access to Compass reporting** continues after the program and is set by your agreement with TalentMap. It is not part of the Step 7 duration.
{% endhint %}

***

## Related Articles

* [Getting Started](/knowledge-base/getting-started.md)
* [What are the recommended timelines for various project phases?](/knowledge-base/step-1-prepare-for-action/prepare-for-action-faq/what-are-the-recommended-timelines-for-various-project-phases.md)
* [Who will be responsible for different aspects of the project?](/knowledge-base/step-1-prepare-for-action/prepare-for-action-faq/who-will-be-responsible-for-different-aspects-of-the-project.md)
* [Schedule a Meeting with your Consultant or Project Manager](/knowledge-base/step-1-prepare-for-action/schedule-a-meeting-with-your-consultant-or-project-manager.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-1-prepare-for-action/timelines-and-deliverables.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.
