> 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/the-full-lifecycle.md).

# The full lifecycle

The whole flow, from the first draft to the live survey. Each step opens the page that covers it.

**Step 1: Set up the study and generate the draft.** In the **Setup** tab, enter the research brief, the target population, the target LOI, and any questions or drafts that you have. Then select **Generate Questionnaire**.

[Setting up and generating the questionnaire](/design-collaboration/setting-up-and-generating-the-questionnaire.md)

**Step 2: Review the draft with the AI Assistant.** The AI Assistant adds design flags and LOI suggestions as it generates the draft. Go through the suggestions before you share anything with your client.

[The Design Assistant](/design-collaboration/the-ai-assistant-review.md)

**Step 3: Check the edits and discuss them with your team.** Each edit shows in the **Tracked Changes** tab. Use comments to ask questions about a question.

[Comments & tracked changes](/design-collaboration/comments-and-tracked-changes.md)

**Step 4: Set up client access.** Select who can open the link, what your client can do, and what your client can see.

[Setting up client access](/design-collaboration/setting-up-client-access.md)

**Step 5: Your client reviews the questionnaire.** Your client comments and replies. With **Edit** access, your client can also change the questionnaire.

[What your client will experience](/design-collaboration/what-your-client-will-experience.md)

**Step 6: Act on client feedback.** Read each client comment and edit. Make the agreed changes, then reply to or resolve the comments.

[Reconciling client feedback](/design-collaboration/reconciling-client-feedback.md)

**Step 7: Hand off the version to programming.** Metaforms saves the questionnaire as a numbered version and sends it to the SP.

[Versions & handing off to programming](/design-collaboration/versions-and-handing-off-to-programming.md)

**Step 8: The SP scripts the survey.** The SP works in the Programming workspace and selects **Mark ready** when the survey is scripted.

[The Programming workspace (SP)](/design-collaboration/the-programming-workspace-sp.md)

**Step 9: Review the finished survey.** Open the **Survey Link** on the Design page to check the scripted survey before you approve it for fielding. Add a screenshot to a comment when you see a problem.

[Survey link & screenshots](/design-collaboration/survey-link-and-screenshots.md)

**Step 10: Hand off a new version during scripting.** If you hand off a newer version while the SP is still scripting, the SP decides when to start it. Nothing changes automatically.

[Handing off a new version during scripting](/design-collaboration/handing-off-a-new-version-during-scripting.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://help.metaforms.ai/design-collaboration/the-full-lifecycle.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.