> 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/survey-programming-dimensions/change-management/what-we-support.md).

# What We Support

Change Management works best when the updated questionnaire clearly shows what changed. This helps Metaforms identify the right updates, ask the right follow-up questions, and guide you through applying the changes to your survey.

### Supported Inputs

Metaforms supports questionnaire updates that use:

* **Highlights** to mark new, changed, or important content.
* **Tracked changes** to show edits, additions, and removals directly in the document.

When these are present, Metaforms can use them as signals during the review and apply stages.

### Supported Change Types

Metaforms supports **cascading questions**. This means it can help with changes where one update affects related questions later in the questionnaire, such as follow-ups, dependent questions, or question flows that need to stay aligned.

### Current Limitations

Metaforms cannot yet reliably find every change between two questionnaire versions when the changes are not clearly marked.

For example, if you upload a new questionnaire without highlights or tracked changes, Metaforms may not always identify every difference between the old and new versions. You should review the generated clarifications and applied changes before finishing the version.

### Upcoming Roadmap

We are working on:

* **Better questionnaire version comparison** to improve change detection accuracy between questionnaire versions.
* **Changelog Excel file support** so changelog files can be used as another way to identify updates.

These improvements will help Metaforms identify changes more reliably, even when updates are not fully marked with highlights or tracked changes.


---

# 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/survey-programming-dimensions/change-management/what-we-support.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.
