> ## 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.

# Core concepts

> The records and states that make up the NeuDocs workflow.

NeuDocs is request-centric: work begins with a checklist sent to a client and ends with reviewed items and an exportable package.

## Main records

| Record             | Meaning                                                                                             |
| ------------------ | --------------------------------------------------------------------------------------------------- |
| **Firm**           | Your isolated NeuDocs workspace, settings, subscription, and staff.                                 |
| **Client**         | A person or organization from whom your firm collects documents or answers.                         |
| **Template**       | A reusable checklist definition. Existing requests keep their own snapshot when a template changes. |
| **Request**        | One collection job for one client, including title, due date, reminders, and items.                 |
| **Item**           | One required or optional file, text answer, date, number, or yes/no answer.                         |
| **Upload**         | A privately stored file submission associated with a request item.                                  |
| **Verdict**        | The deterministic or optional AI correctness result for an upload.                                  |
| **Review**         | A staff decision to approve or reject an item.                                                      |
| **Evidence entry** | An append-only record of a meaningful request event.                                                |

## Firm and client access

Staff sign in to the firm workspace and are authorized as owner, admin, or staff. Clients do not create accounts. They receive a time-limited secure link that opens only their request.

## Item types

* **File** — one document or image upload.
* **Text** — free-form written response.
* **Date** — a calendar date.
* **Number** — a numeric response.
* **Boolean** — yes or no.

## The request lifecycle

```text theme={null}
draft → sent → in progress → completed
                 ↘ cancelled
```

Individual items move independently through missing, submitted, review, approved, rejected, or not-applicable states. See [Statuses](/reference/statuses) for the complete behavior.

## Security boundary

Every firm is a separate tenant. Staff authorization is enforced server-side and tenant records are protected by PostgreSQL row-level security. Client links are scoped to a single request; possessing a client link does not create staff access.


## Related topics

- [Bulk and recurring requests](/workflow/bulk-recurring.md)
- [Clients](/workflow/clients.md)
- [Exports](/workflow/exports.md)
- [Reminders](/workflow/reminders.md)
- [Review and completion](/workflow/review.md)