> For the complete documentation index, see [llms.txt](https://docs.vcheckglobal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vcheckglobal.com/platform/submitting-an-order.md).

# Submitting an Order

## Creating a new Project

To create a new project, follow the steps below:

{% stepper %}
{% step %}

### Click the "New" button on the left navigation

This will open the order submission form.

<figure><img src="https://1961724198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcemwDxV2fVyrqg1tE12%2Fuploads%2FKNCIDtvJjEdD4gWltQ1J%2Fimage.png?alt=media&amp;token=108f6f26-bb5c-42a3-b2af-036905b8b6f7" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the product you would like to order

You may see multiple options depending on your account permissions
{% endstep %}

{% step %}

### Complete order flow for your selected product

**For background checks, you need to provide:**

* Project Name
* Estimated Deal Closing Date
* Project Participants: people who are authorized to receive final reports
* Background Check Scope & Turnaround
* Subject information: provide key subject details such as: Name, Date of Birth, Social Security Number & Address.
* **Notes:** Add any important details or instructions.
* **Estimated Close Date:** Indicate the date the deal is closing
* **Attachments:** Upload any relevant documents or forms related to this order.<br>

**For monitoring, you need to provide:**

* Subject Information
  * First Name (required for individuals)
  * Middle Name (optional)
  * Last Name or Entity Name (required)
  * Date of Birth (required for individuals)
  * Company Name (optional)
  * Refinements (optional search qualifiers for more relevant searches)
  * Product(s) (required)
  * Group(s) (required for organizing subjects and controlling visibility of subjects and alerts)
* Group Information
  * Group Name
  * Participants (other people who should see the monitored subjects and their alerts)
  * Monitoring end date (only if your subscription requires it).

Monitoring subjects may be added by Excel upload or by using our Add Subjects form. Click down below to download our step-by-step guide to adding subjects to monitoring.

{% file src="/files/kyo2fl8ZUbwGzxSTjptT" %}

**For ID Verification, you will need to provide:**

* Product
* Project Participants: people who are authorized to receive final reports. (*Do not add the subject of the IDV as a project participant)*
* Subject Information
  * First Name (required)
  * Last Name (required)
  * Email (required)
  * Mobile Phone (optional)
  * Country (optional)
  * Requisition Number or Internal ID (optional)
    {% endstep %}

{% step %}

### Submit the Order

When all the required fields are completed, click **Submit**.\
You’ll see a confirmation message with your Project Number, and a confirmation email will be sent to you.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Bulk Subject Upload:** If you have a bulk of subjects to upload, click **"Subject Template"** to download an Excel template. Once you have filled out the document, you can upload it to the system.
{% endhint %}


---

# 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.vcheckglobal.com/platform/submitting-an-order.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.