> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pollandroll.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome to poll&roll

> Understanding the platform, its modules and a survey's journey from A to Z.

poll\&roll is Discurv's marketing-research platform. It covers the whole cycle of a survey: designing the questionnaire, collecting the responses, analyzing the results and producing the report. All in one place.

<Note>
  The poll\&roll interface is available in French and English. Pick your language from the dropdown in the navigation bar: the choice is saved on your account and applies to all your visits, as well as to the notification e-mails poll\&roll sends you. French is the default, and the users you invite start with your language.
</Note>

This page introduces the concepts to know before you start. You do not need to be a research expert: every term is explained as it comes up.

## The platform's three modules

The platform is built around three main modules.

<CardGroup cols={3}>
  <Card title="Questionnaire editor" icon="pen-to-square">
    The interface where you build and configure your questionnaire.
  </Card>

  <Card title="Respondent questionnaire" icon="mobile-screen">
    What participants see when they answer (the respondent front end).
  </Card>

  <Card title="Deliverables" icon="chart-column">
    The heart of the analysis: results, visualizations, reports and exports.
  </Card>
</CardGroup>

## The survey, your unit of work

Everything revolves around the **survey**. A survey brings together a questionnaire, its response collection and its results. It is the object you create, share and analyze.

You work through each survey via a series of tabs, in a logical order: the **questionnaire**, then **data collection**, then the **results**, and finally the **report**.

### The statuses of a survey

A survey goes through four successive statuses, driven from the **Launch** tab: **Draft** (the survey is editable, you build the questionnaire), **Pending** (you put the fieldwork online), **Fieldwork** (responses come in live), then **Complete** (fieldwork is closed: no further interview is added and the results are final).

<Warning>
  Launching the fieldwork **locks the questionnaire**: it can no longer be edited until the survey is switched back to **Draft**. Check everything before you launch.
</Warning>

## A survey's journey in 5 steps

This documentation follows the natural flow of a survey. You can read it in order.

<Steps>
  <Step title="Getting started">
    Log in, understand the concepts, navigate the platform and create a survey.
  </Step>

  <Step title="Questionnaire">
    Build and configure the questionnaire in the editor.
  </Step>

  <Step title="Data collection">
    Set up the sample sources, launch the fieldwork and track the responses in real time.
  </Step>

  <Step title="Results">
    Explore the results, filter, crosstab and prepare the data.
  </Step>

  <Step title="Report">
    Build a PowerPoint report slide by slide (**Reports** tab).
  </Step>
</Steps>

## The basic vocabulary

A few terms come up constantly. Here are the essentials.

| Term | Definition |
| - | - |
| **Sample source** (or respondent provider) | Where the respondents come from: a panel, a contact file or social networks. A survey can combine several sample sources. |
| **Interview** | An individual response to the questionnaire, whatever its status. |
| **Complete** | An interview taken all the way through and valid. |
| **Screen out** | A respondent set aside because they do not match the target. |
| **Target** | The population you are trying to survey (e.g. women aged 18-49). |
| **Quota** | The number of respondents you are aiming for per profile (e.g. 250 men, 250 women). |
| **Weighting** | A statistical adjustment that rebalances the sample to align it with objectives. |

<Tip>
  No need to remember all of this now. Each concept is detailed in the step where it comes up (the target and quotas in **Data collection**, weighting in **Results**).
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.