> 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/handling-a-new-version-mid-scripting-sp.md).

# Handling a new version mid-scripting (SP)

If the PM freezes and hands off a new version (e.g. **V2**) while you're still scripting **V1**, you won't be silently overwritten. Here's what to expect and what to do.

**Step 1:** Notice the alert. The version bar shows a **V2 is newer** control instead of switching automatically.

**Step 2:** Review the diff before accepting anything. Incoming XML changes appear as a reviewable diff. Nothing is auto-applied.

**Step 3:** Choose how to bring the update in. Opening V2 shows the *Start Version 2* modal with two independent choices. **Survey project:** *Duplicate Survey* creates a new Decipher survey project, *Continue in Existing* updates the existing one in place. **Change Management:** *Use Change Management* has the AI review the questionnaire changes and help apply them systematically — recommended, and it works best with Word tracked changes or highlighted edits; *Proceed Normally* continues in the standard workspace without AI-assisted reconciliation.

**Step 4:** Confirm. **Start Version 2** stays disabled until both choices are made.

{% hint style="info" %}
For the full Change Management walkthrough see Change Management.
{% 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/review-collaboration/handling-a-new-version-mid-scripting-sp.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.