# Requesting Analyses
## How to Create an Order for Analysis
1. Click the **Create order** button on the **Orders** tab.
2\. Select media files to upload to the system or drag and drop them to the selected area.
3\. After the download is complete, the analysis types become available for selection. By default, there are all possible checkboxes.
* **Document check** – recognition and verification of the document fields.
* [**Image Biometry check**](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/biometry.md) – comparing multiple photos and assessing the level of similarity.
* [**Collection check**](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/collection.md) – compare the uploaded photo with the scammers' photos from the collection database.
* [**Liveness** ](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/liveness.md)– an algorithm for determining liveliness is designed to check the presence of a living person by a short video fragment. The checkbox is available for selection only when uploading a video.
Uncheck the (or not installed components) analysis types you don't need.
4\. Next, select tags – the type of content for each uploaded file and at the end click the **Submit analysis** button.
* Options for choosing the **Document** type (you can load several pages of one document at once):
* Document with photo
* Document without photo
* if there is a face in the image, not a document, select the **Selfie** content type.
* For videos, only **Selfie** is available along with qualifying tags:
* orientation: **Portrait** or **Landscape**
* type of action (what action was performed by the person in the video): scan, turn left, turn right, turn down, turn up, smile, close eyes. The video with a certain type of action is recorded via the [Oz Mobile SDK](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk.md) and [Web SDK](/oz-knowledge/guides/developer-guide/sdk/oz-liveness-websdk.md). For regular videos, use the **Scan** tag.
{% hint style="info" %}
Please note: if the tags are chosen incorrectly, the analysis results might be flawed.
{% endhint %}
5\. Upon the analysis completion, you'll see the results for the previously selected analysis types:
* analysis succeeded – everything went fine;
* analysis failed – faces don't match, Liveness check failed, an error emerged during the processing, etc.;
* operator required – this means the system requests for the additional check made by your employee.
To get the detailed result for a specific type of analysis, click on the mark near the analysis' name.
`OPERATOR` and `CLIENT OPERATOR` can change the analysis verdict. These roles have access to an additional button: **Make decision**.
To change the verdict, the user should select the decision from the drop-down menu and click **Apply**.
Once analyses are finished for a folder, this folder gets status according to the analyses' results:
* `SUCCESS`– everything went fine, all analyses completed successfully;
* `OPERATOR_REQUIRED` – there are no analyses with the `DECLINED` status, but one or more analyses have been completed with the `OPERATOR_REQUIRED` status;
* `DECLINED` – one or more analyses have been completed with the `DECLINED` status.
The other two statuses that you might encounter are FAILED and INITIAL. FAILED means that one or more analyses are finished with an error. INITIAL stands for folders with no analyses applied.
A report on the study will be available in the PDF format by clicking the **PDF list** button (1) from the list of orders. For this option to become available, you should have a pre-configured report template for your company. Additionally, you can create a report from the order screen by clicking the **Show Report** button at the bottom of the page below an image.
Any order can be deleted either by clicking the **Trash bin** button from the list of orders (2) or by clicking the **Delete** button from the order form.
## Filters
Analysis orders can be filtered by several parameters. The scope of visibility is limited by the access rights of your user's role.
* In the **Orders** tab, click the **Filter** button
* you can use one or more fields for filtering:
* **Order number** – enter the full alphanumeric order number or type the first few characters.
* **Date/time** – the range of dates of orders' creation.
* **Company** – the company that owns the orders.
* **Manager** – the user who created the orders.
* **Consolidated folder status** – the overall analyses' result for the folder.
* **Analysis type** – the type of the analysis applied.
* **Analysis result** – choose the result to display all orders where one or more of the analyses have been completed with this result.
* **Meta** – you can filter orders by specific meta tags by adding their name and value using the **Add** button. A meta tag is any information that a programmer can transmit when submitting an order via API. Enter the name and range of values into the field manually.
* After filling in the fields, click the **Search** button.
* To reset the current filter, hit the **Reset** button.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://doc.ozforensics.com/oz-knowledge/guides/user-guide/oz-webui/webui-order.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.