> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/interactive-validations.md).

# Interactive Validations

The Interactive Validation performs checks on annotations data before the task moves to the next stage and can be configured during the setup phase ([label validation](/3d-multi-sensor-fusion/labeling/category-schema/label-validation.md)). It uses pre-defined validations set during the setup and highlights potential issues. The tool allows users to view, validate, and fix problems interactively without leaving the annotation workspace.

{% hint style="info" icon="lightbulb-on" %}
Validation enhances the workflow by ensuring consistent and high-quality results across various business requirements.
{% endhint %}

![](https://content.gitbook.com/content/TcOUG6rfWxqGM0N4db2P/blobs/78dpcxWTlYOnUdciFshG/image)

***

## Use Cases

* Quality Assurance: Automatically catch incomplete or incorrect annotations
* Progression Control: Block data from progressing to the next stage (e.g., internal review, customer auditing) if it fails basic validation
* Consistency Check: Ensures consistency in object properties across frames and sequences
* Customer Business Rule: Enforce project-specific rules without manual checks
* Real Time Feedback: Show validation errors as annotators work, enabling faster correction

***

## Benefits

* Prevents invalid or incomplete annotations from progressing
* Saves time by linking validation errors directly to their locations
* Customizable per workflow to match specific project needs
* Non-disruptive: user can keep the report open while annotating

***

## Steps to Use Interactive Validation Reports

{% stepper %}
{% step %}

#### Annotate and extend

Annotate the object and extend it until its last visible frame.
{% endstep %}

{% step %}

#### Trigger validation

Click the shield icon to trigger validation.
{% endstep %}

{% step %}

#### Open report

The Interactive Validation Report opens on the right panel.
{% endstep %}

{% step %}

#### Review issues

Review the list of issues - each card links to the exact location in the sequence.
{% endstep %}

{% step %}

#### Fix issues

Fix issues as you go, with the report panel open for reference.
{% endstep %}
{% endstepper %}


---

# 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.imerit.net/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/interactive-validations.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.