> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neudocs.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Create a client, send a checklist, receive an upload, and complete your first request.

Complete one document request end to end. Most firms can finish this walkthrough in a few minutes.

## Before you begin

You need:

* a NeuDocs owner, administrator, or staff account;
* the client's name and email address; and
* a short checklist of files or answers you need.

<Note>
  Use a test client and non-sensitive sample files while learning the workflow.
</Note>

## 1. Add the client

Open **Clients**, choose **New client**, enter the client's name and email, and save. See [Clients](/workflow/clients) for editing, archiving, and imports.

## 2. Create the request

Open **Requests**, choose **New request**, select the client, and add a title and due date. Start from a [template](/workflow/templates) or add each required file or question manually.

For each item, write a clear label such as “2025 bank statements — all months” instead of a broad label such as “statements.” Add an expectation or structured capture fields only when the review needs them.

## 3. Choose verification behavior

NeuDocs always applies upload safety and deterministic checks. If your firm configured bring-your-own AI, you can also enable document correctness for the request and choose advisory, soft-nudge, or hard-gate behavior.

Start with advisory mode until your expectations work reliably on representative files. Learn the tradeoffs in [Document correctness](/verification/correctness).

## 4. Send the secure link

Review the recipient and checklist, then send the request. NeuDocs emails one short-lived portal link; the client does not create an account. Sending a newer link invalidates the previous one.

Never paste a client portal link into a public channel or a ticket. Treat it as a credential.

## 5. Upload as the client

Open the link using your test client. Upload a supported file or take a photo on mobile. The portal shows received items, remaining items, and any replacement instructions. See the [Client portal guide](/workflow/client-portal).

## 6. Review the submission

Return to **Review** in the staff workspace. Check the file, correctness result, captured fields, and evidence details.

* **Approve** when the item satisfies the request.
* **Reject** with a specific reason when the client must replace it.
* Use an override only when an authorized reviewer has independently confirmed a hard-gated exception.

## 7. Complete and export

The request completes when every required item is approved. Download the organized package, manifest, and evidence from the request, or use an approved [Dropbox export](/integrations/dropbox).

## Next steps

* Automate repeat work with [templates](/workflow/templates) and [bulk or recurring requests](/workflow/bulk-recurring).
* Configure [reminders](/workflow/reminders) and [notifications](/workspace/notifications).
* Review [security and privacy](/verification/security-privacy) before using production client data.
* Connect accounting contacts, the REST API, or signed [webhooks](/integrations/webhooks).

***

## title: "quickstart"