> 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/configuration/case-management.md).
# Case management
**A case aggregates Insights based on specific rules**, such as:
* The distance between insight centers being less than X meters.
* Insights having the same change type (or not) to qualify for aggregation.
These settings can be configured in SurfaceScout to ensure Case creation aligns with business needs. Typically, we observe that users aggregate Insights when they are within 30 meters of each other and share the same change type.
**Example:**
2 cases are created:
* **C1**: A new construction site has started, generating new Insights every two weeks, such as container movement, excavation, material buildup, etc.
* **C2**: A logging activity area, where a forestry company cuts trees every two weeks. This activity is visible through the Insights we generate.
Case creation and update
On December 5, 2024, 2 new insights were generated. One of them could be connected to C1 as it is within 30 meters of other insights. The other insight triggered a new case because it was unrelated to the existing ones.
Case creation and update
In real life, aggregating relevant items makes information much easier to digest. For example, consider a large construction operation near a pipeline. SurfaceScout has detected multiple insights over several months, all aggregated into a single **Case**.
Same location over time
---
# 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/configuration/case-management.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.
