> 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/managers-dashboard/analytics-and-performance/change-management.md).

# Change Management

Use Change Management analytics to understand where your team uses Change Management and how review sessions are progressing.

<figure><img src="https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2F9vzphdGzFePwd2x7HDn3%2Fclipboard.jpeg?alt=media&amp;token=ce599aeb-672f-4219-90f2-e8807c20e3d6" alt=""><figcaption></figcaption></figure>

Open **Manager → Analytics & Performance**, select **Change Management**, and choose a date range. Then select **Users** or **Projects**.

## Understand the summary

<figure><img src="https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FQibANHo3QGGtaqfkndam%2Fimage.png?alt=media&amp;token=0c97e40f-d01e-4392-ad14-27cbb764c34a" alt=""><figcaption></figcaption></figure>

**CM adoption** shows the share of SP-initialized projects created in the selected period that have used Change Management.

**Completion rate** shows the share of CM sessions started in the selected period that are currently complete. Those sessions can belong to projects created earlier also.

These cards use different starting populations, so do not compare their counts as if they describe the same set of projects. A session that is not complete may still be in progress.

## Users: review team activity

<figure><img src="https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FQYeLemNyZHSnOk7cEOqM%2Fimage.png?alt=media&amp;token=df0710ad-bb86-4a55-91ab-707193aa207d" alt=""><figcaption></figcaption></figure>

Select **Users** to see activity by person.

1. Open **All members** and search for a user or group.
2. Select one or more users or groups. The button shows how many filters you selected.
3. Clear selections when you want to return to the full list. The member filter applies to the user table; the summary cards show the overall organization.
4. Expand a user to see their Change Management activity by project.
5. Select **Export CSV** to download the report.

| Column        | What it shows                                                                                       |
| ------------- | --------------------------------------------------------------------------------------------------- |
| User          | A person who started a CM session or applied or skipped changes.                                    |
| Projects      | Distinct projects where the user started a session or resolved a change during the selected period. |
| CM sessions   | Shows how many Change Management sessions the user started and how many of those are complete.      |
| Resolved      | Shows how many changes the user has dealt with, whether by applying or skipping them.               |
| Applied       | Changes the user marked as applied during the selected period.                                      |
| Skipped       | Changes the user marked as skipped during the selected period.                                      |
| Last activity | The latest recorded session start or change resolution attributed to the user.                      |

## Projects: review adoption

Select **Projects** to see qualifying SP-initialized projects created in the selected period that have used Change Management. The CM session can have started outside the selected period. The version count and latest-session details reflect the project's CM history. Use **Search projects** to find a project by name or customer project ID, and select **Export CSV** to download the available report.

<figure><img src="https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FP4nBvx6AKqEOoiX5Prxy%2Fimage.png?alt=media&amp;token=e65392dd-cb60-46b7-a59e-bb6eb5e76f4e" alt=""><figcaption></figcaption></figure>

| Column            | What it shows                                                                             |
| ----------------- | ----------------------------------------------------------------------------------------- |
| Project           | Project name, customer project ID, and current project status.                            |
| Platform          | The survey platform connected to the project.                                             |
| Versions using CM | Shows how many versions of the project have used Change Management.                       |
| Current review    | Shows progress through the latest review, including changes that were applied or skipped. |
| Latest outcome    | The outcome of the latest CM session in the latest project version.                       |
| Last Activity     | The most recent activity across the project's CM sessions.                                |

## Example: explore a team's CM usage

Choose a date range and open **Users**. Select a group in **All members**, then expand a person to see their project activity. Compare sessions started, completed, applied and skipped to understand how reviews are progressing.

To investigate a particular project, switch to **Projects** and search by project name. Check the latest outcome and current review together. A low completion rate on its own does not explain why a session is incomplete.


---

# 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/managers-dashboard/analytics-and-performance/change-management.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.
