> 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/handing-off-a-new-version-during-scripting.md).

# Handing off a new version during scripting

You can continue to change the questionnaire after a handoff. Your changes go into the next version. When you are ready, hand off that version, even if the SP is still scripting the earlier one. Nothing changes in the SP's work until the SP decides to start the new version.

## Hand off the new version

1. Make your changes on the Design page.
2. Select **Hand off V2** at the top of the page.
3. Read the dialog **Hand off Version 2 to Programming**. It shows how many questions and sections Programming will receive, and the items that you did not finish.
4. Select **Hand off**.

If you did not change anything since the last handoff, the button is not available. It shows the message **This version was already handed off.**

## What the SP sees

The SP gets the notification **Version ready for Programming** again. In the version control of the Programming workspace, the SP sees **Start V2** (**Complete V1 and begin scripting V2**).

When the SP selects **Start V2**, the **Start Version 2** dialog opens. Starting the new version marks Version 1 as completed. The SP makes two choices:

| Choice                | Options                                                                                                                                            |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Survey project**    | **Duplicate Survey** makes a new Decipher survey. **Continue in Existing** updates the current survey.                                             |
| **Change Management** | **Use Change Management** lets the AI find the changes between the versions and help apply them. **Proceed Normally** continues without this help. |

Then the SP selects **Start Version 2**. For more information about Change Management, refer to [Change Management](/survey-programming-decipher/unified-flow/change-management.md).

{% hint style="info" %}
Make your changes clear for the SP. The Word file of the new version has your **Client** comments only. If you made an important change, tell the SP about it.
{% endhint %}


---

# 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/handing-off-a-new-version-during-scripting.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.