> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/surfacescout/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/surfacescout/mitigating-risks-from-the-field.md). # Mitigating risks from the field If you have been using the web version on your computer, the use should be pretty straightforward! Here is your landing page:

The Case list is at the bottom left 1. You can search for specific Cases here 2. To enhance case visualization on the map, you can toggle between different basemaps by clicking this button multiple times. 3. Additionally, you can filter by various attribute values and, of course, identify the latest cases for review. Let’s now jump to the Case list And select one specific Case to review

Once you click on of the insights you should find again some very familiar concepts: 1. The slider to see the before/after images of the changes with the dates respectively at the bottom left and right 2. Some details about the Insight 3. The option to change the view mode 4. And off course the option to give some feedback directly from the field!

Let’s now focus on how to update the Insight! This is where you field companion makes the most sense, you have the reality in front of you to adjust things, feel free to: to change the Change Type, the criticality level, add a note, add a photo, rate the insight, etc. Once it is done click on Save at the bottom of the page!

Insight update and feedback view on mobile

--- # 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://docs.live-eo.com/surfacescout/mitigating-risks-from-the-field.md?ask=&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.