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

# The full lifecycle

The whole flow, end to end. Each step opens the page that covers it.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>1. Open &#x26; review with the Agent</strong></td><td><a href="/review-collaboration/the-agent-review-pm.md">The Review Agent</a></td></tr><tr><td><strong>2. Triage suggestions</strong></td><td><a href="/review-collaboration/comments-and-tracked-changes.md">Comments &amp; tracked changes</a></td></tr><tr><td><strong>3. Share client access</strong></td><td><a href="/review-collaboration/setting-up-client-access-pm.md">Setting up client access</a></td></tr><tr><td><strong>4. Client reviews</strong></td><td><a href="/review-collaboration/what-your-client-will-experience.md">What your client will experience</a></td></tr><tr><td><strong>5. Reconcile feedback</strong></td><td><a href="/review-collaboration/reconciling-client-feedback-pm.md">Reconciling client feedback</a></td></tr><tr><td><strong>6. Freeze &#x26; hand off</strong></td><td><a href="/review-collaboration/locking-a-version-and-handing-off-to-programming-pm.md">Locking a version &amp; handing off to programming</a></td></tr><tr><td><strong>7. SP builds the survey</strong></td><td><a href="/review-collaboration/the-programming-workspace-sp.md">The Programming workspace (SP)</a></td></tr><tr><td><strong>8. Survey link &#x26; clarifications</strong></td><td><a href="/review-collaboration/survey-link-screenshots-and-clarifications.md">Survey link, screenshots &amp; clarifications</a></td></tr><tr><td><strong>9. New version mid-scripting</strong></td><td><a href="/review-collaboration/handling-a-new-version-mid-scripting-sp.md">Handling a new version mid-scripting (SP)</a></td></tr></tbody></table>

**Step 1: Open the questionnaire — the Agent review runs automatically** The AI-assisted review starts as soon as the questionnaire is opened; go through its suggestions before sharing anything externally.

{% content-ref url="/pages/ZBzdCcCmTXn11vxvfQEY" %}
[The Review Agent](/review-collaboration/the-agent-review-pm.md)
{% endcontent-ref %}

**Step 2: Triage suggestions, apply fixes, resolve internal questions** Accept, dismiss, or comment on what the Agent surfaces; every accepted fix is a tracked change.

{% content-ref url="/pages/mbN1kKK7vGJNwWlACgrZ" %}
[Comments & tracked changes](/review-collaboration/comments-and-tracked-changes.md)
{% endcontent-ref %}

**Step 3: Configure and share client access** Decide who can use the link, what permission level they get, and what's visible to them.

{% content-ref url="/pages/lKdUkx8RHuQNGj202Z9D" %}
[Setting up client access](/review-collaboration/setting-up-client-access-pm.md)
{% endcontent-ref %}

**Step 4: Client reviews and responds** They comment, reply, and — with Edit access — make direct tracked edits.

{% content-ref url="/pages/gN7rcn4wDB0FT7ulqjV5" %}
[What your client will experience](/review-collaboration/what-your-client-will-experience.md)
{% endcontent-ref %}

**Step 5: Reconcile feedback** Review every client comment and edit; approve what's agreed, resolve or reply as needed.

{% content-ref url="/pages/9wTlEmQY3UNS0Keb5WI0" %}
[Reconciling client feedback](/review-collaboration/reconciling-client-feedback-pm.md)
{% endcontent-ref %}

**Step 6: Freeze the version and hand off to programming** Lock the questionnaire as a numbered version and pass it to the SP.

{% content-ref url="/pages/3cetIntcXHmylqqXsiPT" %}
[Locking a version & handing off to programming](/review-collaboration/locking-a-version-and-handing-off-to-programming-pm.md)
{% endcontent-ref %}

**Step 7: SP builds the live survey** Working in the Programming workspace, validate and sync the build, then mark it ready.

{% content-ref url="/pages/NRHrXb65oAlXnYxL8ioP" %}
[The Programming workspace (SP)](/review-collaboration/the-programming-workspace-sp.md)
{% endcontent-ref %}

**Step 8: Review the live survey via the Survey Link** Once the SP marks the build ready, the **Survey Link** tab is available to you and to your client. Open the live survey, comment on it, and attach screenshots; the SP can ask you for clarification the same way.

{% content-ref url="/pages/v9RLTKt17qGfjWzl9ybU" %}
[Survey link, screenshots & clarifications](/review-collaboration/survey-link-screenshots-and-clarifications.md)
{% endcontent-ref %}

**Step 9: Handle any new version that arrives mid-scripting** If the PM freezes a newer version while you're still scripting, you're prompted to reconcile it deliberately — nothing is applied automatically.

{% content-ref url="/pages/lw7NriJynA4gmhmwM1ia" %}
[Handling a new version mid-scripting (SP)](/review-collaboration/handling-a-new-version-mid-scripting-sp.md)
{% endcontent-ref %}


---

# 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/review-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.