> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow/manage-reports/comparing-follow-up-report-content.md).

# Comparing follow-up report content

To see what has been changed in a follow-up report, go into the report by clicking the Worldwide Unique ID (WWUID).

<figure><img src="https://844234868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7MbxF2Gm1Bf1uqE3mOA%2Fuploads%2F7v2OIxqHm04qS5vtTyUq%2FCompare.png?alt=media&amp;token=8fa0038b-0326-4147-87d8-48e5726f3daf" alt="" width="447"><figcaption></figcaption></figure>

1. Click the **`Compare`** button in the top menu.
2. This will open a new window where you have two versions of the report displayed with the newer version on the right.
3. Use the dropdown menus at the top to select which versions to compare. \
   Chagnges are marked in yellow.\
   New sections of a report are marked as New.

<figure><img src="https://844234868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7MbxF2Gm1Bf1uqE3mOA%2Fuploads%2FmtI1KWrecXSHuAfYHyKN%2FCompare_2.png?alt=media&amp;token=c9463212-3148-4f5c-ba77-4f5a6f7438a5" alt=""><figcaption></figcaption></figure>

Follow-ups received from companies are marked “**`Imported`**”, whereas any other change to the report will be marked “**`Edited`**”.


---

# 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://support.who-umc.org/vigiflow/manage-reports/comparing-follow-up-report-content.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.