> For the complete documentation index, see [llms.txt](https://help.timebook.ai/hc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.timebook.ai/hc/product-guide/core-concepts-and-objects/research-and-planning-objects/product.md).

# Survey

## What are Surveys?

The **Survey** module in Timebook is designed to help your team organize and analyze survey results after they’ve been distributed and completed. Instead of managing survey creation or distribution, Timebook focuses on what happens next—turning responses into actionable **Insights** and mapping them to **Opportunities** for your product roadmap.

Surveys serve as another key source of Insights in Timebook. While **Interviews** capture qualitative feedback through conversations, **Surveys** allow you to validate findings, identify patterns, and measure trends across larger groups.

### Survey Cards

Each Survey in Timebook has its own **card**, which contains all the properties and options for managing it. The card design follows the same logic as **Interviews** and **Feedback**, making it simple to work across different object types.

#### Sections

On the left side of a Survey card, you’ll find sections for describing, categorizing, and enriching your Survey:

* **Summary** → Provides a high-level overview of the Survey, including its purpose, status, total participants, and response count. This section acts as a reference point for the entire Survey.
* **Data** → Stores the actual responses (imported from an external survey tool) and allows you to review them individually or in aggregate.
* **Insights** → Displays Insights generated from the responses—either automatically by AI or added manually.
* **Participants** → Shows a list of people who took part in the Survey, helping you track segments and sources of feedback.

### Generating Insights from Surveys

Survey responses can be transformed into actionable Insights directly in Timebook:

1. Click **\[Generate Insights]** to analyse responses with AI.
2. The system highlights recurring themes, pain points, and feature request.
3. Insights are stored in the **Insights** section of the Survey card, where you can also add or edit them manually.

This ensures that even large volumes of survey data can be quickly distilled into meaningful outcomes.

***

### Mapping Insights to Opportunities

To connect feedback directly to your product strategy, you can map Insights from Surveys into Opportunities:

* Click **\[Map to Opportunities]** to analyze collected Insights.
* The AI will link them with **existing Opportunities** or generate **new Opportunities** automatically.

This ensures that user feedback doesn’t remain as raw data but is actively transformed into inputs for roadmap planning.

***

### Why Surveys Matter

Surveys complement Interviews by **scaling discovery**:

* Validate findings across larger user groups
* Quantify trends and patterns in feedback
* Prioritize product decisions with measurable evidence

Together, **Interviews** and **Surveys** form a strong foundation for data-driven discovery and decision-making in Timebook.


---

# 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://help.timebook.ai/hc/product-guide/core-concepts-and-objects/research-and-planning-objects/product.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.