> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/design-collaboration/overview.md).

# Overview

How questionnaire design, client collaboration, and the programming handoff work in the Design module of Metaforms.

This guide is for you if you generate a questionnaire in the Design module of Metaforms, as a Research Manager, a Project Manager, or in another role. It explains how to set up the study in the Setup tab, how the AI Assistant generates and checks your draft, how comments and tracked changes work, how to share the questionnaire with your client, and how to hand it off to programming. It also shows what your client sees, so that you can set expectations with them.

![The Design page: the questionnaire on the left and the AI Assistant on the right](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FEgFYbqf2mafskGj171kZ%2F20-design-page.png?alt=media)

## Your role in the workflow

**You**: you own the questionnaire from the brief to the handoff. You generate the draft with the AI Assistant, work through its suggestions, discuss changes with your team, share the questionnaire with your client, act on client feedback, and hand off each version to programming.

**Client**: reviews the questionnaire through a secure link that you control, with **View**, **Comment**, or **Edit** access. The client sees only what you allow.

**SP (Survey Programmer)**: receives each version that you hand off and builds the live survey from it. For the SP steps, refer to [The Programming workspace (SP)](/review-collaboration/the-programming-workspace-sp.md).

## What to expect, at a glance

| If you…                                | This is what happens                                                                                                           |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Ask the AI Assistant for a change      | The AI Assistant changes the questionnaire immediately. The change shows in the **Tracked Changes** tab.                       |
| Select **Add to chat** on a suggestion | The suggestion goes into a queue above the chat box. The questionnaire changes only when you send the queue.                   |
| Edit a question yourself               | The edit shows in the **Tracked Changes** tab. Send **Review my changes** in the chat to let the AI Assistant check your edit. |
| Add a comment                          | The comment is **Internal** by default. Only your team can see it.                                                             |
| Set a comment to **Client**            | Your client can see the comment and reply to it in their review link.                                                          |
| Your client adds a comment             | The comment shows in your **Comments** tab immediately.                                                                        |
| Your client edits the questionnaire    | The edit applies immediately and shows in the **Tracked Changes** tab with the email address of the client.                    |
| You do not agree with a change         | Select **Revert** on the change in the **Tracked Changes** tab.                                                                |
| Select **Hand off**                    | Metaforms sends the questionnaire as it is to Programming. You can continue to work on the next version.                       |
| Open an earlier version                | The questionnaire is read-only. Select **Return to latest** to edit again.                                                     |


---

# 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://help.metaforms.ai/design-collaboration/overview.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.